ezhik

If I don't get one, can I buy a few? I have 3 unRAID servers.

well done.

Updated three systems, no problem. Rock on!

Nice, noted. This doesn't provide you with redundancy, but you can compensate with daily backups through other plugins.

Would be nice to have 'cache groups' for different purposes. For example: "cache group":storage -> used strictly for storage "cache group": docker -> used strictly for docker images "cache group": VMs -> used strictly for VMs That way they won't have to fight for Disk I/O. One can only dream...

You can also use this tool to check what vulnerabilities your CPU is susceptible to.

Interesting, I wonder if you had a beta P20 release. Also, no expander here so I cannot comment on the compatibility.

What type of chaos and what release of the firmware?

Sacrificing performance over stability makes sense, when that's the case. It is also important to make the distinction that new doesn't always mean good. Majority of us worked in IT for decades (possibly including yourself) and we know that new releases cause all sorts of sh*t storms incompatibility and stability issues. Hence why you always read the release notes and assess whether or not you even need these new updates. Obviously security comes first and we have to deal with repercussions as they come. NOTE: It seems LSI mostly patched the IR firmware and IT doesn't seem to need as many patches.

1) If you review the release notes between P16 and P20, most fixes are not for IT mode. 2) You are assuming everybody has SATA3 (6gb/s) ports available on their motherboards for SSDs. One of my servers only has SATA2 ports. 3) Drivers are generally built with backwards compatibility and I doubt it for HBAs it would play a big role if you are running it on an older firmware.

So I've tested several firmware version to track down where the issue was introduced and the firmware that I was able to get this working correctly is P16. (LSI HBAs LSI SAS2308/SAS2008) To those who are seeing this error, you might want to downgrade to P16 firmware and your FSTRIM would work with your SSDs (obviously if it is supported). Tested firmware version: P14 -> YES P15 -> YES P16 -> YES P17 -> NO P18 -> NO P19 -> NO P20 -> NO Cheers. Guide and files for 9201-16i and 9207-8i: lsi-flash-efi.zip NOTE: You need to boot the efi shell attached in order to proceed with the flashing process.

Respect. Thank you for bringing security first and release a patch for this. Cheers.

1 x Antec 1200 (Twelve Hundred) case 1 x Supermicro X9SRL-F 1 x Noctua NH-U12DX i4 1 x Intel Xeon E5-2695v2 1 x Antec 850W 3 x LSI 9211-8i 5 x Noctua NH-F12 1 x Lexar 32GB USB 4 x 16GB DDR3L-1600 ECC REG 4 x 5-in-3 Hard Disk Cage / Enclosure 20 x WD RE4 4TB 2 x 400GB OCZ Deneva 2 SSD NOTE: Not super pretty, but gets the job.

I am sorry I am going to have to skip this update. I just can't... Any ETA on 6.6.7?

or reboot. seems to fix the issue, not ideal though.

you have to add it from the beginning, during the VM creation.

I had to re-create the VM with shares configured from the start. No issues so far. I should probably write a guide about how to accomplish this properly...

I confirm, same issue here.

I can confirm. Hit the same issue... Quite annoying. unraid 6.6.5.

Thanks. Let's not flood this thread with a separate topic, I see you've addressed this previously. Thank you! Let's stay focused on HP H240 now

Thanks.

Not to digress from the original conversation, can this be corrected? If this a longer a conversation, I don't want to get started on this here. Let's take it to IRC?