Hi, > - I screwed up the first time and had to switch to the console on ALT-2 > and use dd to overwrite the MBR because the third disk wasn't recognized. > In the past, this would crash the installer, so I'm glad to see that's > fixed, but it would be nice if all disks were recognized or the existing > disk layout was ignored. > > OK, I think that’s worth a bug report against Anaconda! Unfortunately I > don’t have a 3 disk test equipment here at the moment. > > Would be helpful to know it someone can reproduce the issue or is it > specific to a special property of the hardware you are using. I suppose, > the disk are used and already had some data on it. Ist there something > special? E.g. had they different partitioning schemes?
Nope, they were all just type fd (Linux RAID), created by anaconda. > - Both times I tried to install, the systemd-resolved daemon wouldn't > resolve hostnames, as the "software selection" menu could not identify a > local mirror. I had to remove the /etc/resolv.conf symlink and create it > using 8.8.8.8. > > Obviously you didn’t used the distributed installation media to boot the > server. How did you create the boot medium? > This was from the fedora40 server netinstall ISO here. https://fedoraproject.org/server/download
-- _______________________________________________ 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
