This morning, I turned on the computer and got the problem. "The disk drive for /backup is not ready yet or not present"
I can swear lvbackup was owned by the root group when I turned it off, and I assure you I've never done anything with udev. I checked ownership : lvbackup was this time owned by the disk group and, surprise, lvroot (which holds the system root), was owned by the disk group too (but was mounted)! I performed a chgrp on lvbackup, and type reboot in a terminal. Same problem on boot, but this time lvroot is owned by the root group, as it was before. I changed ownership again, but this time performed the reboot through the graphical interface. And, guess what ? It booted fine and lvbackup was owned by root.root. This is pretty freaky, isn't it ? My guess is the "reboot" process launched through the graphical interface actually holds some data in memory, while the reboot command in a terminal performs a clean reboot. I performed a "shutdown" through the GUI, then pressed the power button. Boot failed. Finally, I can say that ownership *is not* persistent across reboots, making this bug more annoying than I thought. -- lucid hangs on boot because of device ownership https://bugs.launchpad.net/bugs/557909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
