Some more details:
Acer nitro
Duel boot; Windows 10 and Fedora
Couple hours ago had a windows update that blue screened it (something about boot). I went into safe mode and uninstalled the update. It worked fine.
Afterwards I tried booting into fedora but it just gets stuck on the boot logo.
Not well versed in Linux so if giving instructions please include the steps of how to do xyz.
I have googled the job thing and while there are a few posts about it, I do not know how to do anything that they mention.
Hello @darkking202 ,
If you can please select the boot option in the grub menu you show in the second pic, that is at the top, but don’t press the enter key on it press e to edit the command line, look for resume= ..., delete that part of the command line and only that (resume=whateverelse) and I think you press x but it says how to continue with booting the edited command line.
This should get you booting into the latest kernel you have installed. You will still have to do more after but this is the starting point. Once you get this step to work, come back and I’ll help you move forward.
Thank you for helping me out. Sorry for the response delay, I’m back now and will be online indefinitely.
I believe I got to the requested menu but the specified command “resume” was not present. I’ll add pictures. Also let me know if you prefer landscape or portrait. I’ll also add a picture of bios settings for additional information.
I’ve also attempted using Live Media (did Fedora and Ubuntu) boot from a USB and once booted, browsing possible drives, it does not seem to view/see the M.2 SSD that Windows and Fedora is on. Only the 2.5" SSD Drive that’s used as additional storage space.
In the command line menu, where it has load_video and more, I am able to edit the lines. I have not changed anything just checked if its possible.
Hi @darkking202 ,
Sorry for the radio silence. I was moving halfway across Canada and had some major move issues. To make a long story short, a drive that should have taken say 18 to 19 hours took me from Wednesday evening to Sunday very early AM . So I will take a look at this more closely tomorrow, I’m just a bit fatigued right now.
Hi yeah, I guess you could say that, but there aren’t many cool (temperatures) around Canada this week. I moved (back) to Nova Scotia, a place I think is very cool, after all it’s Canada’s Ocean Playground.
and its 100% the issue i experienced with the same events leading up to error.
Now i have no idea what they’re talking about but they mentioned booting from live-media which I’d already used and even after booting into it, the m.2 disk that had my windows and fedora wasn’t showing up. In that thread they mentioned lsblk and fdisk neither of which recognized the existence of the other drive.
Not sure what or why but I searched something online and a reddit post recommended checking if ahci or something was set instead of raid in the computers bios SATA Mode (apparently bios is called UEFI). In that post OP said they switched to ahci and it magically worked. Sure enough after doing so, i rebooted into the live media and now it showed my m.2 drive and the windows and fedora partitions. At this point I thought about continuing using that earlier post link to try and fix it but figured what the heck may as well try to boot into the m.2 fedora partion. Back to computer bios settings to set boot order from live media to the fedora one (this was the one that was hanging on boot) and sure enough it worked!
Some other things that i click and clacked that may have mattered:
-While diagnosing, setting secure boot to disabled.
-Fast Boot disabled.
That posted link stated that windows update (in my cade update that blue screened so i undid the update after which at somepoint i tried booting fedora and found it to hang) erased some sort of references to grub and that’s what they spent their time trying to fix. However, perhaps this wasn’t the case in my situation? Like i said, I only followed the thread up to the lsblk and fdisk commands since they failed to display the presence of another drive (unlike OP in that thread). Oh right that was what I searched, something along the lines of “fedora not finding disk” or something.
Point is, try this first by loading the BIOS (UEFI) going to “Main” tab, and changing the “SATA Mode” from (in my case) “RST with Optane” to AHCI and then trying to boot back into the problematic fedora partition (right lingo?).
For me, fastboot sometimes comes back and I have to used a Control Panel “rescue” option to get back to the grub2 menu. This week: one of my systems was updating Windows 10. Updates normally require multiple reboots that bypass the usual grub2 menu. Windows 10 updates appeared to be finished, but system was still booting directly into Windows 10. I used the rescue option to get the UEFI menu where I could choose to boot Fedora (from an external drive). A day later an additional update arrived and after that was installed the system is back to normal.
