• 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.

[Cubox/Hummingb.1] Suddenly no ssh conn., no video output but seems to boot
1 1

10 posts in this topic

Recommended Posts

Until yesterday my humminboard 1 i2ex worked without any flaws.

Now after a restart I cannot access it via ssh anymore.

I thought the Ip adress my have changed somehow cause I also restarted my router but it under active clients in router webif either.

Also no video output via hdmi...guess that's normal since it's a debian server image.

What I can see is the uboot showing up the count down, just quick, I could read ..wrong image format..and something with source.. that's it.

Then screen turns black.

I have the rootfs on msata ssd and if I remember correctly I removed all other unnecessary files from micro sd card many month ago.

 

Is there any keyboard combination to get output of a console or something via hdmi?

 

 

 

Share this post


Link to post
Share on other sites

I don't know how to troubleshoot this, I connected a wired keyboard and at boot where it says "Hit any key to stop autoboot" it does not recognize any key presses from my keyboard.

 

Share this post


Link to post
Share on other sites
17 hours ago, martinayotte said:

Do you have any USB-Serial dongle connected to debug ?

No, I don't really know how this works.. Would I need an adapter from usb to serial? And then...to pc?...

 

Could I get output by adding console=tty1 to the armbianEnv.txt file?

I didn't find time 'til now, I'm gonna look into it this weekend.

I just hope it's no kernel panic :unsure: ..had these before using archlinux on that thing.

Share this post


Link to post
Share on other sites

@trohn_javolta What you'd need is re USB-Serial is basically this. If you're in the US, and prefer Adafruit, grab the serial to TTL cable they sell, but otherwise, something like the one I linked should work.  There will be some pins on the board somewhere (not familiar with that particular board) that you plug three of the wires in to be able to interact with the board via a serial console (so no display, keyboard, etc needed on the board itself).

Share this post


Link to post
Share on other sites

SD card failure is possible in this case since even you have installed a system to SSD, u-boot, boot script and kernel remain on / are loaded from SD card. With each update, there are writings to SD card. Enough to kill it after a certain time. Recent Hummbingboards 2 (rev. 1.4 +) support booting directly from eMMC/m2 SATA/USB.

 

Without seeing logs, we can only guess.

Share this post


Link to post
Share on other sites
2 hours ago, Igor said:

SD card failure is possible in this case since even you have installed a system to SSD, u-boot, boot script and kernel remain on / are loaded from SD card. With each update, there are writings to SD card. Enough to kill it after a certain time. Recent Hummbingboards 2 (rev. 1.4 +) support booting directly from eMMC/m2 SATA/USB.

 

Without seeing logs, we can only guess.

Yeah..I also could prepare another SD Card and copy the armbianEnv.txt from the old SD Card to have it "point to" the msata ssd.

Do you think that would work?... This way I would be able to determine if its a SD card failure.

Share this post


Link to post
Share on other sites
51 minutes ago, trohn_javolta said:

Yeah..I also could prepare another SD Card and copy the armbianEnv.txt from the old SD Card to have it "point to" the msata ssd.

Do you think that would work?... This way I would be able to determine if its a SD card failure.


Yes, it should work. Just double check/compare boot.cmd and armbianEnv.txt to make sure you adjusted everything.

Share this post


Link to post
Share on other sites
7 hours ago, Igor said:


Yes, it should work. Just double check/compare boot.cmd and armbianEnv.txt to make sure you adjusted everything.

Well... booting with new sd card i get this output:

 

IMG_20170804_201652.thumb.jpg.27df64b704c4fa889e9bd3b091d8b039.jpg

 

I checked the UUID, it's correct.

Next I ran armbian from sd card, msata ssd is still connected, and blkid does not show me anything:

 

 

 

 

 

IMG_20170804_203928.thumb.jpg.249392c0a4557cedc53ed55041d08be3.jpg

 

Hmm.. maybe the ssd got messed up somehow? Now I'm thinking of hooking the ssd up to my pc and run fsck, does anyone have a better idea?

Share this post


Link to post
Share on other sites

:( The msata ssd is not recognized at all anymore.. I also put it in my sata enclosure and tried it on my pc...nothing, not showing up. My last hope is the application testdisk.

Good thing, the sata-nand install script didn't work when I started to use armbian, so I pretty much set everything up on sd card. Also good thing that the script didn't delete stuff on my sd card afterwards so now I only have minor things missing.

 

Besides that once again I did not backup my stuff...which was stupid :(

 

I once used an application called rsnapshot that can make scheduled backups using rsync. It was a bit of work to set it up, maybe this could be included in the softy area in the armbian-config script sometime in the future...would be great... Like with some predifined setting: choose place to backup and done.

 

Can I close this thread somehow? Since it has nothing to do with armbian itself, this is a fantastic and rock solid distribution! 

 

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

1 1

  • 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.