Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

xtacie

1 Message

103697

June 13th, 2014 19:00

TONS of ID: 2095 Unexpected sense. SCSI sense data: Sense key: 5 Sense code: 24 Sense qualifier: 0

​I have inherited a T710 (i believe, case is in horrid shape) and it has Server 08R2 Preinstalled.​


​When booting up i get an error: Memory/Battery problems were detected. The adapter has recovered but cached data was lost.​

​When I load windows and go into OPENMANAGE Server Admin I see TONS of these errors (see below). I guess my questions are, What are these issues? How can I fix it? ​


​PERC 6/i Integrated - Firmware 6.2.0-0013 and shows theres a newer firmware version. Should I update? How do I? and will it fix my issue?​

​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​​ ​
​2095​​Fri Jun 13 20:44:28 2014​​Storage Service​​Unexpected sense. SCSI sense data: Sense key: 5 Sense code: 24 Sense qualifier: 0: Physical Disk 0:0:2 Controller 0, Connector 0​
​2095​​Fri Jun 13 20:44:27 2014​​Storage Service​​Unexpected sense. SCSI sense data: Sense key: 5 Sense code: 24 Sense qualifier: 0: Physical Disk 0:0:2 Controller 0, Connector 0​
​2095​​Fri Jun 13 20:44:27 2014​​Storage Service​​Unexpected sense. SCSI sense data: Sense key: 5 Sense code: 24 Sense qualifier: 0: Physical Disk 0:0:2 Controller 0, Connector 0​
​2095​​Fri Jun 13 20:44:27 2014​​Storage Service​​Unexpected sense. SCSI sense data: Sense key: 5 Sense code: 24 Sense qualifier: 0: Physical Disk 0:0:2 Controller 0, Connector 0​
​2095​​Fri Jun 13 20:44:27 2014​​Storage Service​​Unexpected sense. SCSI sense data: Sense key: 5 Sense code: 24 Sense qualifier: 0: Physical Disk 0:0:2 Controller 0, Connector 0​
​2095​​Fri Jun 13 20:44:26 2014​​Storage Service​​Unexpected sense. SCSI sense data: Sense key: 5 Sense code: 24 Sense qualifier: 0: Physical Disk 0:0:1 Controller 0, Connector 0​
​2095​​Fri Jun 13 20:44:26 2014​​Storage Service​​Unexpected sense. SCSI sense data: Sense key: 5 Sense code: 24 Sense qualifier: 0: Physical Disk 0:0:1 Controller 0, Connector 0​
​2095​​Fri Jun 13 20:44:26 2014​​Storage Service​​Unexpected sense. SCSI sense data: Sense key: 5 Sense code: 24 Sense qualifier: 0: Physical Disk 0:0:1 Controller 0, Connector 0​
​2095​​Fri Jun 13 20:44:26 2014​​Storage Service​​Unexpected sense. SCSI sense data: Sense key: 5 Sense code: 24 Sense qualifier: 0: Physical Disk 0:0:2 Controller 0, Connector 0​
​2095​​Fri Jun 13 20:44:25 2014​​Storage Service​​Unexpected sense. SCSI sense data: Sense key: 5 Sense code: 24 Sense qualifier: 0: Physical Disk 0:0:0 Controller 0, Connector 0​
​2095​​Fri Jun 13 20:44:25 2014​​Storage Service​​Unexpected sense. SCSI sense data: Sense key: 5 Sense code: 24 Sense qualifier: 0: Physical Disk 0:0:1 Controller 0, Connector 0​
​2095​​Fri Jun 13 20:44:25 2014​​Storage Service​​Unexpected sense. SCSI sense data: Sense key: 5 Sense code: 24 Sense qualifier: 0: Physical Disk 0:0:1 Controller 0, Connector 0​
​2095​​Fri Jun 13 20:44:25 2014​​Storage Service​​Unexpected sense. SCSI sense data: Sense key: 5 Sense code: 24 Sense qualifier: 0: Physical Disk 0:0:1 Controller 0, Connector 0​
​2095​​Fri Jun 13 20:44:24 2014​​Storage Service​​Unexpected sense. SCSI sense data: Sense key: 5 Sense code: 24 Sense qualifier: 0: Physical Disk 0:0:0 Controller 0, Connector 0​

theflash1932

9 Legend

 • 

16.3K Posts

June 13th, 2014 21:00

The controller is out of date.  Updating it may help.  Make sure to update the iDRAC/LCC and BIOS firmware before updating the PERC firmware, and update the driver (when available) before the firmware.

The drives could be bad, but it is unlikely that all are bad at once.

It could be the drives are incompatible.  What make/model are the drives?  This would not be uncommon if desktop/laptop drives were used instead of certified/enterprise drives.

The array could be corrupt.  You said it came this way ... I would suggest wiping everything out (including the RAID array), running diagnostics on everything, throw away anything that doesn't pass (drives), then configure RAID and install OS from scratch.

Also, if you are getting the memory/battery message on EVERY boot, you need to replace the memory and/or battery.  What errors are listed on your LCD screen and in your hardware log (in OMSA)?

View More

View All

No Events found!

Top