I was absolutely not sure where to post this. It could be a software issue, a Windows issue or a hardware issue, so I thought I'd start here. An apology if this is the wrong place.
On my father’s system he uses Acronis True Image to do his backups, Kudos to him I say. But recently he had to restore a backup and he started it in the normal fashion by running the Windows 7 client and choosing the image and letting it restart etc... However whenever he does it that way instead of it starting the restore he gets a 'non system disk' error.
We were still able to boot into the current install if he reboots after that but he could not restore this way. If we used the Acronis restore CD however the restore went fine. He even tried restoring both the MBR and Disk Signature but still whenever he tries to start a restore from the Windows client he gets the disk error after it reboots.
Is this a general MBR corruption problem? If so how can we fix it? If not any ideas on what is going on?
He has a home built PC with Windows 7 SP1 x64 Ultimate. 2 SATA III HDs each on a separate channel, they are WD Caviar 1 gigs and were originally partitioned, formatted and installed all by the original Windows disk. He does not have a ton of stuff installed on it, other than the stuff that comes with Windows, he has MS Office 2010 Standard, Norton 360 v.6, Adobe CS5.5, Firefox, Acronis 2012, Perfect Disk 12.5, MS Money and a few other small things I am not even sure he uses much. Nothing that I am personally aware of that could corrupt a disk. He uses NO registry cleaners and only used Windows Disk Cleaner before using Perfect Disk then doing a backup with Acronis.
He is very good with his system which is why I can't understand it. We called Western Digital and they would not help because the warranty on these drives JUST wore out, literally 2 weeks ago, and they are usually very good about helping people. All they said was to download the WD DIAG tools. We did and both drives passed fine.
Wasn't sure if he screen shot would help, it's pretty lame just a snap of the error, but he insisted I include it.
Not sure of the next move.