Port-amd64 archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
RE: HDD errors.
Still getting these error..
ccd0: error 5 on component 0
sd1(ahd0:0:2:0): Check Condition on CDB: 0x28 00 00 70 fc e0 00 00 10 00
SENSE KEY: Hardware Error
INFO FIELD: 7404777
ASC/ASCQ: No Defect Spare Location Available
FRU CODE: 0x4
ccd0: error 5 on component 0
Any idea what this could.. I have replaced 3 drives on the server.. This is
an HP DL385 I move the drive to another location on the bay and still see
the problem...
Regards
Derrick
-----Original Message-----
From: port-amd64-owner%NetBSD.org@localhost
[mailto:port-amd64-owner%NetBSD.org@localhost] On
Behalf Of Derrick Lobo
Sent: Friday, September 05, 2008 9:14 AM
To: port-amd64%NetBSD.org@localhost; netbsd-users%netbsd.org@localhost
Subject: HDD errors.
Seeing the following errors on dmesg
ccd0: error 5 on component 0
sd1(ahd0:0:1:0): DEFERRED ERROR, key = 0x4
sd1(ahd0:0:1:0): Check Condition on CDB: 0x0a 0a 01 40 10 00
SENSE KEY: Hardware Error
INFO FIELD: 655609
ASC/ASCQ: No Defect Spare Location Available
FRU CODE: 0x4
ccd0: error 5 on component 0
sd1(ahd0:0:1:0): DEFERRED ERROR, key = 0x4
sd1(ahd0:0:1:0): Check Condition on CDB: 0x2a 00 00 63 6e 20 00 00 30 00
SENSE KEY: Hardware Error
INFO FIELD: 6516033
ASC/ASCQ: No Defect Spare Location Available
FRU CODE: 0x4
ccd0: error 5 on component 0
sd1(ahd0:0:1:0): Check Condition on CDB: 0x08 0a 00 f0 30 00
SENSE KEY: Hardware Error
INFO FIELD: 655609
ASC/ASCQ: No Defect Spare Location Available
FRU CODE: 0x4
ccd0: error 5 on component 0
sd1(ahd0:0:1:0): Check Condition on CDB: 0x08 07 6a e0 20 00
SENSE KEY: Hardware Error
INFO FIELD: 486126
ASC/ASCQ: No Defect Spare Location Available
FRU CODE: 0x4
ccd0: error 5 on component 0
sd1(ahd0:0:1:0): Check Condition on CDB: 0x08 07 6a e0 20 00
SENSE KEY: Hardware Error
INFO FIELD: 486126
ASC/ASCQ: No Defect Spare Location Available
FRU CODE: 0x4
I have changed the drive 3 times but I still key getting this error... I
will try to replace the SCSI controller to see if the message goes away..
could also be a failed port on the backplane.
Regards
Derrick
Home |
Main Index |
Thread Index |
Old Index