[Bug 438962] Re: upstart/mountall does not boot after mounting crypto disks
*** This bug is a duplicate of bug 441367 *** https://bugs.launchpad.net/bugs/441367 ** This bug has been marked a duplicate of bug 441367 udevd[828]: inotify_add_watch(6, (null), 10) failed: Bad address -- upstart/mountall does not boot after mounting crypto disks https://bugs.launchpad.net/bugs/438962 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 438962] Re: upstart/mountall does not boot after mounting crypto disks
Me too. A _clean_ reinstall with Karmic-Beta1-desktop fixed most bootup problems. System is working again with luks-encrypted root partition and btrfs (- with manual conversion after install). Guess: some remaining Alpha5 init.d/ scripts (or udev rules??) caused most of the upgrade / boot problems. No idea if that helps - but I just attach my etc/ directory here. (karmic-tbz2, some cruft removed) ** Attachment added: "compacted /etc directory after alpha5->alpha6 apt-upgrade on luks-btrfs-rootfs" http://launchpadlibrarian.net/33050071/karmic-sda2btrfscrypt-etc.tbz2 -- upstart/mountall does not boot after mounting crypto disks https://bugs.launchpad.net/bugs/438962 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 438962] Re: upstart/mountall does not boot after mounting crypto disks
My problem went away by reinstalling jaunty from scratch and then upgrading to karmic via aptitude. Don't know what triggered this. New install has the same filesystem setup with crypto disks. -- upstart/mountall does not boot after mounting crypto disks https://bugs.launchpad.net/bugs/438962 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 438962] Re: upstart/mountall does not boot after mounting crypto disks
Architecture: i386 Date: Fri Oct 2 19:13:12 2009 DistroRelease: Ubuntu 9.10 Package: upstart 0.6.3-5 ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) Uname: Linux 2.6.31-4-generic i686 System: IBM Thinkpad X40, 2371LG3 # /etc/fstab: static file system information. /dev/mapper/sda2_crypt /btrfs errors=remount-ro,compress,ssd 0 1 /dev/sda1/boot ext2defaults0 2 I've seen the same behaviour after an update. Persists even after a tried reinstall. My root partition is a luks-encrypted btrfs, which worked fine with Alpha5. I'm still using the older kernel, because the alpha6 initrd doesn't even find the cryptoroot. Cannot decipher where exactly the boot/upstart hang occours, but mountall.conf seems a problem spot on my setup too. The initial error message is identical: "udevd[1283]: inotify_add_watch(...) Bad address". The initrd cryptsetup ran through fine. upstart/initctl doesn't give any details to where or why it hangs. Is there a debug mode or /etc/init.conf setting to make it verbose? -- upstart/mountall does not boot after mounting crypto disks https://bugs.launchpad.net/bugs/438962 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 438962] Re: upstart/mountall does not boot after mounting crypto disks
Don't know if this will help you track it down, but I have several identical computers, each running an identical imaged Karmic installation. One of them is unaffected by this bug, and the other two will not boot no matter what I do--including re-imaging from the working one. (???) Could the BIOS configuration/version have any role in this? -- upstart/mountall does not boot after mounting crypto disks https://bugs.launchpad.net/bugs/438962 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 438962] Re: upstart/mountall does not boot after mounting crypto disks
** Tags added: ubuntu-boot -- upstart/mountall does not boot after mounting crypto disks https://bugs.launchpad.net/bugs/438962 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 438962] Re: upstart/mountall does not boot after mounting crypto disks
Pasting the user's fstab as requested (non-booting systems make cut-n-paste !fun) # /etc/fstab: static file system information. # # Use 'vol_id --uuid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # proc/proc procdefaults0 0 /dev/mapper/vg1-root_crypt / ext4relatime,errors=remount-ro 0 1 # /boot was on /dev/mapper/vg0-boot during installation UUID=350a70dd-78c3-4616-ae04-7038341cda18 /boot ext3relatime 0 2 /dev/mapper/vg1-swap_crypt noneswapsw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 /resumefile swap swap noauto,defaults 0 0 ** Changed in: udev (Ubuntu) Importance: Undecided => High ** Changed in: udev (Ubuntu) Status: New => Confirmed ** Also affects: udev (Ubuntu Karmic) Importance: High Status: Confirmed -- upstart/mountall does not boot after mounting crypto disks https://bugs.launchpad.net/bugs/438962 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 438962] Re: upstart/mountall does not boot after mounting crypto disks
** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/32725236/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/32725237/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/32725238/Dependencies.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/32725240/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/32725241/Lsusb.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/32725243/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/32725244/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/32725245/ProcModules.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/32725246/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/32725247/UdevLog.txt -- upstart/mountall does not boot after mounting crypto disks https://bugs.launchpad.net/bugs/438962 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
