inconsistent parity errors on vd strip after restoring image to new machine
Posted on 2012-08-12
We had a SBS server that had some issues, including inconsistent partity on vd strip.
We were sent a new server to replace a bad server. we performed a Windows Bare-Metal Backup using Widows Backup.
On the new server we restored the bare-metal backup and the server came up fine. However running a consistency check on the virtual disks, we still get the parity errors we were getting on the old server
The other symptom we are still getting is the inconsistency check on a 1TB raid 1 drive is taking over 24 hours to complete. Whenever i have performed these in the past, they usually take about 3-4 hours to check 1 TB.
What I want to rule out is the bare-metal restore. Would the restore bring over a bad array which would cause both the parity errors as well as the slow disk checks?