Has anybody bricked a Z because of...

[pHluid]

Out of curiousity, I\'m wondering if any of you guys have ever managed to brick your Z due to excessive internal flash writes? We all know it COULD happen, but has anybody ever actually done it?

I\'m a bleeding edge OZ user who flashes quite a bit, and having burned out an SD card already it made me feel a bit uncomfortable... I think from now on I\'m moving all the often-written-to directories onto SD (/opt, /home, /root - any others I should move?) ... that should at least cut down on it.

[tumnus]

See this Zaurus DevNet thread here: http://www.zaurus.com/dev/board/index.php?...wtopic=7239&hl=

[pHluid]

Good stuff, but it doesn\'t definitevely rule it out. That crazy super high limit is supposed to apply to SD cards, too, and I\'ve already managed to trash one of those (And nah, I wasn\'t doing anything silly like swapping to it)

All in all probably just a defective card. But the question still remains.

[VeeDubb]

Usualy what burns out on SD cards is the controller in the card and not the actual memory.  THat is probably not an issue with the rom in the Z.

[Anonymous]

Interesting... What symptoms would a burned out controller exhibit?

On the SD card in question, I\'m unable to format it... pauses for an insanely long time across particular inodes under mkfs.ext2 ... I would assume that to be from block burnout on the card...?

[VeeDubb]

In my experience it has basicaly the same simptoms.  The only reason I know this is because I have talked to people who know far more than I do who have disected flash memory cards after death and found it was other components such as parts of the controller that failed.  Typicaly it\'s the same symptoms.  Inability to format, garbled data, the usual.