> Am 11.07.2024 um 16:56 schrieb François Patte > <francois.pa...@mi.parisdescartes.fr>: > > Le 2024-07-10 19:55, Mike Wright a écrit : >> On 7/10/24 10:48, François Patte wrote: >>> Le 2024-07-10 18:26, Mike Wright a écrit : >>>> On 7/10/24 09:19, François Patte wrote: >>>>> Le 2024-07-10 18:05, Mike Wright a écrit : >>>>>> On 7/10/24 08:33, François Patte wrote: >>>>>>> Le 2024-07-10 15:12, Mike Wright a écrit : >>>>>>>> On 7/10/24 01:15, François Patte wrote: >>>>>>>>> Bonjour, >>>>>>>> Bonjour, François, >>>>>>>>> Now, if someone could tell me how to mount an lvm2_member, I will be >>>>>>>>> happy! Indeed, my personnal data are on a disk from the f36 install >>>>>>>>> which is a RAID1 member and an lvm2_member. If I try: >>>>>>>>> mount /dev/sdd2 >>>>>>>>> I get "unknown filesystem linux_raid_member" >>>>>>>>> I can bypass this error typing >>>>>>>>> mount /dev/md5 >>>>>>>>> But the error is now: "unknown filesystem lvm2_member" and I don't >>>>>>>>> know how to bypass this error. >>>>>> When a partition is added manually to a system by mounting the system >>>>>> needs a hint as to what to do. I think what you need here is to >>>>>> activate the LVM member: vgchange -y. If this is to be permanent you >>>>>> would need to use -ay. Little command, tons of options. Man >>>>>> vgchange. >>>>> I read this on some posts on the internet... but if I do something like >>>>> this will it change something on this partition making it unusable with >>>>> the f36 install as the /home partition.... I want to keep this f36 >>>>> install untill f40 will be completely configured (because I use it to >>>>> work!) >>>> I do not think it modifies the partition in any way whatsoever. It >>>> just advises the o/s what to do with it. >>> OK. I tried and nothing has changed... What can I do! >> Go Canes, in a reply to me, suggested pvscan|vgscan|lvscan. This is >> most likely the missing ingredient. Sorry I missed that. > > No success with pv|vg|lv-scan it is as if this lvm2_member does not exist, > except if I want to mount it! >
I don't know if the following is relevant to your problem (I don't have the full context here), but: LVM defaults have been changed recently. If there is a file in /etc/lvm/devices, all vg…/lv… commands just use those partitions which are listed in that file. All other partitions, specifically those which are new in a system, are not included in the processing. You either have to add the device to that list or use an option in any of those commands. See: https://bugzilla.redhat.com/show_bug.cgi?id=2247872 -- Peter Boy https://fedoraproject.org/wiki/User:Pboy p...@fedoraproject.org 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@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
