It seems I can't smarm monitor disks on RAID controllers? I tried on several machines with two different controllers and on all I get this when starting up smartd: Jul 27 14:36:43 c1 smartd[5944]: Opened configuration file /etc/smartd.conf Jul 27 14:36:43 c1 smartd[5944]: Configuration file /etc/smartd.conf parsed. Jul 27 14:36:43 c1 smartd[5944]: Device: /dev/sda, opened Jul 27 14:36:43 c1 smartd[5944]: Device: /dev/sda, Bad IEC (SMART) mode page, err=4, skip device Jul 27 14:36:43 c1 smartd[5944]: Unable to register SCSI device /dev/sda at line 32 of file /etc/smartd.conf Jul 27 14:36:43 c1 smartd[5944]: Device /dev/sda not available /dev/sda is the virtual disk as it appears to CentOS as I can access it with hdparm. Do I need to use another device for the RAID array (which?) or is it impossible to smart monitor "thru" a RAID controller? Kai -- Kai Sch?tzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com
On Sun, Jul 27, 2008 at 8:51 AM, Kai Schaetzl <maillists at conactive.com> wrote:> It seems I can't smarm monitor disks on RAID controllers? I tried on > several machines with two different controllers and on all I get this when > starting up smartd:> /dev/sda is the virtual disk as it appears to CentOS as I can access it > with hdparm. > Do I need to use another device for the RAID array (which?) or is it > impossible to smart monitor "thru" a RAID controller?This depends on the raid controller. 3ware and a few others will pass info, though you have to tell smart about them in the config. Many hardware raid controllers will not pass smart info, as it's not just one drive you're watching, and the vendor has their own solution for that. -- During times of universal deceit, telling the truth becomes a revolutionary act. George Orwell
Am 27.07.2008 um 14:51 schrieb Kai Schaetzl:> It seems I can't smarm monitor disks on RAID controllers? I tried on > several machines with two different controllers and on all I get > this when > starting up smartd: > > Jul 27 14:36:43 c1 smartd[5944]: Opened configuration file > /etc/smartd.conf > Jul 27 14:36:43 c1 smartd[5944]: Configuration file /etc/smartd.conf > parsed. > Jul 27 14:36:43 c1 smartd[5944]: Device: /dev/sda, opened > Jul 27 14:36:43 c1 smartd[5944]: Device: /dev/sda, Bad IEC (SMART) > mode > page, err=4, skip device > Jul 27 14:36:43 c1 smartd[5944]: Unable to register SCSI device /dev/ > sda > at line 32 of file /etc/smartd.conf > Jul 27 14:36:43 c1 smartd[5944]: Device /dev/sda not available > > /dev/sda is the virtual disk as it appears to CentOS as I can access > it > with hdparm. > Do I need to use another device for the RAID array (which?) or is it > impossible to smart monitor "thru" a RAID controller? >What controller would that be? Rainer
> > /dev/sda is the virtual disk as it appears to CentOS as I can access it > with hdparm. > Do I need to use another device for the RAID array (which?) or is it > impossible to smart monitor "thru" a RAID controller? > > Kai >Kai Shouldn't there be another "layer" ? Is this a real hardware raid controller? I do not remember the specifics, yet when we did this on HP proliant boxes with hardware raid, we had to play with the config files and setup for the raid *drivers* so to speak On old boxes with raid5 we would be monitoring something like /dev/ida/c0d0 And on newer boxes with raid1 or raid5 we would be monitoring something like /dev/cciss/c0d0 - rh
> > /dev/sda is the virtual disk as it appears to CentOS as I can access it > with hdparm. > Do I need to use another device for the RAID array (which?) or is it > impossible to smart monitor "thru" a RAID controller?You probably will want to install the "HP Proliant Support Pack" as it will include the hpasm command line tools as well as a handy HP System Management home page. You can set it up to send you email alerts or send snmp traps to a central server running the HP SIM software any time one of your hard drives fails. We use HP SIM in production to monitor both our Dell and HP servers, and it works great. I get an alert any time a RAID card or hard drive has issues. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20080728/1170b816/attachment-0001.html>