[Sticky] Running Big Sur (beta) on Intel Macs
I resolved this with:
sudo kextcache --prune-staging
EDIT: I seldom post without an edit.
Maybe you know:
What is the difference between these:
sudo kmutil clear-staging
sudo kextcache --prune-staging
I usually send users these:
sudo kmutil clear-staging
sudo kextcache -i /
I purchased SoftRAID end of March 2018 for $179, and now you want me to upgrade so I can use your software for $99.99. That is a giant steaming pile of SH!#. Horrible way to treat your customers who have already spent a lot of money on overpriced software.
I already got softraid with Thunderbays i boughtin 2017-2018, but in 2018 i needed a function that i was told was not supported by the included softraid so i had to pay $179 to upgrade. And now you want another $100 so i can continue to have functionality. YOU PEOPLE ARE F'N STONED!
Guess what? My Thunderbay RAID just hosed itself running the released version of SoftRAID XT. I checked with OWC techsupport and they say no version of SoftRAID supports APFS. "As of this time with a full release of SoftRAID 6, there are no supported APFS RAID volumes." Anyone care to comment????
There goes my Time Machine backup. I'm going to try RAID using Apple's Disk Utility.
SoftRAID can create a APFS problem, but at present only beta versions. You can run the beta (don't even install the driver, just create and quit), create an APFS volume, then use Time Machine on it.
the reps need to give advice on "released" versions. 6.1 will fully support AFPS, but we do not have the new user interface for that working yet.
@softraid-support Understand. Tech support suggested using Disk Utility (RAID 0 and 1) for now. Hadn't tried using it before and it was very easy.
One thing I did notice, and a little off topic, is that my ThunderBay RAID mini is a little weird, shutting down when I close the lid on my M1 MBA. When I use TouchID to unlock the screen, I get a message saying I didn't disconnect the RAID properly and while it spins the drives back up it doesn't remount them. OWC Unmounter app said it was ok to disconnect meaning it unmounted everything from the OWC TB3 14-port dock automatically. This doesn't have anything to do with SoftRAID or Disk Utility but with the way the ThunderBay turns on. There isn't an ON/OFF switch, it turns on when it senses a Thunderbolt connection. It was doing this when using SoftRAID as well so I'll need to contact OWC tech support and see if there's a sleep setting I can turn off.
Wonder if you are describing two issues.
when you unmount (or ejecting) are you waiting for all activity lights to go off on the drives? Big Sur flushes the drives one at a time, which can take quite a while. That may cause part of the issue.
WHen the volume does not remount what do you do to get it to remount?
@softraid-support What I described had nothing to do with unmounting. When I closed the M1 MBA's lid, I believe it goes to sleep. When I open it and log in, the RAID usually powers up but then just sits there. It give me the prompt about ejecting properly but I never ejected anything, I just closed the lid. It appears closing the lid shuts down the RAID and maybe even the TB3 dock. I guess the proper way to shut the MBA lid would be to unmount the dock, which unmounts everything attached to the dock, wait for everything to spin down, then close the lid. Of course, with a laptop, this never is the process anyone would take. I leave an external NVMe drive (OWC's) attached to the MBA directly for Time Machine and it doesn't have any issues staying mounted and waking up(?) when the lid is opened.
As for remounting, I haven't actually tried that other than unhooking the TB cable, which shuts the RAID off, then reattaching, which powers up the RAID and mounts it again. Not the normal way to do things.
the disks ejecting improperly means the connection was lost, even if for a microsecond.
The unusual part is the disks not immediately remounting. This indicates a connection issue. I assume you checked that cables are tightly inserted on all connection points?
How long after closing the lid do the drives spin down? Immediately? or after a short period of time?
If you direct connect the drives, is the behavior the same? Or is the dock necessary in the chain to get this issue?
@softraid-support Ok, figured out it was a passive TB3 cable. Not sure where I got this cable from. It works with the Fledging 1TB external drive but not with the RAID. Here's my exhaustive testing:
1. MBA opened up, operational. Not external disks attached.
2. Plugged power to RAID in, OWC icon front of drive lights up, disks silent. Checked all cables were inserted properly.
3. Plugged TB3 cable into MBA from RAID, drives spin up and RAID mounted.
Test 1: Close lid of MBA.
Result 1: RAID stayed mounted, disk access lights all off (no activity)
Notes: Noticed OWC icon light was blue when mounted. When lid closed, disks spun down but fan still running. OWC icon light bright white.
4. Unmounted RAID by dragging to Trash (OWC unmounted only unmount everything attached to dock). OWC icon stayed blue, disks spun down, fan still running, drive ejected.
5. Pulled TB3 out of MBA, added TB3 dock, plugged dock into MBA. OWC icon turned white, fan turned off.
6. Plugged TB3 dock into MBA. Noticed OWC Dock Ejector doesn’t recognize dock is attached. Blue light on bottom of dock is on.
7. Plugged RAID into dock. Nothing happened to RAID. Re-checked cables. These have “3” on cable.
8. Switched cables (one had label saying it was passive cable). Now says safe to unplug dock. Both blue and yellow light on bottom of dock are on.
8a. Using passive cable, connected a Fledging external NVMe drive and it mounted. Now OWC Dock Ejector changes to Eject volumes, which worked.
9.Had to go look for another cable. Found one with a “4” on it so not sure which TB product included this cable.
10. Used TB cable with “4” on it between RAID and dock and RAID spun up and mounted. Dock Ejector says it can eject volumes.
Now that I have RAID running I’ll close lid of MBA and see what happens.
11. Waited for a minute for RAID to stabilize then opened lid, logged on and RAID still mounted.
Conclusion: Must have been a weird TB3 cable (with “3” on it) that didn’t have enough electronics in it to work with everything.
Extra: I now have the following OWC Thunderbolt items
1. TB3 dock 14-port
2. TB3 mini dock (not really needed now since I got the 14-port dock)
3. TB hub (says it includes TB4 cable so that’s where I got it) (will try this between dock and RAID to make sure it works, then I’ll have three TB3 ports available)
Yep, too many but at least I’ll have enough ports for older hardware.
@softraid-support Well, I sent my last reply a little early. Everything appeared to be working fine but after leaving the MBA lid closed for a few hours, when I opened it I had four notifications that I hadn't ejected the drives properly. Something is going to sleep and not waking up properly. I didn't move anything so cables were all in place.
Your scenario is exactly what we and many others warned Apple/intel about when they wanted one connector for all new cables, USB, Active/passive, etc. Chaos.
Its possible if that one cable has a 3 on it, and is causing issues, it is faulty. If it is ours, we would replace it for you, I would guess (I am not in RMA department, however)
Thunderbolt 4 helps a little, as at least USB can work with the TB 4 cables, etc.
Sorry about this. 4 notices are what you generally would get, as 4 disks did eject, this is a disk issue, not a volumes issue.
I do think you are on the right track, however. was this eject with a thunderbolt 4 cable, or "3" cable?