+- PINE64 (https://forum.pine64.org)
+-- Forum: Pinebook (https://forum.pine64.org/forumdisplay.php?fid=76)
+--- Forum: Linux on Pinebook (https://forum.pine64.org/forumdisplay.php?fid=79)
+--- Thread: Splash But No Login After Low Battery (/showthread.php?tid=5987)
Splash But No Login After Low Battery - robbiemacg - 04-19-2018
My battery was almost fully discharged yesterday. Today, after 2hours charge time, I get the Pinebook splash, a flicker, then nothing.
Any thoughts on how to recover form this? I'm in the process of prepping another SD to test the machine, but don't want to have to do a full re-install if I can avoid it. Can I access the update scripts from an SD boot and see if that brings things back to life?
*Interestingly Linux finger magic (Alt+SysRq with r, e, i, s, u, b) will still trigger a reboot from that blank screen, so there's some bit of OS in place to interact with…
RE: Splash But No Login After Low Battery - robbiemacg - 04-20-2018
So, '/home' was not mounting (my home directory is on a micro SD card) due to a bad block or a checksum error. I can't swear that it occurred when I tried to boot with a low battery or whatever, but it's possible. I've had discs fail in the past, and it doesn't usually look like a single bad block/number that's so easily fixed as this was.
'fsck.ext4 -vy [/path/to/card]' and a reboot, I'm back in business.
RE: Splash But No Login After Low Battery - calcmandan - 05-06-2018
How did you manage to get to a command prompt in this condition? I have the same problem, but it's been over a year since this happened so I don't recall the exact cause of this.
RE: Splash But No Login After Low Battery - robbiemacg - 05-17-2018
(05-06-2018, 06:39 PM)calcmandan Wrote: How did you manage to get to a command prompt in this condition? I have the same problem, but it's been over a year since this happened so I don't recall the exact cause of this.
I had to check/repair the card on a second machine.
Alternatively, I suppose I might have booted from a secondary card and either temporarily commented out the fstab line that points to the device on which /home is located... or reflashed the eMMC (all my settings being preserved on the card, I'd be back up and running minus a few apps once I set up the fstab again).