Every time it ran, it deactivated all vg's while running its install- system.
Reactivating them & then re-trying accomplishes nothing, as the install- process itself breaks the activation of all vg's. --- 1 other detail: this system has a former-btrfs-raid1 device in it, which cannot be mounted without mount being given the -o degraded option. Because btrfs won't permit mounting without that added option, that may have been part of what is breaking the fstab module. ( the reason I'm installing into mdadm raid1 pairs, with 1 in write- mostly, is simply because all my stuff from the old distro is in the other fast-device, the no-longer-raid1 btrfs filesystem, until I can get the new system up & running. Once it's proper, then I can finish copying stuff over from the former- btrfs-raid1 to the new system, get that emptied-device put into the mdadm, & then my system will be proper again. ) Also, I never linked to any other bug with any copy/pasta. I typed-in what I'd recorded from the error-boxes that Calamares put on the screen, into this bug-report-system, but there's no link to any other bug in what I'm seeing, or what I entered. Maybe you mean the bug-report I put on github? I've no idea who needs to see the bug- report, but I'm presuming that both Calamares & Ubuntu ( relying on Calamares ) need-to. So how the hell can one manually override an automatic deactivate-all- vg's in Calamares, that destroys its ability to mount the target- partitions, then? _ /\ _ that deactivation-of-vg's is coded into Calamares, so -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2097706 Title: 24.04 & 24.10 installers break LVM, deactivating all vg's, AND can't install into a non-VM partition in the same system, either. To manage notifications about this bug go to: https://bugs.launchpad.net/calamares/+bug/2097706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
