Log in

No account? Create an account
'Twas brillig, and the slithy toves did gyre and gimble in the wabe [entries|archive|friends|userinfo]

[ website | Beware the Jabberwock... ]
[ deviantArt | the-boggyb ]
[ FanFiction | Torkell ]
[ Tumblr | torkellr ]

[Random links| BBC news | Vulture Central | Slashdot | Dangerous Prototypes | LWN | Raspberry Pi]
[Fellow blogs| a Half Empty Glass | the Broken Cube | The Music Jungle | Please remove your feet | A letter from home]
[Other haunts| Un4seen Developments | Jazz 2 Online | EmuTalk.net | Feng's shui]

[Sunday 1st July 2012 at 11:29 am]

[Feeling |pissed offpissed off]

Usually, when a disk or memory card has bad sectors attempting to read those sectors returns an error. Y'know, so that whatever was trying to read it actually knows that that particular bit of data can't be read and so can do something sensible.

Unless it's a crappy microSD card, in which case attempting to read a bad sector will cause the card to stop responding. Actually that's not quite what happens - it does return an error, but then doesn't respond to any further reads. Okay, that's mildly annoying but I can deal with it.

Unless it's a really crappy microSD card, in which case most of the time it won't bother with any kind of error but will just return garbage. And not consistent garbage, but different garbage whenever you try to read that sector.

Unless it's a really really crappy microSD card, in which case it's not just one bad sector, but about 100MB that's now effectively gone. Except because the card doesn't bother with actual errors, you don't know which 100MB is gone.
Link | Previous Entry | Share | Next Entry[ Penny for your thoughts? ]