MadDiplomat

Thanks for the advice, I really appreciate it! I will stick to XFS, as it seems there is no point in rushing into early adoption of ZFS of array drives. Especially if speeds still need ironing out, as I will be getting rid of the last few 5400 RPM drives in my array.

Hello, I have an array of 7 drives with a single parity and XFS - encrypted FS. Does it make sense to break everything and use ZFS in the following situation? I've never used ZFS before, but I've heard endless of praise for it, so it must be the latest trend. Here's the situation: I want to upgrade to dual parity and replace about half of the drives with larger models. I could do this step by step, but it seems like it would take a really long time. So, I'm considering speedrunning it by backing up my entire array to another NAS, then destroying the array, installing the new drives all at once, creating a fresh configuration, and finally copying all the data back from the other NAS. Simultaneously, I'm thinking that I may as well format the "new" array's drives into ZFS with encryption (array drives can be encrypted if using ZFS, right?). I understand that since I will not use a ZFS pool, I won't get the best perks like bitrot healing, but supposedly, using ZFS for UnRAID's array drives still has certain benefits vs. XFS. If anything above is a bad idea, please stop me :).

No change with the latest UnRAID version. This plugin will put my system to sleep after the specified "extra delay" (in my case 99 minutes) and ignore other rules (array inactivity & network traffic), which were working as intended a few UnRAID versions ago. Is there any way to increase the delay beyond 99 minutes? It would make a useful workaround until this plugin is fixed. For some reason, the plugin will not let me input more than 99 minutes in the GUI (I'm not sure if this limit is intentional). Edit: I changed the "timeout" from 99 to 180 in /boot/config/plugins/dynamix.s3.sleep/dynamix.s3.sleep.cfg. This change is now reflected in the GUI, which previously did not allow me to enter a value greater than 99. I just hope it works and that I didn't break anything further. Edit 2: Well that did nothing. It says 180 minutes but it is still 99. Why is this even programmed like that is beyond me.

This plugin is broken now. Ever since I updated to UnRAID v. 6.11.1, it will go to sleep after the "delay" time, no matter what. I have increased the delay to 99 minutes and it just goes to sleep after 99 minutes. It even went to sleep while I was streaming a video from my server, ignoring all rules about array inactivity and traffic. It worked perfectly until I updated. I will now update to 6.11.3 and report if anything changes.

I just wasted 30 minutes on this. Today, 32GB flash drives are actually harder to find in stores than one would imagine. But even when I found one, the utility did not like it, even if I put it in a USB 2.0. port. I had to do the manual approach, but luckily the stick boots just fine now with UnRAID. If the app can't be updated, the legacy approach should be the default one presented on the web page.