1 |
On Sat, Jun 13, 2009 at 9:52 AM, Florian |
2 |
Philipp<lists@f_philipp.fastmail.net> wrote: |
3 |
> Wil Reichert schrieb: |
4 |
>> I think one of my drives is on its way out, tho I've never seen a |
5 |
>> drive fail like this before. Drive is a year old WD 640G & I use it |
6 |
>> as my system drive. Via SMART, I've been doing daily short & weekly |
7 |
>> long tests since I installed it. Starting last week I woke up to my |
8 |
>> keyboard lights blinking and the sound of the heads thrashing & the |
9 |
>> drive repeatedly attempting to spin up. On my desktop the mouse was |
10 |
>> still moving but any command (dmesg, less /var/log/messages) resulted |
11 |
>> in an IO error. I restarted the computer and everything came up fine. |
12 |
>> I dug through the logs but there were no IO errors of any sort to be |
13 |
>> found. All I could see was that the extended SMART test successfully |
14 |
>> started (from smartd.log): |
15 |
>> |
16 |
>> Jun 6 03:10:31 void smartd[5056]: Device: |
17 |
>> /dev/disk/by-id/ata-WDC_WD6400AAKS-22A7B0_WD-WMASY0830809, starting |
18 |
>> scheduled Long Self-Test. |
19 |
>> |
20 |
>> But then it failed to complete (from smartctl -a): |
21 |
>> |
22 |
>> # 7 Extended offline Interrupted (host reset) 50% 7699 - |
23 |
>> |
24 |
>> None of the other SMART attributes indicate any other potential. I |
25 |
>> used my computer with no problems all week thinking perhaps it was a |
26 |
>> fluke. This morning I woke to an similar situation as last week. The |
27 |
>> smartd log indicated that the extended test had started, but oddly |
28 |
>> enough smartctl has no record of the test starting. |
29 |
>> [...] |
30 |
> |
31 |
> Do I understand you correctly: It happended both times when the long |
32 |
> SMART test started? Can you actually trigger the behavior by forcing |
33 |
> such a test? |
34 |
|
35 |
Seems to be the case, yes. I'm not going to attempt another long test |
36 |
until I've migrated everything off it tho =) |
37 |
|
38 |
Wil |