Monterey 12.2.1 SoftRAID 6.2.1 Cannot create APFS RAID1 Time Machine
Having a frustrating morning trying to create RAID1 Time Machine volume.
Other specs: M1Max MacBook Pro 14, the discs are 6TB WD Red Plus HDD in OWC ThunderBay Flex 8.
All seems fine during the creation of the volume process:
1. Initialize both HDDs in SoftRAID
2. Select both discs to create new volume
3. Select RAID1, APFS, optimized for digital photography and max volume size @ 6TB (volume safeguard currently unchecked for easier deletion of unsuccessful attempts)
4. At the end of the process, I get the error message.
5. As it stands, Time Machine volume I created shows up looking fine, but cannot mount, therefore cannot be found in Time Machine app.
Any help or workaround appreciated - please see attached screenshots.
It seems to me the SoftRAID driver is not loading, so the volume file system is not created.
Have you done this?
Select reduced security and enable this:
Select the “Allow user management of kernel extensions from identified developers” checkbox to allow installation of software that uses legacy kernel extensions.
After enabling third party extensions, reinstall the SoftRAID driver, (do not immediately restart) and go to System Preferences / Security to "Allow" OWC as an identified developer.
If you do not do both, then the SoftRAID driver is not loading in macOS. Let me know if this is the issue.
Thank you, that worked and now I have a 2-disk RAID1 Volume in APFS (case sensitive) format. Beyond APFS, I didn't see the choice of making non-case sensitive, encrypted etc. as I am used to seeing with Apple's disk utility.
Do I need to go back into startup options and revert to Full Security or do I keep it at reduced security?
With regards to running Time Machine backup, I've hit another roadblock:
I get error message noting, "Two of the disks to back up have the same name. Rename one of the disks named “Macintosh HD”.
I understand when Apple introduced Catalina, many have encountered this issue. Within APFS formatted disk, there is the system and data, both named Macintosh HD. I've tried to rename either but so far no success. The disks I've used for Time Machine are brand new and have no previous Time Machine data stored. Also, I've already made two Time Machine backups on USB drive, once when I first received this MBP14 and again when I've loaded all the main apps I've been using. There were no issues during those two sessions, but this time around, I have no success trying to set up Time Machine with the RAID1 Volume.
This is more likely non SoftRAID related issue but if you could point me to the right direction, I'd be grateful.
Time Machine will convert the volume to case sensitive, so don't worry about that end. We cannot support encrypted yet, there is still a bug we are waiting to get resolved on encryption.
You need to keep third party security to enable developers, for M1. Each boot system has to have this correctly set also, as it is not computer based, but macOS based.
I don't know about the volume naming at all. I did find this note. Is your volume a Fusion volume?
Thanks. I've been reading up on this issue. It's not a fusion drive - it's SSD on my MBP14 and destination drives are HDD in OWC ThunderBay Flex 8. I may have renamed something incorrectly and now I seem to have created something above Macintosh HD system volume - there is another level of system snapshot that should not be there when I compare it with my other Macs.
I am now reinstalling Monterey, hope that restores the original structure.
I am going to erase the entire drive and start over. I am using "Erase All Content and Settings" from Apple Menu, new feature in Monterey I've found out about during looking into erasing the drive and starting anew.
I've disconnected Thunderbay Flex 8 and Thunderbolt Hub, and connected Envoy Express with newly erased M2 SSD to make one last attempt at Time Machine backup and curiously, it worked this time. When I reconnected ThunderBay Flex 8, however, the same error message appeared, even when I tried to back up to Envoy Express that worked only a few minutes ago. Would you be able to investigate this? From what I just observed, it's not an Apple Time Machine or OS issue but it's something that has to do with ThunderBay connection.