Re: 1st problem when installing f38

2023-06-10 Thread Samuel Sieb
On 6/10/23 16:35, Samuel Sieb wrote: On 6/6/23 01:28, François Patte wrote: Bonjour, I am following advices given in answering my previous post "issue" and I get f38 installer. The installer complains that there is a duplicate UUID on some disks : parts sde1 and sdf1 That's true!

Re: 1st problem when installing f38

2023-06-10 Thread Samuel Sieb
On 6/6/23 01:28, François Patte wrote: Bonjour, I am following advices given in answering my previous post "issue" and I get f38 installer. The installer complains that there is a duplicate UUID on some disks : parts sde1 and sdf1 That's true! Running blkid gives: /dev/sde1:

Re: 1st problem when installing f38

2023-06-10 Thread stan via users
On Fri, 9 Jun 2023 21:56:03 +0200 Peter Boy wrote: > I probably don’t count as an expert. But software raid introduces a > property „raid-member“ (not literally but something like that). Each > raid gets a UUID and all members of a specific raid get the same UUID > that identifies them as

Re: 1st problem when installing f38

2023-06-10 Thread stan via users
On Fri, 09 Jun 2023 10:02:19 -0700 "Doug Herr" wrote: > On Fri, Jun 9, 2023, at 9:38 AM, stan via users wrote: > > On Fri, 09 Jun 2023 09:48:25 +0200 > > François Patte wrote: > > > >> No answer... Is this problem so uncommon? Or so obvious? > > [snip] > > It is as if > > they were

Re: 1st problem when installing f38

2023-06-09 Thread Peter Boy
> Am 09.06.2023 um 18:19 schrieb François Patte > : Sorry for the delay. > Le 2023-06-09 14:01, Peter Boy a écrit : >>> Am 09.06.2023 um 09:48 schrieb François Patte >>> : ... Is it possible to unplug one of the disks (say sdf) and make an install with a raid1 in degraded

Re: 1st problem when installing f38

2023-06-09 Thread Peter Boy
> Am 09.06.2023 um 18:38 schrieb stan via users : > > On Fri, 09 Jun 2023 09:48:25 +0200 > François Patte wrote: > >> No answer... Is this problem so uncommon? Or so obvious? > > I haven't seen it even mentioned before and not obvious at all to me. > Perhaps there is an expert who would

Re: 1st problem when installing f38

2023-06-09 Thread Doug Herr
On Fri, Jun 9, 2023, at 9:38 AM, stan via users wrote: > On Fri, 09 Jun 2023 09:48:25 +0200 > François Patte wrote: > >> No answer... Is this problem so uncommon? Or so obvious? > [snip] > It is as if > they were assigned the same UUID *because* they were in a raid. [snip] That is normal for

Re: 1st problem when installing f38

2023-06-09 Thread stan via users
On Fri, 09 Jun 2023 09:48:25 +0200 François Patte wrote: > No answer... Is this problem so uncommon? Or so obvious? I haven't seen it even mentioned before and not obvious at all to me. Perhaps there is an expert who would immediately understand what happened, and how to either fix or

Re: 1st problem when installing f38

2023-06-09 Thread François Patte
Le 2023-06-09 14:01, Peter Boy a écrit : Am 09.06.2023 um 09:48 schrieb François Patte : ... Is it possible to unplug one of the disks (say sdf) and make an install with a raid1 in degraded mode (+lvm) then, when the install is finished, to plug again the disk sdf and synchronise the

Re: 1st problem when installing f38

2023-06-09 Thread Peter Boy
> Am 09.06.2023 um 09:48 schrieb François Patte > : > >> ... >> Is it possible to unplug one of the disks (say sdf) and make an >> install with a raid1 in degraded mode (+lvm) then, when the install is >> finished, to plug again the disk sdf and synchronise the partitions >> with mdadm? >>

Re: 1st problem when installing f38

2023-06-09 Thread François Patte
Le 2023-06-06 10:28, François Patte a écrit : Bonjour, I am following advices given in answering my previous post "issue" and I get f38 installer. The installer complains that there is a duplicate UUID on some disks : parts sde1 and sdf1 That's true! Running blkid gives: /dev/sde1:

1st problem when installing f38

2023-06-06 Thread François Patte
Bonjour, I am following advices given in answering my previous post "issue" and I get f38 installer. The installer complains that there is a duplicate UUID on some disks : parts sde1 and sdf1 That's true! Running blkid gives: /dev/sde1: UUID="4a28174a-f38b-4938-233f-85f76ce585a8"