I tried SoftRAID on a MacBook with two hard drives (striped). It will "initialize" and create the SoftRAID partitions, but complains that it cannot create the volume. No errors are evident.
This is using Yosemite and two identical 850 Pro Samsung drives.
Unless someone can suggest a fix soon, I will go back to using AppleRAID.
Here's the log:
Feb 7 1431 Balls-MBP SoftRAID Tool[693] : Deleting the volume "1TBSSD" ().
Feb 7 1432 Balls-MBP SoftRAID Tool[693] : The volume delete command for the volume "1TBSSD" () completed successfully.
Feb 7 1446 Balls-MBP SoftRAID Tool[693] : Creating the stripe (RAID 0) volume named "1TBSSD" of size 953 GB with the following disks: disk0, SoftRAID ID: 069D219C11804780, SATA bus 0, id 0, disk1, SoftRAID ID: 069D219C11479BC0, SATA bus 0, id 1.
Feb 7 1456 Balls-MBP SoftRAID Tool[693] : The volume create command for volume "1TBSSD" () failed with an error (error number = 31).
SoftRAID calls OS X (disktool) to create the file system on a new volume. disktool is failing for some reason.
Try a couple things:
Repair permissions on the boot volume and restart
Try a new admin account.
Let us know.
Well I tried it on two different boot volumes, the other one was Mavericks even.
What re the command line arguments for disktool
You should not have two systems with the same symptoms. There may be a third party utility interfering.
Do not use Disk utility to erase the volume, it does the wrong thing and puts another volume inside the SoftRAID volume.
I don't know the diskutil commands.
Did you try a clean admin account in the same boot OS?
Are you booting from an admin account? Has root been enabled in your system?
This is starting to sound like one of those "just reinstall your OS" kind of tips.
I only have one user. This failed on two different boot devices. If there is no way to diagnose the problem I'm not going to start doing completely random things in hopes it will magically work.
Is there, or is there not a way to diagnose the problem? I already asked for the disktool command line so I don't know what else to suggest.
The only other thing I could try is running the application AS root (not administrator)
So much for that idea
No there is no magic bullet here. I do not know what causes this, its a "one in a thousand scenario", i.e. this happens ,but rarely. Generally restarting, creating a new admin account, or booting from a clean OS works. I can check with engineering on Monday for additional ideas.
Please send a SoftRAID technical support file from a System that this failed from. support@softraid.com
What about safe boot. I could try that
I don't think so, but you can try. SoftRAID calls OS X after creating a volume. There is a rate issue where this does not work. We have never seen this in our lab, so don't know what is causing it. The fix is generally repairing the System, permissions, another admin account, or a clean install on another system. We have not had any user where one of the above did not work. Let us know if Safe boot gets around this or not, but I am dubious about it working based on the other attempts not resolving this.
Safe mode didn't help
It is a matter then of "what's different" from your system and 99.9% of others.
Was one of your systems a clean one? Or are they essentially snapshots or clones of one originating OS X install?
Do you have a standard password on your machine, or are you using it without a password?
Do you have any third party utilities installed that "manage", "clean" or "maintain" your system?
Hate to ask all these questions, but see if you can think of anything about your system that is different.
BTW: disable root, if you enabled it for testing this. root opens up several security holes in OS X.
Repairing permissions did not help
OK, I fixed the problem. I searched the entire disk and deleted every softraid file and reinstalled to get a new trial