Dear all,

I setup my rootfs as an LVM, the menu.lst of grub looks like this;

title Debian GNU/Linux, kernel 2.6.18-4-386
root (hd0,0)
kernel /vmlinuz-2.6.18-4-686 root=/dev/volume/root ro
initrd /my_init
savedefault

Error happens when the kernel tried to mount the root filesystem:
The error message is "Waiting for root file system..."
yuwen check root=bootarg cat /proc/cmdline or missing modules, devices; cat
/proc/modules ls /dev/

I setup /boot as a seperate disk parition. The rest is for LVM.
/dev/volume/root is OK when I use a rescue CDRom. And I re-build the
initrd, adding all dm-* modules to the initrd. Any suggestion?

Best regards,
Yuwen

> I setup my rootfs as an LVM, the menu.lst of grub looks like this;

> title Debian GNU/Linux, kernel 2.6.18-4-386
> root (hd0,0)
> kernel /vmlinuz-2.6.18-4-686 root=/dev/volume/root ro
> initrd /my_init
> savedefault

> Error happens when the kernel tried to mount the root filesystem:
> The error message is "Waiting for root file system..."
> yuwen check root=bootarg cat /proc/cmdline or missing modules, devices; cat
> /proc/modules ls /dev/

> I setup /boot as a seperate disk parition. The rest is for LVM.
> /dev/volume/root is OK when I use a rescue CDRom. And I re-build the
> initrd, adding all dm-* modules to the initrd. Any suggestion?

Try use /dev/mapper/volume-root instead.
I'm not sure why, but I recently had a similar problem where using
/dev/Debian/root didn't work but /dev/mapper/Debian-root did (even though
once the boot is over, /dev/Debian/root can be used just fine, it looks
like the alternate name is constructed later).


Stefan


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

>
>
> Try use /dev/mapper/volume-root instead.
> I'm not sure why, but I recently had a similar problem where using
> /dev/Debian/root didn't work but /dev/mapper/Debian-root did (even though
> once the boot is over, /dev/Debian/root can be used just fine, it looks
> like the alternate name is constructed later).


I fell into a busybox command. There's no dirs in /dev/mapper, only
control:

ls /dev/mapper
control

What is control?

Best regards,
Yuwen



Stefan
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>
>

>
> > I setup /boot as a seperate disk parition. The rest is for LVM.
> > /dev/volume/root is OK when I use a rescue CDRom. And I re-build the
> > initrd, adding all dm-* modules to the initrd. Any suggestion?
>
> Try use /dev/mapper/volume-root instead.
> I'm not sure why, but I recently had a similar problem where using
> /dev/Debian/root didn't work but /dev/mapper/Debian-root did (even though
> once the boot is over, /dev/Debian/root can be used just fine, it looks
> like the alternate name is constructed later).


Hi Stefan,

Would you please tell me how to create a initrd with LVM support in Debian?
I used the initramfs tool. Thank you very much!

Best regards,
yuwen




Stefan
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>
>

>> Try use /dev/mapper/volume-root instead.
>> I'm not sure why, but I recently had a similar problem where using
>> /dev/Debian/root didn't work but /dev/mapper/Debian-root did (even though
>> once the boot is over, /dev/Debian/root can be used just fine, it looks
>> like the alternate name is constructed later).

> Would you please tell me how to create a initrd with LVM support in Debian?
> I used the initramfs tool. Thank you very much!

I don't know: it just works. As long as you have the lvm2 package installed
and the initrd package was created after the lvm2 package was installed, it
should just work.


Stefan


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Wed, May 09, 2007 at 09:23:52AM -0400, Stefan Monnier wrote:
> >> Try use /dev/mapper/volume-root instead.
> >> I'm not sure why, but I recently had a similar problem where using
> >> /dev/Debian/root didn't work but /dev/mapper/Debian-root did (even though
> >> once the boot is over, /dev/Debian/root can be used just fine, it looks
> >> like the alternate name is constructed later).
>
> > Would you please tell me how to create a initrd with LVM support in Debian?
> > I used the initramfs tool. Thank you very much!
>
> I don't know: it just works. As long as you have the lvm2 package installed
> and the initrd package was created after the lvm2 package was installed, it
> should just work.
>

if installed after the fact, then do this as root:

update-initramfs -u -k all

to rebuild the existing initrd's

A

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD4DBQFGQgFCaIeIEqwil4YRAgdtAJ9HBDmXr+1FCQ3MWdIgcv 79iAqyfgCUCPph
gSvjfe0YPRDj+zJyq3GbrA==
=fLEO
-----END PGP SIGNATURE-----

>
> I don't know: it just works. As long as you have the lvm2 package
> installed
> and the initrd package was created after the lvm2 package was installed,
> it
> should just work.


Hi Stefan,

After I changed root device to /dev/mapper/volume-root, Linux boots
successfully. And I didn't make anything special for LVM when creating
initramfs. Thank you very much.



Stefan
>