Third Party > Repairing and Upgrading Rockbox Capable Players

iriver H120 after CF mod: *PANIC* error dc_writeback_callback ()

<< < (3/5) > >>

entne:
Now I took the CF card out of the player. I borrowed another card reader and it could be connected to the pc without any trouble. Then I did a Full Pattern Write And Read Test with CheckFlash (first app from your link). I used the set value on access type "use temporary file" because I wasn't sure about the other options for NT-based systems only ("as logical drive" or "as physical device"). It passed without errors. Afterwards, I built the CF card into the player again, connected it to the pc (which took some time just as before) and repeated the test in CheckFlash (for testing via built-in CF adapter). It passed without errors.

I took the CF card out again and connected it via card reader to pc. Then I used HDD LLF Low Level Format Tool to fully format it. After that the app noted "remember to create new partitions". I just accessed the drive in windows and windows asked to format it - which I did with "cluster size" (I am using german Win 10 so I am not sure about the translation) set to standard size (initially at first use of the card I chose 16 which was the set value). Then the drive was accessible again and I copied over the stable rockbox build and some music files. I turned on the player and went to the database. Player asked to initialize because db was not ready. I confirmed and unfortunately it got stuck again with "searching... 0 found" and presented the error after a while, though it was slightly different than before:

*PANIC*
dc_writeback_callback ()
- Could not write sector
  32898 (error -2)

Next step trying new CF card and/or adapter (latter is much cheaper so that would be my idea at the moment)? Or any other idea I can try?

Bilgus:
Sorry to hear it, I find it odd that the sector failing has moved but maybe it is genuinely bad or maybe it is Rockbox,
maybe you could try older firmware this user says 3.9.1 works for his cf modded device

http://forums.rockbox.org/index.php/topic,52528.msg243012.html#msg243012

entne:
How could it be that after replacing the current build with 3.9.1 the booting screen still says it's running 3.14? I deleted the current build folder before I copied  the older release...

Bilgus:
probably just the bootloader version

what does System>Rockbox Info>Version show?

entne:

3.14!

I thought bootloader has a different version naming ("7pre4 or something").

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version