you cannot just do a hard shutdown you must use a shutdown now command
you always risk file system corruption if you do not

On 4/4/2018 8:24 AM, Tarmo Kuuse wrote:
> On Monday, 19 March 2018 23:55:04 UTC+2, Troy Weber wrote:
>
>     Hello!
>
>     I have an application running on the Beaglebone Black. It runs
>     from the eMMC because we need to mount a blank SD card and
>     occasionally store data or video on the external SD card. Here are
>     some details to jog ideas:
>
>       * using a Bealgebone black
>       * connected to a powered hub and running 2 led strips and 1 camera
>       * made a custom cape/shield that allows us to interface with
>           o an RGB button
>           o a 16x2 char lcd
>           o an optically isolated relay module
>       * the relay module runs a solenoid circuit (in which I'm
>         currently debugging the need for a flyback diode)
>       * the SD card is mounted using */etc/fstab* with the line
>         */dev/mmcblk0p1 /media/sd auto
>         auto,nofail,user,dmask=022,fmask=111 0 0*
>       * SD cards are inexpensive and found
>         here: 
> https://www.amazon.com/gp/product/B00WUCNGVQ/ref=oh_aui_search_detailpage?ie=UTF8&psc=1
>         
> <https://www.amazon.com/gp/product/B00WUCNGVQ/ref=oh_aui_search_detailpage?ie=UTF8&psc=1>
>
>     My application is writing files to the SD card only on certain
>     occasions during which the Beaglebone will not be hard-rebooted.
>     However, it will be hard-rebooted (and the application started by
>     systemd on next boot) as a means of shutting it down.
>
>     The problem is that I've recently began to discover issues with
>     the blank SD card on next boot after a hard reboot. For a short
>     time I can *touch* and write *vim* files on the card just fine.
>     Once I start up the node.js program, part way through it complains
>     about the SD card being read-only. From then on I cannot
>     *touch* or *vim* files anymore. So I reformat the card and copy
>     the configuration files back on. I've noticed that one of my
>     configuration files is chopped short.
>
>     Here are some things I've tried and intend to try:
>
>       * have tried
>           o removing the power to the hub which seemed to be
>             back-powering the BBB (still fails on reboot)
>           o stopping the program that writes files entirely (still
>             fails on reboot)
>       * intend to try
>           o writing the configuration files elsewhere (on the eMMC for
>             example)
>           o better SD cards
>
>     In the meantime, any ideas?
>
>
> What's the file system on the SD card? FAT? ext4?
>
> --
> Tarmo
> -- 
> 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 [email protected]
> <mailto:[email protected]>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/ea6a9f55-220d-40c0-8781-5dfffee87178%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/ea6a9f55-220d-40c0-8781-5dfffee87178%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/46947563-9e92-ca7e-a0ce-094b6e449db2%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to