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
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/Debia
>> 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 con
> 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 pro
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 lat
> 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
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 m
7 matches
Mail list logo
