On Wednesday 02 Jul 2008 20:10, Arun Khan wrote: > On Wednesday 02 Jul 2008, Nadeem M. Khan wrote: > > On Wed, Jul 2, 2008 at 3:29 PM, Arun Khan <[EMAIL PROTECTED]> wrote: > > > On Wednesday 02 Jul 2008, ravi kuamar wrote: > > >> Then how do we find which hard disk had failed from the > > >> several hard disk in the server remotely. we need to hav > > >> certain command for this in linux. > > > > > > Individual disks or hardware RAID? > > > > If the disk is a member of a raid array, you can do a cat > > /proc/mdstat to know its health. > > This will work only for sw raid. In the hardware raids I have come > across the array is presented as a monolith device e.g. /dev/sda > > > If its an individual disk, I don't know of any direct, linux > > native way of finding it. Your hardware vendor might provide some > > daignostic software that can be run without rebooting the system. > > If the disk does not show up in "fdisk -l " certainly rip'd. This > is the easy one. If it is on it's way out, there will be timeouts > or read errors. > > But detecting such errors (OP) from a remote location. Hmmm, may > be some kind of SNMP report?
remote syslog n nagios might be a lot simpler. > > -- Arun Khan -- Rgds JTD -- http://mm.glug-bom.org/mailman/listinfo/linuxers
