ATIH 2011 backup killed target drive, source drive had issues.
Backing up an 80GB drive and I used a portable drive to receive the image. The portable drive had several partitions including a Windows 7 partition with about 100GB free. So I backed up the 80GB drive and specified the image file should be placed on the partition with 100GB free. There was a warning regarding errors on the source drive so it had to utilize a sector by sector copy. I go to restore the image and when I look at the partition in TI 2011, it shows the 242GB partition, 0 bytes free but no files or folders seem to exist. Anyone have any thoughts as to the cause and solution? I would like to get the data back if at all possible, was holding on to the drive until I was sure no data was needed off it anymore. I also have to admit I was going somewhat by feel on the backup as I believe something is wrong with the graphics on the machine, so the video display from TI was pretty messed up.
I imagine I will also stop my frequent practice of backing up images to my 3 TB raid array where all my precious data is kept. If I had lost that instead...
- Anmelden, um Kommentare verfassen zu können
Yes - I was expecting an 80GB .tib file in the 284 GB partition along with all the other files and folders that normally go along with a W7 installation. Instead there's nothing there anymore. I've attached the portable drive to an XP machine and Windows is reporting the partition as corrupt and unreadable. Not sure what happened, whether is was not checking off sector by sector, ATIH 2011, the target drive has issues perhaps? But then why would just the one partition where I happened to be placing the image file get corrupt unless ATIH 2011 did it? The others partition on the drive are okay (Dell recovery partition, etc.).
I've tried again with another portable drive, and ATIH 2012. This time I actually checked off the sector by sector, still received the message the source disk has errors, must be sector by sector, are you sure? I ran the backup and things went as expected (I've got a big .TIB on the partition drive, no corrupted partition, etc. Restore to another drive ran fine...
- Anmelden, um Kommentare verfassen zu können
Don't forget to run the Chkdsk c: /R on the target disk as the errors were transferred to the new destination and will need to have the sector status changed from the bad to good.
- Anmelden, um Kommentare verfassen zu können
Thanks, once again, a very disturbing outcome using the Acronis product. I can't even get chkdsk to run. I get a message chkdsk cannot open volume for direct access. Will try from an XP repair session off an install disk. This machine was badly infected leading up to these issues...
- Anmelden, um Kommentare verfassen zu können
Normally, the check for errors will only run as part of a new bootup and can only run when no files are open or locked. This is not unusual.
Windows will normally advise that a reboot will be required in order for the check to do its thing . Reboot and see if the check will start. Initiating the check via a command prompt is one method but it can also be done using the Windows which is
Right click on drive C
Choose properties
Choose tools
Choose Error checking -check now
Clheckmark both options to be checked.
Click Start and agree to run at next boot.
Repeat the process for each drive being checked.
- Anmelden, um Kommentare verfassen zu können
Thanx for the assist. Issue is on the reboot, so it comes up every time and fails to get access. Hopefully I can clear the flag to run by running off the repair option. Anyway, off topic now, but thanx again
Anyone else want to guess why ATIH 2011 killed my partition?
- Anmelden, um Kommentare verfassen zu können
Ignore. I was thinking of something else.
- Anmelden, um Kommentare verfassen zu können
Nope - vanilla XP back from the infested dead. I'll figure it out, thanx. I would really like to know why ATIH 2011 killed my partition though (which it seems to be the only culprit around.
- Anmelden, um Kommentare verfassen zu können
From a command prompt
Try the Chkdsk C: /R /X
as per this link.
http://help.lockergnome.com/windows/CHKDSK-run--ftopict537472.html
Added:
the chkdsk /?
indicates that you still need the /r with the /x key
with only the /x key, there seems only to be a file check and not a disk check.
- Anmelden, um Kommentare verfassen zu können