Issues with my shares. with 6.6.0-rc1 to rc4

Can't do anything without seeing diagnostics.zip captured when issue is happening.

Changed Status to Retest

Oh ok, I am sorry. I will upgrade again. and do that. Cuz I will get this error again. It seems to happen when something is being transcoded though. I will attach that zip when I have the problem again. I do have a log zip that i downloaded. 

Around the time of the error these errors occured.

 

Sep 18 20:57:36 FischersMedia kernel: BTRFS warning (device md3): md3 checksum verify failed on 450625536 wanted 39C8DAEA found CF6E462F level 0
Sep 18 21:08:12 FischersMedia kernel: ata10.00: exception Emask 0x10 SAct 0x0 SErr 0x400000 action 0x6 frozen
Sep 18 21:08:12 FischersMedia kernel: ata10.00: irq_stat 0x08000000, interface fatal error
Sep 18 21:08:12 FischersMedia kernel: ata10: SError: { Handshk }
Sep 18 21:08:12 FischersMedia kernel: ata10.00: failed command: WRITE DMA EXT
Sep 18 21:08:12 FischersMedia kernel: ata10.00: cmd 35/00:00:30:92:40/00:02:22:00:00/e0 tag 26 dma 262144 out
Sep 18 21:08:12 FischersMedia kernel:         res 50/00:00:6f:65:db/00:00:21:00:00/e0 Emask 0x10 (ATA bus error)
Sep 18 21:08:12 FischersMedia kernel: ata10.00: status: { DRDY }
Sep 18 21:08:12 FischersMedia kernel: ata10: hard resetting link
Sep 18 21:08:12 FischersMedia kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Sep 18 21:08:12 FischersMedia kernel: ata10.00: configured for UDMA/133
Sep 18 21:08:12 FischersMedia kernel: ata10: EH complete
Sep 18 22:04:25 FischersMedia kernel: BTRFS warning (device md3): md3 checksum verify failed on 22380544 wanted 1D6EB673 found 7DA15F35 level 0
Sep 18 22:04:25 FischersMedia kernel: BTRFS: error (device md3) in btrfs_finish_ordered_io:3088: errno=-5 IO failure

 

I will get the Diagnostic.zip file when it happens again. 

Those are hardware problems, also there's data corruption on disk3 (can't say if it's ATA10 without the diags), but check SMART and run a scrub on it.

 

 

Edited September 19, 2018 by johnnie.black

Oh ok, I will. there are no smart errors on it. That would make sense. Not sure why it never messed up on the older version of Unraid. But it makes sense that it writes just fine to the cache drive, but not the array disks. It is probably trying to write to disk 3 maybe.