I have not, and I've been running my beaglebone Black since release last
year(on, and off, with uptimes of over months at a time. ).

The difference between you and I ? Most likely that I am running my rootfs
from an NFS share over our network.

So, with this in mind, I would think you need to investigate running read
only, and / or you need to stop logging to the sd media you're using.


On Thu, Jun 12, 2014 at 7:06 AM, <talam...@gmail.com> wrote:

> Hi everyone,
>
> I've been using the BeagleBone Black for a while now. I got my apps
> running just fine for like *2-3 months* straight, not a single problem.
>
> OS : Debian Wheezy installed on Samsung 4GB µSD card.
> Cross compilation platform : ELDK (armv7-hf)
>
> I've tested my apps on *different brands of SD Cards* (Kingston, samsung,
> sandisk ...) and have killed several *Kingston* cards in a matter of
> days. By killing, I mean the BeagleBone wasn't booting on them anymore and
> they were no longer mounted when plugged via a USB-Card-reader. I had this
> kind of dmesg output (the [...] here means a lot of the same 7 lines in a
> loop):
>
> [626903.528266] sd 11:0:0:0: [sdd] Device not ready
> [626903.528268] sd 11:0:0:0: [sdd]  Result: hostbyte=DID_OK
> driverbyte=DRIVER_SENSE
> [626903.528272] sd 11:0:0:0: [sdd]  Sense Key : Not Ready [current]
> [626903.528275] sd 11:0:0:0: [sdd]  Add. Sense: Medium not present
> [626903.528279] sd 11:0:0:0: [sdd] CDB: Read(10): 28 00 00 00 00 00 00 00
> 08 00
> [626903.528287] end_request: I/O error, dev sdd, sector 0
> [626903.528290] Buffer I/O error on device sdd, logical block 0
> [626903.530266] sd 11:0:0:0: [sdd] Device not ready
> [626903.530269] sd 11:0:0:0: [sdd]  Result: hostbyte=DID_OK
> driverbyte=DRIVER_SENSE
> [626903.530272] sd 11:0:0:0: [sdd]  Sense Key : Not Ready [current]
> [626903.530275] sd 11:0:0:0: [sdd]  Add. Sense: Medium not present
> [626903.530279] sd 11:0:0:0: [sdd] CDB: Read(10): 28 00 00 00 00 00 00 00
> 08 00
> [626903.530287] end_request: I/O error, dev sdd, sector 0
> [626903.530290] Buffer I/O error on device sdd, logical block 0
> [626903.532391] sd 11:0:0:0: [sdd] Device not ready
> [626903.532393] sd 11:0:0:0: [sdd]  Result: hostbyte=DID_OK
> driverbyte=DRIVER_SENSE
> [626903.532396] sd 11:0:0:0: [sdd]  Sense Key : Not Ready [current]
> [626903.532400] sd 11:0:0:0: [sdd]  Add. Sense: Medium not present
> [626903.532404] sd 11:0:0:0: [sdd] CDB: Read(10): 28 00 00 00 00 08 00 00
> 08 00
> [626903.532412] end_request: I/O error, dev sdd, sector 8
> [...]
> [626903.812724] sd 11:0:0:0: [sdd] Device not ready
> [626903.812725] sd 11:0:0:0: [sdd]  Result: hostbyte=DID_OK
> driverbyte=DRIVER_SENSE
> [626903.812728] sd 11:0:0:0: [sdd]  Sense Key : Not Ready [current]
> [626903.812731] sd 11:0:0:0: [sdd]  Add. Sense: Medium not present
> [626903.812734] sd 11:0:0:0: [sdd] CDB: Read(10): 28 00 00 00 00 00 00 00
> 08 00
> [626903.812740] end_request: I/O error, dev sdd, sector 0
> [626903.814725] sd 11:0:0:0: [sdd] Device not ready
> [626903.814728] sd 11:0:0:0: [sdd]  Result: hostbyte=DID_OK
> driverbyte=DRIVER_SENSE
> [626903.814731] sd 11:0:0:0: [sdd]  Sense Key : Not Ready [current]
> [626903.814735] sd 11:0:0:0: [sdd]  Add. Sense: Medium not present
> [626903.814739] sd 11:0:0:0: [sdd] CDB: Read(10): 28 00 00 00 00 00 00 00
> 08 00
> [626903.814747] end_request: I/O error, dev sdd, sector 0
> [626903.820536] sdd: detected capacity change from 3947888640 to 0
>
>
> That's why I chose to use *Samsung* sd cards instead. Everything was fine
> for *2-3 whole months*, but now I had one of my systems getting the *exact
> same symptoms* as when using the Kingston cards.
>
> Did anyone experience this kind of problem using his beagle bone so far ?
> Does anyone have an idea of something that could damage the SD card so
> much which is or isn't directly related to the use of a beagle bone black
> (Heat, compulsive logging, ...) ?
> Can anyone suggest a brand that has solid and enduring SD Cards for an app
> that is logging quite regularly ?
>
> Thank you for your time,
> FT
>
> --
> 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.
>

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

Reply via email to