Notifications
Clear all

SoftRAID Volume Locked error

190 Posts
16 Users
11 Likes
8,279 Views
(@mountaincat)
Posts: 56
Trusted Member
 

I have not had the event for 11 days. But nothing else changed. So the solution is to post here and have you say "wait until you get another event", like bring an umbrella so it won't rain :)

I hope I have seen the end of it, but who knows. Literally nothing changed on the system, but I wonder if it could be that something worked its way through??

 
Posted : 28/04/2021 10:19 am
(@softraid-support)
Posts: 8008
Member Admin
 

These events are caused by the disks being reassigned new bsd numbers (disk numbers) waking from sleep, which is "forbidden", but happens anyway. We put this code in to prevent data corruption, when we discovered this.

It has not been fixed it, it is a kernel issue.

 
Posted : 28/04/2021 10:59 am
(@scatteredbrain)
Posts: 5
Active Member
 

May 01 22:46:32 - SoftRAID Driver: One or more of the disks for the volume "Hotblack Desiato" (disk8) is no longer usable. The volume is now locked to prevent data corruption. Please restart your Mac to use this volume again.

May 01 22:46:32 - SoftRAID Driver: The SoftRAID volume "Hotblack Desiato" (disk8) encountered an error (E00002E4). A program attempted to read or write to a volume which was no longer accepting i/o requests.

 

Howdy.

2014 Mac mini, MacOS 10.14.6, OWC Thunderbay 4(8TB x4 RAID5), Softraid 6.0.3, Softraid Driver 6.0.3

I found this thread because I noticed this has been happening to me as well(see error above).

 

Not as frequently(3 times in the past month), but I only really noticed it this last time(today) because my machine actually woke up from sleep with this message.

I have had my machine become unresponsive while asleep and I've unfortunately had to restart it with the power switch in the back because I could not wake it from sleep to do a proper reboot.

Now, after reading some of the messages in this thread and others, I'm wondering if it has to do with my cabling setup?

 

Currently I have the OWC connected directly to the Mac mini thunderbolt port and I have a Dell monitor connected to the OWC thunderbolt port next to it. 

e.g.: 

Mac ------TB------>OWC------TB------>DELL

 

Could the "wake from sleep" signal be *causing* the problem above or do you think it's *being caused* by the above error?

 

I have attached my softraid report file(NOT the log).

 

Thanks

 

 
Posted : 02/05/2021 7:26 am
(@softraid-support)
Posts: 8008
Member Admin
 

@scatteredbrain

The trigger for this error is the disks having different disk identifiers when they go to sleep, then when you woke up.

Yes it is possible it is an interaction with the Monitor and drives, but its not easy to know. You can try as a test, putting the monitor on the other thunderbolt port. I have tested this for several months on a Mac Pro 2019  with Thunderbolt monitors to try to replicate this but was not able to. Just never happened, where I was hoping it would. This is a vexing problem, without a clear solution.

 

BTW: its unfortunate SoftRAID cannot pull SMART data from your internal drive (its a change we need to make in SoftRAID), but it appears to be failing.

You can get a second option from a trial of DriveDx and see what it says. But start planning to do open heart surgery on your Mini and put a new drive in it. With the right tools it is not bad, but you need to buy a kit with the parts to do the take apart. its possible to put 2 drives in this Mini, by getting the correct adapter. But be careful, go very slow. Take photos as you take it apart and be careful removing the little connectors especially.

 
Posted : 02/05/2021 10:25 am
 CR7
(@cr7)
Posts: 7
Active Member
 

@mountaincat and @steve223, I, too, am seeing these exact issues after moving my newish (Dec 2020) ThunderBay 8 from a MacBook Pro running Catalina (zero issues) to an M1 Mini running Big Sur 11.3.1 and SoftRAID 6.0.3 (many, many issues). I'm not using docks and have the ThunderBay plugged right into the M1 Mini with a brand new Apple Thunderbolt 3 Pro cable. 

 

I'm seeing disk ejects and locked volumes with two new (Dec 2020) certified Toshiba 10TB disks with volumes created in SoftRAID 5.8.4 and 6.0.3. Interestingly, the other disks I have in the ThunderBay 8 are fine, including a few OWC SSDs and one striped volume I've been using with SoftRAID since 2012. 

 

