I did respond to your last email, this is additional... I don't normally top post, but in this situation I thought it appropriate: I found the following: https://discussion.fedoraproject.org/t/fedora-live-install-to-hard-drive-... Which is exactly what I am seeing. reboot as required. I think what I should do is unplug the sda and sdb drives from the computer (/home only). sdc and sdd are 120G ssd's and only have the OS. clear the partitions on sdc and sdd and install plugin the sda/sdb drives back in for /home and add to /etc/fstab That should take care of the UUID problems.

Thanks for your help, David ---- On Mon, 01 May 2023 16:48:25 -0500 david woodyard <david.woodyard(a)rdwoodyard.com&gt; wrote --- ---- On Mon, 01 May 2023 16:12:20 -0500 Peter Boy <mailto:pboy@uni-bremen.de> wrote --- > Am 01.05.2023 um 22:22 schrieb David Woodyard > <mailto:dwoody5654@gmail.com>: > > > > On Mon, May 1, 2023 at 11:33 AM David Woodyard > <mailto:dwoody5654@gmail.com> wrote: the server is what I need to > install. > > David > > On Mon, May 1, 2023 at 11:28 AM Peter Boy > <mailto:pboy@uni-bremen.de> wrote: > > > > Am 01.05.2023 um 18:12 schrieb David Woodyard > > <mailto:dwoody5654@gmail.com>: > > > > 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 suppose you mean my last reply. I add it at the bottom. > > 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? No, that’s not correct. 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. Anaconda can install on existing raid anyway. And there are several ways to fix the issue with the UUID. But I have to know more details. First question is, which of your disks is affected and what is the output of 'fdisk -l'. I deleted /dev/sdb1 (see blkid output after fdisk-l output) to get rid of the UUID error another UUID error occurred because of another raid1, that is when I stopped trying anaconda. After fdisk -l there is a bklid output as well Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: WDC WD10EZEX-08W Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x0009d086 Device     Boot    Start        End    Sectors   Size Id Type /dev/sda1           2048   30738431   30736384  14.7G 83 Linux /dev/sda2       30738432 1953523711 1922785280 916.9G fd Linux raid autodetect Disk /dev/sdb: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: ST1000DM003-1ER1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x0009d086 Device     Boot    Start        End    Sectors   Size Id Type /dev/sdb2       30738432 1953523711 1922785280 916.9G fd Linux raid autodetect Disk /dev/sdc: 111.79 GiB, 120034123776 bytes, 234441648 sectors Disk model: Patriot Burst    Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x2bca7198 Device     Boot Start       End   Sectors   Size Id Type /dev/sdc1  *     2048 234441647 234439600 111.8G 83 Linux Disk /dev/sdd: 111.79 GiB, 120034123776 bytes, 234441648 sectors Disk model: Patriot Burst    Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xc7ede561 Device     Boot Start       End   Sectors   Size Id Type /dev/sdd1  *     2048 234441647 234439600 111.8G 83 Linux Disk /dev/sde: 28.64 GiB, 30752636928 bytes, 60063744 sectors Disk model: Ultra            Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: EAECC2D5-8FE6-4C20-96D9-9044734B1928 Device     Start      End  Sectors  Size Type /dev/sde1   2048     4095     2048    1M BIOS boot /dev/sde2   4096 60061695 60057600 28.6G Linux filesystem Disk /dev/zram0: 8 GiB, 8589934592 bytes, 2097152 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/md0: 111.73 GiB, 119964893184 bytes, 234306432 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md127: 916.73 GiB, 984331845632 bytes, 1922523136 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes blkid output: has UUID, UUID_SUB, PARTUUID /dev/sdd1: UUID="2485c56c-c073-e680-ecc5-cd786aa01699" UUID_SUB="87595d10-1fb4-b431-ed8f-ecb52dfb39e0" LABEL="star1.home.com:0" TYPE="linux_raid_member" PARTUUID="c7ede561-01" /dev/sdc1: UUID="2485c56c-c073-e680-ecc5-cd786aa01699" UUID_SUB="7b55919e-4cca-3575-b6ce-f0a0749ff897" LABEL="star1.home.com:0" TYPE="linux_raid_member" PARTUUID="2bca7198-01" /dev/sdb2: UUID="a92ca2fd-998f-d542-feb8-59fa8bd7ab33" UUID_SUB="748fd654-f6a6-b72e-dab0-75dfb8b9f1af" LABEL="star11.home.com:home" TYPE="linux_raid_member" PARTUUID="0009d086-02" /dev/sda2: UUID="a92ca2fd-998f-d542-feb8-59fa8bd7ab33" UUID_SUB="dc6884eb-956e-aa80-8b52-5656365517d1" LABEL="star11.home.com:home" TYPE="linux_raid_member" PARTUUID="0009d086-02" /dev/sda1: UUID="19e00749-fb48-4708-8c7f-20378bc9ac03" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="0009d086-01" /dev/sdb1 does not exist because I removed it from the raid  and then deleted the partition /dev/md0: UUID="90d875a6-2643-434b-88f6-e51d8a5324ac" BLOCK_SIZE="4096" TYPE="ext4" /dev/sde2: UUID="eab43a73-d799-470a-9355-f6a518aadf8b" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="f83f8fd2-d7f4-4216-ae8f-8334a7f19461" /dev/md127: UUID="8d1f20a0-33a5-426f-aef0-2d40f1aac2b3" BLOCK_SIZE="4096" TYPE="ext4" /dev/zram0: LABEL="zram0" UUID="7f6046f8-bcbf-4000-b45e-0b4fbd967f74" TYPE="swap" /dev/sde1 if the usb drive I am using to boot the computer. /dev/sde1: PARTUUID="1a6240c3-8fb0-4d03-b803-a751bcf65726" Thanks, David > - - - - - repeating my previous post - - - - - - < >> Am 01.05.2023 um 19:39 schrieb David Woodyard >> <mailto:dwoody5654@gmail.com>: >> >> ... >> 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.