additional information on "cciss" device support?
Nathan Stratton Treadway <[email protected]>
| Newsgroups | gmane.linux.utilities.smartmontools |
|---|---|
| Message-ID | <[email protected]> |
We have a number of servers with CCISS RAID controller cards, and I'm experimenting with using the "-d cciss,N" option to check the SMART status of the drives behind the controller cards. In looking for information on this I found the brief discussion in the smartctl man page: http://www.smartmontools.org/browser/trunk/smartmontools/smartctl.8.in , as well as the overview on the Wiki page: http://www.smartmontools.org/wiki/Supported_RAID-Controllers However, these seem to leave out a lot of details on how the CCISS support works. Am I missing some other documentation on the CCISS support that I should be looking at? Some examples of things that have come up: * how do the drives get assigned to the "N" index used in the "-d cciss,N" option? (They don't show up in the same order as the hpacucli utility uses....) * When I use "-d sat" on an USB bridge, the output of "smartctl -a" looks essentially the same as what I get from a directly-connected SATA drive... but the output from a "-d cciss,0" command is much shorter (even when the drive in question is a SATA drive). What controls the information included in the output, and would it matter what Linux kernel version I'm running, etc. (Is there any way to view the SMART Attributes table, for example?) * The Supported_RAID-Controllers wiki page lists the device file to use under Linux as "/dev/sdX", but on our systems the actual device is /dev/cciss/sXdX. Is this an outright mistake (copied from the line for another device type?) on the wiki page, or a change between Linux versions or something along those lines? Thanks. Nathan ---------------------------------------------------------------------------- Nathan Stratton Treadway - [email protected] - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239 ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y