Hi,
I just had standard updates and now windowsfx (an ubuntu distro) won't boot, it hangs at the loading initial ramdisk part and I'm not sure why the boot-repair-disk boot repair tool isn't working.
Here's the pastebin link it gave me, I hope this is the right place (I followed a link from here to here to here):
http://paste.ubuntu.com/p/gz8Xkd2ynY/
My main partition is sda2, for clarity, I'm not sure how clear or relevant that is, as I'm very out of my depth here.
Thanks for any assistance,
Maia
edit: gonna put any further pertinent information from later posts here, in the interest of clarity:
p1:
Also, there's only one OS here, I'm not dual booting: I'm in the process of migrating data FROM windows TO windowsfx, as I've decided to jump ship and this seemed an accessible-ish step for me.
What appears to be a windows drive is a copy of the windows install I had on THIS SSD, which I cloned to an HDD partition while I set up my main OS back over here on my SSD, and as I said this was working perfectly fine, fresh out the box so to speak, after a clean install directly to the SSD. That is, until this round of updates did something weird to the boot files, from what i can gather.
I followed the instructions I was given when I googled around and found the boot-repair-disk utility seemed to be the best option, and I already had it on my medicat drive, so gave it a go.
Now I'm in completely over my head and I'm afraid I need complete newbie level advice here. I am a brand new linux user.
sda2 is where my main OS is, from what I can tell, which is windowsfx, and I intend to use this machine to boot directly into windowsfx, and did have the boot manager hidden entirely until all of this suddenly started happening after those updates. Now I don't know WHAT'S going on.
p2:
I am and have always been booting in UEFI mode. My BIOS settings have remained unchanged since well before the round of updates that caused Windowsfx to begin hanging at "loading initial ramdisk".
I proceeded to plug in my ventoy-based wd passport that runs Jayro's Medicat USB recovery drive and through that booted into boot-repair-disk and ran the boot repair tool provided, on its recommended settings. You may be seeing that in there somewhere, as it's what I was running to generate the program output you see above.
After this failed, said output led me here with the pastebin link in hand, and that's all that's happened thus far.
I am still able to access the grub menu, I can select the correct operating system, and it just hangs seemingly indefinitely (I don't have the money for the electricity meter to keep my gaming rig on for 24 hours, waiting to see if it does anything, but if it takes more than a half hour--which it does--then something's deeply wrong regardless of how long I'm prepared to wait).
Bookmarks