Red Hat Bugzilla – Bug 124230
smartd fails during boot due to missing /dev/hda
Last modified: 2015-01-04 17:06:18 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; nl-NL; rv:1.6) Gecko/20040510
Description of problem:
My motherboard (Asus A7V) has an ATA66 controller to which I connected
a DVD-burner as master on the secondary bus (/dev/hdc). Besides, a
Promise ATA100 controller is available to which two ATA100 harddisks
are connected as master and slave on the primary bus (/dev/hde and
/dev/hdf). Finally I have a SCSI disk (/dev/sda).
When smartd starts, I get the following feedback in /var/log/messages:
May 24 18:30:30 localhost smartd: smartd version 5.21 Copyright
(C) 2002-3 Bruce Allen
May 24 18:30:30 localhost smartd: Home page is
May 24 18:30:30 localhost smartd: Opened configuration file
May 24 18:30:30 localhost smartd: Configuration file
May 24 18:30:30 localhost smartd: Device: /dev/hda, No such
device or address, open() failed
May 24 18:30:30 localhost smartd: Unable to register ATA device
/dev/hda at line 30 of file /etc/smartd.conf
May 24 18:30:30 localhost smartd: Unable to register device
/dev/hda (no Directive -d removable). Exiting.
May 24 18:30:30 localhost smartd: smartd startup failed
This also happened when I ran Fedora Core 1.
I know how to fix it (edit /etc/smartd.conf), but for other people it
might be confusing that after a fresh install they see error messages
Is it possible to create the /etc/smartd.conf during the install after
detection of the available hardware? This would be the most generic
solution that would work on all systems.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.look in /var/log/messages
Actual Results: See the feedback in /var/log/messages above
Expected Results: It should activate smartd for hde and hdf, not nag
about hda not being present, and ignore sda (because it does not
Duplicate of bug 110747 ?
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
Closing per previous comment.