I intended to remove the drive and run chkdsk /f /v on the drive from my Windows 7 recovery console, after ddrescue was complete. It isn't coming up with any more data from Splitting failed blocks right now and it has 536 errors.
It has rescued all but 2306KiB (errsize) of data. Reboot into Windows twice and schedule scandisk for the third reboot.I am a newbie to Linux, using ddrescue v1.14 on a SystemRescueCD USB drive to clone a 320GB IDE drive to a 640GB SATA drive using the following command:ĭdrescue /dev/sdb /dev/sda ddrescue_logfile.log -r3 -B -v -force.Restore the second partition image: ntfsclone -restore-image -overwrite /dev/sda2 /mnt/20190403-DT192530-sda1.img.Restore the first partition image: ntfsclone -restore-image -overwrite /dev/sda1 /mnt/20190403-DT192530-sda1.img.Write the MBR to the new disk: dd if=/mnt/20190403-DT192530-mbr.dmp of=/dev/sda.Write the partition table to the new disk: sfdisk /dev/sda Clone Partition 2: ntfsclone -rescue -force -save-image -output /mnt/20190403-DT192530-sda2.img /dev/sda2.Clone Partition 1: ntfsclone -rescue -force -save-image -output /mnt/20190403-DT192530-sda1.img /dev/sda1.Backup Partition Table: sfdisk -d /dev/sda > /mnt/20190403-DT192530-partition-table.dmp.I logged, checked some things, rebooted several more times and all was good and stable. Unbelievably, the machine was sitting at the Windows login screen. I walked back to my office, across the hallway, and checked it again. It seemed to be taking longer that I expected so I walked over to the customers office and filled him in on the progress and explained it might be several more hours before I would know with high confidence that the solution worked. Windows started and I again logged in as admin and scheduled another scandisk. The system asked for another reboot and I did so. After ntfsclone finished the system was rebooted into Windows and logged in as an admin. The failing drive was replaced with a drive of the same size and reversed the steps. I started the imaging process over and it finished without incident. When it finally did finish, reboot once and then into SRCD, It took several hours and while occasionally checking the progress I was not sure it would actually complete. So, I bootup Win 7, logged in as an admin and opened the Drive Tool and scheduled a scan and fix on the next reboot. I thought I was back to the drawing board until I noticed instructions within the error message to boot back into window and run scandisk /f to mark the bad sector and try to recover any data within the bad sectors. But when attempting sda2 ntfsclone failed almost immediately with an error about bad sectors. Partition sda1, being 25MB, dumped quickly without errors. And lastly, ntfsclone for the partition images.
First, running sfdisk to dump the partition table then dd to dump the boot record. I booted to a flash drive with a System Rescue CD (SRCD) image on it and started there. Did some internet sleuthing and came across a website call, with an article titled "How to clone and restore an NTFS image of a faulty Windows hdd with ntfsclone and Ubuntu." written by Andrea Matesi (hat tip). For technical and logistical reasons having our vendor reinstall was time/cost prohibitive.įirst tried creating an image of the bad drive using Clonezilla but immediately failed. No image available to just throw in a new drive and go. Mission Essential Document Management Desktop with a failing hard drive.
0 kommentar(er)
