Solution for me was to address volumes in fstab by their UUID. When I first saw 7.04's new UUID convention I didn't like it, didn't at all appreciate the automatic edits to my fstab, and didn't like how a portion of my hard-won (though limited) understanding of volume mounting had been broken without announcement. So I immediately changed my fstab volume names back to traditional `/dev/sda<n>`.
Something about the -16 patch caused bad superblock reads on _some_ of my volumes. Not the root/boot one, but the one I use for /home and another. When I changed my fstab entries to UUID the bad reads went away. fsck _did_ turn-up and fix some garbage on my root volume on re- boot. The effect of all this, intended or not, seems to be that you must use the UUID notation. That may not be literally true, but as a practical matter I took it as sign to stop resisting. This sort of thing will keep coming up, I think. Learn volume UUIDs with `vol_id -u /dev/sda<n>`, probably as root. In fstab, replace volume names (the filesystem column) with `UUID=<UUID string from `vol_id -u>`. All's well now. I documented the `vol_id` syntax in comments to my fstab, so I won't have to look it up next time. HTH LQ -- latest kernel(2.6.20-16.28) update gives boot problems https://bugs.launchpad.net/bugs/117314 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
