• Before reporting problems with your board running Armbian, check the following:

    • 1. Check power supply, check SD card and check other people experiences   06/23/17

      Power supply issues are one of the three biggest issues you'll face when starting with Single Board Computers (SBCs). SD card issues, whether fake or faulty, are another and issues resulting from poor board design is the other common issues you can encounter.   Power supply issues can be tricky. You might have a noisy power supply that works with one board because it has extra filtering, but won't work with another. Or you're using that cheap phone charger because your board has a microUSB connector, and it is either erratic, or doesn't start up, or even becomes the cause of some SD card issues.    Some tips to avoid the most common causes of problems reported:   Don't power via micro USB  - unless you have optimised your setup for low power requirements. Micro USB is great for mobile phones because they are simply charging a battery. It's bad for SBCs. Yes, it does work for a lot of people, but it also causes more problems and headaches over time than it is worth, unless you know exactly what you are doing. If you have a barrel jack power connector on your SBC, use it instead! If there is an option for powering via header connections, use that option!
        Don't use mobile phone chargers. They might be convenient and cheap, but this is because they are meant for charging phones, not powering your SBC which has particular power requirements.
        When you are evaluating a power supply, make sure you run some stress tests on your system to ensure that it will not cause issues down the path.   (Micro) SD card issues can be sneaky. They might appear right at the start causing strange boot and login errors, or they might cause problems over time. It is best to run a test on any new SD card you use, to ensure that it really is what it is, and to ensure that isn't faulty. Armbian provides you a simple way to do this   --   armbianmonitor -c /path/to/device/to/test  
    • 2. Make sure to collect and provide all necessary information   06/24/17

      We can only help if you provide quality information for us to work with. All stable images from the download section are tested, most stable upgrades are tested and we have tens of thousands of users. Even with regular and extensive testings, bugs sometimes do slip through. This is a voluntary support service and is unrelated to board makers, and is not obligated to provide you any answers. Repeated asking the same questions because you're not happy with the answers will result in you being ignored.

      Before you post a question, use the forum search as someone else might have already had the same problem and resolved it. And make sure you've read the Armbian documentation. If you still haven't found an answer, make sure you include the following in your post:   1. Logs when you can boot the board: armbianmonitor -u (paste URL to your forum post)   2. If your board does not boot, provide a log from serial console or at least make a picture, where it stops.   3. Describe the problem the best you can and provide all necessary info that we can reproduce the problem. We are not clairvoyant or mind readers. Please describe your setup as best as possible so we know what your operating environment is like.     We will not help in cases you are not using stable official Armbian builds, you have a problem with 3rd party hardware or reported problem would not be able to reproduced.

Bananapi pro bricked
0

8 posts in this topic

Recommended Posts

Hello,

 

I run Debian/Jessie on a bananapi pro.

 

The board suddenly stopped working completely.

 

When I plug the power supply, the red led shows up (not blinking) and nothing more,  no sign of activity at all, like on screen (hdmi).

 

It is very surprising as it has been running very well for two years now, with a 5V/3A power supply and a sandisk SD card (like those advised).

 

I checked that the sd card runs well on my laptop, the filesystem was not broken and no sign of corruption so far, especially in the /boot directory,

no changes made lastly in this directory : latest modification dater are a few months ago.

 

EDIT: I decided to completely reinstall debian/jessie on the sdcard, following the guidelines, checking the image and burning integrity. Same symptoms.

 

I also tried to boot with two other power supplies with only the board, nothing connected on usb or sata ports, no sign of activity at all except the red led.

 

I sometimes had troubles with debian updates, but in this case the hdmi screen is working and I can debug.

Also, I looked into the system logs (on the sd card), no sign of dysfunctioning at all, I just now more or less the last time it booted properly.

 

The AC power supply is itself plugged on a lightning protector socket.

 

So I doubt it is the power supply or the sdcard in itself that is causing the issue.

 

The only change I made lastly is to plug a 2.5" hard drive (wd red) on one usb port, in addition to the one plugged on the sata port.

 

Could this be the cause ?

 

Thanks in advance for your help

 

Regards

 

Share this post


Link to post
Share on other sites
8 minutes ago, deb2016 said:

So I doubt it is the power supply or the sdcard in itself that is causing the issue.

1


I have plenty of top quality dead SD cards around. Trying with another SD card is the first step.

Share this post


Link to post
Share on other sites

Thanks for your fas t answeer,

 

That is the next point I want to test, another sd card.

 

But do you mean it can be dead for the board and "alive" for my laptop ? Indeed, I was able to burn a new image on the sdcard with my laptop.

Share this post


Link to post
Share on other sites

Same happened to me with the original Raspberry Pi Model B few months ago. I thrashed it, at was clear it was hardware failure and there was nothing obviously damaged (burnt, broken or bad looking).

Enviado desde mi Jolla mediante Tapatalk

Share this post


Link to post
Share on other sites

I fear also this,

 

I wonder if plugging two hard drives (one on sata and one on usb) could have caused a hardware damage,

especially at boot time when hard drives ask a lot of power ... that would have overwhelmed the board capacity.

 

Nevetheless I do not want to throw it away before being sure it is not just a sdcard issue.

Share this post


Link to post
Share on other sites

The banana pi has absolutely no protection between the PMIC and the USB port -> if you plug a peripheral that use more current that the PMIC can provide you get magic smoke

 

I don't know if the pro is the same

Share this post


Link to post
Share on other sites

I tried again with a new power supply and a new sd card. Same issue.

 

I cannot access the serial debug output (ttl to usb), so I think I am about to consider the board completely lost.

Naguissa likes this

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

0

  • Support the project

    We need your help to stay focused on the project.

    Choose the amount and currency you would like to donate in below.