Michael Tokarev wrote:
michael@xxxxxxxxxxx wrote:
[]
Using the filesystem ID doesn't work either because /dev/sda,
/dev/sdb, and /dev/md0 all have the same UUID since it is a mirror.
How do you tell the system to mount /dev/md0 and not the individual
drives which is what it is trying to do now.
The tools/library that looks up filesystem UUIDs/labels are smarter than
that. Or are supposed to be smarter. That it - the tools are able to
recognize and skip components of a raid array, since raid superblock is
present on the device - which is not present on the array itself.
Well, the tools just might be smarter than me.
I tried boot via UUID again tonight using the filesystem UUID and it is
working. I haven't messed with the udev rules or changed anything I can
think of to account for the change in behaviour. I have also rebooted a
number of times and it seems to work every time.
Good news it is fixed and I appreciate all the suggestions from
everyone. I have learned a lot about linux software raid ( and LVM ) in
the course of this little project. Bad news I don't know why it is fixed.
Thanks everyone!
Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
