Migration Assistant...
 
Notifications
Clear all

Migration Assistant doesn't see SoftRAID Volume

(@bldraid)
Eminent Member

The disk on my Late 2014 iMac failed, and I am trying to use its Time Machine backup on a SoftRAID RAID 5 volume to restore the data onto another machine, a MacBook Pro Late 2019.

When booted into Big Sur 11.4 and with a ThunderBay attached via Thunderbolt 2 cable -> Thunderbolt 2 to 3 Adapter -> MacBook Pro Late 2019, I  can see my SoftRAID volume containing my Time Machine backups in Finder. However, when I launch Migration Assistant, it says "Looking for other sources..." forever and never finds the SoftRAID volume.

Thoughts?

Quote
Topic starter Posted : 01/07/2021 1:14 pm
Topic Tags
(@softraid-support)
Member Admin

This used to work, I have not tried this in Big Sur.

the SoftRAID volume is mounted on the desktop, that shows the driver is loaded and Migration Assistant should definitely see it. I would have to test this to ensure it works. Its possible this broke in Big Sur.

ReplyQuote
Posted : 01/07/2021 4:17 pm
(@bldraid)
Eminent Member

Yes, please test it.

ReplyQuote
Topic starter Posted : 01/07/2021 4:23 pm
(@bldraid)
Eminent Member

Apple Tier II support couldn't figure it out either and blamed the disk. I think Apple is wrong -- Time Machine data is found in Recovery Mode (but strangely only very old snapshots over 6 months old) and in Finder (which can see all the snapshots up to the most recent). I've had to resort to manually copying files.

But if restoring from a Time Machine volume to a new machine doesn't work with a SoftRAID RAID 5 volume on a Thunderbay, that is a huge problem.

ReplyQuote
Topic starter Posted : 02/07/2021 2:55 am
(@softraid-support)
Member Admin

@bldraid

I just ran a test and it worked. Perhaps there was a problem with the Time Machine backup.

My test was straightforward:

Create a time machine backup on a SoftRAID volume

Boot into Time Machine, to be told you must use Migration Assistant (normal behavior)

Restarted, ran Migration Assistant and after a few dialog boxes, passwords, etc, was able to migrate data.

 

So this still works as expected.

I did not try a Time Machine from an older OS.

ReplyQuote
Posted : 02/07/2021 8:56 am
(@bldraid)
Eminent Member
Posted by: @softraid-support

Boot into Time Machine, to be told you must use Migration Assistant (normal behavior)

What do you mean precisely by "boot into Time Machine?"

Here is precisely what is not working for me:

1) Time Machine backup on SoftRAID (RAID 5) volume on machine 1 (Late 2014 iMac), attached via Thunderbolt 2. Running Big Sur 11.4.

2) Reattach volume via Apple Thunderbolt 2 -> Thunderbolt 3 adapter to machine 2 (Late 2019 MacBook Pro). Also running Big Sur 11.4.

3) Machine 2 already has a running system. SoftRaid volume is visible in Finder and appears fine (has Time Machine icon).

4) Run Migration Assistant directly on Machine 2 -- it closes all applications and logs out.

5) The volume never appears on the list -- just says "Looking for sources..." forever.

ReplyQuote
Topic starter Posted : 02/07/2021 11:04 am
(@softraid-support)
Member Admin

@bldraid

the first step was booting into internet recovery mode. Seeing if a user can select it there. You may want to try it, to be sure macOS sees it as OK. I was checking where the bug was, assuming this was a generic bug.

When I ran Migration Assistant, as you, the volume appeared and allowed migration.

 

What if you run Disk First Aid on this volume? Does it give any errors? (Disk Utility)

ReplyQuote
Posted : 02/07/2021 11:28 am
(@bldraid)
Eminent Member

Yes, in Recovery Mode, the volume also appears for me too. But it only contains the full TM backups, none of the incremental ones. And my last TM full backup was over 6 months ago. Googling finds similar experiences for others (that a TM source in Recovery Mode only makes available full backups).

Yes, Apple had me run Disk Utility's First Aid on the TM volume. It found no errors and changed nothing.

I need to run the Migration Assistant directly after booting into an existing system in order to access the latest incremental backup. This should work but does not. Are you saying it did for you?

