similar to: Smartd Warning in logwatch report

Yohoo! I have some issues with the smartd in CentOS5/x64 I edited the /etc/smartd.conf for my needs and restarted the smartd with "service smartd restart". But the start script is overriding my file. I checked it and saw the following lines: ---------------/etc/init.d/smartd------------ case "$1" in start | reload | restart) GEN_CONF="*SMARTD*AUTOGENERATED*" [ !

last night I checked the log messages on the server Dell PE2950 6xSAS 146G I found the smartd running , I did not request such daemon [root at PowerEdge1 pons]# tail -f /var/log/messages Aug 25 08:27:30 PowerEdge1 smartd[8039]: Home page is http://smartmontools.sourceforge.net/ Aug 25 08:27:30 PowerEdge1 smartd[8039]: Opened configuration file /etc/smartd.conf Aug 25 08:27:30 PowerEdge1

It seems I can't smarm monitor disks on RAID controllers? I tried on several machines with two different controllers and on all I get this when starting up smartd: Jul 27 14:36:43 c1 smartd[5944]: Opened configuration file /etc/smartd.conf Jul 27 14:36:43 c1 smartd[5944]: Configuration file /etc/smartd.conf parsed. Jul 27 14:36:43 c1 smartd[5944]: Device: /dev/sda, opened Jul 27 14:36:43

I'm looking to do a bit more monitoring of my 3ware 9550 with smartd, and wanted to see what others were doing with smart for monitoring 3ware hardware. Do you have the smartd.conf configured to test, or simply monitor health status? Are you monitoring the drive as centos sees it (/dev/sdX) or are you using the 3ware /dev/twaX for monitoring? Opinions and discussions are welcome :-P --

Hi, I've CentOS5 box with 3ware RAID controller in it. I can't get the tw_cli command line tool to work, and smartd also barks on me. The tw_cli simply doesn't see the controller, no errors logged anywhere. When starting smartd, it is much more verbose. I'm getting a bunch of messages like this: Oct 9 22:15:15 toporko kernel: program smartd is using a deprecated SCSI ioctl,

I notice that the smartd service is not running by default on a new installation. But palimpsest seems to get updated statistics every so often as when I check the statistics on a drive it says "last updated" some number of minutes ago. So if smartd isn't running, where does palimpsest get its information from and what is updating it? Second question, what would enabling the smartd

I decided, after the last discussion of smartd and S.M.A.R.T. disks, to take a look in my /var/log/messages, and I'm seeing fair bit of this: Sep 10 20:11:23 mhrichter smartd[3361]: Device: /dev/sda, 4294967295 Offline uncorrectable sectors Sep 10 20:41:23 mhrichter smartd[3361]: Device: /dev/hdb, 21 Currently unreadable (pending) sectors Sep 10 20:41:24 mhrichter smartd[3361]: Device:

I'm running a CentOS 4 and smartd fails to start on boot the centos 4 smartd service doesn't support scsi ? <mailto:denis.machard at enst-bretagne.fr> Denis -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20061128/8f430d4c/attachment-0002.html>

Hello, I'm using HP homeserver where host system run CentOS 6.3 with KVM virtualization with SELinux enabled, guests too run the same OS (but without SELinux, but this does not matter). Host system installed on mirrors based on sda and sdb physical disks. sd{c..f} disks attached to KVM guest (whole disks, not partitions; needed to use zfs (zfsonlinux) benefit features). Problem is that disks

I have begun to notice that the smartd stalls my machine's boot process for as much as 2-3 minutes while it is coming up. I have the BIOS SMART function enabled, and I removed the bad SG400GB drive from the box yesterday, but I think this goes back farther than that. Why does it take so long? Is the BIOS SMART involved in this (and how)? Also, sendmail and sm-client take 30s-2m to come up

We have about 50 CentOS servers with software RAID level 1 (mirroring). Each week, we swap out one of the drives (the one in the second of four hot-swap bays, only the first two of which contain drives) on each server and take them offsite for safekeeping. The problem is, the kernel seemingly randomly switches between /dev/sdb and /dev/sdc for these devices. This makes the process slower by

A few weeks ago, one of my servers started complaining, via smartd, that one drive had one unreadable sector. I umounted it, and ran an fsck -c, then remounted it. Error didn't go away. Now, what's really annoying is that I've gotten back to it today, and it's reporting the problem, as it has for weeks now, every half an hour. However, when I run > smartctl -q errorsonly -H -l

Hello, I'm running CentOS 4.4 and am getting an error from smartd. This machine has a single ide drive in it /dev/hda and i was getting a bootup error from smartd, so i uncommented the /dev/hda line in /etc/smartd.conf. The error persisted when i tried to restart smartd, i got a service restart failed and the below error. Any suggestions? On another unrelated subject i'm

Hi, I have a software mirror with 2 IDE disks - hda and hdc. I would like to be able to monitor their health using smartd, and I am running /etc/init.d/smartd as a service. I placed the folloing in the /etc/smartd.conf /dev/hda -H -m root /dev/hdc -H -m root I case of a problem I want to be notified by mail, and a message to be logged to the system log. Just want to know if this

I have a system that is logging: smartd /dev/sda currently unreadble (pending) sectors smartd /dev/sda offline uncorrectable sectors The box continues to run fine. Doing "smartctl -H /dev/sda" says: test result: PASSED I have ran the "smartctl -t offline /dev/sda", after the 300+ seconds I rebooted and waited about 30 minutes and again got the above error, and smartctl -H

I'm not used to using smartd, but have a new set of systems that don't have any sort of RAID on them, so I enabled smartd (18 systems 4 SATA drives each). Running CentOS 5.4 64-bit .. One of them has emailed me twice(despite it saying it would only email me once) saying it has 1 Offline uncorrectable sectors But when I try to find more information, smartctl seems to think everything is

Hello, My machine is running Software RAID 5 on /dev/hde1, /dev/hdg1,/dev/hdi1. I noticed on the log that suddenly we are getting messages such as : Oct 14 01:27:16 localhost smartd[4801]: Device: /dev/hde, SMART Prefailure Attribute: 8 Seek_Time_Performance changed from 247 to 246 Oct 14 01:57:15 localhost smartd[4801]: Device: /dev/hde, SMART Prefailure Attribute: 8 Seek_Time_Performance

Hi All, I don't know enough about when errors are *really* errors. So I google a lot to read and learn. I have a few things in my Logwatch that I want to make sure I understand 1. smartd **Unmatched Entries** Problem creating device name scan list Device /dev/sda: using '-d sat' for ATA disk behind SAT layer. Device /dev/sdb: using '-d sat' for ATA disk behind SAT layer.

dmesg is not reporting any issues. The /proc/mdstat looks fine. md0 : active raid1 sdb1[1] sda1[0] X blocks [2/2] [UU] however /var/log/messages says: smartd[3392] Device /dev/sda 20 offline uncorrectable sectors The machine is running fine.. raid array looks good - what is up with smartd? THanks, Jerry

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, I have recently bought a new disk (Seagate 500G, ST3500320NS). I have enabled SMART checking using the smartmontools as usual for the disk (/dev/ad6 -a -S on -s (S/../.././03|L/../../7/03) -m root). The problem is that each time the test runs I get messages like the following in /var/log/messages: Oct 26 04:54:15 35 kernel: ad6: TIMEOUT -