FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Smartd does hard drive reliability monitoring. Most modern drives can keep track of errors and relay them to the OS. Smartd under FC2 is failing on all of my systems, but I assume that it is caused by FC2 not being able to read the information through the PCI-based hard disk controllers (Promise Ultra100 TX2) installed in the systems.
Since the drives are super reliable Western Digitals, I don’t worry about the smartd failure. I would be more concerned if the drives were Quantums or Maxtors, but that’s just based on my own bad experiences with them.
satimis: Typically, hda/hdb and hdc/hdd are the master/slave drives on the motherboard-based primary and secondary IDE channels, respectively. Likewise, hde/hdf and hdg/hdh typically refer to the master/slave drives on the PCI-based controller card primary and secondary IDE channels, respectively. Your hard drive is probably plugged into the secondary IDE channel on the controller card.
Regarding “electronically” identifying drives, Seagate drives typically are identified by model number, such as ST3120026AS, which is an SATA 80GB drive. The model number may be displayed during the initialization of the controller card at startup or may be readable from the IDE section of the BIOS setup pages. It is usually not in both places. So, in other words, reboot and watch the monitor.
You can look up the drive characteristics using the model number at the Seagate web site.
Actually, I didn't edit the script itself. I moved the file in /etc/rc.d/rc5.d/S40smartd (which is the same file as: /etc/rc5.d/S40smartd 'cos /etc/rc5.d is a shortcut to /etc/rc.d/rc5.d/ I think) to another folder like UnusedRC5Scripts. Then it won't be loaded at normal startup (runlevel 5 that is). I'm quite a newbie
I had this happen. With the coming of FC2, the cdrom was changed to /dev/hda.
But smartd didn't change its config file (smartd.conf or whatever)
It still tries to scan /dev/hda and the cdrom will not give it hard drive info, if any.
Change the smartd config file to scan the drive(s) that are listed in fdisk -l.
For me I changed /dev/hda to /dev/sda, /dev/sdb, and /dev/sdc as I use scsi.
Afterwards smartd gave me the 3 scsi disks info, huzzah.
satimis: Typically, hda/hdb and hdc/hdd are the master/slave drives on the motherboard-based primary and secondary IDE channels, respectively. Likewise, hde/hdf and hdg/hdh typically refer to the master/slave drives on the PCI-based controller card primary and secondary IDE channels, respectively. Your hard drive is probably plugged into the secondary IDE channel on the controller card.
After plugging HD to primary IDE channel of the PCI-based controller.
Regarding “electronically” identifying drives, Seagate drives typically are identified by model number, such as ST3120026AS, which is an SATA 80GB drive. The model number may be displayed during the initialization of the controller card at startup or may be readable from the IDE section of the BIOS setup pages. It is usually not in both places. So, in other words, reboot and watch the monitor.
You can look up the drive characteristics using the model number at the Seagate web site.
Noted with thanks. HD idenfication is displayed during booting
Is there any way to display HD identification after booting, i.e. during working? TIA
Originally posted by 4hp Actually, I didn't edit the script itself. I moved the file in /etc/rc.d/rc5.d/S40smartd (which is the same file as: /etc/rc5.d/S40smartd 'cos /etc/rc5.d is a shortcut to /etc/rc.d/rc5.d/ I think) to another folder like UnusedRC5Scripts. Then it won't be loaded at normal startup (runlevel 5 that is). I'm quite a newbie
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.