You are not logged in.

#1 2024-11-09 06:32:45

adrit1234
Member
Registered: 2023-06-21
Posts: 26

NVME drive not detected anymore after grub reinstall

I run a dual boot archlinux/windows system on my dell inspiron laptop installed on separate SSD and a NVME drive respectively, and ran into this issue today.
I was playing a game on my archlinux system and then manually rebooted by pressing the power button when I thought the game wasn't running too well. When the laptop booted again, grub got broken, showing the: symbol grub is shim lock enabled not found error. I managed to get it back up and running by reinstalling grub with a live cd, but now the NVME drive where windows was installed on has disappeared completely. Using lsblk only shows the SSD drive and not the NVME, and running OS prober doesn't work as grub cannot detect the NVME drive or windows at all. I would like some help and explanation on this issue.

Last edited by adrit1234 (2024-11-09 06:33:25)

Offline

#2 2024-11-09 07:30:26

kermit63
Member
Registered: 2018-07-04
Posts: 258

Re: NVME drive not detected anymore after grub reinstall

Does your UEFI firmware detect the drive?


Never argue with an idiot, they will drag you down to their level and then beat you with experience.
It is better to light a candle than curse the darkness.
A journey of a thousand miles begins with a single step.

Offline

#3 2024-11-09 08:16:07

adrit1234
Member
Registered: 2023-06-21
Posts: 26

Re: NVME drive not detected anymore after grub reinstall

Doesn't look like it. There's no option for the NVME drive in the boot menu. Booting windows shows the BSOD with the error code(boot drive inaccessible).

Offline

#4 2024-11-09 08:44:33

kermit63
Member
Registered: 2018-07-04
Posts: 258

Re: NVME drive not detected anymore after grub reinstall

I don't mean just the boot menu. There are usually some settings in the UEFI firmware that allows you to adjust certain properties of the drive, assuming it's detected at all.

If there is no mention whatsoever of the drive within the UEFI firmware, chances are it's a hardware failure, possibly caused by forceful unclean shutdown with the power button. Nothing you can do within arch can fix that. The OS can only work on hardware that the firmware can detect.


Never argue with an idiot, they will drag you down to their level and then beat you with experience.
It is better to light a candle than curse the darkness.
A journey of a thousand miles begins with a single step.

Offline

Board footer

Powered by FluxBB