On 2018-11-19, E <n...@p...pl> wrote:
> Error 426 [17] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
> When the command that caused the error occurred, the device was in an unknown
state.
>
> After command completion occurred, registers were:
> ER -- ST COUNT LBA_48 LH LM LL DV DC
> -- -- -- == -- == == == -- -- -- -- --
> 40 -- 00 00 08 00 51 00 00 e0 00 00 00
>
> Commands leading to the command that caused the error were:
> CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
> -- == -- == -- == == == -- -- -- -- -- --------------- --------------------
> 00 76 25 08 7c 00 00 00 00 00 00 00 00 00:00:00.000 NOP [Reserved
subcommand] [OBS-ACS-2]
> 00 08 00 00 00 07 31 00 8a 25 00 00 00 00:00:00.008 NOP [Abort queued
commands]
> 00 a0 b0 06 97 00 08 00 00 00 00 00 00 00:07:12.033 NOP [Reserved
subcommand] [OBS-ACS-2]
> 00 08 00 00 a0 06 15 12 89 25 00 00 00 00:00:57.345 NOP [Abort queued
commands]

Może inni coś więcej z tego wyciągną, ale ja nie widzę niczego jakoś
silnie niepokojącego. Te błędy to może być np. poluzowany kabel sata lub
coś w podobnym stylu.

Zapuść proszę, najpierw:

smartctl -d sat -t short /dev/sdb
wyniki w sekcji SMART Self-tests log ......

A jeśli nie zwróci błędów to długi:

smartctl -d sat -t long /dev/sdb
To protrwa.
Status możesz sprawdzać smartctl -a -d sat /dev/sdb|grep remaining

--
Marcin