Turns out that even though the drive shows no OEM information and a valid Firmware version (an older version), it is indeed an OEM drive. Two problems were encountered the drive activity LED was on constantly and flickered during use and the drive would randomly drop out of the array and then pop back in, causing a rebuild and all the associated alarms and alerts. Since there were no custom labels or any indication of these being OEM drives we were blind sided when all of them had problems when configured in a raid array. We first encountered a problem when we bought a batch of drives that were new, but were OEM drives (for Dell I later found out). Most of these issues are related to the fact that the drives I am dealing with are end of life and my customer has not gone through the approval process for new drives. WARNING: Following some of my examples will not only brick your HDD, it will void the warranty! Proceed with caution!
Some of this will bore people to death and some will beg for more detail. Some of these issues apply to SATA and PATA drives and CD/DVD optical drives as well (since they use the SCSI commands). I have been dealing with some SAS drive issues and thought I would document them here.
0 kommentar(er)
