Is resize issue fixed in 7.x?

It's not working for me. I have 4x4TB drives configured for RAID 5. I shrank one of my 3 volumes in order to increase the other two. One volume shrank, but I haven't been able to increase either of the other two.

I upgraded SoftRAID from 7.5 to 7.6, but it still didn't work. I tried increasing one of the volumes (from 3TB to 4TB) and the log said it succeeded, but both SoftRAID and the Finder didn't show an increase.

I noticed that SoftRAID was v7.6, but the driver was v7.5, and read that upgrading to Sonoma would automatically upgrade the driver to 7.6. I upgraded to Sonoma (and now the driver is 7.6), but it still doesn't work. I tried resizing to different sizes (5TB, 6TB) and the log changed to say error = 101. I tried again to resize to 4TB and now instead of saying it succeeded, it says error = 101.

Doesn't look like the problem has been fixed in 7.6.

Oct 02 00:45:29 - SoftRAID Monitor: Starting SMART test on all disks which support SMART.
Oct 02 00:45:32 - SoftRAID Monitor: SoftRAID XT license activated for all users on this computer (nickname “Douglas’s MacBook Pro (2)”). This license is for disks in select OWC enclosures. Upgrade & Support Plan: Active (expires on Nov 15, 2023)
Oct 02 00:45:36 - SoftRAID Monitor: Starting SMART test on all disks which support SMART.
Oct 02 00:45:37 - SoftRAID Monitor: Finished SMART test on all disks. No disks failed the SMART test.
Oct 02 00:46:16 - SoftRAID Application: Launching application: SoftRAID version 7.6
Oct 02 00:47:31 - SoftRAID Application: Resizing the volume "TM Backup" (disk10) to 3,999,999,983,616 bytes.
Oct 02 00:48:46 - SoftRAID Application: The volume resize command for volume "TM Backup" (disk10) completed successfully.
Oct 02 00:52:27 - SoftRAID Application: Resizing the volume "TM Backup" (disk11) to 3,999,999,983,616 bytes.
Oct 02 00:53:31 - SoftRAID Application: The volume resize command for volume "TM Backup" (disk11) completed successfully.
Oct 02 00:55:51 - SoftRAID Application: Resizing the volume "TM Backup" (disk16) to 5,999,999,975,424 bytes.
Oct 02 00:56:56 - SoftRAID Application: The volume resize command for volume "TM Backup" (disk16) failed with an error (error number = 101).
Oct 02 00:57:10 - SoftRAID Application: Resizing the volume "TM Backup" (disk19) to 4,999,999,979,520 bytes.
Oct 02 00:58:15 - SoftRAID Application: The volume resize command for volume "TM Backup" (disk19) failed with an error (error number = 101).
Oct 02 00:58:53 - SoftRAID Application: Resizing the volume "TM Backup" (disk22) to 3,999,999,983,616 bytes.
Oct 02 00:59:58 - SoftRAID Application: The volume resize command for volume "TM Backup" (disk22) failed with an error (error number = 101).

@dkrugman 
We did fix this in 7.6. Please attach a SoftRAID tech support file, so I can take a look at the problem.

There is no worry about 7.5. This is an application issue, not a driver issue and Ventura will always load 7.5.

File attached.

I tried one last time before creating the file. It took much longer than previous attempts. After 15min an error message said to check that SoftRAID had Full Disk Access. It did not, so I did that and restarted SoftRAID. After 15 min it failed with the same error message. I confirmed that Full Disk Access had been enabled.

NOTES:

During the resize SoftRAID showed one of the volumes (Media) as unmounted and blinked "mounting" for about 5 min. That volume appeared to be mounted and accessible the whole time. For the next 10 min the volume I'm trying to resize (TM Backup) blinked "mounting". That volume also appeared to be mounted and accessible the whole time.

After the resize failed I noticed that SoftRAID showed TM Backup as "HFS+ (journaled)". My recollection is that all three volumes always showed as "HFS+" before that. I believe they are all journaled, so it's confusing that SoftRAID shows one differently from the others.

I set TM to manual trigger, so it's not trying to access the TM Backup volume.

(Full disclosure) I do have SuperDuper! updating a TM backup from a NAS drive to a sparsebundle on the third volume of the array (Data), but I think I had the same problem before running SuperDuper!.  I don't want to stop that as it takes days for the process to complete. Even with Smart Update it takes hours to get back to the point it was at when stopped.

@dkrugman 

Next time you attempt to resize, unmount the volumes on those disks first. that should avoid this issue.

BTW: you need to (soon) delete your Time Machine volume and recreate it as an APFS volume. Apple does not support new Time Machine volumes that are HFS and soon my guess is, Time Machine will stop working on your volume. So be proactive and do it when convenient to you.