Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Crc Error In Raid - Which Drive Died?


  • Please log in to reply
8 replies to this topic

#1 Hunter_Thompson

Hunter_Thompson

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:08:09 PM

Posted 03 September 2007 - 08:15 PM

Hi Everyone,

I recently was asked to look at a server that was giving disk {CRC} read errors. It is setup as a Virtual Machine {VM ware} server.

I was instructed to break the raid (raid-0), perform a low-level format of the three Sata drives that were in the raid array, and then recreate the raid, reinstall Windows Server 2003 (R2) and the VM ware images. The instructions given to me to low-level format the drives should format around any bad sectors on the hard drive.

I did all of the above, and now we still get the CRC error.

So it seems one of the drives needs to be replaced, but I don't really want to have to buy 3 new drives when only one is down.

Can anyone recommend a method or application that will allow me to establish what drive or drives have the problem? Will a chkdisk command do it?

Thanks for any advice, I realise whatever I use will take a fair whack of time.

Hunter

BC AdBot (Login to Remove)

 


#2 Hunter_Thompson

Hunter_Thompson
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:08:09 PM

Posted 03 September 2007 - 08:44 PM

Found a SeaGate Tool

http://www.seagate.com/www/en-us/support/d...ols/seatooldreg

As I have SEAGATE Barracuda 7200.7 / 120GIG Sata / Model # ST3120827AS, so maybe this tool will work as well.

Will post back my findings.

Hunter

#3 Hunter_Thompson

Hunter_Thompson
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:08:09 PM

Posted 03 September 2007 - 09:13 PM

OK so the RAID manager has no option to check for errors or anything like that - it has Create Raid, Delete Raid, Repair Raid1, Low-Level Format, Resolve Conflicts (cant find any) and Logical Drive Info.

The SeaTools utility says no hard drives found. Maybe it wont see a Raid array... might try breaking the Raid and running SeaTools again.

#4 arcman

arcman

  • Members
  • 706 posts
  • OFFLINE
  •  
  • Location:Michigan
  • Local time:06:09 AM

Posted 03 September 2007 - 09:22 PM

Download the Ultimate Boot CD from here: http://www.ultimatebootcd.com/download.html
Extract the .ISO file and burn it as a CD image as instructed here.

Boot up with the CD and choose one of the hard drive diagnostic programs. I recommend either Drive Fitness Test or SeaTools. Although if you know the make of the hard drive it's best to use the diagnostic tool from the manufacturer (use SeaTools on Maxtor and Seagate drives, use DFT on IBM/Hitachi drives, etc.)
Posted Image

#5 Hunter_Thompson

Hunter_Thompson
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:08:09 PM

Posted 03 September 2007 - 09:57 PM

Very nice link, arcman. This is going in my bag o' tricks. I am currently using SeaTools as I have Seagate Barracuda SATA drives.

Looked at the motherboard, and the 3 SATA drives were plugged into SATA ports 3, 4 and 5. Hmmm... I unplugged them all and plugged one into SATA port 1.

Now SeaTools sees this drive. I am now erasing, and will then do diagnostics. I have 3 drives to do this to so it may take a while!

Will post result.

Hunter

#6 Hunter_Thompson

Hunter_Thompson
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:08:09 PM

Posted 04 September 2007 - 07:30 PM

There were 3 drives in a Raid0 array.

Drive 0, Drive 1, Drive 2

Drive 1 was the culprit - SeaTools has identified it as the dodgy disk.

Thanks for all the advice.

Hunter

#7 DaChew

DaChew

    Visiting Alien


  • Members
  • 10,317 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:millenium falcon and rockytop
  • Local time:06:09 AM

Posted 04 September 2007 - 08:06 PM

so much for redundancy and raid, in effect you had a 1 in 3 drive failure but had to start over anyway

your raid bios should have tipped you off to the drive failure and you could have pulled the bad drive and rebuilt the mirror

adding a replacement stripe drive later?
Chewy

No. Try not. Do... or do not. There is no try.

#8 arcman

arcman

  • Members
  • 706 posts
  • OFFLINE
  •  
  • Location:Michigan
  • Local time:06:09 AM

Posted 04 September 2007 - 09:20 PM

He couldn't have done any rebuilding if it was raid0 like he described--zero parity.
Posted Image

#9 DaChew

DaChew

    Visiting Alien


  • Members
  • 10,317 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:millenium falcon and rockytop
  • Local time:06:09 AM

Posted 04 September 2007 - 09:39 PM

striping 2 drives is dangerous, three more so, I assumed he had built a raid 5 array with distributed parity

never hear much about servers using stripe with no parity

Edited by DaChew, 04 September 2007 - 09:39 PM.

Chewy

No. Try not. Do... or do not. There is no try.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users