SoftRAID fails afte...
 
Notifications
Clear all

SoftRAID fails after MacOS Clean and install (erase and install) MacOS 12.3

Page 2 / 3
(@softraid-support)
Member Admin

@henry-in-florida 

Use APFS. I am indicating it is your choice.

ReplyQuote
Posted : 23/03/2022 2:46 pm
Henry-In-Florida
(@henry-in-florida)
Estimable Member Customer
Posted by: @softraid-support

xattr /Library/Extensions/SoftRAID.kext

No response. So that's OK.

Macbook Pro Retina 2019, internal 1TB storage, 32GB RAM, two external T3 enclosures (2.5TB online storage), 6x500GB, EVO SSD, RAID 4; MacOS Mojave.

ReplyQuote
Topic starter Posted : 23/03/2022 2:47 pm
(@softraid-support)
Member Admin

@henry-in-florida 

Some users want to keep HFS, it is faster, there are recovery/repair tools (Disk Warrior for example), and they understand HFS. Some applications don't work well with APFS.

APFS is "the future", we default to APFS on flash media. APFS has no volume repair tools yet, unfortunately, but at the same time, volumes should get corrupted less often, as there are some protections built in against that.

Don't stress over this. Use APFS, unless you have a reason or preference not to.

ReplyQuote
Posted : 23/03/2022 2:49 pm
(@softraid-support)
Member Admin

@henry-in-florida 

Correct, no response is good.

If you reinstall 6.2.1, you should be OK. I do not know exactly what happened, but I seriously doubt it was a bug specific to 6.2.1.

ReplyQuote
Posted : 23/03/2022 2:51 pm
Henry-In-Florida
(@henry-in-florida)
Estimable Member Customer
Posted by: @softraid-support

@henry-in-florida 

Use APFS. I am indicating it is your choice.

Just so I don't have to redo this later on for the reason. The array has worked fine as GUID up to now. Can I batch format the partitions used? I have a 1TB split into the extra separate partition that I do not want destroyed. So that 1TB physical drive would end up with a partition as APFS and one GUID...

 

Macbook Pro Retina 2019, internal 1TB storage, 32GB RAM, two external T3 enclosures (2.5TB online storage), 6x500GB, EVO SSD, RAID 4; MacOS Mojave.

ReplyQuote
Topic starter Posted : 23/03/2022 2:51 pm
(@softraid-support)
Member Admin

@henry-in-florida 

When recreating the volume, there is no need to reinitialize the disks. Initializing just lays out the partition map for SoftRAID. Deleting/creating the volume completely refreshes everything.

We only added full APFS support in SoftRAID recently, you are correct.

ReplyQuote
Posted : 23/03/2022 2:52 pm
(@softraid-support)
Member Admin

@henry-in-florida 

Deleting the RAID 4 volume, with not affect your non RAID volume on the 1TB, correct. Creating a new volume will not affect it either.

ReplyQuote
Posted : 23/03/2022 2:55 pm
Henry-In-Florida
(@henry-in-florida)
Estimable Member Customer

 

Posted by: @softraid-support

@henry-in-florida 

Deleting the RAID 4 volume, with not affect your non RAID volume on the 1TB, correct. Creating a new volume will not affect it either.

After your comments, I did some more investigation. Found a couple of things that lead me to believe it's a combination of SoftRAID 6.2.1 and the Finder in MacOS 12.3. May I tell you why? 

Here's what I experienced. With all due respect for your opinion and previous testing, however here's what I experienced and how I overcame the difficulties:

  1. In OS 12.3 and SoftRAID 6.2.1 installed when you choose to un-mount from the app (via its Menu or KBD short cut ⌘+M), there appears to be a condition in Finder that prevents un-mounting or mounting. I was able to duplicate the condition and in Finder trying to eject the array if does fail and then gives me an error which SoftRAID app doesn't do while refusing to unmount. I was able to clear the problem by re-launching Finder through Force Quit. Don't know if you'll see it in the attached Tech Support file or the previous logs I sent you.  Once cleared BOTH finder eject AND SoftRAID eject work. 
  2. Logging out the user and logging in again doesn't affect this condition. 

