Later it goes back and splits those areas up into smaller zones and tries to re-read any good sectors between the bads.Ī better extesion would be. So you've actually rescued very very little so far.ĭdrescue first skipps large blocks of sectors on an error. Later in the scraping phase it'll try to read more data in those areas. The "non-tried" includes the skipped areas before the 14Gb mark where it's currently trying. A bonafide lab will have tools/methods to fix and stabilize the drive but there isn't much you can DIY (thus the suggestion of pro help for important data). The drive likely has a firmware malfunction and/or weak read/write heads making it get these constant errors. Don't do that or you'll be re-reading already read sectors over and over. Your naming it as "forwardrun" suggests you plan to use another log for the reverse run. The scraping only happens AFTER it's done the initial pass, and you want that to happen to maximize how much data you get.Īlso, you want to use a single log file the entire time as this is effectively your good/bad sector logging. Also, you don't need either the -f (which you'd need if you were writing to a drive rather than an image file), or the -n which skips the scraping phase at the end after the initial pass. It shouldn't be at the end but rather right after the ddrescue command. Naming it as an ISO (which it isn't) might later confuse other software. Now, assuming this is just some pirated movie collection and you don't plan to pay for recovery, there's a lot wrong with your process.įirst off, it's not an ISO file so the extension should more properly be. This is the first time i am doing such things, so please bear with me.įirst off, as everyone else is saying, if this is important data STOP and go to a pro. I still have time it seems, at the current rate this run will not be finished for the next 1 day and 18 hours. How should I proceed as soon as run of ddrescue is done? Can i try to improve the image with more data? I read a lot about ddrescue commands, but I am not really sure where to go from here. Is that recommended if i want to run data recovery software later on? I know i could just save the copy directly into an own partition on my target drive, but i guess saving to an image is better? What are the non-trimmed? These are at 9000kB so far. Im not sure I understand correctly, but shouldnt the ipos + the non-tried match the size of the drive (e.g. I said the ipos is 140000MB, but the non-tried are 157000MB. Am i correct? Is this normal? Can i improve this? In my understanding this means that ddrescue already tried to access 14GB worth of sectors but could only recover 2GB from them. My average read rate is 515 kB/s, im at 14000MB ipos and only 2800MB rescued. Often the drive cuts out, it gets lost from /dev/, forcing me to restart ddrescue from the log position. This drive produces a lot of read errors (hundreds of read errors, and im only 14GB in on this 160GB drive). I read that this is basically the first thing I should do, as the "-n" flag only tries to read the easily accessible sectors / files on the drive. I am using the command "ddrescue /dev/sdb /root/Desktop/usbgreen/forwardrun.iso /root/Desktop/usbgreen/forwardrun.log -f -n". The working drive to hold the copy is mounted to /root/Desktop/usbgreen I read a lot about ddrescue and tried a few things, but I still have some questions, maybe you can help me: So I never used linux, but i managed to get myself a SystemRescueCD, made a bootable usb stick, mounted my drives and started ddrescue. Long story short, I found out i should use linux and ddrescue to make a raw copy of the hdd as fast as possible. So after all, im sure this drive is nearly dead. Probably the drive has a messed up MBR and bad sectors, pretty sure it has bad heads as well. I got the PCB replaced with a matching one, now the drive spins up, but windows wont let me access it. This drive was dead when i plugged it in some days ago, didnt make any sound. Alright, I am trying to recover data from an old Samsung 160GB 3.5 IDE HDD.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |