I'm trying to install AlmaLinux on a used Dell Optiplex 3000 thin client. The system boots to BIOS without any issues (I wiped the SSD with a secure erase), and I can select the USB drive as the boot option. However, when I attempt to boot from the installation media, it starts off fine, shows a 'headless mode active' message, then returns to another BIOS screen (with the Dell logo) and just hangs there for 10-20 minutes before restarting. I can hear it making some noise, which suggests it's doing something, but it doesn't seem unresponsive since I can use Ctrl + Alt + Del to restart it.
I've tested the installation media on my Windows machine and can access the installation menu, but when I try to run the 'test media and install' option, I hit a known issue where it fails at 4.8%. I've tried several things: using both minimal and full Debian ISOs with verified checksums, two different USB drives, and different tools like Rufus, BalenaEtcher, and even dd on my Ubuntu server.
I'm considering erasing the USB drive with zeros before writing the image to ensure it's completely clean. Is there any way to bypass the BIOS splash screen to see the installation progress, or do you have any other ideas?
4 Answers
First off, make sure you set the USB drive as the primary boot option in the BIOS. Double-check that it's not trying to boot from the wiped SSD. You should also check if you can bring up a one-time boot menu using F12 during startup to choose the USB directly. This sometimes works better than the default boot order.
Don't forget to check that the SSD is plugged in properly! Sometimes, even if it seems secure, loose connections can cause boot issues. If all else fails, consider trying an earlier version of AlmaLinux or a different distro altogether just to isolate the problem with the hardware or BIOS settings.
Thanks for the tip! The SSD is beneath a heat sink, so I’ll take a look. I want to stick with current versions, but if I get stuck, I guess it wouldn’t hurt to try something else like an older version or even a different distro.
About that 4.8% media test failure you're encountering: it’s actually a sign that there's something wrong with the installation media. It’s usually best to not bypass that test since you're not sure if the media is corrupt. It could lead to more issues down the line if you try to proceed with a flawed setup. Really, it’s worth fixing this before moving on so you don’t waste more time trying to troubleshoot potential problems.
Exactly! Stay thorough with this. Corruption might be low probability after all your precautions, but it'd be smart to double-check everything before assuming that's the only issue.
I get that. I’m really hesitant to skip any tests but I can't see past the splash screen right now to figure out what's actually happening. It might not even be a media issue at all but could be something else entirely.
For additional guidance, we have installation tips available in our community wiki! It's also suggested to always use an Ethernet connection when installing. And don't forget to remove your boot media when you're finished!
Good idea! Sometimes testing with a different distro can help narrow down if it's a hardware or software issue.