| 1 |
Michael wrote: |
| 2 |
> On Sunday, 22 March 2020 07:53:18 GMT Stefan Schmiedl wrote: |
| 3 |
>> "Caveman Al Toraboran" <toraboracaveman@××××××××××.com>, 22.03.2020, 02:29: |
| 4 |
>>> On Saturday, March 21, 2020 8:03 PM, Stefan Schmiedl <s@×××.de> wrote: |
| 5 |
>>>> "Caveman Al Toraboran" toraboracaveman@××××××××××.com, 21.03.2020, 14:49: |
| 6 |
>>>>> questions: |
| 7 |
>>>>> * what's going on? |
| 8 |
>>>>> * how to find out? |
| 9 |
>>>> "dmesg -T" is your friend. It should show the error messages |
| 10 |
>>>> with their timestamps. |
| 11 |
>>>> |
| 12 |
>>>>> * how to fix? |
| 13 |
>>>> For spinning HDs: |
| 14 |
>>>> |
| 15 |
>>>> If the error messages point towards faulty sectors that can't be |
| 16 |
>>>> written, get a new drive and migrate your data. If the messages |
| 17 |
>>>> don't contain sectors, check and/or replace the cabling. If the |
| 18 |
>>>> problem persists, get a new drive etc... |
| 19 |
>>> i get this: http://codepad.org/MVeqeBBu |
| 20 |
>>> it mentions "sector", but not sure if it is what you mean. |
| 21 |
>> Messages like |
| 22 |
>> |
| 23 |
>> >> [sda] tag#6 Sense Key : Medium Error [current] |
| 24 |
>> >> [sda] tag#6 Add. Sense: Unrecovered read error - auto reallocate failed |
| 25 |
>> |
| 26 |
>> usually point towards towards problems with the magnetic layer |
| 27 |
>> on the disk. These do not get better over time, they only get |
| 28 |
>> worse. |
| 29 |
>> |
| 30 |
>> Then we have "auto reallocate failed", which means that the HD |
| 31 |
>> controller tried to reassign the damaged sector to another working |
| 32 |
>> sector, unsuccessfully. |
| 33 |
>> |
| 34 |
>>> what do you think? |
| 35 |
>> If there is anything of value on the disk, get a new one right now. |
| 36 |
>> |
| 37 |
>> Good luck, |
| 38 |
>> s. |
| 39 |
> What Stefan said - the disk is on its way out and autorecovery of bad sectors |
| 40 |
> is failing. You could run: |
| 41 |
> |
| 42 |
> smartctl -a /dev/sda |
| 43 |
> |
| 44 |
> to see what errors it reports, but in the first instance if the data on this |
| 45 |
> disk is valuable I suggest you get another disk and *immediately* transfer all |
| 46 |
> useful/recoverable files off this drive. If the value of the data is not |
| 47 |
> high/irreplaceable, then carry on using it - it may take years and years |
| 48 |
> before it fails completely. |
| 49 |
> |
| 50 |
> To reallocate a bad block on your disk and hope more won't arrive overnight, |
| 51 |
> have a read at this page: |
| 52 |
> |
| 53 |
> https://www.smartmontools.org/wiki/BadBlockHowto |
| 54 |
|
| 55 |
|
| 56 |
Just to add something to think about. I can't recall how SMART says |
| 57 |
this but a drive that failed on me several years ago said the drive was |
| 58 |
dying and it was going to die soon, I think 24 hours was mentioned. I |
| 59 |
unmounted that drive and removed power until I had a replacement drive. |
| 60 |
Once the replacement drive came in, I hooked the drive back up and |
| 61 |
copied the data over to the new drive. I seem to recall I had a couple |
| 62 |
pics and a couple text files that were corrupted. I might also add, I |
| 63 |
started running some tests on the drive and it died a few hours later. |
| 64 |
I could hear it spin but it wouldn't even mount anymore. |
| 65 |
|
| 66 |
If you see something similar to that, I suggest you take action since it |
| 67 |
could be accurate. It was in my case. If the data has no value or you |
| 68 |
have known good backups, then it may not matter so much. |
| 69 |
|
| 70 |
Dale |
| 71 |
|
| 72 |
:-) :-) |
Archives