JorgeB

You're having issues with multiple disks, this is usually a power/connection problem, also note that SAS2LP controllers are not recommended, but that's not the only reason for issues since one of the affected disks is on the Intel ports.

Forgot to mention, with the info you posted I'm not seeing anything that points to issues with the filesystem, but that's how you run it.

First you need to decrypt the device, you can replace externaldrive with any name you want: cryptsetup luksOpen /dev/sda1 externaldrive After entering the correct passphrase you can then run fsck, for example for a xfs formatted drive it would be: xfs_repair -v /dev/mapper/externaldrive

No need, I think I see your problem, you are passing through this device to a Windows 10 VM: -device '{"driver":"vfio-pci","host":"0000:0a:00.0","id":"hostdev0","bus":"pci.3","addr":"0x0"}' \ -device '{"driver":"vfio-pci","host":"0000:0a:00.1","id":"hostdev1","bus":"pci.4","addr":"0x0"}' \ -device '{"driver":"vfio-pci","host":"0000:0a:00.2","id":"hostdev6","bus":"pci.9","addr":"0x0"}' \ -device '{"driver":"vfio-pci","host":"0000:0a:00.3","id":"hostdev7","bus":"pci.10","addr":"0x0"}' \ I assume this was a GPU before, but you need to keep in mind that when you add or remove hardware the devices ID can change, device 0a:00.0 is now the SATA controller: 0a:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] So when you start the VM the controller is no longer available to Unraid and all disks connected there will be gone.

Run it again without -n or nothing will be done, if it asks for -L use it.

libvirt image is corrupt, you need to restore from backups, by default Unraid disables checksums for the system share, so if there's corruption it can't be fixed.

Multiple disks dropping at the same time it's not a disk problem. Post new diags after array start.

Not seeing any disk errors as before.

Apr 19 10:51:57 Server kernel: ata5.00: disabled ... Apr 19 10:51:57 Server kernel: ata6.00: disabled ... Apr 19 10:51:57 Server kernel: ata9.00: disabled ... Apr 19 10:51:57 Server kernel: ata10.00: disabled Multiple disks dropped offline, this is usually a power/connection problem, power cycling the server should bring them online, then check array status, one of them might be disable.

https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/next/unRAIDServer-6.10.0-rc4-x86_64.zip

The problem is not being mounted, but being in use, with reads or writes, that will slow down the zeroing speed by a lot.

That only makes sense if you were still using the array before.

The array is stopped in the diags, which drive were you removing? You have some SMR drives, those can be slower, you can also run the diskspeed docker test to make sure all disks are reading at normal speeds.

You can't do that with the drive mounted, parity likely won't be valid in the end, but shouldn't be the reason for the low speed, possibly it's hardware related, diags might show something.

It's known issue with the scrip and current releases, it should not be used, you can still do it manually: https://forums.lime-technology.com/topic/61614-shrink-array-question/?tab=comments#comment-606335

That's a CA backup.

SATA controllers are still failing to initialize, if there's no newer BIOS try v6.10-rc4, newer kernel might help.

Apr 18 17:22:11 Tower kernel: ahci: probe of 0000:27:00.0 failed with error -22 Apr 18 17:22:11 Tower kernel: ahci: probe of 0000:28:00.0 failed with error -22 Apr 18 17:22:11 Tower kernel: ahci: probe of 0000:2c:00.0 failed with error -22 SATA controllers are failing to initialize, make sure they are set to AHCI, BIOS update might also help.

Controller is not being detected, they are not working or there's some compatibility issue with that board, if you have a different PC available test it there.

Please use the existing plugin support thread:

Some data corruption is being detected causing the balance to abort, you can run a scrub to list the corrupt files in the syslog, then delete/replace those, also a good idea to run memtest.

Don't quite understand what you mean, during boot you should see the LSI BIOS and it will list all the devices detected, check if the SAS drive is listed there.

Best bet is to backup that pool and re-format, then see below for how to better monitor pools for errors: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582

See if this applies to you, if yes, upgrading to v6.10 and switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.: https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

Check the board's system even log in the BIOS, there should be more info there.