JorgeB

Try deleting from the cfg.

By swapping the cables on the HBA, if the problem follows the port it's not correctly flashed.

Disk1 is dropping offline: Jun 10 23:27:10 Do-Minion kernel: usb 2-2: USB disconnect, device number 3 Jun 10 23:27:10 Do-Minion kernel: scsi 3:0:0:0: rejecting I/O to dead device Jun 10 23:27:10 Do-Minion kernel: print_req_error: I/O error, dev sdd, sector 466674336 Jun 10 23:27:10 Do-Minion kernel: md: disk1 read error, sector=466674272 Jun 10 23:27:10 Do-Minion kernel: md: disk1 read error, sector=466674280 We really discourage using USB disks as array devices.

Check filesystem on disk6: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui Disk is usually a bad SATA cable, replace it.

Last unofficial information I have is that this issue is hopefully fixed and the fix will be in v6.9-rc1 which is expected soon™, no idea if a patch/update for v6.8 will be available, but very much doubt that as LT doesn't usually patch older releases after a newer one is in active development, maybe if it was a critical security issue. Also, and completely by accident I might have found a "fix" for current users, at least it's working for be and it's repeatable, this is iotop after 5 minutes with just the plex docker installed (which appears to be one of the most active): The "fix" is using the mover to move the docker image to the array (docker service must be stopped first and share set to cache="yes") then back to the cache device (set share to cache="prefer"), start the docker service back up and this is the same docker image running for 5 minutes after the move: So a 10x decrease in write activity, please try and let me known if it helps.

You need to reset the array errors, I believe just clicking "Clear Stats" next to start/stop array in sufficient, if not re-start the array or reboot.

"Problem" is that those values are not 0, hence the warnings, UDMA CRC is usually a connection issue, like bad a SATA cable, other ones are a disk issue, but as long as they remain stable it should be OK, you can also run an extended SMART test on that disk.

Cache filesystem is corrupt and going read-only, hence then the docker image errors, backup cache, re-format and restore the data.

You can just upgrade current parity first and when that's done add the old parity as a data disk, alternatively you can a new config to do both things at the same time (though with some increased risk).

Please post the diagnostics: Tools -> Diagnostics

There's no driver for that NIC, it should work with v6.9-beta1.

You can try resetting the network, delete/rename network.cfg and network-rules.cfg (both on the flash's config folder) then reboot and re-config the lan.

Yes, but you should avoid the SASLP as it has various known issues with Unraid.

Nothing jumping out, though you're using a RAID controller and those are not recommended, they can sometimes have unpredictable performance issues, cancel/pause the sync and run a diskspeed test to check disks are performing normally.

Please post new diags.

You can try this, also look for a BIOS update. P.S. for the future just post the complete diagnostics.zip.

If you mean Nextcloud best bet is to use the existing support thread, you can find it by clicking on the docker:

You could try v6.9-beta1, if it was working before it could be a kernel/driver issue.

Jun 10 15:49:36 Tower kernel: usb 2-3: Disable of device-initiated U1 failed. Jun 10 15:49:42 Tower kernel: usb 2-3: Disable of device-initiated U2 failed. Looks like a problem with the USB controller/HUB, try a port on different one if available.

CRC errors are a connection problem, most times the SATA cable, but it can also be the controller, backplane, etc, start by replacing the SATA cable, and note that the attribute doesn't reset, so as long as it doesn't keep increasing the problem is solved.

Please do but start a new topic, and make sure you also post the diagnostics, ideally before rebooting.

It's still the easiest way.

Plus key allows up to 12 connected devices, you currently have 13.

loop2 is usually the docker image, please post the diagnostics: Tools -> Diagnostics

Changed Status to Closed Changed Priority to Other