Hello,
You can update the firmware first. You can find it here https://dell.to/3pehRWZ

If you have downtime for the server that you can update iDRAC, BIOS, and PERC
Then, you can look at the SEL log to see if there are drive-related errors or if there are warnings such as predictive failure. Then, if you have a backup, you can try replacing it to see if the problem is with the hardware. If you have known good parts that you can try to understand which part is the issue by doing X tests, that is, by replacing the parts with known good parts.

Hope that helps!

Thanks for fast reply!

Yes actually I have updated firmware and I have checked disk health and prefailure status.

But my problem is that I have several old R730 servers and they "lose" disks in a random way.

Do I need to replace all controllers? Or it is a drive cage problem?

I think you are suspecting HDD carrier. This is also a possibility if the Drives do not fit the backplane properly. I would check by doing onsite troubleshooting. You can check the latches.

Is it possible that drive carrier is "drive backplane"?

Thanks,

Mario

Mgiammarco,

No, as they are two seperate things. The carrier will house the hard drive, and the backplane is where the drive will connect to the server.

Also, I would suggest trying to update the server completly to start, and would you confirm the specific error you're seeing?

Hello,

 Apologies for the interjection, I am having the same issue with an r710. It has been driving me batty for about a month now. Just the last 3.5" slot. Drive failed. 2 minutes later, operating normally. Rinse and repeat every 10 minutes. Ubad, Ugood, online, rebuild, consistency check, all complete. Get home the next day, Yellow lcd, yelllow blink, same. Another oddity, each time it "fails" out of the array and appears back as foriegn, it flip flops from being seen as enclosure 0 slot 5 to just slot 5, no enclosure.  Smart self test, short test and extended test passed repeatedly. Full test in the support assist bootable diagnostics passes. No errors in syslog. Taken drive out, no interface on these carriers, backplane out, cleaned everything, checked cable routes, power supplies, all to no avail. Only idea I have left is to break the array and use the manufacturers stand alone diag tools on another system, but that takes more than a few days on a 10 TB.  Ideas?  (And yes, all firmware has been updated, though I have never seen one for this backplane).

Hello,

I'm starting this answer with this article that shows how to troubleshooting drives

https://dell.to/3H4IzHr

Please check and make all the suggested steps.

In your case, @alksj460, if diagnostic test out of the OS passes, then probably there are some logical issue on the array.

Which controller is installed? You can verify if there is a sort of check consistency in the BIOS of the controller or via Open Manage Server Administrator.

You said that all firmware are updated, did you check also hard drive firmware?

Thanks

Marco

It has a PERC H700 with 512MB cache, battery backed. I have run the consistency checks and the rebuilds thru both the boot interrupting bios interface, and via the perc cli utility. As to the drive firmware, no, there have been no updates put out from the vendor. The drive in question is one of four in a raid 5, two being matched part numbers, and the fourth being a newer model RMA replacement this past spring, at least a few months prior to the issue.Only slot 5 has the issue. I have NOT tried swapping two in the array around, because I do not remember if it can rebuild from that without data loss. (This is a home media and whole home backup, so offloading 26 TB is going to take quite a while, and required an r730xd purchase.)  And no data loss is the kicker! Even with this drive supposedly failing numerous times; sometimes filing the SEL in an hour or two; when I set it to good and reinsert it to the VD, It's consistent, patrol reads pass, Smartctl under linux passes all tests, Dell diagnostics pass, and the data is all there, no read or write degradation. No errors in the syslog, SEL just says it failed, then operating normally. I have yet to get OMSA to run on this, but the iDRAC is not logging anything more descriptive. the PERC log has a tad bit more info, but is also like trying to decypher a phone number out of the history of the universe.  It is logging SENSE errors, Though I believe these were during boot, mainly b/47/03 and 6/26/00. The b/47/03 looks to be either the cause of or in response to an internal device reset, though as to the requestor, I am unsure.  Log snippet below.

12/06/21 21:41:09: iopiEvent: EVENT_SAS_DEVICE_STATUS_CHANGE
12/06/21 21:41:09: DM_HandleDevStatusChgEvent: devHandle=x000a SASAdd=4433221102000000 TaskTag=xffff ASC=x00 ASCQ=x00 IOCLogInfo x31120303 IOCStatus x8000 ReasonCode x08 - INTERNAL_DEVICE_RESET
12/06/21 21:41:09: EVT#507548-12/06/21 21:41:09: 113=Unexpected sense: PD 05(e0xff/s5) Path 4433221102000000, CDB: 8e 00 00 00 00 04 8c 3f df d5 00 00 00 08 00 00, Sense: b/47/03
12/06/21 21:41:09: Raw Sense for PD 5: 70 00 0b 00 00 00 00 0a 00 00 00 00 47 03 00 00 00 00
12/06/21 21:41:09: DevId [5] Reduce Queue Depth recursive retry: maxQDepth 1 : maxDepthChanged 1 : curQDepth 1

