Re: md device files missing at boot time

Re: md device files missing at boot time

[Ingo Freund]

Hi folks,

I could temporarily only read your answers in archives.
Thank you for your reaction.
Hopefully this answer doesn't break the thread.
If it does:
sorry for it, there were some mail mail problems
which stopped our server receiving mails from this list
and the list auto-unsubscribed me and stopped sending mails :-(
But it is all fixed now.

@Kay
How did you build the initramfs image? /sbin/mkinitrd?

Did you add md support to the image?

Both "Yes".
included modules are (in opensuses /etc/sysconfig/kernel:
INITRD_MODULES="raid1 md reiserfs sym53c8xx pata_serverworks edd"



@J.A. Magallon
yes the partitions in question are all typed "fd"

neither all-drivers-compiled-into-the-kernel nor the
module using version work.
The only difference I find is the exit to an emergency shell
when using modules via initrd while the "only kernel version"
stops commentless when it is time to use /dev/md0 for the first
time.

"dmesg" is not found after exiting to the shell.
I can only post the content of a log file which was written
into the initramfs (which seems to be also a trace of the
in and output of the emergency console).

Content of the log file (/var/log/boot.msg):

Boot logging started on /dev/tty1(/dev/console) at Thu Jul  5 06:36:35 2007

Creating device nodes with udev
Loading md-mod
Loading raid1
Loading sym53c8xx
Loading libata
Loading pata_serverworks
Loading edd
Loading reiserfs
Waiting for device /dev/md0 to appear: ..............................not found -- exiting to /bin/sh
sh: no job control in this shell
$ dmesg
sh: dmesg: command not found
$ fdisk
sh: fdisk: command not found
$ ls /bin
bash  cat  chmod  date  ipconfig.sh  ln  ls  mkdir  mknod  mount  pidof  rm  run-init  sed  sh  sleep  true  umount
...

Question: is the order "creating dev nodes with udev" and after
that "loading the modules" correct?


Thanks - Ingo.

[seems to be SOLVED] Re: md device files missing at boot time

[Ingo Freund]

On 05.07.2007 11:16, Ingo Freund wrote (please find the answer below the original text):
> Hi folks,
> 
> I could temporarily only read your answers in archives.
> Thank you for your reaction.
> Hopefully this answer doesn't break the thread.
> If it does:
> sorry for it, there were some mail mail problems
> which stopped our server receiving mails from this list
> and the list auto-unsubscribed me and stopped sending mails :-(
> But it is all fixed now.
> 
> @Kay
> How did you build the initramfs image? /sbin/mkinitrd?
> 
> Did you add md support to the image?
> 
> Both "Yes".
> included modules are (in opensuses /etc/sysconfig/kernel:
> INITRD_MODULES="raid1 md reiserfs sym53c8xx pata_serverworks edd"
> 
> 

@Kay
there was a hidden hint in your text.
"mkinitrd -f md"  made it at least for boot with initramfs

Thanks - Ingo.

Re: [seems to be SOLVED] Re: md device files missing at boot time

[Jan Engelhardt]

On Jul 5 2007 15:15, Ingo Freund wrote:
>On 05.07.2007 11:16, Ingo Freund wrote (please find the answer below the original text):
>> Hi folks,
>> 
>> I could temporarily only read your answers in archives.
>> Thank you for your reaction.
>> Hopefully this answer doesn't break the thread.
>> If it does:
>> sorry for it, there were some mail mail problems
>> which stopped our server receiving mails from this list
>> and the list auto-unsubscribed me and stopped sending mails :-(
>> But it is all fixed now.
>> 
>> @Kay
>> How did you build the initramfs image? /sbin/mkinitrd?
>> 
>> Did you add md support to the image?
>> 
>> Both "Yes".
>> included modules are (in opensuses /etc/sysconfig/kernel:
>> INITRD_MODULES="raid1 md reiserfs sym53c8xx pata_serverworks edd"
>> 
>> 
>
>@Kay
>there was a hidden hint in your text.
>"mkinitrd -f md"  made it at least for boot with initramfs

That's rather a hack.

I suppose your problem is that mdadm is not inside the initrd.
(gzip -cd /boot/initrd | cpio -t)
Make sure /etc/fstab lists an md device, then mdadm should be added
automatically.


	Jan
-- 

Re: md device files missing at boot time

[Ingo Freund]

Hi folks,

I can temporarily only read your answers in archives.
Thank you for your reaction.
It would be nice, to send responses directly to me too:
"linux-kernel-news at e-dict".
Hopefully this answer doesn't break the thread.
If it does:
sorry for it, there were some mail mail problems
which stopped our server receiving mails from this list
and now the list stopped sending mails to me :-)

@Kay
How did you build the initramfs image? /sbin/mkinitrd?

Did you add md support to the image?

Both "Yes".
included modules are (in opensuses /etc/sysconfig/kernel:
INITRD_MODULES="raid1 md reiserfs sym53c8xx pata_serverworks edd"



@J.A. Magallon
yes the partitions in question are all typed "fd"

neither all-drivers-compiled-into-the-kernel nor the
module using version work.
The only difference I find is the exit to an emergency shell
when using modules via initrd while the "only kernel version"
stops commentless when it is time to use /dev/md0 for the first
time.

"dmesg" is not found after exiting to the shell.
I can only post the content of a log file which was written
into the initramfs (which seems to be also a trace of the
in and output of the emergency console).

Content of the log file (/var/log/boot.msg):

Boot logging started on /dev/tty1(/dev/console) at Thu Jul  5 06:36:35 2007

Creating device nodes with udev
Loading md-mod
Loading raid1
Loading sym53c8xx
Loading libata
Loading pata_serverworks
Loading edd
Loading reiserfs
Waiting for device /dev/md0 to appear: ..............................not found -- exiting to /bin/sh
sh: no job control in this shell
$ dmesg
sh: dmesg: command not found
$ fdisk
sh: fdisk: command not found
$ ls /bin
bash  cat  chmod  date  ipconfig.sh  ln  ls  mkdir  mknod  mount  pidof  rm  run-init  sed  sh  sleep  true  umount
...

Question: is the order "creating dev nodes with udev" and after
that "loading the modules" correct?


Thanks - Ingo.

md device files missing at boot time

[Ingo Freund]

Hi folks,

one of the systems I'm working with was changed (copied) from single (scsi - sda1)
to multiple disk (raid1) (sdb1,sdc1 --> md0).
When I try to boot from the new created md-device it stops with:
...
loading reiserfs
"Waiting for device /dev/md0 to appear: ........ not found -- Exiting to /bin/sh

A
# ls -la /dev/md*
shows nothing, so I understand why the "/" cannot be mounted, but
where are the /dev/md* files (I found them in "/lib/udev/devices")?

The kernel is vanilla 2.6.21.5, the (I think) needed hardware and filesystem
drivers are built in modules and put into an initrd file for loading at boot time.

Does anyone have an idea what I might do wrong?

Thanks - Ingo.

Re: md device files missing at boot time

[Kay Sievers]

On 7/4/07, Ingo Freund <linux-kernel-news@e-dict.net> wrote:
> one of the systems I'm working with was changed (copied) from single (scsi - sda1)
> to multiple disk (raid1) (sdb1,sdc1 --> md0).
> When I try to boot from the new created md-device it stops with:
> ...
> loading reiserfs
> "Waiting for device /dev/md0 to appear: ........ not found -- Exiting to /bin/sh
>
> # ls -la /dev/md*
> shows nothing, so I understand why the "/" cannot be mounted, but
> where are the /dev/md* files (I found them in "/lib/udev/devices")?
>
> The kernel is vanilla 2.6.21.5, the (I think) needed hardware and filesystem
> drivers are built in modules and put into an initrd file for loading at boot time.
>
> Does anyone have an idea what I might do wrong?

How did you build the initramfs image? /sbin/mkinitrd?

Did you add md support to the image?

Kay

Re: md device files missing at boot time

[J.A. Magallón]

On Wed, 04 Jul 2007 15:32:55 +0200, Ingo Freund <linux-kernel-news@e-dict.net> wrote:

> Hi folks,
> 
> one of the systems I'm working with was changed (copied) from single (scsi - sda1)
> to multiple disk (raid1) (sdb1,sdc1 --> md0).
> When I try to boot from the new created md-device it stops with:
> ...
> loading reiserfs
> "Waiting for device /dev/md0 to appear: ........ not found -- Exiting to /bin/sh
> 
> A
> # ls -la /dev/md*
> shows nothing, so I understand why the "/" cannot be mounted, but
> where are the /dev/md* files (I found them in "/lib/udev/devices")?
> 
> The kernel is vanilla 2.6.21.5, the (I think) needed hardware and filesystem
> drivers are built in modules and put into an initrd file for loading at boot time.
> 
> Does anyone have an idea what I might do wrong?
> 

Stupid question, I suppose...
Are you sdb1,sdc1 partitions "Linux RAID _autodetect_" ?
All my raids use the md+raid modules builtin, no initrd, so I don't know
if you have to force load of md on the initrd, or kernel will autoload if
you use root=/dev/md0.

Could you post your dmesg ?

--
J.A. Magallon <jamagallon()ono!com>     \               Software is like sex:
                                         \         It's better when it's free
Mandriva Linux release 2008.0 (Cooker) for i586
Linux 2.6.21-jam10 (gcc 4.1.2 20070302 (4.1.2-1mdv2007.1)) SMP PREEMPT
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0