Timeline for Migration Assistant fail
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 28, 2020 at 9:58 | comment | added | Tetsujin | …except just this once, I didn't want a clone. I've been cloning one machine to the next since 2001. Every other Mac in the building also started as a clone of my setup at the time it was installed, then allowed to diverge since. | |
| Jul 28, 2020 at 9:57 | comment | added | Eric Duminil | @Tetsujin: That's sad that TM doesn't manage to do it. It seems like a perfect job for CCC, though, doesn't it? | |
| Jul 28, 2020 at 9:54 | comment | added | Tetsujin | Wipe TM disk, run TM once. Wipe boot disk, set up as new, Migrate when asked. [& at least 7 other variations on that theme] I have all this cloned & backed up elsewhere too, so I'm in no danger of losing data. I just want a 'clean' migrate. | |
| Jul 28, 2020 at 9:36 | comment | added | Eric Duminil | @Tetsujin: Thanks for the info. I wouldn't be surprised to learn that hard links are used even for just one single TM, along with the corresponding timestamp. It would be interesting to see how the disk looks like in Linux, for example. I guess other macOS programs are trying to play nice with TM structure or ignore it. Just to be clear, you're trying to use TM for cloning a disk right away? | |
| Jul 28, 2020 at 9:27 | comment | added | Tetsujin | to clarify, points 1, 2 & 3 were covered by using a single clean TM run so no hard links, also double-checked with DiskWarrior. Stil 'no werky'. | |
| Jul 27, 2020 at 0:45 | history | edited | Eric Duminil | CC BY-SA 4.0 |
added 1 character in body; edited body
|
| Jul 26, 2020 at 21:18 | review | First posts | |||
| Jul 27, 2020 at 0:31 | |||||
| Jul 26, 2020 at 21:13 | history | answered | Eric Duminil | CC BY-SA 4.0 |