Re: 1st problem when installing f38

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> Am 09.06.2023 um 18:38 schrieb stan via users <users@xxxxxxxxxxxxxxxxxxxxxxx>:
> 
> On Fri, 09 Jun 2023 09:48:25 +0200
> François Patte <francois.patte@xxxxxxxxxxxxxxxxxxxx> 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 workaround it.  But like you, I don't
> understand how the system could assign the same UUID to two disks.   

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 belonging together. I guess, the problem is not that the disks have the same UUID but a missing value of a property elsewhere indicating how to interpret that property. 

I guess it is quite pointless to find the mistake. Even if you would identify it, there might be no tool to fix it. And binary-editing a disk sector may be quite a challenge.


> Is
> it possible that the way you set up raid was different?  It is as if
> they were assigned the same UUID *because* they were in a raid.  Are
> they using hardware raid, or an unusual software raid?  What happens if
> you try to change the UUID on one of the disks?  Don't actually do it
> because you might lose data, but does it give an error or warning?


If I remember the previous thread correctly, there was some disk cloning involved. Maybe that part of the issue.








--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy@xxxxxxxxxxxxxxxxx

Timezone: CET (UTC+1) / CEST /UTC+2)

Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast


_______________________________________________
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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux