Will Not Boot after unplugging Retropie 3.7

andrew_tn

@iconrumble
I installed raspian to see if the same thing would happen after unplugging. Did the shutdown option, then waited for the lights to stop blinking (30 secs) and unplugged. After plugging back in it booted back up, but went into recovery mode, then rebooted and booted right into the raspian os just fine.

Also, I dont know if this has to do with anything, but I am using a hdmi to vga connector in my setup.

opensourcefan

I first had this problem and still have it after updating to the newest kernel (4.4). I believe it's a bug but don't know where to report it.

If I do a hard shutdown by killing the power it'll boot up just fine but when shutdown via the menu it hangs on start up. All of this started after the original kernel update to fix the PS3 bluetooth freeze issue. I did not do the full update which came out a few days later.

andrew_tn

would reverting back to a previous retropie version fix this situation? im just trying to play pre n64 games.

opensourcefan

@andrew_tn

I don't know if it would or not. In my case having the PS3 controller not freezing is more important so I never explored reverting back. Sooner or later though I'm going to have a corrupt card I guess because I've been doing hard shutdowns for a while now.

andrew_tn

Anyone else have any suggestions on fixing this issue? Its driving me crazy!

andrew_tn

I also tried quitting emulation station and doing "sudo shutdown -h now" and it still doesn't boot up after plugging in. Does no one else have this problem?

opensourcefan

Weird huh, it makes me think it's just us or no one is shutting their systems down. Maybe everyone is doing hard shutdowns without caring, that's me right now.

andrew_tn

Well, after much trying of different things, I finally figured out a way to get it to work.

I installed raspbian and just use that to start emulation station. When I want to unplug my unit i quit emulationstation, and go to the prompt and do a 'shutdown -h now' and it seems to do well, no corruption yet, like before.

Not sure why this saves my card but it does.

Hope this helps someone with the same issue.

opensourcefan

Can someone (using the latest update) at least report that the shutdown is working for them?

mediamogul

@opensourcefan

Shutdown works fine for me, although it takes close to a full five minutes with the sheer volume of games I have loaded. Are you able to ssh into the pi while it's hanging? Also andrew_tn, one thing I notice from your description of the events is that you're using activity lights to exclusively judge when the device has completely shutdown. Are you not able to witness the shutdown routine from your monitor? Shutdown times can vary wildly depending on a few factors, but waiting "a whole minute" might not be enough time and sounds a lot like guesswork.

Edit: Nevermind, you meant "a whole minute" after you see the "no hdmi input" message from your monitor.

opensourcefan

@mediamogul

Thanks for the reply, much appreciated. My screen goes dark within 5 seconds of using the shutdown. I watch my green led flash for a bit then it goes out and only leaves the red on obviously. Prior to my kernel update it would shut down with the green light on solid.

Is there another way to tell if it's shut down properly with the screen dark? Upon its hanging the screen stays black and the green led just pulses evenly.

fourlights

I'm getting this on a pi 2 and pi3, with 3 different memory cards and on 3.6 and 3.7 (just freshly downloaded both images). Similarly, I've been waiting 5 minutes+ after the display switches off before unplugging the power. (I've tried multiple power adapters too).

Reboots work fine, but a shutdown from anywhere (cli or emulationstation) bricks it. Only way to fix is to re-image the card. Have tested each device independantly with raspbian on the same cards and they work fine so its not either the pi or the cards. Don't get any display so cant see if its hanging at a particular boot phase or not, but I'd speculate and say its not getting to the OS.

opensourcefan

~~I've reported this issue, anyone having the same issue please go and add whatever information you have to help those in the know fix it.~~

opensourcefan

Fixed:

Okay so in my case I had just upgraded the kernel to 4.4, this was before the whole dist-upgrade was out. Today I did the full dist-upgrade, downgraded my bluetooth to 1.0 and shutdown appears to be working again.

In order this is what I did:

sudo apt-get update && sudo apt-get dist-upgrade
sudo reboot
wget http://archive.raspberrypi.org/debian/pool/main/p/pi-bluetooth/pi-bluetooth_0.1.0_armhf.deb
sudo dpkg -i pi-bluetooth_0.1.0_armhf.deb
sudo reboot

After that the shutdown worked just fine.

mediamogul

Nice job!