smartmontools vs HP Smart Array 642 controller

From: Brian Reichert (reichert_at_numachi.com)
Date: 02/24/05

  • Next message: Seán C. Farley: "Re: setenv/unsetenv's known memory leak"
    Date: Wed, 23 Feb 2005 18:33:51 -0500
    To: hackers@freebsd.org
    
    

    As per the combo in the subject:

    Does anyone have any experience with smartctl and a HP Smart Array
    642 controller?

    When I boot with HP's provided CD, the utility tells me that the
    device is SMART enabled.

    When I run smartctl version 5.32 under 5.3-STABLE (circa yesterdays's
    CVSup), hoever, I get:

      new# smartd -d
      smartd version 5.32 Copyright (C) 2002-4 Bruce Allen
      Home page is http://smartmontools.sourceforge.net/
      
      No configuration file /usr/local/etc/smartd.conf found, scanning devices
      glob(3) found no matches for patterns (/dev/ad[0-9]),(/dev/ad[0-9][0-9])
      Device: /dev/da0, opened
      (pass0:ciss0:0:0:0): MODE SENSE(06). CDB: 1a 0 1c 0 40 0
      (pass0:ciss0:0:0:0): CAM Status: SCSI Status Error
      (pass0:ciss0:0:0:0): SCSI Status: Check Condition
      (pass0:ciss0:0:0:0): ILLEGAL REQUEST asc:24,0
      (pass0:ciss0:0:0:0): Invalid field in CDB
      Device: /dev/da0, Bad IEC (SMART) mode page, err=-1, skip device
      Unable to register SCSI device /dev/da0
      Unable to monitor any SMART enabled devices. Exiting...

    My googling has revealed nothing useful, and I was hoping for some
    feedback on this...

    (HP's supplied Linux-based monitoring was uninstallable, and I was
    in no mood to de-Llinx the instal script.)

    -- 
    Brian Reichert				<reichert@numachi.com>
    37 Crystal Ave. #303			Daytime number: (603) 434-6842
    Derry NH 03038-1713 USA			BSD admin/developer at large	
    _______________________________________________
    freebsd-hackers@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
    To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
    

  • Next message: Seán C. Farley: "Re: setenv/unsetenv's known memory leak"