On 19/01/20 17:02, William Morgan wrote: > But then I get confused about the UUIDs. I'm trying to automount the > array using fstab (no unusual settings in there, just defaults), but > I'm not sure which of the two UUIDs above to use. So I look at mdadm > for help: > > bill@bill-desk:~$ sudo mdadm --examine --scan > ARRAY /dev/md/0 metadata=1.2 UUID=06ad8de5:3a7a15ad:88116f44:fcdee150 > name=bill-desk:0 > > However, if I use this UUID starting with "06ad", then I get an error: Looking at your output (and no I'm not that good at reading traces) it looks to me like this 06ad8de5 uuid should be that of ONE of your partitions. But it looks like it's been cloned to ALL partitions. You didn't do anything daft like partitioning one disk, and then just dd'ing or cp'ing the partition table across? Never a good idea. > > bill@bill-desk:~$ sudo mount -all > mount: /media/bill/STUFF: mount(2) system call failed: Structure needs cleaning. > > But I don't know how to clean it if fsck says it's OK. > > On the other hand, if I use the UUID above starting with "ceef", then > it mounts and everything seems OK. Yup. That looks like the correct UUID for the array. > > Basically, I don't understand why lsblk lists two UUIDs for the array, > and why mdadm gives the wrong one in terms of mounting. This is where > I was confused before about the UUID changing. Any insight here? > Well it LOOKS to me like something has changed all the partition UUIDs to the array UUID, and then the array UUID has changed to avoid a collision. I dunno - let's hope someone else has some ideas ... Cheers, Wol
