JorgeB

One pass might not be enough, 24 hours are recommended, you can also post new diags after two consecutive parity checks, it can give a better idea of the issue.

https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive Recommend replacing/swapping cables before though, to rule them out if it happens again.

Docker image is mounting correctly, but by the transid it's brand new, you should be able to restore previous dockers (assuming appdata is OK)

If the extended SMART passed disk is OK for now, rebooting will clear the array errors, possibly even just clicking "clear stats" button on main page, not sure.

Start by running memtest.

Possibly.

There's a problem detecting the USB device even after multiple tries: Apr 10 17:50:57 Tower kernel: usb 1-6: new high-speed USB device number 4 using xhci_hcd Apr 10 17:51:03 Tower kernel: usb 1-6: unable to get BOS descriptor set Apr 10 17:51:08 Tower kernel: usb 1-6: unable to read config index 0 descriptor/start: -110 Apr 10 17:51:08 Tower kernel: usb 1-6: can't read configurations, error -110 Apr 10 17:51:08 Tower kernel: usb 1-6: new high-speed USB device number 5 using xhci_hcd Apr 10 17:51:14 Tower kernel: usb 1-6: unable to get BOS descriptor set Apr 10 17:51:19 Tower kernel: usb 1-6: unable to read config index 0 descriptor/start: -110 Apr 10 17:51:19 Tower kernel: usb 1-6: can't read configurations, error -110 Apr 10 17:51:19 Tower kernel: usb usb1-port6: attempt power cycle Apr 10 17:51:20 Tower kernel: usb 1-6: new high-speed USB device number 6 using xhci_hcd Apr 10 17:51:25 Tower kernel: usb 1-6: unable to read config index 0 descriptor/all Apr 10 17:51:25 Tower kernel: usb 1-6: can't read configurations, error -110 Apr 10 17:51:25 Tower kernel: usb 1-6: new high-speed USB device number 7 using xhci_hcd Apr 10 17:51:31 Tower kernel: usb 1-6: unable to get BOS descriptor set Apr 10 17:51:36 Tower kernel: usb 1-6: unable to read config index 0 descriptor/start: -110 Apr 10 17:51:36 Tower kernel: usb 1-6: can't read configurations, error -110 Apr 10 17:51:36 Tower kernel: usb usb1-port6: unable to enumerate USB device Try a different port but it's likely some problem with the enclosure itself.

Harder to find when the log is full with other issues, reboot and after array start connect the USB drive, then post new diags.

Yes, but like mentioned it won't show up if the board has legacy boot (CSM) disable. Board. Devices only show up on the LSI BIOS, not the board.

It already works (for new XFS filesystems)

That's up to you, it just working as it supposed to.

Seems unlikely that would be the issue. This would make more sense, but please keep us updated.

No, sorry. NTFS will work but only as unassigned devices, never on the array.

Before thinking of that I would worry about disk13 read errors: Apr 10 01:12:29 Tower kernel: ata7.00: configured for UDMA/33 Apr 10 01:12:29 Tower kernel: ata7: EH complete Apr 10 01:12:29 Tower kernel: ata7.00: exception Emask 0x50 SAct 0x8000000 SErr 0x4890800 action 0xe frozen Apr 10 01:12:29 Tower kernel: ata7.00: irq_stat 0x0c400040, interface fatal error, connection status changed Apr 10 01:12:29 Tower kernel: ata7: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch } Apr 10 01:12:29 Tower kernel: ata7.00: failed command: READ FPDMA QUEUED Apr 10 01:12:29 Tower kernel: ata7.00: cmd 60/00:d8:90:37:3a/01:00:00:00:00/40 tag 27 ncq dma 131072 in Apr 10 01:12:29 Tower kernel: res 40/00:00:90:37:3a/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Apr 10 01:12:29 Tower kernel: ata7.00: status: { DRDY } Apr 10 01:12:29 Tower kernel: ata7: hard resetting link Apr 10 01:12:34 Tower kernel: ata7: link is slow to respond, please be patient (ready=0) Apr 10 01:12:39 Tower kernel: ata7: COMRESET failed (errno=-16) Apr 10 01:12:39 Tower kernel: ata7: hard resetting link Apr 10 01:12:40 Tower kernel: ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 10 01:12:42 Tower kernel: ata7.00: configured for UDMA/33 Apr 10 01:12:42 Tower kernel: sd 7:0:0:0: [sdo] tag#27 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Apr 10 01:12:42 Tower kernel: sd 7:0:0:0: [sdo] tag#27 Sense Key : 0x5 [current] Apr 10 01:12:42 Tower kernel: sd 7:0:0:0: [sdo] tag#27 ASC=0x21 ASCQ=0x4 Apr 10 01:12:42 Tower kernel: sd 7:0:0:0: [sdo] tag#27 CDB: opcode=0x88 88 00 00 00 00 00 00 3a 37 90 00 00 01 00 00 00 Apr 10 01:12:42 Tower kernel: print_req_error: I/O error, dev sdo, sector 3815312 Apr 10 01:12:42 Tower kernel: md: disk13 read error, sector=3815248 Apr 10 01:12:42 Tower kernel: md: disk13 read error, sector=3815256 Apr 10 01:12:42 Tower kernel: md: disk13 read error, sector=3815264 Apr 10 01:12:42 Tower kernel: md: disk13 read error, sector=3815272 Apr 10 01:12:42 Tower kernel: md: disk13 read error, sector=3815280 Apr 10 01:12:42 Tower kernel: md: disk13 read error, sector=3815288 Apr 10 01:12:42 Tower kernel: md: disk13 read error, sector=3815296 Looks like a connection problem.

Link detected: no Check LAN cable/switch

Dis29 is parity2, which dropped offline, disk look OK, so likely a connection/power issue.

You're having issues with multiple drives on the onboard SATA controller, likely a connection or power problem.

Any unclean shutdown since last check? If not run another one and post new diags if there are more errors.

File integrity plugin running?

If the LSI BIOS loads you can enter it and there are some settings that can be changed, but nothing that matters for this, it's enough to see the listed drives, BIOS will only show if legacy boot is enable in the board BIOS, also depending on the board you might need to enable OPT ROM or similar in general or for that PCIe slot, note that the LSI BIOS is not required for Unraid to detect the drives, but since your LSI has one it can be used for troubleshooting. There are some unusual repeating errors but likely unrelated to current issues, bios update might help though: Apr 9 06:53:41 nRy kernel: EDAC sbridge: Seeking for: PCI ID 8086:2fb9 Apr 9 06:53:41 nRy kernel: EDAC sbridge: Seeking for: PCI ID 8086:2fbb (repeats a lot of times for different PCI IDs) Apr 9 06:53:41 nRy kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled Apr 9 06:53:41 nRy kernel: EDAC sbridge: Couldn't find mci handler Apr 9 06:53:41 nRy kernel: EDAC sbridge: Failed to register device with error -19.

They certainly aren't part of a default install, posting the diagnostics might give some clues, you can also try booting in safe mode without any dockers.

Yep, I posted that above a couple of days ago, see if it crashes mounting manually, or just make it unmoutable and start the array, you can do that by changing the filesystem on that disk to another one, just don't format it after array start.

If it's showing 120GB total space it's done.

Like mentioned without diags not much we can see, try to sync again and post diags if the same happens (before rebooting).