Re: [gentoo-user] Does this drive need a funeral?

[Dale]

Dale wrote:
> Hi,
>
> For the first time in my life, I think I have a drive failing on me.
> Here is the info:
>
> <<<< SNIP >>>>
>
> What you folks think?  Can I fix it somehow?  I got a good shovel
> handy just in case.
>
> Dale
>
> :-)  :-)
>


OK.  For those that have never seen this before, here is what messages 
looks like when a hard drive is going belly up:

Nov  1 19:08:09 localhost kernel: ata4.01: exception Emask 0x0 SAct 0x0 
SErr 0x0 action 0x6 frozen
Nov  1 19:08:09 localhost kernel: ata4.01: failed command: WRITE DMA EXT
Nov  1 19:08:09 localhost kernel: ata4.01: cmd 
35/00:8c:7f:78:a8/00:03:04:00:00/f0 tag 0 dma 464896 out
Nov  1 19:08:09 localhost kernel: res 
40/00:01:00:4f:c2/00:00:00:00:00/10 Emask 0x4 (timeout)
Nov  1 19:08:09 localhost kernel: ata4.01: status: { DRDY }
Nov  1 19:08:14 localhost kernel: ata4: link is slow to respond, please 
be patient (ready=0)
Nov  1 19:08:19 localhost kernel: ata4: device not ready (errno=-16), 
forcing hardreset
Nov  1 19:08:19 localhost kernel: ata4: soft resetting link
Nov  1 19:08:19 localhost kernel: ata4.01: failed to IDENTIFY (I/O 
error, err_mask=0x3)
Nov  1 19:08:19 localhost kernel: ata4.01: revalidation failed (errno=-5)
Nov  1 19:08:24 localhost kernel: ata4: soft resetting link
Nov  1 19:08:24 localhost kernel: ata4.01: failed to IDENTIFY (I/O 
error, err_mask=0x3)
Nov  1 19:08:24 localhost kernel: ata4.01: revalidation failed (errno=-5)
Nov  1 19:08:29 localhost kernel: ata4: soft resetting link
Nov  1 19:08:29 localhost kernel: ata4.01: failed to IDENTIFY (I/O 
error, err_mask=0x3)
Nov  1 19:08:29 localhost kernel: ata4.01: revalidation failed (errno=-5)
Nov  1 19:08:29 localhost kernel: ata4.01: disabled
Nov  1 19:08:29 localhost kernel: ata4.01: device reported invalid CHS 
sector 0
Nov  1 19:08:29 localhost kernel: ata4: soft resetting link
Nov  1 19:08:29 localhost kernel: ata4: EH complete
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc] Unhandled error code
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc]  Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc] CDB: Write(10): 2a 
00 04 a8 78 7f 00 03 8c 00
Nov  1 19:08:29 localhost kernel: end_request: I/O error, dev sdc, 
sector 78149759
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc] Unhandled error code
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc]  Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc] CDB: Write(10): 2a 
00 04 a8 7c 1f 00 03 13 00
Nov  1 19:08:29 localhost kernel: end_request: I/O error, dev sdc, 
sector 78150687
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc] Unhandled error code
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc]  Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc] CDB: Read(10): 28 00 
00 00 4a f2 00 00 01 00
Nov  1 19:08:29 localhost kernel: end_request: I/O error, dev sdc, 
sector 19186
Nov  1 19:08:29 localhost kernel: FAT: FAT read failed (blocknr 19123)
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc] Unhandled error code
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc]  Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc] CDB: Read(10): 28 00 
00 00 4a f2 00 00 01 00
Nov  1 19:08:29 localhost kernel: end_request: I/O error, dev sdc, 
sector 19186
Nov  1 19:08:29 localhost kernel: FAT: FAT read failed (blocknr 19123)
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc] Unhandled error code
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc]  Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Nov  1 19:08:29 localhost kernel: sd 3:0:1:0: [sdc] CDB: Read(10): 28 00 
00 00 4a f2 00 00 01 00
Nov  1 19:08:29 localhost kernel: end_request: I/O error, dev sdc, 
sector 19186

More info:

/dev/sdc1             78112544  39098000  39014544  51% /mnt/media

It won't accept any more files either.  That looks like this:

cp: cannot create directory `/mnt/media/home3/home/dale/.porthole': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.adobe': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.cache': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.gconf': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.fonts': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.gnupg': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.hplip': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.local': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.opera': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.tkdvd': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.fontconfig': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.macromedia': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.scribus': 
Input/output error
cp: cannot create directory `/mnt/media/home3/home/dale/.ooo3.old': 
Input/output error
cp: failed to preserve ownership for `/mnt/media/home3/home/dale': 
Operation not permitted
cp: cannot create directory `/mnt/media/home3/home/dale2': Input/output 
error
root@smoker / #


So, if you see things like this in your log file, rescue data real 
soon.  Make a note of this since this could happen on your rig one day.

Now I know this is a Western Digital drive.  Let's all face it, they all 
die eventually.  I just find it ironic that it is only a few months out 
of warranty.  :-@

Oh, funny how that drive ran fine on Linux then croaked when put in a 
windoze rig.  Maybe WD just hates M$ as much as I do.  LOL

Dale

:-)  :-)