Hi, all Hello, mr Scott (I figure you're the mantainer of mountall programm)
this bug is affecting me too NOW ! I did a fresh (may 15th) amd64 dist-upgrade from karmic to lucid on a HP Pavillion dv 6000 notebook (intel core-duo, nvidia go 8300) and after reboot I was not more able to boot with all kernels I experienced: neither with 2.6.31-15, nor 2.6.32-21,nor 2.6.34-2, nor with 2.6.28-11 generic kernel; recovery mode doesn't work I'm using mountall 2.15 and e2fslibs 1.41.11 Console hangs after fsck controls of last primary partition (/dev/sda4) (with no errors report - prior, root partition fsck gone at well) , ctrl+alt+canc works (but no other input in the console). I have no login on all consoles I do not think is graphic card and Plymouth related as some people suggested ; but perhaps is related to a Plymouth mountall error earlier shown. I get a plymouth mount fail error message prior fsck and hang issue. I think the problem could be also related to a ureadahead problem with fsck too (pushing esc or F1 or whatsever similar a line something related appeared) I found a workaround only. Booting from a Lucid CD i substituted my /etc/fsab with the UUID entries with the one of the CD that is with no phisical entries (swap excepted) . So I'm able to boot in the mainstream as root, then later mount the home partition and finally login as user (so it's very slow and annoying) This is the /etc/fstab from CD boot (that goes!) aufs / aufs rw 0 0 tmpfs /tmp tmpfs nosuid,nodev 0 0 /dev/sda7 swap swap defaults 0 0 This one is my usual /etc/fstab (doesn't work) proc /proc proc defaults 0 0 # /dev/sda8 UUID=uuid-number / ext3 relatime,errors=remount-ro 0 1 # /dev/sda2 UUID=uuid-number /dos vfat utf8,umask=007,gid=46 0 1 # /dev/sda4 UUID=uuid-number /home ext3 relatime 0 2 # /dev/sda7 UUID=uuid-number swap swap defaults 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 This bug seems similar to 552018, 580883 (I filled it), 550499, 57144 Be patient but mountall is still not ok! I've seen on google that lot of people are experiencing serious troubles in Lucid booting with similar issues so perhaps the new boot engine is a little immature. Can you suggest a way to not use Plymouth-mountall and use the old booting way meanwhile? Best regards and thank you for the hard work David -- Cant mount hdds on boot, and system boot in maintrance mode https://bugs.launchpad.net/bugs/571277 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
