JorgeB

Aug 18 01:17:33 Messiah kernel: FAT-fs (sda1): Directory bread(block 29687) failed Aug 18 01:17:33 Messiah kernel: FAT-fs (sda1): Directory bread(block 29688) failed Flash drive problems, try reformatting it and restoring from a backup, if available.

Aug 18 08:34:36 Bigboii rc.docker: binhex-couchpotato-git: Error response from daemon: network 255d84a6579f8c87400791f1109ebd9bb1f2a41a504ab97fb3a4f3e9d722e26c not found Aug 18 08:34:36 Bigboii rc.docker: Error: failed to start containers: binhex-couchpotato-git Aug 18 08:34:36 Bigboii rc.docker: binhex-sickchill: Error response from daemon: network 255d84a6579f8c87400791f1109ebd9bb1f2a41a504ab97fb3a4f3e9d722e26c not found Aug 18 08:34:36 Bigboii rc.docker: Error: failed to start containers: binhex-sickchill Aug 18 08:34:36 Bigboii rc.docker: binhex-syncthing: Error response from daemon: network 255d84a6579f8c87400791f1109ebd9bb1f2a41a504ab97fb3a4f3e9d722e26c not found Aug 18 08:34:36 Bigboii rc.docker: Error: failed to start containers: binhex-syncthing Aug 18 08:34:36 Bigboii rc.docker: Unifi: Error response from daemon: network 255d84a6579f8c87400791f1109ebd9bb1f2a41a504ab97fb3a4f3e9d722e26c not found Aug 18 08:34:36 Bigboii rc.docker: Error: failed to start containers: Unifi Some containers are failing to start, not sure what these errors mean though, maybe something is not ready yet, someone else might know what they are about.

Those appear to be just after a reboot, also post the new xfs_repair output.

Check the system/IPMI event log, there might be more info there.

This is used for VMs, not docker, posting diagnostics might show something.

When you add a drive to a pool a full balance is done do data is redistributed by all devices, this can take a long time depending on the data size.

No it doesn't, maybe because it has 4 letters, @dlandonplease take a look.

This suggests a hardware issue but you can enable syslog mirror to flash then post that log to see if it catches anything.

This suggests a hardware issue, please post diags after running xfs_repair.

Yep.

UD settings:

No, that's normal, since they are the same filesystem, and you can't have both mounted at the same time, note that the UUID can be changed in UD if needed.

There's nothing logged about the crash: Aug 16 23:01:10 Orcrist rc.inet1: ip link set lo down Aug 17 08:06:25 Orcrist kernel: microcode: microcode updated early to revision 0xde, date = This usually indicates a hardware problem.

Yes. With the Community Apps plugin.

Unlikely i it's a Supermicro backplane, what model is it?

Except these: ug 16 11:20:32 mitchsserver kernel: ata1: link is slow to respond, please be patient (ready=0) Aug 16 11:20:32 mitchsserver kernel: ata4: link is slow to respond, please be patient (ready=0) Aug 16 11:20:32 mitchsserver kernel: ata3: link is slow to respond, please be patient (ready=0) Aug 16 11:20:32 mitchsserver kernel: ata2: link is slow to respond, please be patient (ready=0) Aug 16 11:20:32 mitchsserver kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 16 11:20:32 mitchsserver kernel: ata2.00: configured for UDMA/133 Aug 16 11:20:32 mitchsserver kernel: ata1: COMRESET failed (errno=-16) Aug 16 11:20:32 mitchsserver kernel: ata3: COMRESET failed (errno=-16) Aug 16 11:20:32 mitchsserver kernel: ata4: COMRESET failed (errno=-16) Aug 16 11:20:32 mitchsserver kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 16 11:20:32 mitchsserver kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 16 11:20:32 mitchsserver kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 16 11:20:32 mitchsserver kernel: ata1.00: configured for UDMA/133 Aug 16 11:20:32 mitchsserver kernel: ata4.00: configured for UDMA/133 Aug 16 11:20:32 mitchsserver kernel: ata3.00: configured for UDMA/133 This are hardware, usually power or controller related.

All those errors appear to come from the plugin, please use the existing support thread or remove it.

Then you can rebuild on top, recommend replacing/swapping cables/slot to rule that out if it happens again to the same disk. https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

What errors? If you mean the problem with FCP looks like it's crashing, no one can help more than the plugin author, if there are other issues please describe them, if not please use only the existing plugin support thread.

With 12 disks or more you should use dual link.

Looks like the common AMD controller issue that happens with some Ryzen boards, best bet is to not use the SATA ports, or use a different board.

Just need one, though most will have at least two, and using two you'll have more bandwidth, but not really needed for 10 disks.

Only when you're on that topic: And as far as I remember it's always been like that.

You can also try it in a different slot to see if there's any difference.