What controls /var/local/emhttp/var.ini? It seems upon modification changes are immediately reverted. Through some poking and proding it seems that MAX_CACHESZ is going from 60 drives in 6.12 to 120 in 7.0. Out of curiosity and boredom I'm trying to see if the same applies for MAX_ARRAZYSZ as I'd really like to toy around with 45 or 60 wide unraid array.

 

In testing it seems the var.ini file is not persistent as any changes are immediately flushed. Was ideally thinking of throwing a sed into /boot/config/go

 

/boot/config/go

#!/bin/bash
# Brute force array change
sed -i 's/MAX_ARRAYSZ="30"/MAX_ARRAYSZ="60"/' /var/local/emhttp/var.ini

# Start the Management Utility
/usr/local/sbin/emhttp &

#resize memory allocation
mount -o remount,size=8G /dev/shm
mount -o remount,size=120G /

#load custom nfs exports
cp /boot/config/custom.exports /etc/exports.d/custom.exports

 

Edited November 23, 20241 yr by DiscoverIt

While we wait for multiple array support, this would be a worthwhile change. If we understand the risk of 1 parity drive for 60 data drives, I don't see why it can't be done. And right now I'm running entirely without parity, so obviously I'm willing to accept the risk of data loss - anything critical and not replaceable is backed up.

 

What say ye unRAIDians?

 

Seems not terribly straight forward with many legacy hard coded sections capping at the 30 disks total for an unraid array.

 

Bummer

That will never work.

I'm not sure how difficult it would be, but since they've already raised the number of pool devices to 60 for 6.12.x and 120 for 7.0+, is there any reason besides risk for not bumping the array slots to 60 or even 90 data slots?

37 minutes ago, JorgeB said:

That will never work.

 

What will never work?

Manually changing MAX_ARRAZYSZ, there's a hard 30 device limit for array devices in other places, IIRC including super.dat, which is where the assignments are stored, LT already mentioned that multiple arrays will be supported soon, but I don't think there are plans to increase max array size, at least AFAIK.

33 minutes ago, JorgeB said:

Manually changing MAX_ARRAZYSZ, there's a hard 30 device limit for array devices in other places, IIRC including super.dat, which is where the assignments are stored, LT already mentioned that multiple arrays will be supported soon, but I don't think there are plans to increase max array size, at least AFAIK.

It’s always soon. I have a growing need for more drives and not incredibly keen on making 30+ individual xfs drive pools

protected by SnapRaid. 
 

I’ll keep poking for another hacky option that will yield better results. Thanks!