[opensuse-factory] dracut and LVM means no boot
Hello, Has anyone tested LVM with dracut? In my case, the initrd produced by dracut in host-only mode, which is the default, does not include LVM support at all, which I found out the hard way and took many hours to recover from, by manually adjusting the initrd on another computer and improvising when it aborted during boot. The initrd created in no- hostonly mode does include LVM support, although it still cannot find the LVM root, because the device mapper becomes confused, dm-linear throws error messages: dm-linear: Device lookup failed ioctl: error adding target to table and I must run: dmsetup remove_all before lvm vgchange -ay, otherwise the disks are treated as separate volumes. In short, automatic boot with an LVM root is impossible at the moment. This is on latest factory, dracut-034-3.1, device-mapper-1.02.78-0.15.3, lvm2-2.02.98-0.31.1. Regards, Peter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/11/13 11:36, auxsvr wrote:
Hello,
Has anyone tested LVM with dracut? In my case, the initrd produced by dracut in host-only mode, which is the default, does not include LVM support at all,
So far, I have been unable to ever generate a bootable initrd with Dracut, using LVM & dm-crypt, so that is definitely a problem!
which I found out the hard way and took many hours to recover from, by manually adjusting the initrd on another computer and improvising when it aborted during boot. The initrd created in no- hostonly mode does include LVM support, although it still cannot find the LVM root, because the device mapper becomes confused, dm-linear throws error messages:
dm-linear: Device lookup failed ioctl: error adding target to table
and I must run:
dmsetup remove_all
before lvm vgchange -ay, otherwise the disks are treated as separate volumes. In short, automatic boot with an LVM root is impossible at the moment.
This is on latest factory, dracut-034-3.1, device-mapper-1.02.78-0.15.3, lvm2-2.02.98-0.31.1.
Regards, Peter
On a somewhat related note, though, next time you run into problems with the initrd: Just start the computer and load a live-cd, then do the following: vgscan vgchange -ay <name> Then mount the root partition (mount <path> /mnt, for example). Afterwards, mount your boot partition (mount /dev/sdX /mnt/boot), then mount /sys, /proc and /dev via 'mount -o bind /mnt/<target>' (accordingly), simply chroot into the mounted root directory (chroot /mnt/ in this case), run mkinitrd, let it finish, and then you can simply restart your computer, since the live-cd should handle all unmounting (or just unmount everything by hand). Takes about 5 minutes to get back to a working, bootable system, since you use the chroot'ed root partition which works just like running the actual system, which means no external trial and error is required! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 10 of November 2013 18:54:33 Peter Hanisch wrote:
So far, I have been unable to ever generate a bootable initrd with Dracut, using LVM & dm-crypt, so that is definitely a problem!
So the default for 13.1 is the old mkinitrd, right?
On a somewhat related note, though, next time you run into problems with the initrd: Just start the computer and load a live-cd,
I rarely use optical media, so the last openSUSE DVD I burned was 12.1, and the only PC with optical drives within reach was the one with the problem, so I didn't have that option. On the bright side, I learned a lot about initrd and LVM... By the way, there are lots of useless files under /etc in the initrd created by dracut. Regards, Peter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 10/11/13 22:04, auxsvr escribió:
On Sunday 10 of November 2013 18:54:33 Peter Hanisch wrote:
So far, I have been unable to ever generate a bootable initrd with Dracut, using LVM & dm-crypt, so that is definitely a problem!
So the default for 13.1 is the old mkinitrd, right?
Correct, the default was changed early for the *next* release (13.2 or whatever)
By the way, there are lots of useless files under /etc in the initrd created by dracut.
Like what exactly and how did you determine they were useless ? booting your faulty initrd, could you provide the debug files it generates on failure ? can you the following RPM as well ? http://cristianrodriguez.net/patches/dracut-034_git201311071423-0.x86_64.rpm -- "Judging by their response, the meanest thing you can do to people on the Internet is to give them really good software for free". - Anil Dash -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 10 of November 2013 22:38:57 Cristian Rodríguez wrote:
El 10/11/13 22:04, auxsvr escribió:
By the way, there are lots of useless files under /etc in the initrd created by dracut.
Like what exactly and how did you determine they were useless ?
Every file under /etc/ld.so.conf.d is obviously useless, especially octave.conf, R.conf and intel-mkl.conf. Their names are enough to infer so.
booting your faulty initrd, could you provide the debug files it generates on failure ?
Perhaps tomorrow, it is too late now. From which initrd would you like the files, the host-only or the non-hostonly?
can you the following RPM as well ?
http://cristianrodriguez.net/patches/dracut-034_git201311071423-0.x86_ 64.rpm
This installation is 32 bit. Regards, Peter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
auxsvr -
Cristian Rodríguez -
Peter Hanisch