Monterey Volume not...
 
Notifications
Clear all

[Sticky] Monterey Volume not mounting

158 Posts
29 Users
2 Likes
8,481 Views
(@softraid-support)
Posts: 8005
Member Admin
Topic starter
 

If you are running SoftRAID under Monterey and cannot get your volume to mount, post here. It is best to include a SoftRAID Tech Support file with your post.

 
Posted : 09/06/2021 3:56 pm
kteare
(@kteare)
Posts: 3
New Member
 

I made 3 volumes and all appear on my desktop but none of them mount and all say "unknown format". They do function inside Monterey. I am running an M1 MacBook Pro 13".

I am also getting intermittent crashes - just a full freeze followed by an automatic reboot after about 60 seconds of being frozen.

I uninstalled and reinstalled 6.1 b3

 

The tech support report is not happening - just hangs forever. I will reboot and try to generate it and post here if successful.

 

 

 
Posted : 21/07/2021 1:29 pm
kteare
(@kteare)
Posts: 3
New Member
 

OK I was able to generate a tech support report after a reboot.

 

 

Screen Shot 2021 07 21 at 11.17.28 AM

 

A crash report following a freeze is here - https://www.dropbox.com/s/1kdsdhhyjugm6oz/Crash%20report.txt?dl=0

 

 
Posted : 21/07/2021 1:45 pm
(@softraid-support)
Posts: 8005
Member Admin
Topic starter
 

@kteare

these are new volumes so there is no data on them. They are also APFS, so SoftRAID cannot read the file system on them, until we release 6.1.

 

I am guessing you created the volumes when the SoftRAID driver was blocked by Big Sur or Monterey.

What if you take one of them and "erase" with Disk Utility? Does that mount it?

 
Posted : 22/07/2021 10:36 am
kteare
(@kteare)
Posts: 3
New Member
 

@softraid-support - I erased and re-did as non-apfs. Then copied data and erased the other, then synced.

 

Both now mount.

 

Softraid did originally allow me to choose apfs as the format. Not sure if the driver was active then, but I had assumed it was.

 

I have to keep the "Backup" raid as apfs for timemachine use. So now softraid reports it as unmounted (see screen share).

 

It is a lot more stable. But I am still getting repeated freezes and reboots. Maybe 2-3 times a day.

Screen Shot 2021 07 22 at 10.09.45 AM

 

 
Posted : 22/07/2021 12:10 pm
(@softraid-support)
Posts: 8005
Member Admin
Topic starter
 

@kteare

Whether the driver actually loads is something SoftRAID application cannot detect. When we originally designed SoftRAID, there was no reason to believe a loaded driver would not load. Its only recently that things like this occur. The driver is required to call macOS to create the file system, which would explain why the file system was not created by macOS.

Lets deal with your hangs now. You should not be getting any. Does the mouse still move? the clock? (set it to show seconds).

Does the machine auto restart, or do you have to hit the power button?

 

I notice one thing, there are devices you have that are showing as USB 2 (Stream Deck and USB Control Link). There is a Thunderdock in that chain.

What if you move the dock to another bus? Worth a try.

 
Posted : 22/07/2021 1:01 pm
(@ricardogf)
Posts: 16
Eminent Member
 

As already informed to SoftRAID support, my RAID5 volume, which mounts perfectly on Mojave and also shows up as a volume in Terminal's diskutil list, cannot be mounted via SoftRAID. I have uninstalled the whole software, its drivers, reinstalled them, etc., to no avail. It is extremely aggravating to pay an extra USD 129 to have it "NOT work" under Monterey. So for the moment, virtually all my files (including photos, music and Steam apps/games) are ALL unavailable.

 
Posted : 02/11/2021 5:01 am
(@ricardogf)
Posts: 16
Eminent Member
 

Correction: the RAID5 volume is NOT shown via diskutil list either - only on Mojave.

 
Posted : 02/11/2021 5:40 am
(@softraid-support)
Posts: 8005
Member Admin
Topic starter
 

@ricardogf

Did you "Allow" OWC in System Preferences/Security when you installed the SoftRAID driver?

