This is actually not he first time this has happened:
After just updating macOS to 13.5.1, one of my SoftRaid volumes is not set to read-only.
And I cannot repair using DiskWariior....because it is set to Read-Only by macos itself.
The last time I fixed this, I moved ALL the content to another drive then re-created the Volume.
But this took many, many hours. And for part of that it, was all on a non-redundant drive.
And it is the same volume and drive as before.
So...is there no way to get macos to make it read-write again?
sincerely, tumbling into despair...
You can absolutely use Disk Warrior. Give it a try.
When your system shuts down, MacOS closes the volume directory on all mounted volumes, then unmounts them. At startup, it checks to see if the volume was unmounted cleanly. (called the dirty bit)
If MacOS detects there was an unclean mount/shutdown, it automatically runs a repair tool to fix the directory. if this tool fails, the volume is marked read only and mounted (if possible).
Unfortunately, I should have been more clear, my bad:
I tried to use DiskWarrior, as I tried the last time this happened, but it fils to even start the rebuild.
https://share.cleanshot.com/cwKkgCMF
It immediately reports the disk is in use and throws an error. Which makes sense, becuase how can it possibly rebuild a volume, which entails reading and writing, if the OS has set the volume ot read-only. Also, the volumes is mounted the problem is trying to *unmount* it so i can try to repair with DW or TechTool.
Unless you mean I run DW from a USB at startup?
also, many thanks for such a quick reply!
So if I try to unmount it with SR, I get:
"SoftRAID Error
An internal part of the SoftAID application has stopped
functioning properly. Please quit SoftRAID and relaunch it"
if I try with DU, I get:
"Failed to unmount "vault-03"
because it is currently in use."
If I use the terminal, i get:
"Volume vault-03 on disk13 failed to unmount: dissented by PID 225 (/usr/libexec/AssetCache/AssetCache)
Dissenter parent PPID 1 (/sbin/launchd)"
So I may not have been clear in my first post, but this is the second thing I tried. The first thing involved the blood of chickens.
Restart and try again, to unmount using Finder. See if that works. Hopefully no further sacrificial rituals required!
sadly, i believe we are not done with the rituals.
each time I reboot, macos immediately reports that there is a fault reading the volume and it has set it to read-only.
can Dw rebuild a softraid volume from a recovery thumb drive?
or even in safe mode?
Disk Warrior can run from thumbdrive (but there is a problem with M1, it cannot, as the driver for SoftRAID will not load) So any intel system, yes.
Easiest is create a new volume, install a new MacOS into it, do not import data. (but use the same admin name) then run Disk Warrior from that clean volume.
Run Disk Utility. select your internal disk Click + volume and create a new volume. Startup into recovery mode, "reinstall MacOS" and point it to the new volume. This does not affect the main volume at all.
I rarely hear of a problem like this, I cannot remember any. Disk Warrior is not always able to replace the directory (MacOS services error), or sometimes fails to scan for various issues (can crash or hang), but not this issue, where it cannot even run the scan.
I am pretty sure its a faulty with the drive. This has only ever happened with this specific unit.
All the drives on it have 20K hours each, and had been certified when i last had to rebuild it.
Frustrating.
I really appreciate all your help

