Hello everybody,

 

recently my unraid log is getting flooded by a BTRFS Error

Oct  3 06:55:10 unraid kernel: sd 12:0:0:0: [sdh] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s
Oct  3 06:55:10 unraid kernel: sd 12:0:0:0: [sdh] tag#15 CDB: opcode=0x28 28 00 00 61 b4 00 00 00 20 00
Oct  3 06:55:10 unraid kernel: blk_update_request: I/O error, dev sdh, sector 6403072 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0
Oct  3 06:55:10 unraid kernel: BTRFS error (device sdi1): bdev /dev/sdh1 errs: wr 1, rd 4820158, flush 0, corrupt 0, gen 0
Oct  3 06:55:11 unraid kernel: sd 36:0:0:0: [sdi] tag#14 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s
Oct  3 06:55:11 unraid kernel: sd 36:0:0:0: [sdi] tag#14 CDB: opcode=0x28 28 00 00 61 14 00 00 00 20 00
Oct  3 06:55:11 unraid kernel: blk_update_request: I/O error, dev sdi, sector 6362112 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0
Oct  3 06:55:11 unraid kernel: BTRFS error (device sdi1): bdev /dev/sdi1 errs: wr 1, rd 4820159, flush 0, corrupt 0, gen 0

The errors produced from an unused btrfs pool, which i created in the past to use it only for docker. (i have never moved something to it, it is empty)

Its a bunch of old SSDs and i have no clue why this error appear nor how to solve it.
 

If you have any advise how to solve the problem, would be great.

 

many thanks in advance

 

unraid-diagnostics-20221003-0716.zip

Log is showing device issues, but since it already rotated cannot see the beginning of the problem please reboot and post new diags after array start.

Two of the ssd's were missing after the reboot. And i didn't get them to work on other sata ports. So I tried to recreated the pool with the four left over ssd's.

Currently there is seems to be no problem with the four left over, but i am unsure if it is save to use for the docker.img?

unraid-diagnostics-20221003-2138.zip

Edited October 3, 20223 yr by Khinsu

Looks OK for now.