Re: Corrupted files support needed

[Roman Mamedov <rm@romanrm.net>]

On Tue, 16 Apr 2019 09:46:39 +0200
Daniel Brunner <daniel@brunner.ninja> wrote:

> Hi,
> 
> thanks for the quick response.
> 
> The filesystem went read-only on its own right at the first read error.
> I unmounted all mounts and rebooted (just to be sure).
> 
> I ran the command you suggested with --progress
> All output is flushed away with thousands of lines like those at the
> end of the log paste.
> 
> Does it make sense to let it run until the end or can I assume that 2
> drives are bad?
> Also I checked SMART values but they seem to be ok.
> 
> https://0x0.st/zNg6.log

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
190 Airflow_Temperature_Cel 0x0022   047   031   040    Old_age   Always   In_the_past 53 (Min/Max 47/53 #5115)

This seems to be normalized as VALUE=100-RAW_VALUE by the SMART firmware, and
looking at the reading in WORST, indicates that some of your drives earlier
have seen temperatures of as high as 69 C.

This is insanely hot to run your drives at, I'd say to the point of "shut off
everything ASAP via the mains breaker to avoid immediate permanent damage";

Not sure if it's related to the csum errors at hand, but it very well might be.

Even the current temps of 55-60 are about 15-20 degrees higher than ideal.

-- 
With respect,
Roman