Am 01.05.2023 um 18:12 schrieb David Woodyard <dwoody5654(a)gmail.com&gt;: I have searched the web for a solution and have found nothing on this topic. The error I get is sda1 and sdb1 have the same UUID. I would rather not remove a drive from raid and unplug it to do the install. I must be missing something.

Am 01.05.2023 um 18:33 schrieb David Woodyard <dwoody5654(a)gmail.com&gt;: the server is what I need to install.

Am 01.05.2023 um 19:39 schrieb David Woodyard <dwoody5654(a)gmail.com&gt;: ... Fedora is the only OS.

Second bunch of questions: (a) Do you need to keep data? If yes, how they are stored? On its own partition? Both / and /home has raid1. / of course will be over written. /home needs to be preserved.

If not, is there anything against completely restructuring the hard disks? Then you wouldn't have to worry about the UUID at all. (b) how are the disk currently formatted, what is the output of Formatted as ext4 for everything. lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 1 931.5G 0 disk ├─sda1 8:1 1 14.7G 0 part └─sda2 8:2 1 916.9G 0 part └─md127 9:127 0 916.7G 0 raid1 /home sdb 8:16 1 931.5G 0 disk └─sdb2 8:18 1 916.9G 0 part └─md127 9:127 0 916.7G 0 raid1 /home sdc 8:32 0 111.8G 0 disk └─sdc1 8:33 0 111.8G 0 part └─md0 9:0 0 111.7G 0 raid1 sdd 8:48 0 111.8G 0 disk └─sdd1 8:49 0 111.8G 0 part └─md0 9:0 0 111.7G 0 raid1 sde 8:64 1 28.6G 0 disk ├─sde1 8:65 1 1M 0 part └─sde2 8:66 1 28.6G 0 part / zram0 252:0 0 8G 0 disk [SWAP] The sde drive is a usb that I am using to boot with until I get the hdd fixed.

Am 01.05.2023 um 18:33 schrieb David Woodyard <dwoody5654(a)gmail.com&gt;: > the server is what I need to install. OK, o I guess Server will be the only Operating System on the device. And because you ‚see‘ sda and sdb, you don’t have a hardware raid but use a software raid. Second bunch of questions: (a) Do you need to keep data? If yes, how they are stored? On its own partition? If not, is there anything against completely restructuring the hard disks? Then you wouldn't have to worry about the UUID at all. (b) how are the disk currently formatted, what is the output of lsblk (c) Do you know, if it is a BIOSboot machine or an UEFI machine?

Am 01.05.2023 um 22:22 schrieb David Woodyard <dwoody5654(a)gmail.com&gt;: On Mon, May 1, 2023 at 11:33 AM David Woodyard <dwoody5654(a)gmail.com&gt; wrote: the server is what I need to install. David On Mon, May 1, 2023 at 11:28 AM Peter Boy <pboy(a)uni-bremen.de&gt; wrote: > Am 01.05.2023 um 18:12 schrieb David Woodyard <dwoody5654(a)gmail.com&gt;: > > I have searched the web for a solution and have found nothing on this topic. > The error I get is sda1 and sdb1 have the same UUID. I would rather not remove a drive from raid and unplug it to do the install. > > I must be missing something. It’s a well proven procedure. What do you want to install? Workstation, Server, one of the Spins? Gmail has deleted your second reply, so I am replying to this one.

I, perhaps, was not as clear as I should have been on my first email. I have a computer that has a raid1 and it has been working for several years. I want to install Fedora-Server 37. When I run the install (anaconda) it gives an error about duplicate UUID's and will not do the install. That tells me that I can not install on a computer that ALREADY has raid1. I was not expecting that error. Is it correct that anaconda can NOT install to a hard drive that ALREADY has a RAID1? Is there a workaround other than removing one drive from the raid and unplugging it from the computer?

- - - - - repeating my previous post - - - - - - <