Sometimes the issues appear when waking from sleep. Other times, Big Sur lets me know the disks were ejected hours before I wake the machine. SoftRAID won't mount the disks, and I have to restart. In fairness to OWC and SoftRAID, BigSur on the M1 has been full of issues and bugs. I've managed to work most of them out except for this one—but this is a big problem. After reading through the boards, though, it looks like this may not be an M1 issue.

 

I purposely waited to move the ThunderBay to the M1 Mini until we had a greenlighted version of SoftRAID. Now I want to cry. Literally.

 

Side note: I'm considering turning the two Toshiba volumes into Apple volumes to see if I can at least get a setup that functions because I use these disks every day for work. 

 

I'm submitting a ticket to SoftRAID but wanted to flag that you're not alone.

Screen Shot 2021 05 08 at 9.13.08 AM
Screen Shot 2021 05 06 at 7.07.42 AM
Screen Shot 2021 05 07 at 1.52.59 PM
 
Posted : 08/05/2021 10:34 am
(@softraid-support)
Posts: 8008
Member Admin
 

@cr7

Broadly it looks like either a bad disk, or enclosure.

Clues: only one disk is ejecting, not all 8, so this is not a thunderbolt chipset issue

Volume locking on one volume in one enclosure. (I am assuming this is only on the Toshiba's based on your description.

the volume locking is when the disk identifier (disk4 for example) changes while the system is running and disks not manually removed. It is "not allowed" by macOS and can cause data corruption, which is why SoftRAID locks the volume. the volume locking is a protection mechanism from a kernel bug, or a hardware issue, not a "bug" in SoftRAID. In your case, it seems clearly like a hardware issue, not a kernel issue. Whether a disk, or enclosure, needs to be isolated.

Attach a SoftRAID tech support file.

Next swap the disk positions. Understand this first: there are 4 PCI lanes in a TB 8. (next to each other).

I will assume the Toshiba's are in AB, CD, EF or GH?

Assuming they are next to each other, then swap for instance AB with GH.

Do the issues follow the disks, or the slots?

That will give a place to start diagnosing this.

 
Posted : 08/05/2021 11:31 am
 CR7
(@cr7)
Posts: 7
Active Member
 

@softraid-support I was going to submit a ticket, but I'll include the details here instead. Thanks so much. 

1) Two different disks are ejecting: Both "TM Backup 1" (Toshiba 10TB disk #1) and "Toshiba Backup (NC)" (Toshiba 10TB disk #2), shown below. I've only gotten the lock message on "Toshiba Backup (NC)."

2) "TM Backup 1" (Toshiba 10TB disk #1) was certified before moving the TB 8 to the M1, and the volume was created through SoftRAID 6.0.3. It's essentially a virgin disk.

3) "Toshiba Backup (NC)" (Toshiba 10TB disk #2) was created on SoftRAID 5.8.4 and has been in use since December 2020.

4) The ejecting issues started the same day I moved the TB 8 to the M1 Mini and upgraded to SoftRAID 6.0.3. No issues before that. Disks eject daily and sometimes multiple times. Could the new computer or new cable have set something off in the ThunderBay?

5) Both the TB 8 and Mini are hooked up to a UPS battery backup. Energy Saver is set to not put the disks to sleep. (Hopefully, I can tick that back on when we're done figuring this out?)

6) Right now, the Toshibas are in bays GH. I'll move the disks and see what happens. 

7) I've attached the tech support report. (You'll see there's a striped disk that's ready to fail, hence why I'm trying to get the issues with the new disks worked out.)

 

Thanks for your help.

 

Screen Shot 2021 05 08 at 12.28.14 PM
Screen Shot 2021 05 08 at 12.28.02 PM
 
Posted : 10/05/2021 8:24 am
(@softraid-support)
Posts: 8008
Member Admin
 

@cr7

Definitely the next test is moving the disks and see if the failure follows the disks, or the drives.

 
Posted : 10/05/2021 9:14 am
 CR7
(@cr7)
Posts: 7
Active Member
 

@softraid-support

