S5520H RAID 5 Drive is Bad

[JDost]

I have an Intel server with a S5520HC server board running in a RAID 5 which consists of three, 1TB Seagate enterprise drives. The server is exactly 3 years old. It is extremely slow. When I check the system logs it shows that I have a bad drive (see below). When I run the RAID web console program it can't discover any hosts so I can't find out which physical drive is bad. How can I determine which physical drive is bad and is there a way to get the RAID web console to discover the server?

[JDost]

UPDATE: Here is the error message from the system log.

Log Name: System

Source: disk

Date: 10/18/2013 6:12:31 AM

Event ID: 7

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: STEARNSSVR.jfstearns.local

Description:

The device, \Device\Harddisk0\DR0, has a bad block.

Event Xml:

http://schemas.microsoft.com/win/2004/08/events/event">

7

2

0

0x80000000000000

1605368

System

server.domain..local

\Device\Harddisk0\DR0

030080000100000000000000070004C0000100009C0000C0000000000000000000C076AB5D010000CECC8B0000000000FFFFFFFF010000005800008402020000ED200A124207204000200000410000000060000000000000A032494280FAFFFF0000000000000000600C032280FAFFFF000000000000000060BBD5AE000000002800AED5BB6000001000000000000000700003000000000B00000000000000000000000000000000

[idata]

jwdost,

There's a couple ways to install RAID Web Console 2. Checkout the http://www.intel.com/support/motherboards/server/sb/CS-022358.htm RAID Software User Guide in Chapter 8 to see if you can find any installation issues.

John

[BPres1]

Our theory is that the bad block is in the logical drive, not the physical drive. We have done the chkdsk and found no errors. We have seen this same error on a set of mirrors drives using RAID 1. We first replaced drive 0 of the pair, it was rebuilt but the error continued. So we moved the drive taken from drive 0 and installed it as Drive 1. Once it was rebuilt, the error continued.

[AP16]

Windows writes event about bad block in two cases: in case the verify read returns different from what should be written (applicable only for certain operations) and in case that system cannot complete read at all. You are likely faced with RAID 5 'write hole' trouble, when because of wrong data or parity chunk controller takes a lot of time in hopeless data block reconstruction. The solution is a full backup and full array recreation.

About RAID Web Console: check that its system service is running and allowed in Windows Firewall.

[idata · Accepted solution]

Hello,

Our best recommendation is running the Intel System Information Retrieval Utility (sysinfo) For UEFI and sending the logs to your local support group for further assistance:

https://downloadcenter.intel.com/download/19657/Intel-System-Information-Retrieval-Utility-sysinfo-For-UEFI Download Intel System Information Retrieval Utility (sysinfo) For UEFI

http://www.intel.com/p/en_US/support/contactsupport http://www.intel.com/p/en_US/support/contactsupport