Disk removed & out ...
 
Notifications
Clear all

Disk removed & out of sync errors (RAID5 / 6.2.1 b3 / M1 Max on 12.1)

10 Posts
3 Users
0 Reactions
1,230 Views
(@jeroen020)
Posts: 4
Active Member
Topic starter
 

I've recently set up a Flex 8 on a 14" MBP M1 Max on Monterey 12.1 using Softraid 6.2.1 b3 with a 4 disk RAID5 array and have been getting removed disk warnings, as well as an out of sync error that happened today. There are no OS crashes or panics, only errors reported by Softraid as seen in the log entries below. Any ideas what I can do to prevent issues? Or is it too early to reliably use this setup?

Jan 02 16:53:50 - SoftRAID Driver: A disk (disk14, SoftRAID ID: 0924EEBD95C0B880) for the SoftRAID volume "42TB RAID 5" (disk5) was removed or stopped responding while the volume was mounted and in use.

Jan 02 17:02:01 - SoftRAID Driver: A disk (disk4, SoftRAID ID: 0924EEB91CB43A80) for the SoftRAID volume "42TB RAID 5" (disk5) was removed or stopped responding while the volume was mounted and in use.

Jan 04 01:03:23 - SoftRAID Driver: A disk (disk14, SoftRAID ID: 0924EEBD95C0B880) for the SoftRAID volume "42TB RAID 5" (disk5) was removed or stopped responding while the volume was mounted and in use.

Jan 04 02:07:30 - SoftRAID Driver: The RAID volume "42TB RAID 5" (disk5) is out of sync. A rebuild has started automatically.
Jan 04 02:07:49 - SoftRAID Driver: The RAID volume "42TB RAID 5" (disk5) has been rebuilt successfully.

Jan 04 03:32:17 - SoftRAID Driver: A disk (disk13, SoftRAID ID: 0924EEC0BF785500) for the SoftRAID volume "42TB RAID 5" (disk5) was removed or stopped responding while the volume was mounted and in use.
 
Posted : 04/01/2022 4:46 am
(@softraid-support)
Posts: 9200
Member Admin
 

Are all SoftRAID disks being noted as ejected, or a subset?

are they the same disks each time?

If more than one (It appears 2 above), are they next to each other?

 

A tech support file would help.

 
Posted : 04/01/2022 11:21 am
(@jeroen020)
Posts: 4
Active Member
Topic starter
 

@softraid-support 

Are all SoftRAID disks being noted as ejected, or a subset?

No, only individual disks, not multiple at the same time I included all log file entries in my original post

are they the same disks each time?

No, it happened to disk4 and disk13 (see log file in original post)

A tech support file would help.

Alright, will do next time - for now I moved the Thunderbay back to my Intel Mac mini as I don't want to risk data loss.

 

 
Posted : 06/01/2022 6:39 am
(@softraid-support)
Posts: 9200
Member Admin
 

@jeroen020 

Looking forward to the support file, it will clarify things for me.

 
Posted : 06/01/2022 12:13 pm
(@americanedgemedia)
Posts: 5
Active Member
 

I am running four thunderbolt raids on an m1 max macbook pro. Every time I start up my mac, I get a missing disk error. It is always the same disk in the same enclosure. If I pull that drive out of the enclosure and put it back in, the drive is then readable and "out of sync" then after a few minutes, softraid rebuilds the volume and it functions normally for as long as I keep the computer turned on, even for several days. As soon as I restart or shut down and boot up my computer, that same drive shows up as missing again, and I have to begin the same process of physically removing and reseating into the enclosure and letting softraid fix the "out of sync" issue. Any thoughts on what could be causing this? The enclosure is the Akitio Thunder3 Quad X, which was performing perfectly on my old imac, but started doing this on my fresh install of Monterey (not migrated from old computer)

 
Posted : 09/01/2022 12:24 am
(@softraid-support)
Posts: 9200
Member Admin
 

@americanedgemedia 

Try two tests. (I think it is the disk, but it could be the enclosure)

With only the one enclosure connected, I assume this still happens?

If you swap that disk with another one on the other side of the enclosure, does the problem follow the disk, or the slot?

 
Posted : 09/01/2022 1:37 pm
(@jeroen020)
Posts: 4
Active Member
Topic starter
 

@softraid-support I decided to use an Intel Mac mini for a few months which worked flawless. As 6.2.1 came out of beta I figured I'd try it again on my M1 Max MBP. After plugging it in I got several errors:

SoftRAID Volume Out-Of-Sync
The SoftRAID volume "42TB RAID 5" is out-of-sync. The
SoftRAID driver has automatically started rebuilding this
volume. You can continue to use this volume while it is
rebuilding.

It then rebuilt for a minute or two after which the RAID 5.

Also when ejecting using the OWC Dock Ejecter, I get this error when unplugging the thunderbolt cable:

SoftRAID Error
An internal part of the SoftRAID application has stopped
functioning properly. Please quit SoftRAID and relaunch it.

I'll attach a support file.

Two questions:

- I was assuming M1 hardware is by now fully supported, but I can't find this mentioned in the release notes?

- What's causing the Dock Ejector error? Any risk of unplugging the cable if it means getting this error?

 

 
Posted : 15/03/2022 3:55 pm
(@softraid-support)
Posts: 9200
Member Admin
 

@jeroen020 

Is the disk you are ejecting a Time Machine volume?

It would explain this behavior...

 
Posted : 15/03/2022 10:26 pm
(@jeroen020)
Posts: 4
Active Member
Topic starter
 

@softraid-support the out of sync error is on a regular 42TB RAID 5 volume. The enclosure that I’m ejecting has 8 disks, 4 are in the RAID 5 volume, and 4 are single disks, one of which is indeed Time Machine. 

Do I understand it correctly that SoftRAID crashes when I eject it after using the OWC ejector app if there’s a Time Machine volume in the enclosure? If so, how do I safely unplug the dock from my laptop?

My other question was if the M1 is now officially supported/stable? It wasn’t stable a few months ago when I first tried, but I hoped that 6.2.1 would fix this so I can sell my Intel mac.

 
Posted : 16/03/2022 2:10 am
(@softraid-support)
Posts: 9200
Member Admin
 

@jeroen020 

Time Machine received some changes in Monterey. One of the changes requires APFS. As a result, new bugs were introduced, one of them seems to be it "holding on" to SoftRAID volumes, which I have replicated.

Its not "dock ejector" causing the issue, it is the fact that Time Machine is not letting go of an unmounted volume.

We are looking at whether there may be a workaround to this behavior, I don't know of one yet.

 
Posted : 16/03/2022 10:43 am
Share:
close
open