You are not logged in.
Pages: 1
Previous to linux 3.0 kernel, mdadm.conf listed uuid formatted such as:
0e55cd32-ad2e-44a9-92d2-6f009176bf1aLatest format in mdadm.conf :
f72d161a:5ae1e852:d6b20ecf:8399b027Exactness is primary in ID's, especially the format.
Thus, addressing the new format as mandatory, does fstab need to be re-formatted if using uuid?
Does grub2 need the same treatment?
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
not sure about grub2, but i did find this debian ticket that seems to be talking about why this happens:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570516
they indicate that in the upgrade, there may be init scripts or elsewhere that "autoupdates" the hostname in the superblocks (and stores same in mdadm.conf). it also adds the hostname to the hash if it hasn't yet been added. not sure if this is what happened to your uuids or not, but it seems to fit.
Offline
here is a discussion about grub2 that reviews the issues around change from superblock 0.9 to 1.2. maybe run grub-mkconfig. anyway, hope it helps.
Offline
Pages: 1