JorgeB

Sometimes with few data disks (or an odd number of data disks), parity can appear to have a valid filesystem, this can happen with any filesystem but it's particularly a problem with btrfs since it scans for all filesystems at boot, and then it gets confused, solution here would be to use parity2 slot instead, the way it's calculated would make it impossible, or at least very unlikely, that a valid filesystem could be detected there, you'd need to unassign parity, wipe it with: wipefs -a /dev/sdb1 Reboot, then assign it as parity2 and let it sync.

Please post the diagnostics: Tools -> Diagnostics (after array start)

If you're using Windows 8 or newer transfer will still be done locally due to Samba's server side copy.

Enable syslog mirror to flash then post that log after a crash together with the diagnostics after rebooting: Tools -> Diagnostics

Syslog is after rebooting so not much to see, when Unraid forces a shutdown it saves the diags in the flash drive (logs folder), post those instead.

See this, it works for some: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/?do=findComment&comment=14530

Cache device dropped offline: Jul 8 09:22:35 Server kernel: ata2: hard resetting link Jul 8 09:22:35 Server kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jul 8 09:22:35 Server kernel: ata2.00: failed to set xfermode (err_mask=0x1) Jul 8 09:22:35 Server kernel: ata2.00: disabled Looks more like a connection/power problem, replace/swap both cables, the related errors are what's causing the log to fill up. Disabled disk needs to be replaced: 197 Current_Pending_Sector -O--C- 081 081 000 - 9496 198 Offline_Uncorrectable ----C- 081 081 000 - 9496

They should work, they are for SAS devices, which will accept a SATA device, strangely the description mentions they are only for SATA devices, which doesn't make any sense, why use SAS plug for SATA devices?

Call trace still seems related to the above.

I used Windows, it was the easiest one for me since it didn't require any extra software, used the 9300-8i for updating, but it should work with any LSI HBA in IT mode, possibly other brands.

Turns out that contrary to what I understood at first the OP didn't have this HBA+expander combo yet, was just thinking of getting it and assumed the performance, I got one recently and tested it with an LSI 9300-8i and SSDs, note that these results are after updating the expander to latest firmware, it performed much worse without it, similar to what would be expected without Databolt or the PMC equivalent. Unraid read test (no parity): RES3TV360 single link with LSI 9308-8i 8 x 490MB/s 12 x 330MB/s 16 x 245MB/s 20 x 170MB/s 24 x 130MB/s 28 x 105MB/s RES3TV360 dual link with LSI 9308-8i 12 x 505MB/s 16 x 380MB/s 20 x 300MB/s 24 x 230MB/s 28 x 195MB/s So up to roughly 4GB/s with single link and 6GB/s with dual link, not that different from the LSI SAS3 expander, unfortunately since my LSI expander is on a backplane I can only test that one with up to 12 devices, this combo with SAS3 devices should be capable of around 4.4GB/s with single link and 7GB/s with dual link. Curiously total bandwidth decreases with more devices, possibly due to the hardware used or Unraid but don't think so, using @UhClem's script only got around 4500MB/s max with dual link (with or without the B option) using 12 or more devices, so there shouldn't be a CPU/Unraid bottleneck, I suspect the technology used by PMC to emulate a 12G link with 6G devices loses some efficiency as you add more devices.

Nope, used the 9300-8i.

Forgot to mention, take a look to here for better pool monitoring, so you're immediately notified if it finds new data corruption.

It's based on the current SMART attributes. It's not, but a short SMART test is usually not enough to find a failing disk, unless there are already pending sectors, but you already get notified if those appear.

Since it rebooted we can't see if the previous sync was successful, but now you need to a correcting check. It will show the errors found next to the parity check button.

VMs pause when they run out of space: Filesystem Size Used Avail Use% Mounted on /dev/sdb1 932G 929G 68K 100% /mnt/cache

Unraid doesn't schedule SMART checks, you can only run them manually or by using for example a script with the user scripts plugin, it does schedule a parity check that is for all practical purposes the same as an extended SMART test.

There's still corruption on the pool filesystem, I would recommend re-creating it: backup, format, restore data.

Not as far as I known, they sometimes work when used with a compatible SAS expander.

You don't use it, it's for backplanes.

For example: https://store.supermicro.com/supermicro-minisas-to-4x-sata-51-51cm-cable-cbl-0097l-03.html?queryID=167cdf8d0cf1db5e79a2daf9b572f9f2&objectID=672&indexName=supermicro_default_products

Those won't work, you need forward breakout.

No, you can post the diagnostics so we can check if the HBA is being correctly detected, another common issue for this is using the wrong cables.

PAL error only happens with UEFI boards, that's why I always use an older board without UEFI when I need to do crossflashing, just flashing/updating the firmware can be made using Unraid, and for that it doesn't matter if the board is UEFI or not, it always works.

https://forums.serverbuilds.net/t/guide-updating-your-lsi-sas-controller-with-a-uefi-motherboard/131