Bug 101415 - smartd startup fails on s390 after install (no /dev/hda)
smartd startup fails on s390 after install (no /dev/hda)
Status: CLOSED DUPLICATE of bug 99156
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel-utils (Show other bugs)
s390 Linux
medium Severity low
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-07-31 16:19 EDT by Daniel Jarboe
Modified: 2007-11-30 17:06 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:57:54 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Daniel Jarboe 2003-07-31 16:19:53 EDT
Description of problem:
After taroon-beta1 install, smartd is started by default in runlevels 3 and 5, 
with a default /etc/smartd.conf of "/dev/hda -H -m root@localhost.localdomain", 
which is inappropriate for s390.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install taroon-beta1 on s390
2. IPL

Actual Results:  smartd dead but subsys locked

Expected Results:  More sensible default config for s390?

Additional info:

in /var/log/messages:
smartd[699]: smartd version 5.1-11 Copyright (C) 2002-3 Bruce Allen
smartd[699]: Home page is http://smartmontools.sourceforge.net/
smartd[699]: Using configuration file /etc/smartd.conf
smartd[699]: Device: /dev/hda, No such file or directory, open() failed
smartd[699]: Unable to register ATA device /dev/hda at line 30 of 
file /etc/smartd.conf
smartd[699]: Unable to register device /dev/hda - exiting.
smartd: smartd startup failed
Comment 1 Bill Nottingham 2003-07-31 16:32:07 EDT

*** This bug has been marked as a duplicate of 99156 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:57:54 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.