Had the HL do a update and reboot and the box never came back up. Hook it up to a monitor and keyboard and it would get stuck on the Bios screen. Tried a few thing took the SAS card out no good. Tried to boot with out the harddrives and this is the only time it would come on tile past the BIOS screen. It would try to boot then throw the following error. Kernel panic - not syncing : VFS inable to mount root fs on unknown-block (0,0). Is there anything I can do outside of reloading the OS?
Just to be clear, this is a fully built HL8 with the Gigabyte B550I Aorus Pro AX motherboard and the m.2 SATA adapter card and you took out the m.2 adapter? Or have you installed your own SAS card?
Also assuming the full build running Rocky/Houston, I believe Rocky retains the last three installed kernels by default. When powering on the HL8, continuously tap Esc or Shift right after the BIOS screen to force the GRUB menu to appear. Selecting the second option (the previous, working kernel) should bypass the corrupted update and boot you straight into the OS.
I don’t use Rocky myself, but that is my understanding.
Once in the prior, stable kernel, fix the broken update by opening a terminal and running dracut -f --kver <broken-kernel-version> to rebuild the missing initramfs, or simply remove and reinstall the newest kernel via dnf.
Once the OS is booting properly again, plug the SATA adapter and drives back in, boot directly into the Gigabyte BIOS settings, and force your NVMe/SSD to be “Boot Option 1”. This may have gotten changed and why the system is hanging with the drives attached.
You could also boot into a Rocky Linux Live USB, mount your system drives (chroot), and repair the kernel from there.
See if that gets you anywhere and report back.
1 Like
There’s a problem with mounting the root filesystem. You’ll want to try to boot into an older kernel like @DigitalGarden suggested or boot into rescue mode to further troubleshoot (link below). If you can you get into rescue mode then I’d start by running sudo fsck -f /dev/sdXX on the root partition. Just like with Windows, the filesystem may have some errors that need repaired which then may allow the system to boot.
1 Like
Ok I got the kernal panic fix by remove the old kernal and updating the system so one win. Back to the other problem which I am wondering is the power supply. When all 8 drives are pluged into the back plan the system will not boot it sill stick at the BIOS screen and hand there I hear the sound of the drive start to spin up but then nonthing I waited and it just will not come on line
Glad to hear your kernel has calmed down. 
How many drives do have to remove for the system to boot? It’s worthwhile narrowing down the problem to a number of drives or a particular slot(s).
1 Like
Final update look like the problem is on my bench. When was working on the unit I pull it on to a test bench with KVM and it would not boot up with all the drives. Moved it back to the rack and it working good now. So I will dig into the power issuse and why it did not trip a breaker if I was pulling too much
2 Likes