Octalbush

I'm also getting this warning, does anyone have a workaround? I tried installing mbuffer from source that this plugin downloads to the root of Unraid, however with no gcc I can't compile. @steini84 Do you have a solution?

Would it be possible to add mbuffer? I'm using the Sanoid plugin and getting warnings that mbuffer is not installed. This issue should likely be on the maintainer of the Sanoid plugin but could be solved here as well. If not mbuffer, gcc would make it possible for me to compile mbuffer from source myself, so maybe add that instead? Thank you

Does this plugin work on 6.12.4 with ZFS pools created via the Unraid method rather than the old ZFS plugin? Looking for an elegant solution for snapshots on default Unraid ZFS.

Update on this. Used the Dynamix Factory Reset plugin to get a fresh USB, then tested cpu isolation before configuring anything else. Still didn't work. I then pulled the USB from the server, used the creation tool and created a new 6.12rc5 install on the same USB. Copied super.dat, pools folder, shares folder, my key, and docker templates. It's working now! Thanks everyone for your help.

Well as I expected the trial USB stick allowed me to use CPU Isolation with no issues, so it seems I have something wrong with my USB. Can someone help me to keep as much data as possible while wiping and creating a new USB Key? I have 63 docker containers, 2 VMs, and a mix of ZFS and BTRFS pools that I would really like to not have to reconfigure. Thanks

Thanks guys, I’m going to create a trial USB and see if I can get it working there. If I can then I will see about Frankensteining my current USB, I mainly just don’t want to lose my pool config and docker. Everything else I should be able to replicate somewhat easily.

Here’s my syslinux

Here’s the latest diagnostic, I chose cores 6-9 to try a lower numbered set. Same issue though. dockerator-diagnostics-20230511-1223.zip

Sure, when do you want me to take the diagnostics? 1. Before isolation is enabled 2. After isolation is enabled but before reboot 3. After reboot when isolation still says it requires a reboot

Hello, thanks for the update. I switched to an Epyc 7302p which is a common CPU and only 16 cores and I have the same issue.

Still an issue on 6.12 rc5. I even rebuilt my entire server with all new hardware and this persisted through that. Can anyone help me with this issue?

Just tested, this is still a present issue on 6.12 rc3.

Yes, I was hoping to see this bug fixed so I don't have to roll back.

How can I find the changes between rc2 and rc3?

My issue with this is that my server was rebuilt from scratch on 6.12, including the USB, so I have no way of rolling back to 6.11 without making a new USB, reactivating the license, and then recreating all of my config from scratch because as far as I know I can’t export and import my docker config or my vm configs from 6.12 to 6.11.