similar to: smartd and 3ware 9xxx configs

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,

CentOS Community, What commands can I use to check the disk health of the system when LVM2 is being used on top of a RAID 10 using a HARDWARE 3ware raid card. The OS sees a hardware raid usually as one big drive. Is there a way to check the disks individually to see if any are failing, or throwing hard or scsi transport errors?

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

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:

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

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

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*" [ !

I had a drive failing on a server. I've replaced it. The old drive was /dev/sdb; the new one's /dev/sdd. The manpage and googling are failing me - anyone know how to tell smartd to stop trying to read /dev/sdb (which I've pulled, and is sitting here on my desk)? I don't need the garbage in the logs, and no, I can't just reboot the server, since it's a home directory

On 4/22/20 8:53 AM, Christopher Wensink wrote: > I had an 8 TB External USB disk plugged into the system, that I had been > using for additional space for backups, I was under the impression that > sda, sdb, sdc, and sdd were the four disks on the raid controller card, Not exactly.? If you have a RAID5 array, then you have one volume spread across the physical disks.? You can then

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 updated the machine that I use for a web/email server last night to 5.9, and I have this in the logwatch report this morning: QUOTE: --------------------- Smartd Begin ------------------------ Warnings: Device: /dev/sda [SAT], WARNING: There are known problems with these drives, - 1 Time(s) **Unmatched Entries** smartd 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-348.el5] (local

How can I tell wich HDD to swap, when the "cat /proc/mdstat" says one HDD of the RAID1 array has died? Does the HDD's has some serial numbers, that I can see in "reality", and I can get that number from e.g.: a commands output? How could I know wich HDD to swap in e.g.: a RAID1 array? thank you -------------- next part -------------- An HTML attachment

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 am running software RAID1 on a somewhat critical server. Today I noticed one drive is giving errors. Good thing I had RAID. I planned on upgrading this server in next month or so. Just wandering if there was an easy way to fix this to avoid rushing the upgrade? Having a single drive is slowing down reads as well, I think. Thanks. Feb 7 15:28:28 server smartd[2980]: Device: /dev/sdb

I restarted the a Centos 5.6 server tonight and I ran in this issue: I was able to boot. Then instead of a normal boot with graphical interface the system requested : 'Enter run level' 'INIT' I typed 5 then I got 'INIT: no more process left in this run level How can I recover from the situation? This is a production system back-up are made but left on the disk and transfer

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>

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

Hello list, I see through the archives that some people here use 3ware RAID controllers with Centos. I have picked up two 9500S-4LP controllers for future servers. I was hoping that if some people could please share their 3ware monitoring scripts with the rest of the group. What I am really hoping to do is have some setup where a cron job runs scripts to test each of the drives connected to the

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

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