HDD GURU FORUMS

I'm working on a monolith (in VNR) that's got quite a lot damaged blocks (0.5M of 8.8M), and unfortunately they are all spread out and not located in a single area. 6% damage doesn't sound much but as for now it's not possible to recover a single photo from it, not even with a carver. Been trying Re-reading for two days and some blocks can be read compared to before but it's awfully slow.

Is there anything I can do that will help the monolith give me its data? Will a decrease in speed increase chances of re-reading?

Want to swap for my 64GB sandisk ? - It has 27GB of read errors, Im about to give up trying with it.

Drop your voltage to around 2.8v and give it a bit of a warm up to around 110c.

Try setting RR for different blocks. Choose a few each time. Also read only blocks with data. A little warm/cold air can improve reading too.

What is the ID?

arvika wrote:What is the ID?

453EAAA27E

Try FE RR Sandisk v1. This chips usually can be corrected without problem.

Go to the configuration window and make sure, the flag “Sandisk/Toshiba VSC” is checked. You will find it below Protocol settings.

You have "Read Retry not found" - so you chose the wrong read retry - it has no right to correct your dump. VNR read retry for Sandisk are: RR8, RR9, RR10, RR11.

arvika wrote:Try FE RR Sandisk v1.

I have no idea what that means.

bos wrote:

arvika wrote:Try FE RR Sandisk v1.

I have no idea what that means.

He mean Flash Extractor and you have VNR.

Just do what I write, ignore other posts

If you right click on ECC - there's a "hidden" option - RR diag report.
Just run it, save file and send it to our Support team. We'll check whether RR works at all.

It seems RR-11 works quite well, but what I don't understand is that if I run "Reread dump" it says 489k dead blocks, but if I use "Reread data blocks" it says 128k dead blocks. That's quite a difference.

Rered dump works on the whole dump. Reread blocks with data as it says - only blocks with data based on XOR. That's why it is good to reread blocks with data only. Unless you use SLC blocks or any other that have translation tables.

So empty blocks that are dead won't affect File assembler, for example?

If that so then it's good since it means around 300k dead blocks are empty.

These are not only dead blocks. Might be never used ones too. Also blocks with FW and other. Also it doesn't mean that 300k blocks are empty. They may have file structures inside, SLC, cache etc.