If not, reinstall the driver, go there and click "Allow", otherwise macOS is blocking the driver from loading.

If you clicked Allow and your volumes do not mount yet, then attach a support file.

 
Posted : 02/11/2021 10:56 am
(@zathras)
Posts: 29
Member
 

I have the release candidate of Monterey installed turned off the Public Beta updates so hoping that the 12.1 update fixes whatever is the problem I'm having mounting my volume currently. 

I tried the final 6.2 installer

and I keep getting the message when I type this command:

eric@Erics-M1-MacBook-Pro ~ % sudo kmutil load -p /Library/Extensions/SoftRAID.kext

Enter PIN for 'Certificate For PIV Authentication (Yubico PIV Authentication)': 

Error Domain=KMErrorDomain Code=71 "Incompatible architecture: Binary is for x86_64, but needed arch arm64e

Incompatible architecture: Binary is for x86_64, but needed arch arm64e

Incompatible architecture: Binary is for x86_64, but needed arch arm64e" UserInfo={NSLocalizedDescription=Incompatible architecture: Binary is for x86_64, but needed arch arm64e

Incompatible architecture: Binary is for x86_64, but needed arch arm64e

Incompatible architecture: Binary is for x86_64, but needed arch arm64e}

zsh: segmentation fault  sudo kmutil load -p /Library/Extensions/SoftRAID.kext

eric@Erics-M1-MacBook-Pro ~ % 

 

Now I'm trying 6.2.b6

Same error.

I'll attach the Report.

I have uninstalled and reinstalled multiple times. Always allowing OWC in the security settings. 

This post was modified 2 years ago by Zathras
 
Posted : 03/11/2021 5:03 pm
(@softraid-support)
Posts: 8005
Member Admin
Topic starter
 

@zathras

In the attached support file, the 6.2 b6 driver is loaded.

the Yubico is a SMART card driver, correct?

I am guessing this support file was saved after the kmutil command, which mounts your volume, but you need to run it each startup?

(I am a little unclear, as it appears the driver is loading)

 
Posted : 03/11/2021 5:11 pm
(@zathras)
Posts: 29
Member
 

@softraid-support Yes, the Yubico Key is my smart card for logging in and typical functions online. 

It may be mounting the driver, but my OWC M42 RAID never mounts for access to it. No matter how many times I run it it shows the RAID volume and the connected volumes, and the green lines connecting them together properly, but it always says "unmounted" to the right of the volume name.

softraid screenshot

I just realized it's showing my boot drive as unmounted as well.

This post was modified 2 years ago by Zathras
 
Posted : 03/11/2021 5:28 pm
(@zathras)
Posts: 29
Member
 

I just looked at it in Disk Utility and tried to mount it and it said it can't mount the APFS volume. I don't remember formatting as APFS, but since it's NVME, maybe that's required? 

Disk Utility image
 
Posted : 03/11/2021 5:38 pm
(@softraid-support)
Posts: 8005
Member Admin
Topic starter
 

@zathras

With 6.2 we default to choosing AFPS for volumes on flash media, as flash is fast enough to handle the extra overhead of APFS.

APFS volumes should not be corrupted, but you notice your volume has a "disk identifier", disk12 at the time of your support file. That means everything is there to publish the volume, the volume is published and then will mount if macOS can mount it. The volume is dated from May, so I am guessing it used to mount? Is it backed up? APFS volumes should rarely get damaged to not  mount, that was the main point of moving away from HFS.

You can try Disk Utility First Aid, but there are few tools to repair APFS volumes. Disk Drill can recover from many.

This post was modified 2 years ago by SoftRAID Support
 
Posted : 03/11/2021 9:08 pm
(@zathras)
Posts: 29
Member
 

@softraid-support - I have it backed up. So I'm guessing that means I need to write it off and create a new volume? It was mounting in the beta back in August and September, and with an update to the beta (not sure which) it stopped working. 

That should probably do the trick. 

Thanks, I knew this kind of thing could happen playing with betas. 

Eric

 
Posted : 03/11/2021 11:02 pm
Page 1 / 11
Share:
close
open