shEiD

running env $(cat /boot/config/plugins/unbalanced/unbalanced.env | xargs) /usr/local/emhttp/plugins/unbalanced/unbalanced --port 7090 gives /usr/local/emhttp/plugins/unbalanced/unbalanced: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by /usr/local/emhttp/plugins/unbalanced/unbalanced)

Running the command above I get this: env: ‘/tmp/unbalanced’: No such file or directory

Help, please - unbalanced does not start at all 😢 Is there a minimum OS version, perhaps? I am running unRAID 6.10.3. I am reluctant to uninstall the older unBALANCE plugin (because it works), until I get this new plugin working... Or should I uninstall the older one?

@dlandon thank You, it worked.

Getting an error, when trying to update the plugin. plugin: updating: unassigned.devices.plg plugin: downloading: "https://raw.githubusercontent.com/dlandon/unassigned.devices/master/unassigned.devices-2023.08.17.tgz" ... done plugin: bad file MD5: /boot/config/plugins/unassigned.devices/unassigned.devices-2023.08.17.tgz

Nice and simple - love it. Never used reiserfs before 😀 I thought I'd mention me not using parity, because with parity you would need to zero out the disk?

I am using unRAID v6.10.3 My array is data disks only - NO PARITY. What would be the correct procedure to re-format array disks? I would love to be able to do it fast and simple: - stop the array - remove the disk from an array slot (it appears in the Unassigned Devices) - delete the partition with UD - put the disk back in it's array slot - start the array and hopefully the disk gets formatted 🤞 without zeroing out? Or do I need to do it long way round: - new config - remove disk - pre-clear - new config - add disk back - auto-format on array start (the usual unraid behavior when adding a new disk to the array)

How can I find out which array disks are actually formatted the "old" and "new" way? I mean, can I get that info without emptying the disks to see how much free space they take up "on empty". Also, what would be the easiest and fastest way to re-format the array disks using the "new" xfs format? I am constantly using hardlinks - I probably have tens of thousands of them on my array, and I am not 100% sure, but it seems, like I am getting way faster results when searching for hardlinks on the "newer" disks, than older ones. or am I just imagining this?

Just wanted to confirm, that this explains some pretty huge difference in used space on empty array disks. I emptied 3 identical 10 TB disks on my array and - 2 older ones have ~10GB used space, while the newest one has ~70GB. I assume, the 3rd disk was formatted with the newer version of xfs? Same with the newest 18TB drives, I guess? They all have 126GB used space freshly formatted, instead of ~18GB... Would very much appreciate, if anyone could confirm, that I'm understanding this correctly.

@trurl Thank You.

Does doing a New Config mean that all the settings, Docker containers and VMs will be gone? I mean, does New Config reset ONLY the disks (array/cache/pools), or does it reset everything? I need to replace 1 failing drive with a new one, and I do NOT have parity. Everything from the failing drive is already copied over to the new drive (rsync). And, no parity means there's nothing to rebuild. Preferably, I would love to simply swap the drives and keep all my setup intact...

It seems fio does not work... I only get "Illegal instruction" on any command. unRAID Version: 6.9.2 NerdPack Version: 2021.08.11

Yes, I have jq in my system, but I think I installed it with NerdPack, iirc. Or am I misremembering? I could swear, jq was in NerdPack before 🤔, but maybe I'm wrong... Does this mean, that now jq comes with unRAID as standard, so it was removed from NP?

Same here - jq is missing - has it been removed? Please, add it back 🙏

Here's the diagnostics with a running array. ungiga-diagnostics-20210904-0125.zip Although, I have already rebooted normally one more time, without starting the array - just to avoid the parity check. I mean I decided enough is enough - 2 parity checks in 2 days (0 errors), I feel 3rd time would be the same. There should have never actually been any writes to the array, when the server hanged... Sorry, if that messed up the diagnostics... did it? I actually thought, if you don't capture stuff before restart - all the info is useless anyways, as unraid is always loaded to memory and completely resets on reboot? Yep, that's how have set them, by using the units: from the smallest 3GB to the largest of 500GB. I usually tend to not fill any drives past 90% on my main server. And yes, on this backup server 500GB is normally way to much for 3TB drives, but meh - this was just temporary. This is as much a backup server, as it is a testing server. That's why I'm copying everything out to the main one. I want to create and properly test multiple btrfs cache pools using these drives. I would love sooooo much to use btrfs pools, if it wasn't so "anecdotally scary unreliable" and did not have so much warnings not to trust in it, all over the internets 😟