Done. I'll keep you posted. (I put two OWC SSDs in bays GH.)

 

Just received this error. From previous support posts, it looks like this isn't an issue, but wanted to flag it just in case:

Screen Shot 2021 05 10 at 10.50.29 AM
 
Posted : 10/05/2021 10:46 am
(@softraid-support)
Posts: 8008
Member Admin
 

@cr7

Most cases of this should be fixed with 6.0.4, which is due in the next 24 hours. Please let me know if it continued after updating to 6.0.4

 
Posted : 10/05/2021 11:07 am
 CR7
(@cr7)
Posts: 7
Active Member
 

@softraid-support

 

So, I've narrowed down that we're looking at a disk communication issue, not a TB 8 issue. 

 

The two Toshibas are now in Bays C and D. Here's a series of events that happened today:

 

1) M1 Mini goes to sleep. Upon waking, both disks disappear:

Screen Shot 2021 05 10 at 5.06.47 PM
Screen Shot 2021 05 10 at 5.06.25 PM
Screen Shot 2021 05 10 at 5.06.33 PM

2) After the error messages display, "Toshiba Backup (NC)" remains mounted. But "TM Backup 1" does not, and I'm not able to mount it via SoftRAID. I can hit "mount" but nothing happens. I usually restart at this point to access the disk, but this time I didn't.

3) The M1 Mini goes to sleep again. "Toshiba Backup (NC)" disappears and gives the usual error message. But then both disks remount on their own, no restart required. 

 

Also wanted to mention:

• Apple has my MacBook Pro right now, but when I get it back I'll doubly confirm that these issues are limited to the M1/Big Sur/SoftRAID 6. All disks were working perfectly on my laptop through May 3rd, when I switched to the Mini.

• "TM Backup 1" doesn't have any data on it. 

 

Next steps? Would it be worth making "TM Backup 1" an Apple volume to see if the sleep issues persist?

 

 
Posted : 10/05/2021 5:39 pm
(@mygiguser)
Posts: 2
New Member
 

This happened to me twice now. I am on 6.0.3 waiting for your fix. Waiting for your 6.0.4 version ...

 

May 10 10:10:29 - SoftRAID Driver: One or more of the disks for the volume "Backup" (disk7) is no longer usable. The volume is now locked to prevent data corruption. Please restart your Mac to use this volume again.
May 10 10:10:29 - SoftRAID Driver: The SoftRAID volume "Backup" (disk7) encountered an error (E00002E4). A program attempted to read or write to a volume which was no longer accepting i/o requests.

May 11 02:23:52 - SoftRAID Driver: One or more of the disks for the volume "DOCS" (disk7) is no longer usable. The volume is now locked to prevent data corruption. Please restart your Mac to use this volume again.
May 11 02:23:52 - SoftRAID Driver: The SoftRAID volume "DOCS" (disk7) encountered an error (E00002E4). A program attempted to read or write to a volume which was no longer accepting i/o requests.

 
Posted : 11/05/2021 5:11 am
(@softraid-support)
Posts: 8008
Member Admin
 

@cr7

Yes test the Time Machine disk as Apple format. macOS tries to suppress some of these eject messages, but if you leave a file open (like a word/text edit file) it increases the chances macOS will report this to you.

 
Posted : 11/05/2021 9:23 am
(@softraid-support)
Posts: 8008
Member Admin
 

@mygiguser

this is not a bug we can fix, it is in the Apple kernel.

SoftRAID is the messenger, telling you that we detected this condition and locked the volume, otherwise you would have data corruption.

The root cause is disks are assigned disk numbers when connected. these numbers are "permanent" until the disk is removed. however, at sleep/during sleep//waking from sleep, these numbers changed, so SoftRAID alerts you.

 

We reported this to Apple several years ago, but it is not fixed yet.

 
Posted : 11/05/2021 9:26 am
(@steve223)
Posts: 151
Member
 

as I said before as sad as it is you should make people aware of the issue and explain that your hardware and software currently is not compatible.

i felt quite deceived having spend thousands of dollars on your products just to discover they don’t work properly with my Mac.

 
Posted : 11/05/2021 5:02 pm
Page 5 / 13
Share:
close
open