[Feisty]fsck stalls boot when UUID of a different partition changes

[Daniel Moyne]

Binary package hint: e2fsck-static

I have a Feisty distro intalled with workable partition hda5 ; I installed in parallel another Feisty distro (planned for test of Gutsy after migration) ; when after installation of this Feisty I boot it fsck stops the boot process saying that hda5 partition has some incoherencies which does not make sense as this hda5 partition is correctly mounted by current Feisty.

[Theodore Ts'o (tytso)]

Please read the "REPORTING BUGS" section of the e2fsck man page. I need to know exactly what sort of inconsistencies were reported by e2fsck. Also, are you sure that /dev/hda5 on your new installation of Feisty is the same as on the other installation of Feisty? You might want to run dumpe2fs and look at the UUID and make sure it really is the filesystem that you think it is. Sometimes different kernels will autodetect different disks in different orders, and /dev/hda is just the first disk detected by the kernel.

[Daniel Moyne (dmoyne)]

Ok I will try to bring more information but I need to understand what is a UUID :
- is this somehow hardware related to the HD partition and in which case it will all the time the same whatever the distro,
- or can it be changed from one distro to another one in which case this sophistication will bring problem when like in my case I want to acces the same partition from.

Now something else : when installing my new distro fstab is rebuilt to assign UUID's to selected partitions and even if the UUID assigned in this later case is different from the one in the current distro there is no reason why data could not be accessed ; if not we are really facing problems !
Regards.

[Aaron Whitehouse (aaron-whitehouse)]

I believe that this is the same problem described in Bug #132762 (albeit from a different perspective).