NetRaid Errors

[calbendin]

Hello,
I have another sense code which I can't decipher:
Rebuild Started on CHNL 0 TARG 2. - Mon Jul 18 13:14:53 2005
NOTIFY:Check Condition on Ch 0 ID 2 with the following sense key - Mon Jul 18 13:15:01 2005
f0 00 04 00 00 04 7c
28 00 00 00 00 03 00
This sense key appear when we change a disk an order rebuilt.

The server is a NetServer LH 6000 U and the disks are in raid 5

Thanks

[kris rombauts]

Hi Calbedin,

the check condition send from the hard disk at address 2 means :

sense key : 04 = H/W error (Indicates that the target detected a non-recoverable hardware failure (for example, controller failure, device failure, parity error, etc.) while performing the SCSI command or during a self test.


ASC/ASCQ = 03/00 = Write fault


So if the initial problem was with a disk at id=2 and the new disk reports this error then i suspect the new disk to have a problem also.

I assume the rebuild fails at some point then right ? it would be usefull to provide the complete raid.log file that shows the error history.



HTH

Kris

[calbendin]

Hi Kris,
Thaks for repply

I change the new disk from other slot and make it hotspare, then netraid rebuild the raid but fail.
This is the complete raid.log


Log Started.
- Thu May 19 16:45:51 2005
Log Started.
- Thu May 19 17:19:23 2005
Log Started.
- Thu May 19 18:13:41 2005
Log Started.
- Wed Jun 29 16:59:27 2005
Log Started.
- Mon Jul 18 12:10:47 2005
Battery backup:Module missing - Mon Jul 18 12:13:36 2005
Log Started.
- Mon Jul 18 13:11:34 2005
Log Started.
- Mon Jul 18 13:12:48 2005
Rebuild Started on CHNL 0 TARG 2. - Mon Jul 18 13:14:53 2005
NOTIFY:Check Condition on Ch 0 ID 2 with the following sense key - Mon Jul 18 13:15:01 2005
f0 00 04 00 00 04 7c
28 00 00 00 00 03 00
NOTIFY:Check Condition on Ch 0 ID 2 with the following sense key - Mon Jul 18 13:15:01 2005
f0 00 04 00 00 04 7c
28 00 00 00 00 03 00
Error on Rebuilding CHNL 0 TARG 2 - Mon Jul 18 13:15:16 2005
Notify message : DRIVE STATE changed in Ch 0 ID 2 to FAILED - Mon Jul 18 13:15:45 2005
NOTIFY:Check Condition on Ch 0 ID 2 with the following sense key - Mon Jul 18 13:16:02 2005
f0 00 04 00 00 04 80
28 00 00 00 00 03 00
Rebuild Started on CHNL 0 TARG 2. - Mon Jul 18 13:40:33 2005
NOTIFY:Check Condition on Ch 0 ID 2 with the following sense key - Mon Jul 18 13:40:41 2005
f0 00 04 00 00 04 7c
28 00 00 00 00 03 00
NOTIFY:Check Condition on Ch 0 ID 2 with the following sense key - Mon Jul 18 13:40:41 2005
f0 00 04 00 00 04 7c
28 00 00 00 00 03 00
Error on Rebuilding CHNL 0 TARG 2 - Mon Jul 18 13:40:56 2005
Notify message : DRIVE STATE changed in Ch 0 ID 2 to FAILED - Mon Jul 18 13:41:16 2005
NOTIFY:Check Condition on Ch 0 ID 2 with the following sense key - Mon Jul 18 13:41:38 2005
f0 00 04 00 00 06 80
28 00 00 00 00 03 00
Log Started.
- Mon Jul 18 14:10:49 2005
NOTIFY:Check Condition on Ch 0 ID 2 with the following sense key - Mon Jul 18 14:10:49 2005
f0 00 04 00 00 09 80
28 00 00 00 00 03 00
NOTIFY:Check Condition on Ch 0 ID 2 with the following sense key - Mon Jul 18 14:10:49 2005
f0 00 04 00 00 09 80
28 00 00 00 00 03 00
NOTIFY:Check Condition on Ch 0 ID 2 with the following sense key - Mon Jul 18 14:10:49 2005
f0 00 04 00 00 09 00
28 00 00 00 00 03 00
NOTIFY:Check Condition on Ch 0 ID 2 with the following sense key - Mon Jul 18 14:10:49 2005
70 00 0b 00 00 00 00
28 00 00 00 00 4d 05
Log Started.
- Tue Jul 19 12:55:11 2005
NOTIFY:Check Condition on Ch 0 ID 2 with the following sense key - Tue Jul 19 12:55:11 2005
f0 00 04 00 00 09 80
28 00 00 00 00 03 00
NOTIFY:Check Condition on Ch 0 ID 2 with the following sense key - Tue Jul 19 12:55:11 2005
f0 00 04 00 00 09 80
28 00 00 00 00 03 00
NOTIFY:Check Condition on Ch 0 ID 2 with the following sense key - Tue Jul 19 12:55:11 2005
f0 00 04 00 00 09 00
28 00 00 00 00 03 00
NOTIFY:Check Condition on Ch 0 ID 2 with the following sense key - Tue Jul 19 12:55:11 2005
70 00 0b 00 00 00 00
28 00 00 00 00 4d 05
Log Started.
- Wed Jul 20 12:15:33 2005
NOTIFY:Check Condition on Ch 0 ID 2 with the following sense key - Wed Jul 20 12:15:33 2005
f0 00 04 00 00 09 80
28 00 00 00 00 03 00
NOTIFY:Check Condition on Ch 0 ID 2 with the following sense key - Wed Jul 20 12:15:33 2005
f0 00 04 00 00 09 80
28 00 00 00 00 03 00
NOTIFY:Check Condition on Ch 0 ID 2 with the following sense key - Wed Jul 20 12:15:33 2005
f0 00 04 00 00 09 00
28 00 00 00 00 03 00
NOTIFY:Check Condition on Ch 0 ID 2 with the following sense key - Wed Jul 20 12:15:33 2005
70 00 0b 00 00 00 00
28 00 00 00 00 4d 05
DRIVE STATE changed in CHNL 0 TARG 8 to HOTSPARE - Wed Jul 20 12:16:19 2005
Rebuild Started on CHNL 0 TARG 8. - Wed Jul 20 12:17:15 2005
Notify message : DRIVE STATE changed in Ch 0 ID 2 to READY - Wed Jul 20 12:17:15 2005
Notify message : DRIVE STATE changed in Ch 0 ID 8 to REBUILD - Wed Jul 20 12:17:15 2005
Error on Rebuilding CHNL 0 TARG 8 - Wed Jul 20 12:17:16 2005
Notify message : DRIVE STATE changed in Ch 0 ID 8 to FAILED - Wed Jul 20 12:17:33 2005
NOTIFY:Check Condition on Ch 0 ID 8 with the following sense key - Wed Jul 20 12:17:48 2005
f0 00 04 00 00 04 7c
28 00 00 00 00 03 00

Thaks.

[kris rombauts]

Hi ,

if i understand well you assigned ID=8 as a hotspare now, then failed ID=2 (so it became in Ready state) and the rebuild started onto ID=8 .

Strange thing is that we see the exact same SENSE key now but from ID=8.

Unless id=8 also has a issue one would suspect another component like cable or the controller itself to have a problem.

Not sure what your options are to try with a new disk or one that works fine in another system or with spare parts and give that one more try before moving to the cable/controller/etc ...


I have seen rebuilds fail but that was due to another non failed disk in the same array that also had a bad block so the rebuild of a stripe could not be performed, if this is the case here i would expect to see a check condition from another disk then ID=2 or ID=8 in this case to explain why the rebuild fails.

Anyhow make sure you take backups, if your backup fails on some file it cannot read (not due to open files but really a read error) then this would indicate their is some file corrupted due to a bad block on one of the remaining disks in the array which means that the array needs to be re-initialized and backup restored before this array can ever be made redundant (raid5)again.


If you have the right management s/w installed you can also look at the Windows System and Application eventlogs, they should also contain entries about problems with the disks or when it initially started to go wrong.



Kris

[calbendin]

Hi Kris,

We put the disk (this disk is a new disk)that was in ID=2 in other SLOT and the disk change to ID=8, when we put the disk in the new slot, the NetServer put the disk in the state online, then we convert this new disk in a hot spare and the NetServer start the rebuild of raid, but fail.

Could we do anything to see wat's the problem?

Thanks