On 2019-12-26 9:05 a.m., Leszek Dubiel wrote:

> 
> I didn't use Raid6, but Raid0.
> 
> 
> Yes I have chcecked dmesg in first place (see original mail).
> 
> Btrfs no error logged.
> 

I'm sorry, that was reading comprehension failure on my part.

But regardless, your dmesg clearly shows drive read failures, (to be
expected with a drive clearly in a failing state.)

Recovery of Raid0 with a faulty drive is a job for restore from backup,
(or attempt to scrape what you can with array mounted ro).. That's what
Raid0 *means*.



Dec 22 19:20:11 wawel kernel: [ 5912.116874] ata1.00: exception Emask
0x0 SAct 0x1f80 SErr 0x0 action 0x0
Dec 22 19:20:11 wawel kernel: [ 5912.116878] ata1.00: irq_stat 0x40000008
Dec 22 19:20:11 wawel kernel: [ 5912.116880] ata1.00: failed command:
READ FPDMA QUEUED
Dec 22 19:20:11 wawel kernel: [ 5912.116882] ata1.00: cmd
60/00:38:00:00:98/0a:00:45:01:00/40 tag 7 ncq dma 1310720 in
Dec 22 19:20:11 wawel kernel: [ 5912.116882]          res
43/40:18:e8:05:98/00:04:45:01:00/40 Emask 0x409 (media error) <F>
Dec 22 19:20:11 wawel kernel: [ 5912.116885] ata1.00: status: { DRDY
SENSE ERR }
Dec 22 19:20:11 wawel kernel: [ 5912.116886] ata1.00: error: { UNC }
Dec 22 19:20:11 wawel kernel: [ 5912.153695] ata1.00: configured for
UDMA/133
Dec 22 19:20:11 wawel kernel: [ 5912.153707] sd 0:0:0:0: [sda] tag#7
FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Dec 22 19:20:11 wawel kernel: [ 5912.153709] sd 0:0:0:0: [sda] tag#7
Sense Key : Medium Error [current]
Dec 22 19:20:11 wawel kernel: [ 5912.153710] sd 0:0:0:0: [sda] tag#7
Add. Sense: Unrecovered read error - auto reallocate failed
Dec 22 19:20:11 wawel kernel: [ 5912.153711] sd 0:0:0:0: [sda] tag#7
CDB: Read(16) 88 00 00 00 00 01 45 98 00 00 00 00 0a 00 00 00
Dec 22 19:20:11 wawel kernel: [ 5912.153712] print_req_error: I/O error,
dev sda, sector 5462556672
Dec 22 19:20:11 wawel kernel: [ 5912.153724] ata1: EH complete

I'm assuming that /dev/sda is the the drive you already identified as
failing,, if not, you're totally hosed.