derekg1023 wrote:
ShadowAndMax; et al:
Can you check to make sure for me? It's going to cost me $50 to purchase the program, and if it doesn't work, I'm out of $50 since software is non-refundable in retail.
I did download the trailware version of it, and it too was giving me CRC Check Invalid errors in Windows, however I am unable to try it in the bootable environment, since I cannot create a recovery CD in the trialware version.
-Derek
Derek,
Symantec has a 60 day return policy no matter where you purchased the product. This should not be an issue.
ghost654321 wrote:
Hi. I just happened to have the same prob - I mean CRC error - I removed all microsoft XP updates from my computer, going back to two months, and guess what ???!!! norton ghost happened to work ghosting successfully again !!!
Now, this is microsoft new windows vista team... putting fakes as updates for XP... I don't trust this new team !!!
Alright for you ?
Were you able to pinpoint which "update" was at fault?
terryjmyers wrote:
I too am having this error. I backup my C drive to my D drive. Then I use a syncing program to backup my entire D drive to an external 1TB USB drive(Drive Z). Therefore I have two independent copies of my ghost images. I have ghost images going back three computers(three different hardware configurations), one of the sets of images is with windowx XP 64.
All of the images on all of the drives are now failing
How could this possibly be happening? I used an MD5 hash check to verify that the files between the two drives(D and Z) are identical. So unless both drives went bad in the past month since my last backup I don't know what.
Luckily I have a Drive E, which I keep a clean version of windows on to do video capture. So I load that up, and try to do a backup of that drive(so I have a good image in case I can never recover these. As I do a backup of this drive to drive D it fails a CRC check during the verification. Same goes if I try to do a backup directly to Z (my ext hdd). I just created the file and it already has a CRC error?! How could it create a file, then immediatly have a bad CRC during verification?
So...I go to the runtime environment before windows, and try to do all of the restore operations described above...I still get the same error while it's verifying the image.
I can no longer backup or restore my computer using this software. It is now useless to me. A little help please
Ghost uses multiple error codes/messages. Could you provide all errors and messages you see in the CRC error message? There should be at least 2, but up to 3-4 errors/messages.
Hi and thanks for coming up here to check out this error. It's nice to see some Symantec interaction on this matter.
In my case, I'm using NS&R, 2.0 (2.0.7.29210).
I just tried to do a backup from C (89GB used) to D:\backups\, a brand new 1TB Western Digital MyBook drive, clean, USB 2.0 External drive.
99 minutes... went all the way through, failed on the validation with the following error:
-Error ED800012: The internal structure of the image file (CRC Check) is invalid, damaged or unsupported.
Drive D:\backups\ is now empty.
NS&R has no facility for checking validity of existing backups, but when I tried to do a restore several weeks ago with the Symantec System Recovery CD, I was warned that the backup image was invalid.
I believe that the backups are fine, but have NOT been able to make a new backup since installing XP-SP3.
I have taken screenshots of all of this, but they basically say nothing more than the error listed above.
You should see a "More info" or "More Details" item. When Ghost displays an error there are 2-4 errors listed. Could you double check so I could have all of the error details?
Erik:
It's not Ghost but S&R. The More Details window shows ONLY the message I typed above. Tony requested I do a complete technical dump and send that info along to him, zipped, which I did yesterday. Without posting pictures on some other web site, I can't post them up here, but I have screen shots of the errors and the window that opens up to more details.
That error is the ONLY error listed, and typed up here verbatim.
Also, S&R has no facility for verifying old backups made with S&R, but when I tried to restore one of the sets a while back using the Symantec System Recovery Disk, I got basically the same message that the image was invalid, damaged or corrupt and in the list of the sets that were there, they ALL had the red X icons next to them. I know these were valid verified backups.
If you want to contact me directly, I can send you screen shots and logs... whatever you need. Tony Weiss has my contact info.
Regards,
Enis Moran
Message Edited by ShadowAndMax on 01-30-2009 11:45 AM
Message Edited by ShadowAndMax on 01-30-2009 11:48 AM
Thanks Enis.
I'll ask one of our developers to take a look at the logs.
Much appreciated Erik...
This is very frustrating. As you can see if you look at the past traffic, most people that are posting are having exactly the same issue... Old backups are now useless too.
For what it's worth, I DID restore one of the backups it said was invalid (ignored the error), and everything came back fine. However, I haven't been able to make a new backup with S&R for months now, very disconcerting with the way things change on a daily basis here...
Enis
erik_carlstrom wrote:
Ghost uses multiple error codes/messages. Could you provide all errors and messages you see in the CRC error message? There should be at least 2, but up to 3-4 errors/messages.
This is the errors that I get in the Ghost 12.0 Event Log when my backup fails to a network disk:
Error EC8F17B7: Cannot create recovery points for job: My Computer Backup. Error ED800012: The internal structure of the image file (CRC Check) is invalid, damaged or unsupported.
Details: 0xED800012
Source: Norton Ghost
I am glad to finally see someone from Symantec on this board responding to this ongoing question about the CRC errors that makes our backups unrecoverable!
Tom
ShadowAndMax wrote:
Much appreciated Erik...
This is very frustrating. As you can see if you look at the past traffic, most people that are posting are having exactly the same issue... Old backups are now useless too.
For what it's worth, I DID restore one of the backups it said was invalid (ignored the error), and everything came back fine. However, I haven't been able to make a new backup with S&R for months now, very disconcerting with the way things change on a daily basis here...
Enis
After a disk crash, I tried to restore from my Ghost 12 backup to a new hard drive, and it gave the CRC errors. I told it to ignore them, and the restored image would not boot Windows. So I did a reinstall of Windows, and restored just My Documents from the backup (again ignoring the CRC errors). Most of the files were intact, but several documents were corrupted. I was able to recover the contents of some of the Word .DOC files I had using another utility (costing more money), as several critical documents I was not able to open with Word. I was sorely let down by Ghost, as the default settings do not enable checking of the backup, so many users out there don't know they have CRC errors until they try to recover from the backup, but then it is too late!
My Ghost backups now always check for errors after the backup, because it has burned me in the past and I don't want to be burned again. I still get the CRC errors randomly during my backups to my network disk. Repeated attempts eventual backup without CRC errors.
Tom
Tom:
In Save & Restore, it goes through the entire backup, tries to validate it, fails the CRC check, then erases the backup it made.
In addition, there's no way to vaildate a recovery point that exists. It does it internally.
But, unless it passes the CRC check, it won't backup. However, you CAN tell it not to validate, and it'll keep the image, but you have no way of knowing if it's OK or not.
Message Edited by ShadowAndMax on 01-30-2009 06:18 PM
ShadowAndMax wrote:
Tom:
In Save & Restore, it goes through the entire backup, tries to validate it, fails the CRC check, then erases the backup it made.
In addition, there's no way to vaildate a recovery point that exists. It does it internally.
But, unless it passes the CRC check, it won't backup. However, you CAN tell it not to validate, and it'll keep the image, but you have no way of knowing if it's OK or not.
Ghost backups behave the same way, in that once the entire backup completes, it then optionally runs the verify to validate it (not on by default). If the validation fails with CRC or other errors, it then erases the backup it just made. Ghost 12 also includes their Symantec Recovery Point Browser, which can validate backup files that are already completed.
I don't know if Ghost can restore or validate the backups made by Save & Restore. Perhaps you can try a trial version of Ghost 14 to see if it can validate your S&R backup.
Tom
Thanks Tom, but I feel like an idiot. I completely forgot that I could verify a backup (recovery point) in the Recovery Point Browser... Oops!
Doesnt matter though. I took every back up I had, ran them through verification, and they all failed the CRC Check with this same error...
Go figure!
For those that have run CHKDSK on their source and destination drives, did you use /r or /f or no switch? In order to force the repairs you must run /r. For Enis, the logs show that there are I/O control calls failing so something is corrupting the image. If Checkdisk /r is what you did, could you check your cables? There might be a bad cable that’s causing this.
erik_carlstrom wrote:
For those that have run CHKDSK on their source and destination drives, did you use /r or /f or no switch? In order to force the repairs you must run /r. For Enis, the logs show that there are I/O control calls failing so something is corrupting the image. If Checkdisk /r is what you did, could you check your cables? There might be a bad cable that's causing this.
I ran "CHKDSK /f /r" on both the source and destination drives, which required reboots on both the source and destination computers so that the chkdsk could run at Windows boot time. My log files from the chkdsk did not report any errors corrected on either disk. Running a backup to my network drive once again sporadically fails with the CRC errors reported above.
Tom
Hi Tom,
I've sent you an email with log creation information and an upload location. Please let me know if you are able to get the logs to us, and when you have uploaded them. Thanks!
Thanks for coming up Tony.
I'm going to switch some hardware around tonight and see if I can get through a complete verified backup. It may be my USB hub. I'm going to remove that from the equation and see what happens.
Thanks again Erik...
Enis
Tried another back-up this afternoon. First, I unplugged EVERYTHING from the machine and blew it out with a compressor so there were no over-heating issues. Then, closed everything, started S&R and left...
Brand new drive, brand new cable, direct plug-in into a usb port on the back of the machine... no hub...
Same thing... Error ED800012.
It's not my hardware. It went all the way through, then errored on the validation...
I'm sure the i/o errors the logs showed were for not being able to find the drives when they weren't powered up.
Message Edited by ShadowAndMax on 02-03-2009 03:24 PM
Thanks for the update Enis. I've passed this along.
Erik...
Tell me how to clear out ALL the logs and I'll run another backup and do the technical gathering again. This way, we'd have a clean log of just the one operation.
Thank you SO much for the unbelieveably speedy reply up here!
Enis