JorgeB

Yep, have the same one for a couple of months, note that this is a fairly new controller but all indications are that it works great with Unraid.

Thanks for reporting back.

Yes, I've seen it a few times on the forum before with Ryzen boards, the SATA controller stops responding.

Diags are after a reboot so we can't see what happened, but the description suggests a controller issue, for now resync parity, if it happens again grab diags before rebooting.

You're trying to use a device (af:00.0) that doesn't exist, remove it from the xml.

There are also ATA errors on disk3, you should also check/replace those cables.

if 4 ports are enough get a 4/5 port controller based on the JMB585 chipset, or get one of the recommended 8 port LSI controllers.

Yes, you're right, it was something related to the docker network: Feb 17 22:31:46 Shed kernel: IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready Glad it's fixed.

Run a long SMART test.

That one has a port multiplier and it's not recommended, if 4 ports are enough get a 4/5 port controller based on the JMB585 chipset, or get one of the recommended 8 port LSI controllers.

Rebooting should fix it.

See if this helps: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

Some Ryzen related info here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

After a correcting check you should always get 0 errors, suggest running memtest

Feb 17 17:14:50 unraid kernel: BTRFS warning (device nvme0n1p1): chunk 4462761476096 missing 1 devices, max tolerance is 0 for writeable mount Pool wasn't redundant, possibly because of this bug, you should still be able to recover some data using these options, but if part of the metadata is missing it might fail or be incomplete.

SAS disks are having issues when formatting: Feb 16 13:42:28 Meningitis kernel: sd 1:0:0:0: [sdb] tag#2460 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 16 13:42:28 Meningitis kernel: sd 1:0:0:0: [sdb] tag#2460 Sense Key : 0xb [current] [descriptor] Feb 16 13:42:28 Meningitis kernel: sd 1:0:0:0: [sdb] tag#2460 <<vendor>>ASC=0x81 ASCQ=0x0 Feb 16 13:42:28 Meningitis kernel: sd 1:0:0:0: [sdb] tag#2460 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 Feb 16 13:42:28 Meningitis kernel: print_req_error: I/O error, dev sdb, sector 0 Feb 16 13:42:28 Meningitis kernel: sd 1:0:0:0: [sdb] tag#2463 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 16 13:42:28 Meningitis kernel: sd 1:0:0:0: [sdb] tag#2463 Sense Key : 0xb [current] [descriptor] Feb 16 13:42:28 Meningitis kernel: sd 1:0:0:0: [sdb] tag#2463 <<vendor>>ASC=0x81 ASCQ=0x0 Feb 16 13:42:28 Meningitis kernel: sd 1:0:0:0: [sdb] tag#2463 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 00 08 00 00 00 20 00 00 Feb 16 13:42:28 Meningitis kernel: print_req_error: I/O error, dev sdb, sector 8 Feb 16 13:42:28 Meningitis kernel: sd 1:0:0:0: [sdb] tag#2464 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 16 13:42:28 Meningitis kernel: sd 1:0:0:0: [sdb] tag#2464 Sense Key : 0xb [current] [descriptor] Feb 16 13:42:28 Meningitis kernel: sd 1:0:0:0: [sdb] tag#2464 <<vendor>>ASC=0x81 ASCQ=0x0 Feb 16 13:42:28 Meningitis kernel: sd 1:0:0:0: [sdb] tag#2464 CDB: opcode=0x8a 8a 00 00 00 00 01 5d 50 a3 88 00 00 00 28 00 00 Feb 16 13:42:28 Meningitis kernel: print_req_error: I/O error, dev sdb, sector 5860533128 Feb 16 13:42:28 Meningitis kernel: sd 1:0:0:0: [sdb] tag#2469 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 16 13:42:28 Meningitis kernel: sd 1:0:0:0: [sdb] tag#2469 Sense Key : 0xb [current] [descriptor] Feb 16 13:42:28 Meningitis kernel: sd 1:0:0:0: [sdb] tag#2469 <<vendor>>ASC=0x81 ASCQ=0x0 Feb 16 13:42:28 Meningitis kernel: sd 1:0:0:0: [sdb] tag#2469 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 Can't tell you the reason though, try formatting them elsewhere or with a different controller to try and rule things out.

Old bug, error isn't helpful:

Does it work if you boot in safe mode?

Start by recreating the flash drive with current release, first backup the config folder, recreate flash with USB tool, then restore config folder, it it still doesn't boot you can downgrade by replacing the bz* files with the ones from an older release, keeping your config.

If there were any unclean shutdowns a few sync errors are normal after that.

Disk2 should be backed up and re-formatted, a btrfs filesystem will quick corrupt with bad hardware, like bad RAM, check this to make sure your RAM isn't being overclocked, which is a known cause of data corruption with some Ryzen systems.

Check filesystem on disk1, disk3 looks healthy, you can rebuild on top.

Please post v6.8 diags.

Look for CA Appdata Backup

Can't tell you what happened, on the diags posted it was already like that at boot time so can't see if something wiped it, and if it failed it doesn't really matter how many moths it has, any device can fail at any time.