Will Dormann
Explorer
- Joined
- Feb 10, 2015
- Messages
- 61
Hi folks,
I've reviewed https://forums.freenas.org/index.ph...ed-drive-if-you-have-an-lsi-controller.30823/ and it appeared to be viable at the time that I tested it. However, I recently attempted to use that technique to find a drive that wasn't responsive (some level of dead). The problem I ran into was that the sas2ircu command wasn't able to identify the drive because it wasn't responsive. After a long delay, it reported with:
After replacing the drive, the exact same command above worked just fine.
So the problem here is that one might want to identify a dead drive to know which bay to pull. But ironically, the command used doesn't appear to work on dead drives. In the end, I identified the drive by its lack of activity when the FS was being stressed. But I'm a little uncomfortable with this as a reliable way of identifying a dead drive.
What is the recommended way for locating a dead drive? I suspect that the answer may depend on the hardware being used.
I've reviewed https://forums.freenas.org/index.ph...ed-drive-if-you-have-an-lsi-controller.30823/ and it appeared to be viable at the time that I tested it. However, I recently attempted to use that technique to find a drive that wasn't responsive (some level of dead). The problem I ran into was that the sas2ircu command wasn't able to identify the drive because it wasn't responsive. After a long delay, it reported with:
# sas2ircu 0 locate 2:0 on
LSI Corporation SAS2 IR Configuration Utility.
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved.
SAS2IRCU: Drive specified by 2:0 is not available.
SAS2IRCU: Error executing command LOCATE.
LSI Corporation SAS2 IR Configuration Utility.
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved.
SAS2IRCU: Drive specified by 2:0 is not available.
SAS2IRCU: Error executing command LOCATE.
After replacing the drive, the exact same command above worked just fine.
So the problem here is that one might want to identify a dead drive to know which bay to pull. But ironically, the command used doesn't appear to work on dead drives. In the end, I identified the drive by its lack of activity when the FS was being stressed. But I'm a little uncomfortable with this as a reliable way of identifying a dead drive.
What is the recommended way for locating a dead drive? I suspect that the answer may depend on the hardware being used.