Okay, this is NOT exactly a bug. It may be caused by the use of /dev/hdxx device identifiers in fstab. Evidently this latest kernel no longer recognizes those and the partitions are now identified as /dev/sdxx. The problem in this case is caused by a bug in the upgrade path from Dapper to Edgy. Edgy is supposed to convert the fstab to UUID identifiers, but if there are duplicate UUID's it does not. In fact, if you have duplicate UUIDs you cannot successfully mount all drives using UUID identifiers. I have not yet tried using /dev/sdxx identifiers in the fstab, but if I convert the fstab to use UUID and do not mount any of the duplicate UUID drives it will work with the 2.6.20 kernel.
If there is a bug it is this: There is no way (that I am aware of) to change the UUID of an NTFS or FAT32. So if UUID identifiers are required in fstab, there is no way to mount NTFS or FAT32 drives that have been cloned, and thus have duplicate UUID's. -- Superblock not read at boot https://bugs.launchpad.net/bugs/120285 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
