Boot into Blank screen after battery ran out

Sphor

So, the battery ran out, I rushed to plug it back, and the music came back (had Spotify on).
I was happy because I thought I caught it in time, but I realised everything else froze. the device became unresponsive, so I forced shutting it down.

I then pressed the power button and ever since then, I only get a blank screen.

I have an external Solus Disk I can boot from, but I have no idea how to repair the internal one.

Any tips please?
And,
Does this usually happen after Solus gets a power loss?

brent

I sat on this a couple days and did a tiny bit of research as I'm sure you have.
A power outage and non-boot is not a Solus thing at all---it's all PCs everywhere.
This reminds of windows days and having the Hiren Boot disk tools handy.

Because this is likely corrupt boot. Very rarely in my reading did I see where an outage (surge maybe) will destroy a HDD. It's usually the boot.
So take live CD and use gnome disks or gparted or a forum post and see if there's a problem in host HDD.

Sphor

brent

Thank you so much,
Yes, I did try to look around for a bit, but I didn't see things quite matching my situation, so I thought it would be best to add my question on the Forum just in case this happens to someone else who is as clueless as me.

I don't know what to say about it being a thing about all computers everywhere, because I did not unplug the battery while using the laptop, so it should not have been an unforeseen, total power outage;
...and the percentage did not reach 0%, though I know that the battery charge is just an approximation of what it's power is likely to be, mostly due to the battery getting older and other variables which makes it difficult to provide a precise timeline of when the battery will fail to provide enough power for keeping the device running.

Whenever my battery was dying on Windows, however, I was able to boot it the next time normally, without having to repair the boot partition.

Also, I believe I should've also mentioned that the laptop is dual-boot, and Windows boots well, hence the theory that it could be a "Solus thing".
Either way, I am not very techy, so I find it difficult to "Get my hands dirty" and sort the Boot partition myself, so I'll have to look around a bit to figure out how to do it.

All this being said, thank you for your reply!

brent

Sphor Either way, I am not very techy, so I find it difficult to "Get my hands dirty" and sort the Boot partition myself, so I'll have to look around a bit to figure out how to do it.

I understand. Repairing/rebuilding a boot partition is a tricky thing to do and easier said than done. And that's if I even diagnosed your problem right to begin with...
...but if you boot up the live usb you can easily get an idea if your hdd's health by opening a couple programs. Consult the board when you are ready. Someone will walk you through it. edit: browser will work in live usb
At the very least, it would be a self-diagnosis and confirmation.

Sphor

brent I confirm that the issue is not with the host drive,
I chrooted into the device as per the OS's documentation, updated everything, etc... no change, however.

I now theorize it may be due to the boot partition, although I got no errors initially.

Thing is, I do not know what to do now as I fear I might end up messing with my 2nd booting OS, and I wouldn't want Windows to break on that machine.

WetGeek

Sphor

I boot ONLY to Solus, but have VMs for both Windows 10 and Windows 11. No problems at all with any of them. Might be a better solution for you? If you ue Windows predomintly, you could also boot into Windows ONLY, and create a VM for Solus. Both Solus and Windows can create VirtualBox VMs. Just install VirtualBox on both. Either one would solve all of the dual boot issues.

brent

from what I can tell WetGeek 's vm suggestion is excellent. but that's a world I haven't dabbled in.

In the live CD you can use Disks or Gparted to confirm your boot was 512MB. It won't boot Solus if it's smaller than that.
Both programs have functions to "check" and separately "repair" the boot partition. Pressing 'check' will at least give you a health report. And Disks is friendlier than Gparted.
Chrooting is a brave task! You did it, though.

WetGeek

brent that's a world I haven't dabbled in

I still haven't given up on you. Just trying to remain tactful.

Robotmike2

AFAIK many systems try to perform a "suspend to disk" (hibernate) when battery is low, depends on settings and swap size. I guess it's not even broken, but tries to resume into a (firsthand) failed RAM image.
But I don't exactly know how to fix this, will also depend on the used boot loader. When in trouble I tend to randomly delete suspicious entries from whatever configuration files in the boot partition, but can't recommend that...