JorgeB

Are you using 6.2-beta? If yes use the new preclear beta plugin or patch the script.

Low priority but when possible please adjust display so there's no need to scroll right to see all disks.

I knew TRIM didn't work for me with a LSI controller, didn't know it does work with some models, thanks for the link.

The 850 EVO supports TRIM.

Looking at your mb manual this is the problem, SAS3 is onboard LSI, when we say onboard controller we mean the PCH ports, connect the SSD to one of those and trim should work.

No, default BTRFS supports TRIM, you usually get that error when the controller doesn't support it, looks like you're virtualizing unRAID, so maybe that's the cause (if you're using the mb controller). you're right, i do virtualize unRAID, in that hardware controllers are passthrough completely to unRAID. all (to me) known/used hardware features (esp. such as sleep function of hdd) do work properly. even all operations, which do change the boot usb-stick – so no tricks used/necessary here. the SSD is on the same controller (SAS3 from MB) as other HDDs. not an TRIM expert here, but my reading showed, that they use the fstrim command on mountpoints of filesystems and not on devices directly. well, i tried that too, but same result. Is the SAS3 controller from intel PCH or other, like LSI, some LSI controllers don't support trim, e.g., 9211.

No, default BTRFS supports TRIM, you usually get that error when the controller doesn't support it, looks like you're virtualizing unRAID, so maybe that's the cause (if you're using the mb controller).

Looks fine.

Correct, the beta plugin is stand-alone.

It's confusing because of the many versions and because the original plugin is just a front-end for the scrip while the beta plugin is stand-alone: Working with v6.2-beta: Edited original Preclear script (command line only) Edited unofficial faster Preclear script (command line only) Preclear plugin with either of the edited(*) scripts Stand-alone beta Preclear plugin * When editing the script don't forget that the plugin uses the script located in /boot/config/plugins/preclear.disk/ directory.

I could add my v6.2-beta servers, both auto and manual working. Request: Option to sort servers (or auto sort alphabetically).

V1: ST8000AS0002 V2: ST8000AS0022 Differences: https://lime-technology.com/forum/index.php?topic=47509.0

If you mean the Seagates speeds are normal in a dual parity setup, same as single parity.

I have better results with speedtest-cli: Ping - DL - UL Browser: 3ms - 213.13 - 210.75 Plugin: 7ms - 208.58 - 50.99 stest-cli: 7ms - 208.30 - 203.80 stest-linux: 12ms - 205.12 - 170.15

That's normal and OK, it can even change between reboots with same hardware, unRAID tracks disks by serial number.

Same characteristics and chipset, they should perform identically.

Similar: http://lime-technology.com/forum/index.php?topic=43026.0

I believe he's asking how to rebuild to the same disk, if so: -unassign disk -start array -stop array -reassign same disk to begin rebuild

Yes.

I've one different manufacturer, but virtually identical, same marvell 9230 chipset, it works fine but there could be issues if you use virtualization.

This is a good tip, I use it myself, just a small correction, the number is a percent of your free RAM, i usually set it at 99. Edit to add: This tweak should only be used on a server with a UPS.

Performance should be similar for HDDs, for SSDs use eSATA.

Didn't see the sig since they don't appear on tapatalk, but still believe my impression was right, some users confuse parity disk size with parity protected array size.

Probably means 9TB total array size, based on the duration I'm guessing parity disk is 3TB.

V6.2-beta21 uses samba 4.4 with experimental smb multichannel support, I can't get it to work for now but it should work in the near future.