Sunday, May 5, 2024
 Popular · Latest · Hot · Upcoming
2
rated 0 times [  2] [ 0]  / answers: 1 / hits: 3422  / 3 Years ago, sat, july 31, 2021, 6:35:06

I had dual boot working for the last few months on my PC, with Windows 10 and the EFI partition on a NVMe drive and Ubuntu on a SATA SSD. Both the Windows Boot Loader and Grub are installed on the NVMe drive, while the Grub config is on the SATA SSD.


Unfortunately, the last time I used Windows it did not shut down properly (I had to power cycle the PC) and now grub only displays the grub> prompt. Selecting the Windows Boot Manager from the motherboard's EFI does boot Windows correctly.


So I booted from a live USB, installed boot-repair and ran the utility. Whether I used the recommended repair or selected Purge GRUB before reinstalling it and Upgrade GRUB to its most recent version I had the same result as before.


Though when I unselected SecureBoot I had another result, grub is now showing error: no such device: b5d41058-ecac-4877-895d-2f9206cef3d2.


I have been looking into this issue for five hours, so I am now enlisting your help.


I generated a boot info using boot-repair, it should contain everything needed. Note that sdb is the live USB.


Also noteworthy, I'm using an AMD B550 chipset, which required me to update grub when I first moved my disks to my current PC.


Thank you very much!


More From » boot

 Answers
0

So, I tried reinstalling Ubuntu onto the SATA SSD with no luck: grub was still broken. What I ended up doing was switching to a NVMe SSD (Samsung 980), which fixed my issue.


I'm not sure whether my 860 was dead (though SMART is OK and Ubuntu seemed fine to install on it) or if it's a weird behavior caused by a mix and match of SATA and NVMe drives (and probably the AMD chipset).


I hope this will somehow help anybody with a similar issue, I wished I knew what was the exact issue with my PC.


Update over a year later:


I tried using the same SATA SSD as the sole boot drive in another computer and I add a similar issue: it was picked up by the motherboard something like once every five boots, even after fiddling with BIOS setting.


Only after I used another SATA cable that it was consistently picked up by the motherboard, so maybe the original issue was the SATA cable (as I re-used the exact same one).


[#1263] Monday, August 2, 2021, 3 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
epypian

Total Points: 130
Total Questions: 111
Total Answers: 113

Location: Romania
Member since Mon, Jun 6, 2022
2 Years ago
epypian questions
Sun, Oct 24, 21, 23:28, 3 Years ago
Sun, Dec 26, 21, 12:08, 2 Years ago
Tue, May 9, 23, 21:23, 1 Year ago
Thu, Mar 16, 23, 10:31, 1 Year ago
;