Hardware or software raid typically makes and exact copy of what they are mirroring. Hardware raid typically mirrors the entire disk (all UUIDS on the disk will be duplicated on the 2nd device, but in real hw raid the raid controller hides the underlying devices), software raid can do the entire disk or simply do one or more partitions, but exactly clones what is in the mirrored partition, there will be design be duplicate UUIDs for any FSes and/or PV/VG/LVM's. It sounds like MD-RAID is creating the correct raid1 MD device(with duplicate UUID for the fs as would be expected), but anaconda is not correctly ignoring the underlying components in use and being managed by MD-RAID. On Tue, May 2, 2023 at 9:45 AM Tim via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > 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. > > -- > > uname -rsvp > Linux 3.10.0-1160.88.1.el7.x86_64 #1 SMP Tue Mar 7 15:41:52 UTC 2023 x86_64 > > Boilerplate: All unexpected mail to my mailbox is automatically deleted. > I will only get to see the messages that are posted to the mailing list. > > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
