You are not logged in.
So I have quite a curious problem. It's probably not 100% related to arch itself, but idk where else to get help.
The problem is that I cannot boot off my NVME anymore. It's not even available when I try to adjust the boot order in the BIOS. Instead, it goes straight to network boot.
https://realitaetsverlust.dev/share/arch2.jpg
I've ran a scan offered by my BIOS and it said no errors found. The drive is also detected by my motherboard as it shows up in the hardware manager.
https://realitaetsverlust.dev/share/arch3.jpg
I also mounted the root partition into a live USB and the partitions are all there. I have also arch-chroot'ed into the root partition and the files and everything are all there.
https://realitaetsverlust.dev/share/arch1.jpg
My suspicion is that the drive is, for whatever reason, is not bootable anymore. But I don't know how to fix this and I'm also not sure if I can just reinstall grub without putting my current system in jeopardy.
What I also did was using fdisk to check the state of the drive and I noticed that no partition is bootable:
https://realitaetsverlust.dev/share/arch4.jpg
I'm not sure if that is the cause, even tho it is quite likely.
If anyone has an idea on how to fix it, I'd be extremely grateful. Also, if anyone knows WHY this happened, I'd be even more grateful.
I'd also like to apologize for the quality of the post, but I can't make any screenshots as I don't have an HDMI grabber or something.
moderator edit -- replaced oversized images with links.
Pasting pictures and code
Last edited by realitaetsverlust (2022-02-05 14:20:49)
Offline
The NVRAM entry got deleted, it likely has nothing to do with your disk. Reinstall grub just like you did the first time, it'll recreate the entry.
As for the 'why', Windows update? System firmware update?
Offline
Ah wow, yeah. That was simple. grub-install fixed it again. Thanks for that.
The reasons are both very unlikely tho, I do not have a windows partition on my system, and I also didn't do any firmware updates. What I do have is a drive that runs windows 10, but that's a completely different drive and it's only used via the KVM I've setup so I'm not quite sure if that could've affected my linux drive?
Offline
Again, it's not the drive. NVRAM entries are stored in on the motherboard.
Offline
Okay, so I still have to pay attention when the windows KVM does update. That's a bit annoying, but at least I now know a fix.
Thank you ![]()
Offline