From: udo <ud...@ya...> - 2002-11-10 14:46:39
|
Hello, I have just installed smartmontools 5.0 on my Immunix (redhat) system. When I start the daemon I get: Nov 10 15:42:45 dubbeltje smartd[2972]: Device: /dev/hda, opened Nov 10 15:42:45 dubbeltje smartd[2972]: Device: /dev/hda, not SMART capable, or couldn't enable SMART Nov 10 15:42:45 dubbeltje smartd[2972]: Unable to register ATA device /dev/hda at line 19 of file /etc/smartd.conf although a smartctl -Pa /dev/hda does yield some output. How do I fix /etc/smartd.conf so I cna use this daemon with the drive? Thanks, Udo __________________________________________________ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2 |
From: Bruce A. <ba...@gr...> - 2002-11-10 19:38:58
|
Hi Udo, > I have just installed smartmontools 5.0 on my Immunix > (redhat) system. > When I start the daemon I get: > > Nov 10 15:42:45 dubbeltje smartd[2972]: Device: > /dev/hda, opened > Nov 10 15:42:45 dubbeltje smartd[2972]: Device: > /dev/hda, not SMART capable, or couldn't enable SMART > Nov 10 15:42:45 dubbeltje smartd[2972]: Unable to > register ATA device /dev/hda at line 19 of file > /etc/smartd.conf > > although a smartctl -Pa /dev/hda does yield some > output. How do I fix /etc/smartd.conf so I cna use > this daemon with the drive? I'm not sure if your drive supports SMART. The "-P" option to smartctl makes it ignore the drive capabilities and try anyway. Please send the complete output of smartctl -a /dev/hda smartctl -V /dev/hda smartctl -aP /dev/hda and smartd -VX to the mailing list. [By the way, you did enable SMART, right? It's the "-e" option to smartctl.] One other suggestion: have you checked Quantum's literature to see if your drive does support SMART? Cheers, Bruce |
From: Bruce A. <ba...@gr...> - 2002-11-10 20:10:45
|
Hi Udo, I looked at a bit of Quantum's literature, and it says somethign a bit odd. It says that the drive supports SMART. It also says that it's an ATA-2 drive. Since SMART was not introduced until ATA-3, this may be part of the origins of the problems you are having. Please send the complete outputs that I asked you for -- it will help to sort this out. Cheers, Bruce |
From: Bruce A. <ba...@gr...> - 2002-11-10 20:50:16
|
Hi Udo, I've thought about this a bit more and I think I know what is going wrong in smartd. Because your drive pre-dates the ATA-3 spec, it doesn't have the "SMART Capability Bit" that is part of the official ATA-3 SMART spec. When you use the -P option with smartctl, it ignores this missing bit, and tries anyway. THe outputs I asked for should confirm this. If so, I'll add an equivalent "Permissive" directive to smartd, so that you can use the SMART capabilities of the drive. Cheers, Bruce |
From: Bruce A. <ba...@gr...> - 2002-11-10 22:04:18
|
Hi Udo, As I said earlier, I think that the problem was that your drive pre-dates the ATA-3 Rev 4 spec where SMART was first added, so smartd does not know that it is SMART capable. I've added a new Directive: "-P" for the smartd.conf configuration file, that I hope should enable you to use the SMART capabilities that are there. I have not had a chance to test this carefully, so I have not generated a new .rpm release. Could you please get the code from CVS and try it to see if it fixes your problem? To get the code from CVS, go to http://smartmontools.sourceforge.net/ and follow the instructions to get the code from CVS. You will want to use the tag RELEASE_5_0_36, so you'll have (all on one line) cvs -d :pserver:ano...@cv...:/cvsroot/smartmontools co -r RELEASE_5_0_36 sm5 You'll need to do: make make install and then add the -P directive to smartd.conf Finally restart smartd. Please email to list to say if this does or does not fix your problem. I would still like to see the output that I asked you for earlier to confirm my suspicions about what is going wrong. Sincerely, Bruce Allen |