That would be my guess. Yes, making it read only will help. Or attach a battery that can keep it powered up until shutdown can occur, and have the kernel shut it down. A lot of discussion in the forum on this topic.
Gerald On Wed, Feb 3, 2016 at 1:17 PM, <cjacu...@gmail.com> wrote: > So you are implying this is a corrupt filesystem issue? > > I won't be able to guarantee power failures won't occur during runtime for > this application, but if this is a corruption issue I don't have a problem > making the root partition read-only. > > Chris > > On Wednesday, February 3, 2016 at 2:09:20 PM UTC-5, Gerald wrote: >> >> Shutdown Linux before powering down. >> >> Gerald >> >> On Wed, Feb 3, 2016 at 1:04 PM, <cjac...@gmail.com> wrote: >> >>> Also the u-boot messages seem mangled. Not sure what would cause that -- >>> if it's a problem with my serial connection I would expect to see further >>> mangling once the kernel starts to boot, and on the initramfs prompt, but >>> that all seems intact. >>> >>> >>> On Wednesday, February 3, 2016 at 2:01:09 PM UTC-5, cjac...@gmail.com >>> wrote: >>>> >>>> Hi, >>>> >>>> I'm currently diagnosing a Beaglebone Black (A6A) failure. It's been >>>> running for a few months at about 20% cpu load on average. Yesterday I was >>>> looking into some intermittent ethernet issues (may be unrelated to this >>>> issue) and, after power cycling it, I was not able to communicate with it >>>> at all (not via ethernet over network, not via ethernet directly, and not >>>> via the onboard USB ethernet connection). The heartbeat light still >>>> flashes. >>>> >>>> The microHDMI port does not show anything on the screen (but looks like >>>> it does have a signal). >>>> >>>> I attached the serial port output. It seems to point to eMMC issues. Do >>>> these error messages indicate a hardware failure or could it just be a >>>> corrupt filesystem? I have not yet tried to flash the eMMC in order to keep >>>> it in its current state. >>>> >>>> Thanks, anyone who can provide insight, >>>> >>>> Chris C >>>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "BeagleBoard" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to beagleboard...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Gerald >> >> ger...@beagleboard.org >> http://beagleboard.org/ >> > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Gerald ger...@beagleboard.org http://beagleboard.org/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