12/06/21 21:41:09: iopiEvent: EVENT_SAS_DEVICE_STATUS_CHANGE
12/06/21 21:41:09: DM_HandleDevStatusChgEvent: devHandle=x000a SASAdd=4433221102000000 TaskTag=xffff ASC=x00 ASCQ=x00 IOCLogInfo x00000000 IOCStatus x0000 ReasonCode x0e - INTERNAL_DEVICE_RESET complete

12/06/21 21:41:09: iopiEvent: EVENT_SAS_DISCOVERY
12/06/21 21:41:09: DM_HandleDiscEvent: Discovery started on Port 0

12/06/21 21:41:09: iopiEvent: MPI2_EVENT_SAS_TOPOLOGY_CHANGE_LIST
12/06/21 21:41:09: DM_HandleTopologyChgEvnt: PhysicalPort=0 NumberOfPhys=x08 NumEntries=x01 StartPhy=x2
12/06/21 21:41:09: ExpStatus=x00 PhysicalPort=0 EnclosureHandle=x0001 Expander devHandle=x0000
12/06/21 21:41:09: Phy changed - phy 02 devHandle 000a linkRate aa curLinkRate a
12/06/21 21:41:10: iopiDiscoveryComplete SubSystem 2 Count 26 InitState 1

12/06/21 21:41:10: iopiEvent: EVENT_SAS_DISCOVERY
12/06/21 21:41:10: DM_HandleDiscEvent: Discovery Completed on Port 0

12/06/21 21:41:10: Disc-prog= 0....resetProg=0 aenCount=0 transit=0
12/06/21 21:41:10: EVT#507549-12/06/21 21:41:10: 113=Unexpected sense: PD 05(e0xff/s5) Path 4433221102000000, CDB: 00 00 00 00 00 00, Sense: 6/29/00
12/06/21 21:41:10: Raw Sense for PD 5: 70 00 06 00 00 00 00 0a 00 00 00 00 29 00 00 00 00 00
12/06/21 21:41:10: DM_REC: Timeout TUR complete DevId 5 rdm 807b8000 sts 2
12/06/21 21:41:10: MPT_REC: Protocol ERROR rdm 807b8000, devId 0005, devHandle 000a, Cmd 03, IoReply c053c238, iocSts 0047, IOCLogInfo 00000000
12/06/21 21:41:10: DM_REC: Aborting recovery SM DevID[5], pRdm 807b8000 RDM FLags=1800004 DevFlags f1400005

12/06/21 21:41:10: iopiEvent: EVENT_SAS_DEVICE_STATUS_CHANGE
12/06/21 21:41:10: DM_HandleDevStatusChgEvent: devHandle=x000a SASAdd=4433221102000000 TaskTag=xffff ASC=x00 ASCQ=x00 IOCLogInfo x31120303 IOCStatus x8000 ReasonCode x08 - INTERNAL_DEVICE_RESET
12/06/21 21:41:10: EVT#507550-12/06/21 21:41:10: 113=Unexpected sense: PD 05(e0xff/s5) Path 4433221102000000, CDB: 8e 00 00 00 00 04 8c 3f df d5 00 00 00 08 00 00, Sense: b/47/03
12/06/21 21:41:10: Raw Sense for PD 5: 70 00 0b 00 00 00 00 0a 00 00 00 00 47 03 00 00 00 00
12/06/21 21:41:10: DevId [5] Reduce Queue Depth recursive retry: maxQDepth 1 : maxDepthChanged 1 : curQDepth 1

12/06/21 21:41:10: iopiEvent: EVENT_SAS_DEVICE_STATUS_CHANGE
12/06/21 21:41:10: DM_HandleDevStatusChgEvent: devHandle=x000a SASAdd=4433221102000000 TaskTag=xffff ASC=x00 ASCQ=x00 IOCLogInfo x00000000 IOCStatus x0000 ReasonCode x0e - INTERNAL_DEVICE_RESET complete
12/06/21 21:41:10: EVT#507551-12/06/21 21:41:10: 113=Unexpected sense: PD 05(e0xff/s5) Path 4433221102000000, CDB: 00 00 00 00 00 00, Sense: 6/29/00
12/06/21 21:41:10: Raw Sense for PD 5: 70 00 06 00 00 00 00 0a 00 00 00 00 29 00 00 00 00 00
12/06/21 21:41:10: DM_REC: Timeout TUR complete DevId 5 rdm 807b8000 sts 2

