Hi Steve, to #6: I confirm using UUIDs in /etc/fstab (actually I already stated that in #3).
to #8: Interresting. Is that supposed to be common knowledge ? I only figured it out the hard way, summarising just that in #3. Also it seems it was not obvious to Daniel. Who knows how many people solved it accidentally by "restructuring" their fstab. Do you think it suffices to have that stated just in comment #8 of this bug description ? The same problem happened to me when I was setting up previous systems (in the last 2-3 years): The installation process created an fstab with UUIDs and when I "moved" around files systems "between devices of different dm-layer config properties" (.i.e. in order to get a previously unencrypted fs encrypted), OF COURSE I felt those fstab UUIDs should be left alone. That is communicated "everywhere" as the whole point of the UUIDs of file systems. Each time I spent an arbitrary amount of "reboot days" until everything worked again. Each time I only accidentally ended up with an fstab without UUIDs. Cryptsetup and/or mountall could at least spit some kind of warning if the unsupported case is encountered, at least if the boot process just got stuck. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719563 Title: mountall: fatal error: cannot open /dev/mapper/crypthome_unformatted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/719563/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