So far, the App 6.2.1 has been solid after step #1 above. So, I buy that it likely isn't a SoftRAID problem, however 6.2.0 has never done that. Just sayin', haven't pinned down what in Finder is the cause of the issue. I regularly un mount the attached drives when taking the machine off it' local connection and desktop use to go portable. 

Macbook Pro Retina 2019, internal 1TB storage, 32GB RAM, two external T3 enclosures (2.5TB online storage), 6x500GB, EVO SSD, RAID 4; MacOS Mojave.

ReplyQuote
Topic starter Posted : 26/03/2022 1:47 pm
(@softraid-support)
Member Admin

@henry-in-florida 

Are you able to manually unmount the volume (eject from the desktop?)

Something is holding on to the volume most likely.

If this happens again, use this in terminal, lets assume your volume is named "RAID5" (you can rename it temporarily it is easiest without any spaces in the name)

sudo lsof /Volumes/RAID5

 

See what is open on this volume. It may be a clue.

ReplyQuote
Posted : 26/03/2022 2:13 pm
Henry-In-Florida
(@henry-in-florida)
Estimable Member Customer

@softraid-support 

When the issue happens, cannot delete from either the Finder (eject or drag to trash), I do get a warning the Finder couldn't eject SoftRAID give no warning, just cannot eject. 

Macbook Pro Retina 2019, internal 1TB storage, 32GB RAM, two external T3 enclosures (2.5TB online storage), 6x500GB, EVO SSD, RAID 4; MacOS Mojave.

ReplyQuote
Topic starter Posted : 26/03/2022 3:08 pm
(@softraid-support)
Member Admin

@henry-in-florida 

What happens when you run this when the volume does not unmount?

sudo lsof /Volumes/RAID5

ReplyQuote
Posted : 26/03/2022 9:10 pm
(@jonniemichael)
Active Member

I am running a 2018 Intel Macbook Pro, just updated to Monterey. My Raid 5 was mounting perfectly fine prior to the iOS update.

 

I have tried all of the suggestions above (reinstalling the software, reinstalling the driver, giving permission before restart, etc etc) nothing has helped

 

The drive still will not mount. I have attached a report and a screenshot

Screen Shot 2022 03 27 at 02.19.09
This post was modified 5 months ago 2 times by jonniemichael
ReplyQuote
Posted : 27/03/2022 2:21 am
Henry-In-Florida
(@henry-in-florida)
Estimable Member Customer
Posted by: @softraid-support

@henry-in-florida 

What happens when you run this when the volume does not unmount?

sudo lsof /Volumes/RAID5

Will try it if it happens again. Right now (un)mounting (from within app or via eject in Finder is no problem. Thanks for suggestion. 

Macbook Pro Retina 2019, internal 1TB storage, 32GB RAM, two external T3 enclosures (2.5TB online storage), 6x500GB, EVO SSD, RAID 4; MacOS Mojave.

ReplyQuote
Topic starter Posted : 27/03/2022 9:34 am
(@softraid-support)
Member Admin

@jonniemichael 

the SoftRAID driver is not loading.

When you installed the driver, did you go to System Preferences/Security to "Allow" OWC as a developer to enable the driver?

Try this:

Reinstall the SoftRAID driver. (Utilities menu)

After reinstalling the SoftRAID driver, (do not immediately restart) and go to System Preferences / Security to "Allow" OWC as an identified developer.

ReplyQuote
Posted : 27/03/2022 12:06 pm
(@jonniemichael)
Active Member

@softraid-support I have tried this about a half a dozen times, as well as reinstalling the software itself. The security dialogue only showed up on the first install and I allowed permission. 

ReplyQuote
Posted : 27/03/2022 1:14 pm
Page 2 / 3
Share:
close
open