i/o errors after installing 6.1 beta
Using Accelsior 4M2 with a MacPro 2019. Have used it for a little over a year on Mojave with no problems. Love it. Upgraded Softraid to version 6 last week before upgrading to Big Sur this week. After booting into Big Sur the first time, I got the issue where the Accelsior drive refuses to mount. After reading the support articles on your site, which says the 6.1 beta fixes this issue in Big Sur, I downloaded and installed 6.1b8.
Immediately after installing the beta and restarting, Softraid launched with a series of error messages – stating that there were read/write errors on the drives (3 out 4). At that point the drive mounted, but was read only.
I uninstalled the beta and reinstalled v 6.0.5, but got the same i/o errors upon launch. Screenshot attached shows the errors. However, the volume now allows both read and write. Performed a "Validate" and it was "successful."
It seems an unlikely coincidence that 3 out of the 4 drives would suddenly have simultaneous errors on the first boot after installing the beta. Are these errors legitimate? Has the beta somehow corrupted my drives? Or are these false alarms triggered by beta software?
the actual answer is non of the above. SoftRAID's driver logs and reports all IO errors, regardless of cause. What happened was the directory was damaged slightly from the restart. On the next restart (your reinstalling 6.0.5) macOS auto repaired the directory, so it could mount properly. (MacOS has limited HFS repair utilities, but occasionally they work, as in your case, as the volume is read write again.)
6.1 should fix the Big Sur bug where the driver does not load, else you need to manually load the driver via terminal each restart.
Clear the IO counters on your disks. My guess is the directory (being damaged) was telling macOS to look in a non existent location, so the disk generated an error. What you would call a transient error, but SoftRAID still logs it.
Hope this helps. I would consider when you have time, backup/restore your volume, as with Directory damage, macOS is not very good at repairing this, and your volume may appear to get "slow", so a clean volume start is what I recommend as the best practice in this scenario.
@softraid-support thank you for the reply. I have cleared the IO counters. A couple of followup questions:
Now that the volume is mounted using 6.0.5, I am hesitant to try the 6.1 beta again. Any idea when the final version of 6.1 will be released?
I do have backups, but a full restore to a clean volume would take quite a while. Would DiskWarrior solve the problem with possible directory damage in this case?