> 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.
No, I didn't. Here are the partition UUIDs for disks j,k,l,m:
bill@bill-desk:~$ for i in {j,k,l,m} ; do udevadm info --query=all
--name=/dev/sd"$i" | grep -i UUID ; done
E: ID_PART_TABLE_UUID=bbccfe6f-739d-42de-9b84-99ca821f3291
E: ID_PART_TABLE_UUID=f42fd04d-96e3-4b0c-b20c-5286898b104f
E: ID_PART_TABLE_UUID=f467adc9-dba4-4ee9-95cc-f1a93e4a7d98
E: ID_PART_TABLE_UUID=4805ef03-5bd1-46d1-a0e1-5dde52b096ec
> 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 ...
Well, here is some further info that shows 2 UUIDs for the single array md0:
bill@bill-desk:~$ udevadm info --query=all --name=/dev/md0 | grep -i UUID
S: disk/by-uuid/ceef50e9-afdd-4903-899d-1ad05a0780e0
S: disk/by-id/md-uuid-06ad8de5:3a7a15ad:88116f44:fcdee150
E: MD_UUID=06ad8de5:3a7a15ad:88116f44:fcdee150
E: ID_FS_UUID=ceef50e9-afdd-4903-899d-1ad05a0780e0
E: ID_FS_UUID_ENC=ceef50e9-afdd-4903-899d-1ad05a0780e0
E: UDISKS_MD_UUID=06ad8de5:3a7a15ad:88116f44:fcdee150
E: DEVLINKS=/dev/md/0 /dev/disk/by-id/md-name-bill-desk:0
/dev/disk/by-uuid/ceef50e9-afdd-4903-899d-1ad05a0780e0
/dev/disk/by-id/md-uuid-06ad8de5:3a7a15ad:88116f44:fcdee150
Still not sure why /dev/disk/by-id/ and /dev/disk/by-uuid/ would have
differing UUIDs, but maybe that's normal.
Maybe someone can shed some light here?
Cheers,
Bill
