Softraid 6.0.53/2/2024 I ended up fixing my problem like you by deleting every SoftRaid file I could find after using AppDelete to delete SoftRAID 6.0.5 (SoftRAID would lock up and not let me use the uninstall). You must start with a clean install with no leftover elements of v.5 anywhere on the drive in order for it to work. It seems the whole problem centered around kexts and other elements left over from v.5 still on the system. Once the entire folder was deleted along with the application, I rebooted, reinstalled, and after re-approving identified developer, everything worked perfectly. It had elements of v.5 in there as well as the v.6 install. I went into the root library and deleted the entire SoftRaid folder. I was then unable to reinstall or get that developer approval prompt. When I tried again, I started getting the failure to load messages. I did get the OWC approval message upon original install, but when that worked, it wouldn't let me boot the OWC RAID enclosure. Best wishes and happy holiday.Posted by: got it solved. You've got a ways to go, brothers (or sisters). It's just not nearly as you have claimed with my Samsung SSD's and use case - on MBP 2019 and T3 (OWC brand Thunderbay 4) connected enclosures. Not that SoftRAID isn't worthwhile for speed improvement and large storage. I would have to discount the equivalence of Write and Read speeds you claimed, as that has NEVER been my case. That was the last stable configuration (which, BTW, as previously reported) one that had the same speed results as reported. My next step is more likely to be to put everything back to 5.x and HFS+ once again giving up on a failed experiment of SoftRAID6. So, let me know if that's available to test, I'll be happy to look into it further. When you have something that works in a current Beta version of Big Sur and on a release version of Catalina, it probably will need a complete reboot and reconfiguration anyway. One you admit to be (and I have demonstrated as) full of holes. What I have now is a work-around that barely does what I need with beta software. Even there, it proved dicey last time, so I see no reason to re-attempt it until there is a compatible software version that adapts SoftRAID across all existing platforms. That is in Big Sur and using SoftRAID 6.x. Cannot be Excluded in Time Machine because a duplicate appearance is shown when setting up the only way to certify a APFS disk in any of your apps, is to attempt it on APFS "Friendly" software and a hardware environment.Mount status of the Volume shows as "unmounted" when the volume is clearly mounted and usable in the Finder window and opens up just fine.The attached screenshots show the formatting of the Volumes as incorrect (type of device format = "Unknown Format").Do you have comments about some (apparent) visual issues with the status displays in the app when showing all devices:.The noticed the following problems when using it either in Big Sur or Catalina with the new drivers and the new app: I also replicated a standalone Extra non-RAID Disk volume. All seemed smooth (12 hours later) with the rebuilt Array. Afterwards the data was restored to the Volume from a working data backup in Retrospect Multi-Server. I started from scratch, erasing my drive and reformatting each Disk to APFS, then the built a new Volume from the disks as an APFS Volume. Until I discover a few flaws within the Array. I was all set to write a very complimentary post about how well the newest beta work (b42) in both Big Sur and Catalina. I have issues using the RAID4 array installed with APFS and migrated data from HFS volume->APFS Volume. Hello, this question is about the beta SoftRAID 6.0.1 and use an array within macOS Catalina and Big Sur.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |