Grub boot errors?

I've been on Bazzite about a month, and it's looking good. I had an issue in windows where about 25% of the time it failed to boot and just hanged on the motherboard 'boot' light. Sometimes flipping the switch on the power supply and letting that sit off for a couple minutes solved it. It got more extreme where while it was off, I would re-seat both m2 drives I have as just the manual power cycling of the psu wasn't always working (one being the windows drive, another just plain ntfs drive). I switched to Nobara for a few months at the same time I replaced the mobo, ram and cpu. Didn't have any issues there. Every drive i had i also reformatted to btrfs. I switched to Bazzite when I got a larger m2 drive for boot and wanted to see ease of use for getting people off windows (larger support, but mad props to glorious eggroll), and worked fine until a few days ago. Same issue occured as on windows. Sat on the screen with a little indented '_', and... nothing. Waited about 20 minutes, boot light on on mobo, and still nothing. The psu manual switch cycling solved it. No issues til now, and i wait again. Low and behold, i actually get a grub error. Hoping someone might be able to help me figure out what's wrong with my system. The drive that boot is on is practically brand new. The rest of my drives are... older with a mix of ssd and hdd's of various speeds (hdd's all WD, but a mix of black and blue and none are the same size). Ssd is a Samsung 850 pro, and the other m2 is a WD black 2 tb. Boot drive is a m2 Samsung 990 pro 4tb if any of that helps. Attached phone image of grub error.
No description
3 Replies
Buoll
BuollOP2mo ago
I guess second question is how would I go about running a fsck or something similar? I wanted to check my grub.conf but can't get to /boot/efi or even use 'su' to get into the root admin privileges (a bit concerning since I assumed I would be able to when setting up myself as an administrator, but that's now a secondary question). Wasn't sure after that su failure what I should do to check disks without breaking something
wolfyreload
wolfyreload2mo ago
I had an issue a while back where my OS took forever to boot and was getting weird errors. It turned out that my SATA cable wasn't plugging in properly. Assuming you have NVME drives, it might be worth re-seating the drives and see if it makes a difference. I'm thinking that might be why you are getting that blue light. Might also be worth googling your mainboard model to see what that blue light means
Buoll
BuollOP2mo ago
So I live booted into fedora workstation from usb to run fsck and btrfs check, and all came back clean. Haven't seen anymore issues. It was concerning that grub was giving me bad sectors, but I don't know how all that plays into it. Given some of the hdd's are 10+ years old, it might be worth cutting back a little anyway. My poor sata lines are probably struggling in silence

Did you find this page helpful?