After update to Cat...
 
Notifications
Clear all

After update to Catalina I can no longer share any softraid volumes

5 Posts
2 Users
0 Likes
252 Views
(@planitarygear)
Posts: 3
Active Member
Topic starter
 

I recently, finally, upgraded my house backup server to Catalina as I needed that to run some other things. I also had to upgrade my softraid version to 6.3 and disable secure boot but I believe that is all working now. At least it appears to be working normally locally. In the sharing control panel I can select the raid volume or folders on the raid volume and they appear to share from there. I have selected to share only via SMB as was suggested in the known issues. Other computers on the network running a variety of OS versions can see the computer has shares and you can select the raid share, but as soon as it attempts to mount I get the “The operation can’t be completed because the original “foldername” cannot be found” error and then nothing. I have rebooted all the machines on both sides, done the dance with force quitting the finder, removed everything from the sharing panel, rebooted the server and re-added it. The server will happily share it’s internal volume and those mount just fine too. 

The raid volume is formatted as HFS+ and not APFS. The option to “Convert Volume” in the sofraid app is greyed out when it is selected. I’m not sure this even is for that but I would convert the volume if possible in order to get it to share if that is what the problem is. 

The only other oddness I’ve noticed is that the raid volume does not display in the lefthand list of “Locations” in Finder windows. To get to it I have to click on the computer name icon and then it is shown as a volume there. 

The server is a 2018 Mac Mini running 10.15.7 and softraid v 6.3 and softraid driver v 6.3. Any suggestions greatly appreciated!

Thanks

 
Posted : 12/12/2022 10:10 am
Topic Tags
(@softraid-support)
Posts: 8049
Member Admin
 

We changed SoftRAID volumes to be "removable" in 6.3. This was to avoid some time machine bugs.
this affected sharing, but there is a workaround. In the Sharing Pane, click on + and add the specific volume. If that does not work, then click plus and select any folder in the volume, in addition.

You can drag the SoftRAID volume into Locations. Another side effect of being removable volumes.

 
Posted : 12/12/2022 4:46 pm
(@planitarygear)
Posts: 3
Active Member
Topic starter
 
Posted by: @softraid-support

We changed SoftRAID volumes to be "removable" in 6.3. This was to avoid some time machine bugs.
this affected sharing, but there is a workaround. In the Sharing Pane, click on + and add the specific volume. If that does not work, then click plus and select any folder in the volume, in addition.

You can drag the SoftRAID volume into Locations. Another side effect of being removable volumes.

Hello Softraid, thanks for the update. This is indeed how I have it setup. I have added both the root of the softraid volume as well as 2 folders that are on the softraid volume via the plus button on the sharing control panel. They show up when I connect to the networked computer, but upon attempting to actually mount one I get the same error as above. This worked perfectly in previous OS versions. I will play with permissions and everything else I can think of but something has changed more significantly than just being removable as I’ve done the suggested above several times in various ways now to no effect.

 
Posted : 17/12/2022 3:50 pm
(@softraid-support)
Posts: 8049
Member Admin
 

@planitarygear 

Try "unsharing" and starting over, maybe that can make a difference.

 
Posted : 17/12/2022 8:22 pm
(@planitarygear)
Posts: 3
Active Member
Topic starter
 

I figured out what the problem was and it wasn’t SoftRAID’s fault at all ;) During the update the “Full Disk Access” checkbox had gotten removed for smbd. Once I checked that again in the privacy and security control panel it is working just great again. That gets reset whenever you upgrade the piece of software that you gave the privs for so I shouldn’t be surprised, but still thats frustrating that there was no error message from the OS or anything else that would have led me to find that sooner. Thanks!

 
Posted : 18/12/2022 2:01 pm
Share:
close
open