Quantcast
Channel: PowerEdge HDD/SCSI/RAID Forum - Recent Threads
Viewing all articles
Browse latest Browse all 4121

PERC 4e/DI and Unexpected sense. SCSI sense data: Sense key: 3 Sense code: 11

$
0
0

Have a new client with a PE 2800 server that's throwing the errors below on a RAID 1 array, Server Administrator error 2095.  It's out of warranty so I'm looking to fix/proceed this in the safest manner possible.  I know what errors these drives are throwing (read errors of a variety).  Note that there is also a RAID 5 array in this box that's not reporting any errors or issues.

RAID 1 contains drives 0:5 and 0:9

I'm getting lots of this error for drive 0:9:

'Unexpected sense. SCSI sense data: Sense key: 3 Sense code: 11 Sense qualifier: 1: Physical Disk 0:9 Controller 0, Connector 0'

And this error for drive 0:5, although much fewer than drive 0:9 above.

'Unexpected sense. SCSI sense data: Sense key: 3 Sense code: 11 Sense qualifier: 0: Physical Disk 0:5 Controller 0, Connector 0'

Also some of these:

"mraid35x" - "The device, \Device\SCSI\mraid35x1, did not respond within the timeout period."

I've physically witnessed the server hanging and drive 0:9 sitting there with it's activity light lit during the hang... which tells me that it's this drive that is suspect... although no drives are reporting predictive failure.  What's a bit scary is that BOTH drives are throwing errors of the same, yet slightly different variety.  Could the problem with drive 0:9 create subsequent errors/events on drive 0:5orcould both these drives be slowly failing?

My question is should I proceed with running a check consistency of the RAID array.  Then if errors continue, replace drive 0:9 and let it rebuild to a hotspare that is already present. 

Just looking for a little advise here.


Viewing all articles
Browse latest Browse all 4121

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>