Hello Bruce and Guido,
First, I wonder if I got right to post on smartmontools mailing list,
as I didn't understood at first that CCISS wasn't an "official"
addition to this project.
Here are some more explanations about my problems :
1/ For the env. problem :
Here is what I get in environment in the script called by smartd :
SMARTD_TFIRSTEPOCH=1148018612
SMARTD_DEVICE="
SMARTD_DEVICESTRING=/dev/cciss/c0d0 [cciss_disk_00]
SMARTD_MAILER=/etc/smartmontools/smartd-runner
SMARTD_TFIRST=Fri May 19 08:03:32 2006 CEST
SMARTD_MESSAGE=TEST EMAIL from smartd for device: /dev/cciss/c0d0
[cciss_disk_00]
SMARTD_FAILTYPE=EmailTest
SMARTD_ADDRESS=<my email>
SMARTD_SUBJECT=SMART error (EmailTest) detected on host: <my host>
SMARTD_DEVICETYPE=scsi
SMARTD_FULLMESSAGE=This email was generated by the smartd daemon running on:
In my script (which run successfully on another disk), I do :
/usr/sbin/smartctl -a -l selftest -l error -d "$SMARTD_DEVICETYPE"
"$SMARTD_DEVICE"
To work, it should expand to :
/usr/sbin/smartctl -a -l selftest -l error -d cciss,0 /dev/cciss/c0d0
but I get instead :
/usr/sbin/smartctl -a -l selftest -l error -d scsi "/dev/cciss/c0d0
[cciss_disk_00]"
2/ For smartd applying tests always on the same disk (always on disk 1,
not 0, I want to add that using smartctl with same arguments, it works
well, so it's a smartd problem only I think.
3/ at last, I didn't notice anymore any message from the cpqarrayd
daemon (telling about recovering data from RAID 1 array) : I suspect
that doing SMART tests reveal some bad blocks problems, automatically
corrected by one disk, which causes the second to need to
re-synchronize...
with regards,
Frédéric Boiteux