> Am 01.05.2023 um 19:39 schrieb David Woodyard <dwoody5654(a)gmail.com&gt;: > > ... > Fedora is the only OS. That’s good. So it is quite easy. > > Second bunch of questions: > > (a) > Do you need to keep data? If yes, how they are stored? On its own partition? > Both / and /home has raid1. > / of course will be over written. /home needs to be preserved. That’s not so good, but perfectly doable. Keeping sda2/sdb2 and mounting as /home may cause some headaches in the long run, in organizational and administrative terms. But does not affect the reliability. Maybe, you study https://docs.fedoraproject.org/en-US/fedora-server/installation/#_storage... and https://docs.fedoraproject.org/en-US/fedora-server/installation/interacti... If you haven’t already done so. > > > If not, is there anything against completely restructuring the hard disks? Then you wouldn't have to worry about the UUID at all. > > (b) how are the disk currently formatted, what is the output of > > Formatted as ext4 for everything. > > lsblk > > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS > sda 8:0 1 931.5G 0 disk > ├─sda1 8:1 1 14.7G 0 part > └─sda2 8:2 1 916.9G 0 part > └─md127 9:127 0 916.7G 0 raid1 /home > sdb 8:16 1 931.5G 0 disk > └─sdb2 8:18 1 916.9G 0 part > └─md127 9:127 0 916.7G 0 raid1 /home > sdc 8:32 0 111.8G 0 disk > └─sdc1 8:33 0 111.8G 0 part > └─md0 9:0 0 111.7G 0 raid1 > sdd 8:48 0 111.8G 0 disk > └─sdd1 8:49 0 111.8G 0 part > └─md0 9:0 0 111.7G 0 raid1 > sde 8:64 1 28.6G 0 disk > ├─sde1 8:65 1 1M 0 part > └─sde2 8:66 1 28.6G 0 part / > zram0 252:0 0 8G 0 disk [SWAP] > > The sde drive is a usb that I am using to boot with until I get the hdd fixed. The Harddisks are <2 TB and it looks like a DOS/MBR partitioning. Fedora nowadays used GPT for all disks. As said, you can keep DOS/MBR, but may cause organizational and administrative problems later due to the different default partitioning. Another issue: (a) sdb has just sdb2, no sdb1. So we have to know, how it is partitioned in detail to determine, how we can use the disk as part of a raid. (b) Regarding the mentioned UUID issue you have to check the disk ID. Therefore, use as root / with rood permission (sudo -i) fdisk -l | less You can scroll up and down to check all partition entries. Would be good if you could post the listing here Another question: how do you use sdc/sdd ? They are raid type 1 as well. but obviously not mounted anywhere. To install Fedora Server you have several options: (a) To create a Raid of 14 GB on sda and sdb, format at as xfs (no LVM as Fedora uses by default) and use it as the root file system for system data. Mount the raid on sda2 und sdb2 as /home in the root file system. That’s a bit tricky, but nevertheless just a series of several step-by-step actions. (b) Install the system (root file system) just on sda1 without raid (and therefore without redundancy in case of a disk failure for the system files) and mount the current raid on /home. That’s the easiest way. (c) If you don’t use sdc/sdd, then install Fedora on those disk, and - again - mount sda2/sdb2 as /home. That’s quite easy as well. (d) Backup /home, completely reformat the disks and restore /home. Comparing the alternatives: (c) seems the best solution if you can completely overwrite disks sdc/sdd. (b) is best, if you mainly want to play around and explore Fedora Server (a) Is best if you want to seriously use Fedora Server, but without touching you precious data (provided you can add a partition to sdb as required). (d) is best if you want a long term solution in line with Fedora's development and administrative principles and (upcomming) administrative tools. That’s your choice.

Am 02.05.2023 um 09:05 schrieb Tim via users <users(a)lists.fedoraproject.org&gt;: On Mon, 2023-05-01 at 23:12 +0200, Peter Boy wrote: > I think, no system can use 2 disk which have the same UUID at the > same time (besides maybe one of the Windows BIOS fake controller). > Duplicate UUID is a contradictio in adiecto and should be fixed. Just a guess, but it probably could, if you didn't use the UUIDs to mount the drives by. Such as you mounted them by device names, or volume names. Though, I think it'd be best not to have cloned IDs. 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.

Am 02.05.2023 um 16:45 schrieb Tim via users <users(a)lists.fedoraproject.org&gt;: 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.

Hardware or software raid typically makes and exact copy of what they are mirroring.

I have searched the web for a solution and have found nothing on this topic. The error I get is sda1 and sdb1 have the same UUID. I would rather not remove a drive from raid and unplug it to do the install.

I have searched the web for a solution and have found nothing on this topic. The error I get is sda1 and sdb1 have the same UUID. I would rather not remove a drive from raid and unplug it to do the install.