| 1 |
"Caveman Al Toraboran" <toraboracaveman@××××××××××.com>, 22.03.2020, 02:29: |
| 2 |
|
| 3 |
> On Saturday, March 21, 2020 8:03 PM, Stefan Schmiedl <s@×××.de> wrote: |
| 4 |
|
| 5 |
>> "Caveman Al Toraboran" toraboracaveman@××××××××××.com, 21.03.2020, 14:49: |
| 6 |
>> |
| 7 |
>> > questions: |
| 8 |
>> > * what's going on? |
| 9 |
>> > * how to find out? |
| 10 |
>> |
| 11 |
>> "dmesg -T" is your friend. It should show the error messages |
| 12 |
>> with their timestamps. |
| 13 |
>> |
| 14 |
>> > * how to fix? |
| 15 |
>> |
| 16 |
>> For spinning HDs: |
| 17 |
>> |
| 18 |
>> If the error messages point towards faulty sectors that can't be |
| 19 |
>> written, get a new drive and migrate your data. If the messages |
| 20 |
>> don't contain sectors, check and/or replace the cabling. If the |
| 21 |
>> problem persists, get a new drive etc... |
| 22 |
|
| 23 |
> i get this: http://codepad.org/MVeqeBBu |
| 24 |
> it mentions "sector", but not sure if it is what you mean. |
| 25 |
|
| 26 |
Messages like |
| 27 |
>> [sda] tag#6 Sense Key : Medium Error [current] |
| 28 |
>> [sda] tag#6 Add. Sense: Unrecovered read error - auto reallocate failed |
| 29 |
usually point towards towards problems with the magnetic layer |
| 30 |
on the disk. These do not get better over time, they only get |
| 31 |
worse. |
| 32 |
|
| 33 |
Then we have "auto reallocate failed", which means that the HD |
| 34 |
controller tried to reassign the damaged sector to another working |
| 35 |
sector, unsuccessfully. |
| 36 |
|
| 37 |
|
| 38 |
> what do you think? |
| 39 |
|
| 40 |
If there is anything of value on the disk, get a new one right now. |
| 41 |
|
| 42 |
Good luck, |
| 43 |
s. |
Archives