ARCHIVES
August 2011
July 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
August 2008
July 2008
June 2008
May 2008
March 2008
February 2008
January 2008
November 2007
CONTACT
|
| About this blog: Computers hate me. They really do. Every time I try to do something unusual like add new hardware, something is guaranteed to go wrong. I decided to start writing about my constant problems so that someone else might benefit from my experiences - or at least laugh at them! |
Here's a RAID1 array that I created a few hours ago, then xcopy'd all files from an existing RAID5 array (I'm changing from a 3 x 750GB RAID5 to a 2 x 1TB RAID1). I decided to run a verification to force all sectors to be read, and there are already an alarming number of verification errors being reported. Under RAID1 I presume means that the data on the two disks is not identical - which shouldn't be happening on a fresh array! The screen cap was taken at 1% and it was showing 9,230 errors; it's now at 3% and reporting 47,148 errors.
Earlier, when I was attempting to backup then restore using ntbackup, the restore froze with the HD LED light remaining on. I could switch between windows but the comp was otherwise non responsive. After a reboot one of the drives started thrashing away, even though the HD light was not going on. This phantom thrashing continued for several minutes - with the comp idle - until I did a shutdown. A subsequent diagnostic test does not reveal anything.
Now, the RAID1 array has apparent errors, even though the array has been destroyed, recreated, and reformatted since the freeze. There's either something very wrong with one of the drives, or some sort of bug with Intel's Matrix RAID driver. The only other explanation I can think of is that for some reason mirroring does not work in safe mode (which I used when copying the files) - the driver was definitely loaded, since the source was a RAID5 array.
UPDATE: the comp blue-screened a few minutes after I completed the original post.
|
|
Related posts:
A complete list of all recent hard drive failures in the office
Problem with top cover seal on hard drive
Beware of HDDerase reducing your hard drive capacity
Seagate: Reallocated sector count on "new" drive = 99
Improving the stock Intel cooler
Don't unplug a mounted drive under FreeBSD!
4th WD drive failure
|