| 1 |
James Broadhead wrote: |
| 2 |
> On 2 November 2011 01:17, Dale<rdalek1967@×××××.com> wrote: |
| 3 |
>> Dale wrote: |
| 4 |
>>> Hi, |
| 5 |
>>> |
| 6 |
>>> For the first time in my life, I think I have a drive failing on me. Here |
| 7 |
>>> is the info: |
| 8 |
>>> |
| 9 |
>>> <<<< SNIP>>>> |
| 10 |
>>> |
| 11 |
>>> What you folks think? Can I fix it somehow? I got a good shovel handy |
| 12 |
>>> just in case. |
| 13 |
>>> |
| 14 |
>>> Dale |
| 15 |
>>> |
| 16 |
>>> :-) :-) |
| 17 |
>>> |
| 18 |
>> Nov 1 19:08:09 localhost kernel: ata4.01: status: { DRDY } |
| 19 |
>> Nov 1 19:08:14 localhost kernel: ata4: link is slow to respond, please be |
| 20 |
>> patient (ready=0) |
| 21 |
>> Nov 1 19:08:19 localhost kernel: ata4: device not ready (errno=-16), |
| 22 |
>> forcing hardreset |
| 23 |
>> Nov 1 19:08:19 localhost kernel: ata4: soft resetting link |
| 24 |
> I have RMA'd many drives upon seeing errors like this. I eventually |
| 25 |
> tracked it down to a faulty SATA cable. :-/ |
| 26 |
> |
| 27 |
> |
| 28 |
|
| 29 |
Well, this one does it with two different cables and it is IDE. I have |
| 30 |
to admit tho, I was hoping it would work fine after I brought it down |
| 31 |
here and put it in my rig where it used to be. I even checked the |
| 32 |
jumper to make sure it was set right. |
| 33 |
|
| 34 |
I love grasping at straws tho. |
| 35 |
|
| 36 |
Dale |
| 37 |
|
| 38 |
:-) :-) |
Archives