Rockbox Technical Forums

Support and General Use => Hardware => Topic started by: crypt@ on January 23, 2009, 11:23:11 AM

Title: Repeatable Steps To Corrupt File System On CF
Post by: crypt@ on January 23, 2009, 11:23:11 AM
I'm using 7pre4 bootloader with SVN 19817 compiled with RTC, voice and multi-volume. The CF card is 32GB 233x Pretec, model CFS232G.

I'm using multi-volume to limit file corruption to the smaller partition assigned for .rockbox.

Though I've been having similar problems since moving to CF, I have not been able to pinpoint the sequence before. Now using the following steps, I have "successfully and repeatedly" corrupt the file system.

1. The player is shutdown by reaching the idle poweroff time
2. Hold switch is toggled on
3. Power on the player, and wait for it to shutdown by default
4. Leave hold switch on, and power it on again and wait for the default shutdown
5. Switch hold switch to off, and power up
6. File system on the 1st partition becomes corrupted

At times the file system can be corrupted when the player is shutdown and turned back on with hold switch on just once. But this is quite random.

I notice that when the player shutdown due to low battery, it automatically goes into the bootloader menu on next startup. But may be that is just because the voltage is too low and under such circumstance will default to boot into the bootloader menu. This will go some way to explain the previous instances on file corruptions after power out.

I'm guessing it is bootloader related.

I would rather not come to the conclusion/solution of taking the 1.8" HD out of its snug external enclosure to return it to the H140. :(
Title: Re: Repeatable Steps To Corrupt File System On CF
Post by: Llorean on January 23, 2009, 01:42:18 PM
Can this be reproduced with the official bootloader?
Title: Re: Repeatable Steps To Corrupt File System On CF
Post by: crypt@ on January 24, 2009, 09:26:30 AM
I'm afraid that's going to be difficult, as the Pretec looks to be well and truly toasted this time around.

I cannot delete partition(s), nor format the file system(s). Whenever a write attempt is made, it reports the CF is in write protected mode. This is both through the bootloader, Rockbox as well as 2 different readers.

I'm hoping somewhere in the WWW, there is a post of someone with similar problem and found a solution that does not involving ditching the card into a landfill...
Title: Re: Repeatable Steps To Corrupt File System On CF
Post by: Llorean on January 24, 2009, 01:22:01 PM
If the card is permanently down, are you sure it wasn't just bad and failing?
Title: Re: Repeatable Steps To Corrupt File System On CF
Post by: crypt@ on January 25, 2009, 06:08:16 AM
Found some comments about using 98SE version of fdisk, and with hope held high I followed as instructed. Unfortunately no luck.

I'm trying support from both seller and Pretec. I hope I'll receive some positive response(s).

Hopefully it is just a faulty card and not the Pretec range. I've noted a number of other users have installed 233x 16GB and 64GB Pretec without reporting any problems.

------------- Update

Whilst waiting for RMA on the Pretec, I tried out a "dodgy" RiDATA 512MB CF card. This RiDATA is quite temperamental, it generally takes a few insertion before being recognised  by the reader.

After using 98SE to repartition the card I tried the steps in the 1st post to see if file corruption would happen.

No, it's all good. So this points, as suggested in previous post, to a faulty Pretec CF.

I did notice something unusual though. When plugged into USB and powered on with hold switched on, with 7pre4 the H140 would boot to "bootloader usb mode." Whereas with 6, it switched off after displaying the "hold switch is on" message.