On my PowerVault 124T I can see the following error in the Error Logs screen:
Drv Comm Failure
23:12:41.298 #000I already updated the autoloader firmware and the drive firmware with the latest version, see below
How can I solve this issue ??
What kind of drive do you have in the 124T? One step you can try would be to do a power cycle of the autoloader using the front panel power button. If that doesn’t work we may need to pull the TapeAlert log and see if there is any more specific drive error information. Please let me know how the power cycle goes or if you have any further questions.
Get Support on Twitter @DellCaresPro
Download the Dell Quick Resource Locator app today to access PowerEdge support content on your mobile device! (iOS, Android, Windows)
The drive in the 124T is LTO4-120-1. I already did a power cycle using the front panel, but that did not help. Also checked the tape logs, but it does not help me further.
**** Tape Alert Queue ****
Block 1, 000/017 entries @ 26 bytes each, wrap @ 000, erase @ 001
**** Tape Alert Flags currently set on the Drive **** None
**** Tape Alerts associated with Cartridges located in the library ****
CLNU00L1 is located in slot 1, no Tape Alerts logged.
000001L4 is located in slot 2, no Tape Alerts logged.
000002L4 is located in slot 3, no Tape Alerts logged.
000003L4 is located in slot 4, no Tape Alerts logged.
A tape with no label is located in slot 5, no Tape Alerts logged.
000008L4 is located in slot 9, no Tape Alerts logged.
000005L4 is located in slot 10, no Tape Alerts logged.
000006L4 is located in slot 11, no Tape Alerts logged.
000007L4 is located in slot 12, no Tape Alerts logged.
Ok so what I would recommend is to power down the tape library. Then power down the server, when everything is down I would recommend reseating the cable on both ends. Then power up the tape library and let it boot all the way up. Then finally power onthe server and see if you are still getting the drive comm failure. On your SAS card do you have the one with 2 ports? If so you also may want to switch to the other port to see if that resolves the issue.