| 1 |
Thanasis wrote: |
| 2 |
> on 03/06/2011 07:07 PM Nikos Chantziaras wrote the following: |
| 3 |
> |
| 4 |
>> Before leaving home, I started an fsck.ext4 on a filesystem (500GB) |
| 5 |
>> that resides on a disk that I suspect is damaged: |
| 6 |
>> |
| 7 |
>> fsck.ext4 -c -c -f /dev/sdb1 |
| 8 |
>> |
| 9 |
>> |
| 10 |
> You can check the SMART (Self-Monitoring, Analysis, and Reporting |
| 11 |
> Technology) data, which is built-in in all hard drives today, and allows |
| 12 |
> you to see the status or overall “health” of a hard drive. |
| 13 |
> |
| 14 |
> ( smartctl -a /dev/sdb ) |
| 15 |
> |
| 16 |
> |
| 17 |
|
| 18 |
You can also tell it to run a selftest too. Example commands to look into: |
| 19 |
|
| 20 |
smartctl -t long /dev/<your drive here> |
| 21 |
|
| 22 |
and for the results, usually a good while later: |
| 23 |
|
| 24 |
smartctl -l selftest /dev/<your drive here> |
| 25 |
|
| 26 |
If you think heat may be a issue, try this: |
| 27 |
|
| 28 |
smartctl -a /dev/<your drive here> | grep Temp |
| 29 |
|
| 30 |
With all this, you should be able to find out if you are good to go or |
| 31 |
got a drive going bad. |
| 32 |
|
| 33 |
Dale |
| 34 |
|
| 35 |
:-) :-) |
Archives