Home | Download | Purchase | Support

DIY DataRecovery.nl


 Logfile too large to paste into your forum message?

SUBMIT LOGFILE HERE
Welcome to the DIY DataRecovery Support Forum!

The Forum is monitored working days from 9.00 AM - 5.00 PM (Central European Time).

IMPORTANT! This forum is no longer monitored and is read-only. Visit our new forum!
 
General Forum
Start a New Topic 
Author
Comment
Error: Unable to translate VCN 00000002 to LCN, bad runlist?

Hi,

It i was able to see the root and recover 450+MB of content. Then i had to reboot my machine. Now when i run iRecover and try to retrieve new areas of the file structure, or, even the original ones that worked, it keeps getting "hung" on files and i see many many of these "Error: Unable to translate VCN 00000002 to LCN, bad runlist?" error messages in the log file.

Has the drive finally given up?

Thanks in advance.

Product you are using: iRecover

Operating system / Service Pack: Windows 2003

Size of subject harddisk: 30GB

Re: Error: Unable to translate VCN 00000002 to LCN, bad runlist?

One thing i forgot was this occurs after i've restored the state from a .irs file and attempt to recover data.

I'm trying a fresh disk scan now.

Product you are using: iRecover

Operating system / Service Pack: Windows 2003

Size of subject harddisk: 30GB

Re: Error: Unable to translate VCN 00000002 to LCN, bad runlist?

I've found that if i do the scan from scratch (i.e. no restore state) it works fine.

Product you are using: iRecover

Operating system / Service Pack: Windows 2003

Size of subject harddisk: 30GB

Re: Error: Unable to translate VCN 00000002 to LCN, bad runlist?

Hello,

Good you didn't wait for us ;-). When we can we do visit the forum in the weekends, but this weekend we didn't.

It could also have helped to load statefile 3 rather than the last one, or when loading the 4th to go back one step.

--
Kind regards,
Joep