Ah hah - this is the crucial bit of information. I think I just used the already-existing GPT and deleted the single partition. When I added three partitions, one got the UUID of the previous partition, and the other two got zeros.The gpt command creates GUIDs, including the partition GUIDs when you create the GPT itself. When adding, modifying or removing partitions these are not changed (just the "type GUIDs").
The whole GPT is also CRC checked and all generated GUIDs have some bits set. So it's difficult to understand how you can have a mix of good and bad GUIDs using regular gpt operations.So... how bad is it that I have four GPT partitions with the same GUID?I can only see two all-zero GUIDs, the others are unique. For NetBSD you only need unique "wedge names" that are made from the GPT partition labels or the partition GUIDs if no label was set. Wedges with non-unique names are ignored and the console logs that 'manual intervention' is required.
Sorry, the "four" was because two disks are like this (with two all-zeros each). And the system does seem to be working well enough - but now that I know what's going on I can fix it.
:) Can I edit them? And how do we think this happened?You can use the 'gpt uuid' command to replace the GUIDs with fresh ones.
Sigh. If I'd searched for "uuid" instead of "guid" I would have
found this in the man page. Thanks. *facepalm*
Thanks for the response - I do like to understand what's up, and now I do.
+j
-- Jeff Rizzo riz%tastylime.net@localhost +1 415 823 1847