[hafqa] [hafqa] [Bug 1204] MMC read-only/corruption bug persists...

[From: bugzilla-daemon at lists.maemo.org]

https://bugs.maemo.org/show_bug.cgi?id=1204


danramos at ix.netcom.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |danramos at ix.netcom.com




------- Comment #99 from danramos at ix.netcom.com  2007-09-19 12:31 GMT+3 -------
Wish to add myself to the list of people having SDHC corruption issues with two
A-Data 8GB Turbo-6 chips on my N800 with OS 2007 4.2007.26-8.  From the moment
I used them they both began getting corrupt in either slot at one point or
another and at the same time sometimes.  When I'd finally reformat them they'd
be okay for a good several days before showing at least SOME corruption. 
Tonight my external slot SDHC lost MOST of the files I had on there (close to
6gb of podcasts).  I'm rather furious as MOST of the various branded cards I've
ever used have had problems (except three of the four 2GB chips I've owned..
the one card was ruined so badly while inside the N800 that I couldn't even fix
it with a chip reader which usually does the job.)

I've been using an SDHC card reader to fsck it on my Linux box (and on rare
occasion had to rebuild an MBR with parted before reformatting).  I'm really
frustrated by the fact that I'd love this device except for the awful
experience with corruptions on SD cards where none of my other devices ever
experience these problems (my camera, my Palm Tungsten T5, my card readers,
etc.).  I've even purchased the Navicore kit and was happy to have the nav data
always available along with all the rest of my media with such high capacity
cards--but it's been very tenuous with the corruptions happening so often.

Please, please issue a fix soon!

Thanks


-- 
Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.