![]() May I stop here and ask you if your situation is different from the way I've set out the usual manner of things - especially: did it open to the Welcome screen did you enter a User Name and if so, was it different from your stolen Mac's User Name?įrom your answers, we can sort things out. Especially if it was DIFFERENT from that on the TM - which is what Member gshali was alluding to, I believe. If you did create a User Account on your Mac immediately after you Powered-On, then there could be a conflict, I'm thinking. This is because TM restores everything including your User Account, settings etc, etc. The pre-requisites for this working are that you have NOT created a User account (Username) on your new Mac. Your select PC (TM) and click on Continue. Either the Mac would find it automatically or, more usually, invite to to navigate to the TM BU from whatever sources were mounted - in your case PC (TM). ![]() The conventional method of restoring from TM to a brand new Mac ( or one set up properly by the previous owner), is to Power-On, go through the Welcome in innumerable languages until it comes up "Do you want to restore from backup".Īt this point it gives you the choice of TM, Migration Assistant, other Mac - I think, this is from memory! ![]() Now you have New Mac > Home Network > PC (TM). Your setup was stolen Mac > Home Network > PC (TM) I'm assuming the new Mac was properly set up by the previous owner so that it opened with the Welcome screen. If I may, I'm going to imagine your setup and think through how I'd try to get TM to restore to a new Mac based on how it is done conventionally. I've already admitted that I was unaware that you could create a Time Machine (TM) Backup (BU) on a PC. Thank you for being so considerate and patient. The thing is that I never set a password for that Back Up, the PC has no user password on it and neither does the Mac.Ĭan anyone offer any helpful suggestions? It is so frustrating looking at this big Sparsebundle, that I can see in Finder across the network, but not being able to get to any of my files. The problem is, that having acquired a replacement MBP today (a 2011 13" running Sierra 10.12.3 2.8ghz i7 with 8GB of RAM), when I try to mount the TMBU.Sparsebundle, I am asked for a password before it will mount the file. On the 2nd drive on the PC, I have a 100GB "TMBU.Sparsebundle" file. When I set this up I found a guide online explaining how to get Time Machine to recognise a folder on the PC across the network and it (generally) worked well. To back up I was in the habit of using Time Machine to backup over my home network to a rather old desktop PC running XP SP3 with a big 2nd hard drive. Luckily, I was periodically backing up, but now I am having great difficulty retrieving my back up to a new machine. This is normally done through the -o offset option to mount, but in the case of HFS+ we need to also pass the partition size, otherwise the full size of the dmg image is used, giving errors such as " hfs: invalid secondary volume header" on mount.A few weeks ago my MacBook Pro was stolen. The reason for this error is that the HFS+ partition lives at an offset inside the sparse-bundle, so to successfully mount the partition we need to pass this offset to the mount command. This will manifest as errors such as " wrong fs type, bad option, bad superblock on /dev/loop1" when trying to mount the image. Some sparse-bundles may contain partition maps that mount.hfsplus will fail to process, for example the GUID Partition Table typically created for Time Machine backup volumes. Of allow_other and allow_root, as described in the first paragraph of this section. Permissions are only informative, and the access control happens in FUSE based on the presence Note: Unless the default_permissions option is also enabled, the owner and mount point
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |