‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, March 21, 2020 8:03 PM, Stefan Schmiedl <s...@xss.de> wrote:
> "Caveman Al Toraboran" toraboracave...@protonmail.com, 21.03.2020, 14:49: > > > questions: > > * what's going on? > > * how to find out? > > "dmesg -T" is your friend. It should show the error messages > with their timestamps. > > > * how to fix? > > For spinning HDs: > > If the error messages point towards faulty sectors that can't be > written, get a new drive and migrate your data. If the messages > don't contain sectors, check and/or replace the cabling. If the > problem persists, get a new drive etc... i get this: http://codepad.org/MVeqeBBu it mentions "sector", but not sure if it is what you mean. what do you think?
