Bug#764564: [PKG-OpenRC-Debian] Bug#764564: openrc: fail to boot when encryption + lvm are present
On Friday 10 October 2014 03:20 AM, Robbie Harwood wrote: Don't think it's this, either. I did not interrupt any part of boot in order to get this failure; this failure happens*every time*. It's possible that the filesystem is read-only during boot here which would cause failure, but I don't have a good way to check that. If you agree that this is the same bug, then I may close this one. Unless you see something that I don't, I think this is a different bug. I think you are hit by the same bug as me. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750559 Unfortunately, I did not hear back from the maintainer or the upstream dev on this one. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention.
Bug#764564: [PKG-OpenRC-Debian] Bug#764564: openrc: fail to boot when encryption + lvm are present
Thanks to the folks on #openrc, I was finally able to root cause this bug. In file /lib/cryptsetup/cryptdisks.functions # if there's already a udev-triggered job running for this # device, wait for it to finish, then re-process to confirm # that it's started successfully. In the general case this # will just be a no-op, but we don't want to defer to the # other job entirely because this is the fallback for fixing # up any ordering-dependent decrypting. while status cryptdisks-udev DEVNAME=$dev_match 21 | grep -q 'start' do sleep 1 done Which leads to. [] + echo -n Starting early crypto disks... Starting early crypto disks...+ log_action_begin_msg_post Starting early crypto disks + : + mount_fs + local point + MOUNTED= + egrep -v ^[[:space:]]*(#|$) /etc/crypttab + read dst src key opts + dev_match=UUID=ae658322-236d-489a-8a9c-371a369873ec + [ ae658322-236d-489a-8a9c-371a369873ec != UUID=ae658322-236d-489a-8a9c-371a369873ec ] + readlink -f /dev/disk/by-uuid/ae658322-236d-489a-8a9c-371a369873ec + dev_match=/dev/sda7 + status cryptdisks-udev DEVNAME=/dev/sda7 + grep -q start + sleep 1 + + status cryptdisks-udev DEVNAME=/dev/sda7 grep -q start + sleep 1 + + status cryptdisks-udev DEVNAME=/dev/sda7 grep -q start + sleep 1 + + status cryptdisks-udev DEVNAME=/dev/sda7 grep -q start + sleep 1 + + status cryptdisks-udev DEVNAME=/dev/sda7 Commenting the while loop solves the problem. Should this be assigned to the cryptsetup maintainers ??? Ritesh On Friday 10 October 2014 01:15 PM, Ritesh Raj Sarraf wrote: On Friday 10 October 2014 03:20 AM, Robbie Harwood wrote: Don't think it's this, either. I did not interrupt any part of boot in order to get this failure; this failure happens*every time*. It's possible that the filesystem is read-only during boot here which would cause failure, but I don't have a good way to check that. If you agree that this is the same bug, then I may close this one. Unless you see something that I don't, I think this is a different bug. I think you are hit by the same bug as me. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750559 Unfortunately, I did not hear back from the maintainer or the upstream dev on this one. -- Ritesh Raj Sarraf RESEARCHUT -http://www.researchut.com Necessity is the mother of invention. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention.
Bug#764564: [PKG-OpenRC-Debian] Bug#764564: openrc: fail to boot when encryption + lvm are present
Thomas Goirand z...@debian.org writes: Hi, If I'm not mistaking, this is the same bug as this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754987 Don't think so. While there is a udev hang, it gets past this, as you can see from the messages at the end of the log. Furthermore, sysvinit completes boot even with the udev hang. and some information may be found here too: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758480 Don't think it's this, either. I did not interrupt any part of boot in order to get this failure; this failure happens *every time*. It's possible that the filesystem is read-only during boot here which would cause failure, but I don't have a good way to check that. If you agree that this is the same bug, then I may close this one. Unless you see something that I don't, I think this is a different bug. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764564: [PKG-OpenRC-Debian] Bug#764564: openrc: fail to boot when encryption + lvm are present
On 10/09/2014 11:10 AM, frozencemetery wrote: Source: openrc Severity: grave Justification: renders package unusable Dear Maintainer, When upgrading a sysv system (jessie) to openrc, if the partition table includes a lvm partition with physical volume an encrypted partition, installing openrc will render the system unbootable. That is, the system will hang like so: https://www.club.cc.cmu.edu/~rharwood/tmp/openrc.png with the perf interrupt occuring after a few minutes of waiting and no further activity. This is a major problem because this partition layout is one of those *recommended by the installer* for automatic partitioning. As far as I can tell, openrc is capable of booting both encrypted and LVM partitions individually, but not both. The minimized partition layout I use which fails is: - disk 1: MSDOS table - partition 1: 200MB ext4, /boot - partition 2: *, physical volume for encryption - subpartition 1: *, physical volume for LVM - subsubpartition 1: * ext4, / Hi, If I'm not mistaking, this is the same bug as this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754987 and some information may be found here too: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758480 If you agree that this is the same bug, then I may close this one. Cheers, Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
