| 1 |
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ |
| 2 |
On Saturday, March 21, 2020 8:03 PM, Stefan Schmiedl <s@×××.de> wrote: |
| 3 |
|
| 4 |
> "Caveman Al Toraboran" toraboracaveman@××××××××××.com, 21.03.2020, 14:49: |
| 5 |
> |
| 6 |
> > questions: |
| 7 |
> > * what's going on? |
| 8 |
> > * how to find out? |
| 9 |
> |
| 10 |
> "dmesg -T" is your friend. It should show the error messages |
| 11 |
> with their timestamps. |
| 12 |
> |
| 13 |
> > * how to fix? |
| 14 |
> |
| 15 |
> For spinning HDs: |
| 16 |
> |
| 17 |
> If the error messages point towards faulty sectors that can't be |
| 18 |
> written, get a new drive and migrate your data. If the messages |
| 19 |
> don't contain sectors, check and/or replace the cabling. If the |
| 20 |
> problem persists, get a new drive etc... |
| 21 |
|
| 22 |
i get this: http://codepad.org/MVeqeBBu |
| 23 |
it mentions "sector", but not sure if it is what you mean. |
| 24 |
|
| 25 |
what do you think? |
Archives