[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Hard disk failure?



On Friday, 10 March 2006 11:52, Jim MacBaine wrote:
> Hello,
>
> one of my hard drives seems to be dying.  To me as a layman this looks
> as if the disk should be returned to the shop where I bought it.  Is
> this right?
>
> ata1: translated ATA stat/err 0x51/40 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: error=0x40 { UncorrectableError }
> ata1: translated ATA stat/err 0x51/40 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: error=0x40 { UncorrectableError }
> ata1: translated ATA stat/err 0x51/40 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: error=0x40 { UncorrectableError }
> ata1: translated ATA stat/err 0x51/40 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: error=0x40 { UncorrectableError }
> ata1: translated ATA stat/err 0x51/40 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: error=0x40 { UncorrectableError }
> sd 0:0:0:0: SCSI error: return code = 0x8000002
> sda: Current: sense key=0x3
>     ASC=0x11 ASCQ=0x4
> end_request: I/O error, dev sda, sector 145661514
>
> It is a Seagate Barracuda 7200.8 SATA  drive with 200 GB capacity and
> a member of a raid5 md device.
>
> Shouldn't the md driver kick mark this drive as faulty and kick it out
> of the array? After I noticed the error in the syslog, I had to mark
> it faulty manually with mdadm.
>
> Regards,
> Jim


Since it's a Seagate you're in luck, because they have a carry-in warranty 
replacement policy. I have seen these kinds of errors before, shortly before 
my Barracuda died a tragic death. 

It is most likely to be the drive. Get it swapped out.

cheers
Duncan

		
___________________________________________________________ 
Yahoo! Photos ? NEW, now offering a quality print service from just 8p a photo http://uk.photos.yahoo.com



Reply to: