On Mon, Jun 17, 2013 at 09:51:42PM -0000, Mark Sweeney wrote: > I managed to manually fixed this by adding the UUID of the partion to > fstab, rather than using the file path.
This is not a correct fix, however, as it introduces a race condition since the UUID will be visible over udev before the path has settled. So you can get boot failures with this caused by the device appearing, and then moving to a different name before mountall has a chance to act. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1061190 Title: could not mount /dev/mapper/cryptswap1 M for manual S for skip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1061190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