ReplyQuote
Topic starter Posted : 02/07/2021 11:35 am
(@softraid-support)
Member Admin

@bldraid

It worked, but I only did one backup. I will try tonight after working on the system, so I have an incremental worth testing.

ReplyQuote
Posted : 02/07/2021 2:09 pm
(@bldraid)
Eminent Member

Hrmmm... I couldn't get it to work at all, period, even for the full backups. Migration Assistant, when launched directly from a running OS, simply does not see the TM volume at all.

ReplyQuote
Topic starter Posted : 02/07/2021 2:14 pm
(@softraid-support)
Member Admin

@bldraid

If you run Disk Utility, First Aid? does it fix anything?

Is this an APFS volume? This could be a bug from legacy volumes, as Big Sur requires all new Time Machine volumes to be APFS.

ReplyQuote
Posted : 02/07/2021 4:34 pm
(@bldraid)
Eminent Member

I already said "Yes, Apple had me run Disk Utility's First Aid on the TM volume. It found no errors and changed nothing."

Yes, this is an old MacOS Extended (Journaled) volume, not APFS. But it was working fine with Time Machine on the old iMac (also running BigSur 11.4).

What's really frustrating, is that I was letting Time Machine alternate between this disk and an SMB volume on a Synology NAS, and Migration Assistant can't use that backup either. It sees the NAS, lets me authenticate to it, select the TM volume and then just sits there forever saying "Loading backups..."  I've seen that exact problem mentioned by other users on Synology's forums, and I have a tech support case open with them waiting on response.

But this is maddening that I can't get Migration Assistant on the new machine to adopt either the local TM volume from the SoftRAID disk or the remote sparse bundle one from the NAS. I periodically used both of these backups to restore specific files sporadically on the old machine -- and I watched the logs, so I'm as certain as I can be that both backups are in good shape. I really think this is some kind of Migration Assistant bug for the local volume (maybe you're right about MacOS Extended vs APFS) and a Synology bug for the remote volume. Aaargh.

I tried doing an end run around the Migration assistant by using 'tmutil inheritBackup' directly from a root shell but got a weird error (which I also saw others getting on Google with no solution) -- which definitely lends weight to your MacOS Extended vs APFS theory.

# tmutil inheritBackup /Volumes/SoftRAIDVolume/Backups.backupdb/OldMachine 
Failed to inherit machine store at '(null)', error: Error Domain=TMStructureErrorDomain Code=7 "Structure has wrong type" UserInfo={NSLocalizedDescription=Structure has wrong type}
#
ReplyQuote
Topic starter Posted : 02/07/2021 4:52 pm
(@bldraid)
Eminent Member

This Apple support article clearly states that MacOS Extended Time Machine volumes are still supported in Big Sur.

ReplyQuote
Topic starter Posted : 02/07/2021 6:53 pm
(@bldraid)
Eminent Member

Interestingly, I got the exact same error when trying to go to the NAS spare bundle directly as I did when trying to go to the local disk. That definitely rules out a SoftRAID disk error and makes a corrupted TM backup unlikely too. It really points to "tmutil inheritBackup" not being able to understand HFS+ (which I believe is what the sparse bundle on the NAS is using too).

# tmutil inheritBackup /Volumes/Time-Machine-NAS/OldMachine.backupbundle    
Mounting disk image...
Enter password to access "OldMachine.backupbundle": 
Failed to inherit machine store at '(null)', error: Error Domain=TMStructureErrorDomain Code=7 "Structure has wrong type" UserInfo={NSLocalizedDescription=Structure has wrong type}
#

But why was the old machine running Big Sur as well able to continue using its HFS+ formatted TM volumes? It can continue using it on Big Sur upgrades but not move it to a new machine using Big Sur? If true, that's pretty bad, Apple. (pun intended).

This post was modified 4 weeks ago by bldraid
ReplyQuote
Topic starter Posted : 02/07/2021 7:26 pm
(@softraid-support)
Member Admin

@bldraid

the problem I noticed is Big Sur requires APFS on any new SoftRAID volume, but allows you to move a pre-existing time Machine from Catalina to Big Sur. I am speculating somthing related to this issue is happening to you.

ReplyQuote
Posted : 02/07/2021 10:52 pm
Share:
close
open