Pine A64 stuck in boot process - Printable Version

+- PINE64 (
+-- Forum: PINE A64(+) (
+--- Forum: General Discussion on PINE A64(+) (
+--- Thread: Pine A64 stuck in boot process (/showthread.php?tid=7486)

Pine A64 stuck in boot process - joey - 05-13-2019

Can anyone explain what's going on in this picture? My Pine has been running (Debian or Ubuntu, I can't remember which) flawlessly for about 2 years now, but recently it just stopped responding to network connections. I got my monitor hooked back up to it and reboot it, and this is what I am getting. The output from the console goes by too fast to see the top of the dump, and hitting shift+pg up doesn't scroll up when it hits this phase either. Curiously, it does not show the pine logo in the top left corner like normal. What is also strange is that it responds to pings once it it gets to this stage, but I can't SSH in since it's not done booting. Switching to another console (alt+f2,f3,etc) just leaves me at a blank screen. If I hit ctrl+alt+del when at this stage, it cleanly reboots, but gets to this stage again.

I pulled the SD card out and stuck it in another linux system and ran fsck on it to make sure the OS was ok, but the card is fine. I'm not sure what else to do at this point. Any pointers or suggestions will be appreciated. Thanks!
[Image: badpine.jpg]

RE: Pine A64 stuck in boot process - joey - 05-28-2019

I bought two new Pine A64 boards to see if it was a hardware issue, but the same thing happened with the new boards. I ended up having to just reinstall a fresh copy of Xenial onto a new card. Luckily, the old SD card was in perfect order, so I just mounted it via a USB adapter and was able to copy all of the configuration files for my minidlna server, as well as my cron jobs, and I've got it back up and running. I guess the old SD card just gave up the ghost for booting properly, even though the data was fully intact. It is kind of weird that it is missing the small Fat32 boot partition on the old card. I can't remember if that was always missing, or if that's a new thing. The new disk has one, so maybe that's what caused this mayhem. Any way I slice it, just reloading the OS seems to have resolved the problem.