Using Mercury Elite Pro Quad as a Time Machine drive and SoftRAID with BigSur
I'm brand new to SoftRAID. Bought an OWC Mercury Elite Pro Quad (currently have 4 2GB drives in it) to utilize as a RAID 5 drive solely for Time Machine backups.
First, here's my system:
Mac Mini (2018), 3 GHz 6-Core i5, 32 GB memory
Last week was running Mac OS Big Sur 11.2.2 (Now running 11.3 Beta 3)
SoftRAID v 6.0.1 b52
Initially, had the drives formatted as HFS+ and it kept hanging in the Mac Time Machine dialog with a dialog about preparing the drive for Time Machine.
I enrolled in the Mac OS beta program hoping it would help. Same issue. Then, via SoftRAID, I went ahead and re-initialized all four drives, but formatted them as APFS. Now it gets past the Time Machine preparing the disk, but it keeps trying but fails to do its initial backup to the drive. Also, I'm noting that throughout, it has been able to successfully complete Time Machine backups to a single external drive.
Looking in terminal there are 25 .interrupted files and one .inprogress.
Drive shows up fine and reports properly as 6GB in Finder. I can copy files to and from it fine, but it's not likely something about Time Machine.
Any help would be appreciated.
With Big Sur, Time Machine only works on SoftRAID volumes formatted as APFS .
So delete the volume, create a new one and select APFS as the file system. Then Time Machine will work. I do not think this issue will be fixed by Apple.
Yes, if you re-read my post above, I did eventually reformat to APFS.
It tries its initial backup on the time machine drive, and errors out with the very generic:
Time Machine couldn’t complete the backup to "Drive Name"
An error occurred while copying files.
Within SoftRAID 6 b53 I've been unable to erase or initialize any of the four individual drives to start over fresh/again.
@softraid-support Yes. Tried everything again this morning to be sure.
1. Ejected the volume.
2. Deleted the RAID 5 Volume in SoftRAID.
3. Initialized the four drives in SoftRAID.
4. Create new volume in SoftRAID (APFS)
4. Added drive to Time Machine.
5. Tries to do its first backup
6. Fails with a generic message, "Backup Not Completed. Time Machine couldn't back up to 'Volume Name'"
I've got another external drive that it takes turns with. The other drive completes its backups fine, but the SoftRAID volume continues to be able to complete its first backup.
Interesting that one volume can complete, another cannot. this indicates that the source volume itself should not be damaged.
Not being a Time Machine expert, its hard to know what is causing this and how to get past this problem.
BTW: to retest, all you need to do is erase the volume in SoftRAID.
What if you erase the volume with SoftRAID, select Time Machine, then restart? then Backup now?
The one thing I can think of is if this is a disk issue.
Make sure SMART USB drivers are active via the SoftRAID disk preferences. Shut down. remove ALL USB devices except keyboard/mouse.
Restart. Wait 5 minutes. Plug in your MEPQ and any other devices. This should allow the SMART USB driver to load, hopefully. Look in the disk tiles in SoftRAID. Are any of the disks showing an error condition?
Its worth a try, as I can't think outside of a disk error, why the problem backing up.
Anyone in the forum more of a Time Machine expert?
@softraid-support Sorry, took awhile to get back and try this. It's unable to erase the drive, error is just:
An error occurred erasing the volume "name". SoftRAID was unable to create a file system on this volume."
I Will work through the SMART steps next. The drives and enclosure are all brand new. I'm not saying drives don't fail out of the box, but still.
I do not think the volume type is the problem, Time Machine only sees a volume. Try one more time to unmount/delete/create an APFS volume, then when it mounts, does Time Machine ask to add it?
I will assume it does. Then it certainly ought to be able to complete the backup.
We only offer this when you create a new volume, so delete it create a new volume and select APFS.
This is our bug. We used a build script that had APFS disabled for 6.0.1. We are releasing 6.0.2 very shortly, which will have APFS available.
Sorry for the inconvenience.