HELP! - I can't access my BBB any more.

My BBB was running debian jessie and i could access it over USB and Ethernet. Then, after one power off/power on it stopped booting from eMMC. To be exact I stoped been able too access it over both USB and Ethernet. I can still boot the board from SD and access the bard. eMMC boot though seems never finishes. I can see leds blinking in a normal boot sequence and then they end up with one led blinking for ever.
If i boot from SD i can access eMMC file system (rootfs) and my /etc/network/interface on eMMC looks normal. I do not know of any other way to read a boot log on eMMC or anything to help me to understand the issue.
Of course i could re-flash eMMC but then i will never know what happen :frowning: Any help/ideas are greatly appreciated. Thanks!

when you shutdown your bone did you just pull the plug or use the
shutdown now -h command then remove power ?

No. I am developing some software to run as a part of an automation project, so expect the board to be tolerant to the power loss. So i just pulled the pug out - no shutdown -h.
What could break and what is a way to diagnose it?

"expect", well the board isn't designed for that application...

If your just going to yank power with the BBB, "expect" both software
and hardware failures* (documented in the SRM)..


If you want a board that can be unplugged with no damage better look
Or do what i have done and design around that limitation.

ME and a software buddy have a nice watchdog timer powered from the BBB
battery holds up the BBB till it shuts down then removes power
draws 400uA from the battery while waiting for the power to be reapplied.

So, in a pinch, and if you have physical access to the board. You can use
a LiPO battery, connected to the PMIC battery test points( ask an EE if you
need specifics ), then install the debian package acpid. Then everything
should be fine. e.g. the board will power down cleanly. However, the PMIC
will still be supplying a bit of power from the battery. So if you need it
shutdown for an extended time period. You'll need to disconnect the battery.

As for remotely installed systems. You'll have to design a watchdog / power
management system to disconnect the battery, and reset the processor when
power is reapplied. This is why in Jason's post yesterday, or the day
before. I mentioned I like to see a proper UPS cape with good power
management features built in. The beaglebone as it is is what I'd consider
a very good board, but to cut costs, when designed. Several things were
left out of the board. So instead of paying $100 + per board, we pay ~$50
per board, and design in features we need for our own situations. A fair
trade, but something we need to be aware of.