Comment 6 for bug 1795051
Revision history for this message
| Lee Trager (ltrager) wrote Re: [enhacement] smartctl should try harder with raid controllers | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
I noticed that our CI does have a MegaRAID controller which the smartctl-validate test was skipping. I tried updating drivedb.h but that did not fix the issue. I was only able to get smartctl output when run with -d megaraid,9.
@Peter, James - Do you have a way to programmatically determine what SCSI bus number should be used? I only discovered I should use 9 by trying 0-8 first. It seems this is an issue with many RAID controllers, you need to specify the BUS or port number the device uses.
smartctl returns 2 when the SCSI bus number is wrong. According to the man page 2 mean "Device open failed, device did not return an IDENTIFY DEVICE structure, or device is in a low-power mode." We can't brute force the SCSI bus number as we don't know if 2 means the number is wrong or the device is completely dead.