Comment 8 for bug 11461

Message-ID: <email address hidden>
Date: Mon, 27 Dec 2004 10:25:49 +0100
From: "Marc L. de Bruin" <email address hidden>
To: Guido Guenther <email address hidden>
CC: <email address hidden>
Subject: Re: Bug#287195: smartmontools takes the system down to a near halt

Guido Guenther wrote:

  >>I configured it in such a way that /etc/default/smartmontools contains
>>start_smartd=yes and enable_smart="/dev/hda"; this system actually has
>
> No need for the later. start_smartd is sufficient.

[...]

>
>>/var/log/syslog shows that smartd actually scans more that just
>>"/dev/hda" (also hd[bcde]), but doesn't show any errors.
>
> Sure it does, if you don't configure /etc/smartd.conf, it will do a
> devicescan, this can easily cause problems. Please enable one drive at a

This is confusing to me. Although /etc/default/smartmontools clearly
states that the list mentioned in enable_smart *enables* devices, I
assumed that non-mentioned devices actually are *disabled*. This is not
the case, I guess, if DEVICESCAN is still on. You might want to add just
an extra comment regarding this in /etc/default/smartmontools, since it
doesn't have a man-page.

> time and check which one exactly causee the problem. Also, please read
> at least README.Debian and WARNINGS.gz.

Most of these warnings regard Promise controllers; I'm just using the
on-board ICH5. Furthermore, all problems seem to relate to kernel-2.4.18
up and including 2.4.21. Those are really old, like over 2 years. ;-)
I'm guessing those problems have already been fixed (??).

> Additionally please attach 'grep smartd /var/log/syslog' to this mail, when you
> have DEVICESCAN enabled in smartd.conf.
>
> Oh, and could you also please check if the problem persists with
> smartmontools 5.33 from experimental?

I'll do some more research on wednesday and will get back to you.

Thanks for your quick reply!

Marc.