12/06/21 21:41:11: iopiEvent: EVENT_SAS_DEVICE_STATUS_CHANGE
12/06/21 21:41:11: DM_HandleDevStatusChgEvent: devHandle=x000a SASAdd=4433221102000000 TaskTag=xffff ASC=x00 ASCQ=x00 IOCLogInfo x31120303 IOCStatus x8000 ReasonCode x08 - INTERNAL_DEVICE_RESET
12/06/21 21:41:11: EVT#507552-12/06/21 21:41:11: 113=Unexpected sense: PD 05(e0xff/s5) Path 4433221102000000, CDB: 8e 00 00 00 00 04 8c 3f df d5 00 00 00 08 00 00, Sense: b/47/03
12/06/21 21:41:11: Raw Sense for PD 5: 70 00 0b 00 00 00 00 0a 00 00 00 00 47 03 00 00 00 00
12/06/21 21:41:11: DevId [5] Reduce Queue Depth recursive retry: maxQDepth 1 : maxDepthChanged 1 : curQDepth 1

12/06/21 21:41:11: iopiEvent: EVENT_SAS_DEVICE_STATUS_CHANGE
12/06/21 21:41:11: DM_HandleDevStatusChgEvent: devHandle=x000a SASAdd=4433221102000000 TaskTag=xffff ASC=x00 ASCQ=x00 IOCLogInfo x00000000 IOCStatus x0000 ReasonCode x0e - INTERNAL_DEVICE_RESET complete

12/06/21 21:41:11: iopiEvent: EVENT_SAS_DISCOVERY
12/06/21 21:41:11: DM_HandleDiscEvent: Discovery started on Port 0

12/06/21 21:41:11: iopiEvent: MPI2_EVENT_SAS_TOPOLOGY_CHANGE_LIST
12/06/21 21:41:11: DM_HandleTopologyChgEvnt: PhysicalPort=0 NumberOfPhys=x08 NumEntries=x01 StartPhy=x2
12/06/21 21:41:11: ExpStatus=x00 PhysicalPort=0 EnclosureHandle=x0001 Expander devHandle=x0000
12/06/21 21:41:11: Phy changed - phy 02 devHandle 000a linkRate aa curLinkRate a
12/06/21 21:41:11: iopiDiscoveryComplete SubSystem 2 Count 27 InitState 1

12/06/21 21:41:11: iopiEvent: EVENT_SAS_DISCOVERY
12/06/21 21:41:11: DM_HandleDiscEvent: Discovery Completed on Port 0

12/06/21 21:41:11: Disc-prog= 0....resetProg=0 aenCount=0 transit=0
12/06/21 21:41:11: EVT#507553-12/06/21 21:41:11: 113=Unexpected sense: PD 05(e0xff/s5) Path 4433221102000000, CDB: 8e 00 00 00 00 04 8c 3f df d5 00 00 00 08 00 00, Sense: 6/29/00
12/06/21 21:41:11: Raw Sense for PD 5: 70 00 06 00 00 00 00 0a 00 00 00 00 29 00 00 00 00 00
12/06/21 21:41:11: Recovered Rdm 807b8000 Pd 5 Sense 6 asc 29 ascq 0
12/06/21 21:41:11: updateSectionsCallback: Error, pd=05, err=2
12/06/21 21:41:12: DevId [5] Restore Queue Depth to 40

Hi,

It can be caused by the firmware of the control not being up to date. As far as I understand and I see, there is no failed drive or predictive failure drive. So it would be good to check the firmware first. If multiple VDs were created from the PERC BIOS interface and there were drives removed, sometimes PERC can get confused and send an invalid command because it cannot access it. Sense codes warnings may also occur when the drives used are non-certified. I would also like to share this wiki page for sense codes that I think will be useful https://dell.to/3qk2PhK
FW update of the hard drive may also be useful. You will see the same warning when you look through OMSA. You can also clear these SEL logs via iDRAC or OMSA. Because SEL logs that are not cleared can be listed to remind you again.
I will actually recommend iDRAC, BIOS and PERC controller updates when it can get downtime. You can also check into Drive FW. You can access FWs from here by entering ST https://dell.to/3mxiKYJ

If the you see same unexpected sense warning then please reseat the hard drive and PERC cables.

Hope that helps!