Does it happen with only one connected? Or only when both are?
Lets figure out the trigger, then maybe we can find a solution.
I can think of:
Only 1 of the 2 docks triggers it
requires both to trigger this.
A second Monitor triggers this, either dock.
I am assuming your Mac only has one Thunderbolt bus (two ports)
So there is no way to keep the two docks on separate buses.
Are the extra dock ports for Thunderbolt enclosures? Monitors? or USB devices?
yes only two Thunderbolt ports 2020 5k iMac
I use the docks to connect my devices like SD card reader, microphones, 4 external Raid HD's as i do mainly video and a second Dell U3219Q monitor.
I now disable sleep and have the screen saver going permanently and so far no HD locks but obviously not a good solution for screen longevity
Leaving screen on causes minor electrical loss, (disks more) but LCD screens do not suffer from being on, i.e, the screen saver. LED's last a long time. Plasma, on the other hand, wears out quickly.
For more stable use, can I directly use macos disk tool to manage these disks without using softraid? If you don’t use software raid
I am also seeing this problem far too often - *everyday*
Feb 18 14:45:19 - SoftRAID Driver: One or more of the disks for the volume "Multimedia_HDD" (disk15) is no longer usable. The volume is now locked to prevent data corruption. Please restart your Mac to use this volume again.
Feb 18 14:45:19 - SoftRAID Driver: The SoftRAID volume "Multimedia_HDD" (disk15) encountered an error (E00002E4). A program attempted to read or write to a volume which was no longer accepting i/o requests.
Feb 18 14:45:20 - SoftRAID Driver: The SoftRAID volume "Multimedia_HDD" (disk15) encountered an error (E00002E4). A program attempted to read or write to a volume which was no longer accepting i/o requests.
Feb 18 20:49:07 - SoftRAID Driver: One or more of the disks for the volume "Multimedia_HDD" (disk15) is no longer usable. The volume is now locked to prevent data corruption. Please restart your Mac to use this volume again.
Feb 18 20:49:07 - SoftRAID Driver: The SoftRAID volume "Multimedia_HDD" (disk15) encountered an error (E00002E4). A program attempted to read or write to a volume which was no longer accepting i/o requests.
Feb 19 14:59:20 - SoftRAID Driver: One or more of the disks for the volume "Multimedia_HDD" (disk15) is no longer usable. The volume is now locked to prevent data corruption. Please restart your Mac to use this volume again.
Feb 19 14:59:20 - SoftRAID Driver: The SoftRAID volume "Multimedia_HDD" (disk15) encountered an error (E00002E4). A program attempted to read or write to a volume which was no longer accepting i/o requests.
Feb 20 04:22:51 - SoftRAID Driver: One or more of the disks for the volume "Multimedia_HDD" (disk15) is no longer usable. The volume is now locked to prevent data corruption. Please restart your Mac to use this volume again.
Feb 20 04:22:51 - SoftRAID Driver: The SoftRAID volume "Multimedia_HDD" (disk15) encountered an error (E00002E4). A program attempted to read or write to a volume which was no longer accepting i/o requests.
Feb 20 04:22:55 - SoftRAID Driver: The SoftRAID volume "Multimedia_HDD" (disk15) encountered an error (E00002E4). A program attempted to read or write to a volume which was no longer accepting i/o requests.
Feb 20 04:22:56 - SoftRAID Driver: The SoftRAID volume "Multimedia_HDD" (disk15) encountered an error (E00002E4). A program attempted to read or write to a volume which was no longer accepting i/o requests.
Feb 21 13:36:53 - SoftRAID Application: Launching application: SoftRAID version 6.0.1 b52
Feb 21 13:36:53 - SoftRAID Driver: The SoftRAID volume "Multimedia_SSD" (disk17) encountered an error (E00002C1). A program attempted to read or write to a volume which was not open.
There is not enough information here.
Can you attach a SoftRAID Tech support file? that is a starting point.
Does it happen when the computer is waking from a sleep?
Hello @softraid-support
It does seem to happen when the computer is waking from a sleep - pretty systematically. I want to say always but I believe I experienced it while using the system in the past. Tech support file attached.
Where is the Thunderbay connected? Lets try something.
Correct me if I am incorrect. You have the following connected:
Thunderbolt Monitor
Thunderbays
USB Hub
Misc stuff
Perchance, what if you:
Connect the Thunderbays to the 2 ports on the right, towards the HDMI connection.
Connect the Hub, Monitor and everything to the other two ports.
See if you still get the volume locking. And watch if the Monitor ever (rarely) momentarily blinks black
@softraid-support - very correct
I have recabled everything as asked.
I'll let you know if I still get the volume locking
Please find attached the new
tech support file - after reboot and before any locking issue
@softraid-support I have not experienced the volume locking issue for the last 5 days after doing the changes you requested
I am also seeing this issue daily since the recent change to Big Sur / M1 MacMini / 11.3 beta (4-5-6) / Softraid 6 b53. Thunderbay 4 configured as RAID 5, plugged directly into thunderbolt port via Apple Thunderbolt 2>3 converter. No docks, no other thunderbolt devices. Posted this in the M1 / Big Sur forum but wanted to mention it for the benefit of others. I had this problem maybe once in 6 years on Intel iMac with several MacOSs ending in Mojave, previous to the current system change.
It is frustrating beyond belief, as I cannot use what was supposed to be my "work computer." Not only is locking the drive not helping me, it is not protecting me either. I have a dropbox account connected to this drive and the lock runs the risk of dropbox getting confused and erasing the whole cloud account. It is not acceptable to have to reboot a locked system 1+ times a day. People cannot earn a living that way. My new system is so vanilla, so why is this going on? Must be a bug.
Try resetting SMC and NVRAM. Since this just started, it may be resolvable by resetting the parameters. It has helped in cases where for instance, macOS updates triggered the issue.
@softraid-support it hasn’t just start it’s since I bought device, did reset SMC and NVRAM
@softraid-support I wish I could but to my knowledge there is no way to reset SMC/NVRAM on the M1 macs as this function is now an integral part of rebooting. Still, something has changed on my system. This happened one time in six years before I replaced one of the internal Toshiba 5TB drives with the same model of Toshiba but in 6TB size (as per OWC). The drive was new, passed certify, and the array rebuilt. Perhaps I have to do something to the drives? Why would this problem suddenly start?

