[Bug 509487] Re: [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk
this is fixed with mountall 2.10. on lucid. ** Changed in: cryptsetup (Ubuntu) Status: Triaged = Fix Released -- [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk https://bugs.launchpad.net/bugs/509487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509487] Re: [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk
similar issue reported in bug 497480 -- [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk https://bugs.launchpad.net/bugs/509487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509487] Re: [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk
I have a similar issue without LVM. I installed from netinstall today. i have /boot /dev/sda1 ext2 / /dev/sda2 ext4 /home /dev/sda3 crypt setup ext4 /home is ext4 partition over LUKS encrypted partition -- [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk https://bugs.launchpad.net/bugs/509487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509487] Re: [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk
Please note that Marc Gariepy works with me and lives something like 2 minutes away from me :) I've been seeing the exact same behavior on his laptop as on mine though his is a perfectly clean Lucid install and doesn't use LVM (instead the ext4 /home partition is directly in the LUKS volume). At boot time, we get the passphrase prompt correctly, after entering the key the prompt disappears and we get stuck there (as on my laptop). Commenting the /home line in /etc/fstab and rebooting will make the laptop boot successfully though he'll then have to manually do the cryptsetup luksOpen and mount. -- [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk https://bugs.launchpad.net/bugs/509487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509487] Re: [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk
I have the same problem. My config: / - LVM (PV /dev/sda1) /home - dm-crypt(/dev/sda2) + LVM (PV sda2_crypt) When should I run blkid command? I have currently commented out crypted partition from /etc/crypttab and /etc/fstab and I perform manual cryptsetup + vgchange -ay + mount -- [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk https://bugs.launchpad.net/bugs/509487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509487] Re: [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk
Here you go with the blkid for the partition, the LUKS volume and the LVM partition: stgra...@castiana:~$ sudo blkid /dev/sda2 /dev/sda2: UUID=851db151-043d-46fd-9632-626d6f57bb86 TYPE=crypto_LUKS stgra...@castiana:~$ sudo blkid /dev/mapper/sda2_crypt /dev/mapper/sda2_crypt: UUID=m73M8R-p6Hn-okx2-xFFQ-eEKl-lKbZ-dq0qgK TYPE=LVM2_member stgra...@castiana:~$ sudo blkid /dev/mapper/castiana-home /dev/mapper/castiana-home: UUID=3378fec9-7db2-4a40-90cf-168df7e93deb TYPE=ext4 -- [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk https://bugs.launchpad.net/bugs/509487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509487] Re: [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk
/dev/mapper/sda2_crypt: UUID=m73M8R-p6Hn-okx2-xFFQ-eEKl-lKbZ-dq0qgK TYPE=LVM2_member This should be sufficient to trigger /lib/udev/rules.d/85-lvm2.rules, which I assume you have on your system (since it's from the lvm2 package!). If you can run the commands from that rule's RUN variable by hand, it may be instructive; or to otherwise trace the set of processes running at this point. A good way to do this may be to edit /etc/init/tty2.conf to force a getty to start earlier in the boot sequence. -- [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk https://bugs.launchpad.net/bugs/509487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509487] Re: [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk
Could we track the hang as a separate bug report, as suggested? What does '/sbin/blkid /dev/mapper/sda2_crypt' show for this device? Once unlocked with cryptsetup, the rest of the mounting should be handled via udev rules and mountall. -- [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk https://bugs.launchpad.net/bugs/509487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509487] Re: [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk
So, here's all the calls made by plymouth using the debug code you posted before: open(/lib/plymouth/themes/ubuntu-logo/bullet.png, O_RDONLY) = 12 open(/lib/plymouth/themes/ubuntu-logo/box.png, O_RDONLY) = 12 open(/lib/plymouth/themes/ubuntu-logo/entry.png, O_RDONLY) = 12 open(/lib/plymouth/themes/ubuntu-logo/lock.png, O_RDONLY) = 12 open(/var/lib/plymouth//boot-duration, O_WRONLY|O_CREAT|O_TRUNC, 0666) = 12 open(/lib/plymouth/themes/ubuntu-logo/bullet.png, O_RDONLY) = 12 open(/lib/plymouth/themes/ubuntu-logo/box.png, O_RDONLY) = 12 open(/lib/plymouth/themes/ubuntu-logo/entry.png, O_RDONLY) = 12 open(/lib/plymouth/themes/ubuntu-logo/lock.png, O_RDONLY) = 12 open(/lib/plymouth/themes/details/details.plymouth, O_RDONLY) = 11 open(/lib/plymouth/details.so, O_RDONLY) = 11 open(/lib/plymouth/themes/ubuntu-logo/bullet.png, O_RDONLY) = 11 open(/lib/plymouth/themes/ubuntu-logo/box.png, O_RDONLY) = 11 open(/lib/plymouth/themes/ubuntu-logo/entry.png, O_RDONLY) = 11 open(/lib/plymouth/themes/ubuntu-logo/lock.png, O_RDONLY) = 11 open(/var/lib/plymouth//boot-duration, O_WRONLY|O_CREAT|O_TRUNC, 0666) = 12 -- [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk https://bugs.launchpad.net/bugs/509487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509487] Re: [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk
Current behavior is: - I get prompted for the key (padlock + entry field show up just fine) - I enter the key - If valid, the prompt disappears - If not, I get prompted again as expected - It gets stuck there and never does anything Exitting plymouth (pressing ESC), I can see that crypsetup intializaed correctly and seemed to have unlock the LUKS volume correctly, though it seems it never actually mounted the partition inside it or loaded the LVM making it hang indefinitely there. -- [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk https://bugs.launchpad.net/bugs/509487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509487] Re: [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk
My bad, I wasn't running the right version of plymouth. I just re-tested with 0.8.0~-8 and the result is slightly different. I now see the passphrase prompt (padlock + label), I can type in my passphrase just fine and when validating it seems it's opening the luks volume but nothing happens and I get back to being stuck on a plymouth splash screen (only the ubuntu logo). When pressing escape, I see that the luks volume was opened correctly, so that part seems to work now but something still block the boot process. I'll get you a new trace. -- [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk https://bugs.launchpad.net/bugs/509487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509487] Re: [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk
Ok, marking this task fixed again. The hang is probably unrelated and should be filed separately. ** Changed in: plymouth (Ubuntu) Status: Incomplete = Fix Released -- [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk https://bugs.launchpad.net/bugs/509487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509487] Re: [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk
** Branch linked: lp:ubuntu/plymouth -- [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk https://bugs.launchpad.net/bugs/509487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509487] Re: [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk
This bug was fixed in the package plymouth - 0.8.0~-8 --- plymouth (0.8.0~-8) lucid; urgency=low [ Steve Langasek ] * Include label.so in the initramfs, as well as the font support files it depends on, needed for any text prompts or messages. This will bloat the initramfs substantially (about 3MB) and impact boot performance as a result, but the solution to that is to not include plymouth in the initramfs unless we know it's needed for prompting (e.g., cryptsetup). LP: #496765. * Move x11 renderer into a separate package, to avoid pulling GTK into the server install by default. LP: #509579. * debian/rules: fix up the dh_makeshlibs exclude path to match where we're currently installing. * src/plugins/splash/script/plugin.c: the script plugin has no support at all for text consoles, so if there are no pixel displays available, return an error so that plymouth can fall back to the text plugin. LP: #506717. * Always include the 'details' and 'text' themes in the initramfs, since plymouth uses these as built-in fallbacks and they're tiny. * src/main.c: when a splash plugin fails to load, make sure to unregister any related keyboard handlers. * don't let the password walk off the end of the dialog box. LP: #496782. * split the plymouth upstart job into plymouth and plymouth-splash, so that plymouth starts up early and doesn't have to race gdm; and stop unconditionally adding plymouth to the initramfs now that we can start it this way. * debian/plymouth.postinst: also set the theme on first install, or on upgrade from versions prior to 0.8.0~-7, because update-initramfs called before plymouth has been configured for the first time will accidentally cause a call to --reset to use the text theme instead of the intended default. * debian/plymouth.plymouth-splash.upstart: don't wait on tty-device-added, these are now guaranteed to be available; copied from gdm upstart job. * Depend on mountall (= 2.0) to ensure we have the above guarantee. * Mark /usr/share/initramfs-tools/scripts/init-bottom/plymouth executable, otherwise initramfs-tools skips it. LP: #509487. * Drop the Debian revision (-1) from the version in the symbols file, to fix a lintian warning. -- Steve Langasek steve.langa...@ubuntu.com Tue, 02 Feb 2010 08:11:47 + ** Changed in: plymouth (Ubuntu) Status: Triaged = Fix Released -- [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk https://bugs.launchpad.net/bugs/509487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509487] Re: [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk
I guess that plymouth upload was supposed to close the plymouth part of the issue and not the crypsetup one ? I did a quick test boot with that plymouth, result is still the same. -- [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk https://bugs.launchpad.net/bugs/509487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509487] Re: [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk
Well, fixing the plymouth side of this should have been sufficient to resolve the symptoms. I can confirm here that plymouth now correctly chroots on startup. Can you grab a fresh strace with plymouth 0.8.0~-8? ** Changed in: plymouth (Ubuntu) Status: Fix Released = Incomplete -- [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk https://bugs.launchpad.net/bugs/509487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509487] Re: [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk
It turns out that there *is* chroot handling in plymouth, and /usr/share /initramfs-tools/scripts/init-bottom/plymouth has code to run this. But for some reason, my /scripts/init-bottom/ORDER is missing any references to plymouth: /scripts/init-bottom/udev [ -e /conf/param.conf ] . /conf/param.conf So we need to figure out why that's missing. ** Changed in: plymouth (Ubuntu) Assignee: (unassigned) = Steve Langasek (vorlon) -- [lucid] plymouth in initramfs doesn't know to chroot() when init does, can't load files from disk https://bugs.launchpad.net/bugs/509487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
