0

I shutdown my RPI2 but didn't wait for a full shutdown. Now it wont boot.

I reformatted the SD-card, tried the RUN, connecting the two holes. But nothing Ethernet, neither ACT leds go on.

Did I break my RPI2?

  • What do you mean by connecting the two holes? – Steve Robillard Feb 15 '17 at 21:16
  • In Pi2 there are two holes named Run. I saw it could restart. But no luck – Rodrigo Feb 15 '17 at 23:46
  • 1
    they do restart but keeping them connected will result in the processor continually restarting. – Steve Robillard Feb 16 '17 at 2:02
1

It is unlikely you bricked your pi. Short of pulling the plug when the Pi was flashing its BIOS its pretty hard to kill one. It is more likely that when your pi lost power abruptly that something in the hardware configuration manager got a little confused. This happens from time to time.

Re-flashing your SD card is a good guess but not my default default solution.

First thing I do is to pull power cord and let the Pi cool off for a couple of minutes before I try again. Its also a good thing to double check to make sure the USB cable your using for power isn't frayed or otherwise worn. Swapping cables and/or power supplies here isn't a bad choice either if you have the extras lying around. Remember, with RPi's the shorter the USB power cord is, the better.

The next thing is to pull the network cable if its connected via Ethernet and see if it will boot without the network cable connected. I'm thinking this is where your problem is because you said the Ethernet port lights didn't come on. If this is the case, after a normal shutdown you should be able to plug your network back in and the Pi should boot normally.

Why would the Ethernet make a difference? Some Ethernet controllers and hubs support something called Power-over-Ethernet or PoE. Even if the hub or router does not offer PoE it might offer pass-through support for PoE. If your network cord has the extra pairs of wires inside, thats where PoE flows. 100baseT networking only uses two of the four pairs, and cheaper network cords might only provide those two pairs.

PoE is great for IoT projects but can be a pain in the neck for troubleshooting power issues because if your using a network cable that supports PoE and your using a router that supports PoE or PoE pass-through, you might be supplying some power to the Pi that way unintentionally. The Pi does not support PoE, so this would be like any other undesired voltage.

The Pi has a polyfuse to protect itself from this, but until the current reaches quiescence the polyfuse wont reset and your Pi won't boot.

If that doesn't work, we head into less common areas. Try a different power supply and USB cord next, if you didn't earlier. Its possible that with a different power supply the Pi will fire up and everything will reset during the boot sequence.

If that doesn't do the trick, pull the power and then pull the HDMI cable before plugging the power back in. HDMI can provide limited source current to a HDMI device (for HDMI plug-in hardware like Chromecast or Fire Stick) and like PoE, this can upset the power controller on your Pi too. If you use a display adapter or run headless you can skip this step.

If the unit doesn't have a display, or the display stays blank, how can you tell if the unit booted? Watch the green light next to the red power light. When power is applied to the Pi both red and green lights should come on. The green light should go off and start blinking or flashing as the Pi starts booting. The red power light might go back off and stay off if the power is less than optimal, but the Pi will boot as long as the green light shows activity.

If there isn't a display, how can I safely power it back down after it boots? If you boot to the command line this is relatively easy. Wait five minutes, plug in a keyboard, and carefully key in your login and password. Then type sudo halt and wait until the green light stops flashing.

If you boot into Pixel instead of the command line you have to watch the lights as above. Once the green light stops flashing or blinking and stays off for a few moments, you can kill the power.

If these blind methods make you nervous, you can go a little risky here and hot-plug the HDMI. Unlike a network cord with PoE, it is 'safe-enough' to do this to double check if your Pi is booting. Its not really good for the Pi, but in this edge case we can get away with it.

Still isn't booting? Next remove any hats, including a display module, and anything else connected to the pi like the camera module. Double check to make sure any extra pins or jumpers have been removed from the run holes or the GPIO, and that the Pi is resting on a non-conductive surface. Try again with Pi bare (wait to plug your keyboard in until after you see if it boots) and watch for the behavior of the red and green lights light above.

Then re-flash your Pi and try with just the HDMI or display adapter installed once you have your re-flashed card installed.

As a last ditch, try powering the Pi without a SD card installed. The Green light should stay on, even if the red light goes out. If neither the red or green lights come on, then its time to look into what options for warranty you may have, as its likely the Pi has some other fault. The good news such that it is, that the newer Pi 3's are out and just as inexpensive.

Good luck, and I hope this helps.

  • It's alive Just now I connected HDMI. And shows Kernel panic - Not syncing VFS – Rodrigo Feb 17 '17 at 11:26
  • @Rodrigo Thats probably a file system error. Often seen when the boot partition is full. Perhaps the easiest way to deal with it is to flash the card and start fresh. If you have a USB SD card reader and a different SD card to load Rasbian on, you can mount the old card to try and repair or recover. The method I point out [here][1] will work for this, after step 7, type df -H and it will show all the drives and space remaining. If the new small 52MB+- partition is full, thats your kernel panic. [1]: raspberrypi.stackexchange.com/questions/59078/… – Sandor Dosa Feb 17 '17 at 13:50
  • This is one awesome answer! I can't believe I'm the first to up-vote, much less accept :-( WTH people! @Rodrigo – shellter Oct 26 '17 at 14:23
0

I had an RPi3 fail this way when I used a power connector it didn't like. Try using another cable and power adapter.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.