Notifications
Clear all

SoftRAID lock my volume

(@steve223)
Trusted Member Customer

I was wondering will this ever be fixed as I don't have this issue with any other volumes but OWC Raid's and it's quite annoying having to restart my machine every time this happens which is at least a few times per week and usually after Mac went to sleep

 

Screen Shot 2020 11 24 at 6.54.36 pm
Quote
Topic starter Posted : 24/11/2020 2:06 am
Topic Tags
(@softraid-support)
Member Admin

This is an Apple OS X bug. We have been pushing for it to be fixed for some time now. We have it in Apple engineering's hands at present.

It is a problem for RAID, as a volume is composed of more than one MacOS disk. So if those disk numbers change (called bsd disk identifiers) while disks are connected to the computer, data corruption can result. This message means SoftRAID is preventing data corruption/volume directory damage by pro-actively locking the volume when we detect this state.

We hope this will be fixed in Big Sur, but it is not fixed in the current shipping version.

ReplyQuote
Posted : 25/11/2020 11:17 am
(@steve223)
Trusted Member Customer

so speaking to a few software developers who are much smarter than me they mentioned that most windows software raid solution does not rely on the OS identifier of the drive but write their own identifier in multiple locations on the drive, that way the issue of the Mac changing drive identifiers would not matter as the software determines the drives based on it's own identifiers. Supposedly this would be a much better way as it also means a Raid array could be used in any device which can accommodate a the Raid's HD's. Given that the Mac now exists in Mac OS for a while is it time for you guy's to come up with a  better solution than disabling writing to the Drive. At the present stage, your software is not fully compatible with Mac OS Catlina or BigSure

Screen Shot 2021 02 07 at 7.31.23 pm

 

ReplyQuote
Topic starter Posted : 07/02/2021 7:39 pm
(@softraid-support)
Member Admin

Maybe I can get a better technical explanation for this for you. Disks cannot have different BSD identifiers than what is listed in the IO registry. That is what is happening.

ReplyQuote
Posted : 07/02/2021 9:51 pm
Share:
close
open