Am 02.05.2023 um 16:45 schrieb Tim via users users@lists.fedoraproject.org:
Tim:
Briefly looking at RAID information, there are things that should be unique, and there are some things that can be duplicated (not so sure that they should be, though). Drive IDs would need to be unique for anything that uses IDs to differentiate one drive from other. There's partition and volume IDs that are used for different purposes.
Peter Boy:
I agree. But it’s hard not to use UIEDs and to ignore misconfigured UUIDs. Many Fedora tools use UUID by default, e.g. Cockpit and - if I remember correctly - dbus. Therefore, cloning a disc often ends up in more work than cloning saves.
Since my experience with RAID is minimal (using a motherboard with built-in hardware RAID that could not be shut-off on the drive ports I had to use), I assume that if a mirror drive dies, you swap it, and let the RAID do its own magic to incorporate the replacement drive into the system, it handles filling up the new drive with partitions and data from the other drive without cloning IDs.
Software Raid write various meta data on the drive. Therefor - as I understand the docs - you MUST NOT clone the drive. I use SW Raid on my private servers only, and luckily I had not so much drive failures so far. But SW Raid restored the drive on its own when I tested it a while ago. However, according to my memory, I had created a (empty) partition table. I don't remember if that was necessary or if it just happened.
-- Peter Boy https://fedoraproject.org/wiki/User:Pboy pboy@fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member Fedora docs team contributor Java developer and enthusiast