Hello. I’m attempting to install Fedora Silverblue 38 and am getting the error:
pyanaconda.modules.common.errors.general.AnacondaError: No device at '/sys/devices/virtual/block/md127'
This appears as an unknown error in the GUI right after it loads. I switched to tmux using Ctrl-Alt-F1 to be able to see the actual error.
Extra details:
When I had my disk mode set to Raid, the GUI loaded fine but my hard drive wasn’t listed as a place to install onto. I switched to AHCI and then this error started happening instead.
I’m on an Alienware Aurora R7 running Windows 10. I’m not looking to do anything fancy (no dual booting) and I’m ok with wiping everything on the hard drive including recovery partitions.
I had errors using Fedora Media Writer so I ended up copying the Silverblue ISO to my USB stick using Rufus instead.
It seems that windows probably forces the bios to still see raid mode for the drive.
The cleanest and simplest way, since you are not intending to dual boot with windows, would be to do as you mentioned. Do a complete new install of fedora and just wipe out everything already on the drive as you do the install. I think that is choosing to ‘erase everything and use the entire device’ or something similar.
Thanks for your response, Jeff. I can’t do a complete new install of Fedora because that error prevents me from using the installer. But maybe I could erase everything in advance using a third party tool that I load onto a USB stick, and then the installer will work afterwards? If you know of good software for doing that full wipe, please let me know.
Are you able to boot the install image to a live system? If so then the tools available in the os should be able to manage the drive that is the issue. With raid disabled and the drive in AHCI mode one should be able to boot to the live system then use gdisk to write a new GPT partition table to the drive. After that another reboot to the install media should now allow a full new installation.
Since you are installing silverblue I am not familiar with the installer used there. I normally use Workstation for my systems but suspect that most of the process is similar.
Silverblue doesn’t offer that live system capability (the boot menu only shows installation as an option and takes you into Anaconda), but I was able to use your suggestion by putting Workstation on my USB stick and booting into that live environment, then using gdisk. Then for good measure I did a full install of Workstation, which went smoothly.
Unfortunately the Silverblue installation still doesn’t work. It might be a different root cause now, but I can’t get the logs because it crashes(?) and reboots right after popping up the modal announcing that there was an error.
If I feel motivated I’ll try and find a way to grab the logs so that I can get more help. Otherwise I’ll just stick with Workstation for now.