- Feb 7, 2006
- 57
- 0
- 0
I'm running a RAID 0 array using two WD 400GB RE2 hard drives. One was purchased last January while the other was purchased last summer. Using an ASUS A8N-E with the onboard nVidia RAID program. 
Things were going fine up to today. I booted up my computer and it said my array had an error in it. I attempted booting a couple more times and it either gave me the error or it would hang on checking for the array. I opened my case up and listened for any possible noises. I heard a slight *click* *click* in maybe second intervals. I only heard two of these at a time; no other noises after that other than the seek noises. After a while I kept rebooting and it finally showed it was healthy, but the Windows load would hang.
I went into the details of the array and it showed one of the hard drives like I figured. Only issue is that I'm not certain which of the hard drives was not working at the time.
I figured my array was dead so I had an old Seagate SATA lying around that I was going to install windows to. Plugged it in and booted the system up; the array was still healthy so I figured give it one more shot. Windows finally loaded (I had to go through the CHKDSK before it loaded).
My data has been backed up as of today in case this issue happens. My question is was this just a fluke or should I consider RMA'ing (if possible) the drive back to WD? What steps should I take to finding the HDD with the issue?
In case this is relevant: I have a WD 500GB SE16 hooked up, and the Seagate is a 120GB Sata 150 drive. Running XP Pro. The motherboard has the latest BIOS. The RAID drivers were taken from the original mobo CD.
			
			Things were going fine up to today. I booted up my computer and it said my array had an error in it. I attempted booting a couple more times and it either gave me the error or it would hang on checking for the array. I opened my case up and listened for any possible noises. I heard a slight *click* *click* in maybe second intervals. I only heard two of these at a time; no other noises after that other than the seek noises. After a while I kept rebooting and it finally showed it was healthy, but the Windows load would hang.
I went into the details of the array and it showed one of the hard drives like I figured. Only issue is that I'm not certain which of the hard drives was not working at the time.
I figured my array was dead so I had an old Seagate SATA lying around that I was going to install windows to. Plugged it in and booted the system up; the array was still healthy so I figured give it one more shot. Windows finally loaded (I had to go through the CHKDSK before it loaded).
My data has been backed up as of today in case this issue happens. My question is was this just a fluke or should I consider RMA'ing (if possible) the drive back to WD? What steps should I take to finding the HDD with the issue?
In case this is relevant: I have a WD 500GB SE16 hooked up, and the Seagate is a 120GB Sata 150 drive. Running XP Pro. The motherboard has the latest BIOS. The RAID drivers were taken from the original mobo CD.
 
				
		 
			 
 
		 
 
		 
 
		 
 
		 
 
		 
 
		
 Facebook
Facebook Twitter
Twitter