> -----Original Message-----
> From: Jeffrey Paul [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, August 06, 2000 5:56 PM
> To: [EMAIL PROTECTED]
> Subject: owie, disk failure
> 
> hmmmm, the day i had hoped would never arrive has...
> 
> Aug  2 07:38:27 chrome kernel: raid1: Disk failure on hdg1, 
> disabling device.
> Aug  2 07:38:27 chrome kernel: raid1: md0: rescheduling block 8434238
> Aug  2 07:38:27 chrome kernel: md0: no spare disk to reconstruct 
> array! -- continuing in degraded mode
> Aug  2 07:38:27 chrome kernel: raid1: md0: redirecting sector 8434238 
> to another mirror
> 
> my setup is a two-disk (40gb each) raid1 configuration... hde1 and 
> hdg1.   I didn't have measures in place to notify me of such an 
> event, so I didnt notice it until i looked at the console today and 
> noticed it there...

I think I ran for about 2 weeks on a dead drive.  Thankfully it wasn't a
production system, but notification isn't quite as "out of the box" as it
needs to be just yet.

> I ran raidhotremove /dev/md0 /dev/hdg1 and then raidhotadd /dev/md0 
> /dev/hdg1 and it seemed to begin reconstruction:
> 
> but I got scared and decided to stop it...  so now it's sitting idle 
> unmounted spun down (both disks) awaiting professional advice (rather 
> than me stumbling around in the dark before i hose my data).   Both 
> disks are less than two weeks old, although I have heard of people 
> having similar problems (disks failing in less than a month new from 
> the factory) with this brand and model....   I would like to get the 
> drives back to the way the were before the system decided that the 
> disk had failed (what causes it to think that, anyways?) and see if 
> it continues to work, as I find it hard to believe that the drive 
> would have died so quickly.   What is the proper course of action?

First, do you have ANY log messages from anything other than RAID indicating
a failed disk?  Since these are IDE drives, I'd expect some messages from
the IDE subsystem if the drive really had died (my SCSI messages went pretty
wild when I had a disk fail).  To check and see if the drive is actually in
good condition, grab the diagnostic utility from the support site of your
drive manufacturer, boot from a DOS floppy, and run diagnostics on the
drive.  In order for them to replace my drives, I've had to do "write"
testing, which destroys all data on the drive, so you may want to disconnect
power from one of the drives before you play around with that.  If the disk
is good, then you're all set.  If not, get it replaced.  I've seen drives
fail very quickly before, it's always been a manufacturing defect of some
kind.  HTH,
        Greg

Reply via email to