Time Machine Backup Failure
Well....
More and more frequently, I'm getting a backup failed message from Time Machine. I don't see anything particularly incriminating from the console log...but, generally, it's the same problem (below):
Jun 30 22:45:13 BigMacintosh-2 /System/Library/CoreServices/backupd[313]: Backup requested by user
Jun 30 22:45:13 BigMacintosh-2 /System/Library/CoreServices/backupd[313]: Starting standard backup
Jun 30 22:45:14 BigMacintosh-2 /System/Library/CoreServices/backupd[313]: Backing up to: /Volumes/Big TimeMachine/Backups.backupdb
Jun 30 22:45:14 BigMacintosh-2 /System/Library/CoreServices/backupd[313]: Failed to create progress log file at path:/Volumes/Big TimeMachine/Backups.backupdb/Bob's Big Mac/2008-06-30-194423.inProgress/.Backup.236587514.320138.log.
Jun 30 22:45:14 BigMacintosh-2 /System/Library/CoreServices/backupd[313]: Error: (-50) Creating directory F0BA6CF7-9087-4EB4-A54B-E3561374FBA2
Jun 30 22:45:14 BigMacintosh-2 /System/Library/CoreServices/backupd[313]: Failed to make snapshot.
Jun 30 22:45:20 BigMacintosh-2 /System/Library/CoreServices/backupd[313]: Backup failed with error: 2
I'm wondering if 10.5.3 was the culprit, since I had no problems prior to it. Guess I'll see if 10.5.4 fixes this oddity... Until then, a restart generally gets the next backup going...
Thoughts? Solutions?
Bob
Nope...a third auto backup failed...
Jul 2 10:12:29 BigMacintosh-2 /System/Library/CoreServices/backupd[412]: Starting standard backup
Jul 2 10:12:29 BigMacintosh-2 /System/Library/CoreServices/backupd[412]: Backing up to: /Volumes/Big TimeMachine/Backups.backupdb
Jul 2 10:12:30 BigMacintosh-2 /System/Library/CoreServices/backupd[412]: No pre-backup thinning needed: 269.3 MB requested (including padding), 219.33 GB available
Jul 2 10:12:37 BigMacintosh-2 /System/Library/CoreServices/backupd[412]: Copied 495 files (7.2 MB) from volume Macintosh HD.
Jul 2 10:12:38 BigMacintosh-2 /System/Library/CoreServices/backupd[412]: Starting post-backup thinning
Jul 2 10:12:38 BigMacintosh-2 /System/Library/CoreServices/backupd[412]: No post-back up thinning needed: no expired backups exist
Jul 2 10:12:38 BigMacintosh-2 /System/Library/CoreServices/backupd[412]: Backup completed successfully.
Jul 2 10:19:54 BigMacintosh-2 /System/Library/CoreServices/backupd[427]: Backup requested by user
Jul 2 10:19:54 BigMacintosh-2 /System/Library/CoreServices/backupd[427]: Starting standard backup
Jul 2 10:19:54 BigMacintosh-2 /System/Library/CoreServices/backupd[427]: Backing up to: /Volumes/Big TimeMachine/Backups.backupdb
Jul 2 10:19:55 BigMacintosh-2 /System/Library/CoreServices/backupd[427]: No pre-backup thinning needed: 260.7 MB requested (including padding), 219.32 GB available
Jul 2 10:20:01 BigMacintosh-2 /System/Library/CoreServices/backupd[427]: Copied 441 files (9 KB) from volume Macintosh HD.
Jul 2 10:20:01 BigMacintosh-2 /System/Library/CoreServices/backupd[427]: Starting post-backup thinning
Jul 2 10:20:01 BigMacintosh-2 /System/Library/CoreServices/backupd[427]: No post-back up thinning needed: no expired backups exist
Jul 2 10:20:01 BigMacintosh-2 /System/Library/CoreServices/backupd[427]: Backup completed successfully.
Jul 2 10:27:56 BigMacintosh-2 fseventsd[41]: callback_client: ERROR: d2fcallbackrpc() => (ipc/send) invalid destination port (268435459) for pid 431
Jul 2 10:29:03 BigMacintosh-2 [0x0-0x31031].org.mozilla.thunderbird[447]: Warning: unrecognized command line flag -psn0200753
Jul 2 10:40:48 BigMacintosh-2 fseventsd[41]: callback_client: ERROR: d2fcallbackrpc() => (ipc/send) invalid destination port (268435459) for pid 467
Jul 2 11:11:39 BigMacintosh-2 kernel[0]: SetCryptoKey R: len 32, idx 1
Jul 2 11:12:28 BigMacintosh-2 /System/Library/CoreServices/backupd[505]: Starting standard backup
Jul 2 11:12:28 BigMacintosh-2 /System/Library/CoreServices/backupd[505]: Backing up to: /Volumes/Big TimeMachine/Backups.backupdb
Jul 2 11:12:31 BigMacintosh-2 /System/Library/CoreServices/backupd[505]: No pre-backup thinning needed: 309.8 MB requested (including padding), 219.32 GB available
Jul 2 11:12:49 BigMacintosh-2 /System/Library/CoreServices/backupd[505]: Copied 804 files (40.9 MB) from volume Macintosh HD.
Jul 2 11:12:49 BigMacintosh-2 /System/Library/CoreServices/backupd[505]: No pre-backup thinning needed: 260.7 MB requested (including padding), 219.28 GB available
Jul 2 11:12:57 BigMacintosh-2 /System/Library/CoreServices/backupd[505]: Copied 460 files (0 bytes) from volume Macintosh HD.
Jul 2 11:12:59 BigMacintosh-2 /System/Library/CoreServices/backupd[505]: Starting post-backup thinning
Jul 2 11:12:59 BigMacintosh-2 /System/Library/CoreServices/backupd[505]: No post-back up thinning needed: no expired backups exist
Jul 2 11:12:59 BigMacintosh-2 /System/Library/CoreServices/backupd[505]: Backup completed successfully.
Jul 2 11:36:38 BigMacintosh-2 kernel[0]: disk1s3: I/O error.
Jul 2 11:36:38 BigMacintosh-2 kernel[0]:
Jul 2 11:36:38: --- last message repeated 1 time ---
Jul 2 11:36:38 BigMacintosh-2 kernel[0]: jnl: disk1s3: dojnlio: strategy err 0x5
Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/C9675DCF-6359-43B8-8696-866D96AD91E 1)(Error) IndexCI in storestream_flush:store_streamflush write err:22
Jul 2 11:36:38 BigMacintosh-2 kernel[0]: jnl: disk1s3: end_transaction: only wrote 0 of 57856 bytes to the journal!
Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/C9675DCF-6359-43B8-8696-866D96AD91E 1)(Error) IndexCI in _ContentIndexSyncIndexBulk:Sync error live.0.
Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/C9675DCF-6359-43B8-8696-866D96AD91E 1)(Error) IndexGeneral in notify_lowspace:low space for device 234881029 (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/C9675DCF-6359-43B8-8696-866D96AD91E 1)
Jul 2 11:36:38 BigMacintosh-2 mds[35]: (Error) Volume: LOW DISK SPACE device:234881029
Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4)(Error) IndexCI in ci_ftruncate:ftruncate(57 /Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4/live.0.indexPostings, 4194304) error:22
Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4)(Error) IndexCI in initPayload:ftruncate err: 22
Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4)(Error) IndexCI in ci_ftruncate:ftruncate(18 /Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4/live.0.indexIds, 262144) error:22
Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4)(Error) IndexCI in openindexfile:ftruncate error: 22, size: 262144, live.0.indexIds
Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4)(Error) IndexCI in ContentIndexOpenBulk:Could not open /Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4/live.0.; needs recovery
Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4)(Error) IndexCI in copyFileOrFd:error (22) opening 0.indexGroups
Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4)(Error) IndexCI in recoverIndex:Unrecoverable error: could not recover groups file (0.)
Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4)(Error) IndexCI in CIMetaInfoCreate:Tried to create index when index already existed eMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB9434
Jul 2 11:36:39 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/C9675DCF-6359-43B8-8696-866D96AD91E 1)(Error) IndexCI in ContentIndexOpenBulk:Unclean shutdown of /Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/C9675DCF-6359-43B8-8696-866D96AD91E 1/live.0.; needs recovery
Jul 2 11:36:39 BigMacintosh-2 mds[35]: (Error) Server: registerForDeadNameNotification failed ((os/kern) invalid argument)
Jul 2 11:36:39 BigMacintosh-2 kernel[0]: disk1s3: I/O error.
Jul 2 12:12:28 BigMacintosh-2 /System/Library/CoreServices/backupd[593]: Starting standard backup
Jul 2 12:12:28 BigMacintosh-2 /System/Library/CoreServices/backupd[593]: Backing up to: /Volumes/Big TimeMachine/Backups.backupdb
Jul 2 12:12:28 BigMacintosh-2 /System/Library/CoreServices/backupd[593]: Error: (-50) Creating directory 2008-07-02-121228.inProgress
Jul 2 12:12:28 BigMacintosh-2 /System/Library/CoreServices/backupd[593]: Failed to make snapshot container.
Jul 2 12:12:33 BigMacintosh-2 /System/Library/CoreServices/backupd[593]: Backup failed with error: 2
Similar Messages
-
Time Machine backup failure on case-sensitive disk?
Hello,
I just started getting a Time Machine backup failure error that says "A disk you are backing up is case-sensitive, but the backup disk is not."
None of my external disks have changed and I've not added any new ones.
The error seems to be stemming from the fact that I'm logged in as multiple users on my system, all with MobileMe accounts. When I "get info" on all mounted disks, the only ones that are reporting "Mac OS Extended (Case-sensitive, Journaled)" are the mounted iDisks from the other use accounts that I'm currently logged in as.
Does this mean I cannot use Time Machine while logged in as multiple users, all with the iDisks mounted? That would be a major annoyance to either have to log out/log in to each user as I need them or to disable iDisk syncing in my MobileMe prefs.
Regards,
TerryThat seems odd to me; my iDisk shows WebDAV as the format and doesn't interfere with backups, but I don't have any other users' iDisks, either.
Another possibility would be to reformat your TM drive as case-sensitive. That would, of course, erase all your backups so TM would start over from scratch, and some possible troubles when restoring (see the pink box in #5 of the Frequently Asked Questions *User Tip,* also at the top of this forum, for details); but you'd no longer have the backup problem. -
How can I resolve repeated Time Machine backup failures?
Time Machine stopped backing up from my wife's iMac 2 GHz Intel to a designated Iomega FireWire drive on August 6th. I have since erased, reformatted, and reselected the external drive. The profile for the external drive is as follows:
Manufacturer: Iomega
Model: 0x1
GUID: 0xD0B80E5B000BE6
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Up to 400 Mb/sec
Sub-units:
HDD USB 2.0/1394A Unit:
Unit Software Version: 0x10483
Unit Spec ID: 0x609E
Firmware Revision: 0x12804
Product Revision Level:
Sub-units:
HDD USB 2.0/1394A SBP-LUN:
Capacity: 149.05 GB
Removable Media: Yes
BSD Name: disk2
Mac OS 9 Drivers: No
Partition Map Type: GPT (GUID Partition Table)
S.M.A.R.T. status: Not Supported
Volumes:
Iomega Time Backup HD:
Capacity: 148.73 GB
Available: 148.31 GB
Writable: Yes
File System: Journaled HFS+
BSD Name: disk2s2
Mount Point: /Volumes/Iomega Time Backup HD
I have also performed Tech Tool Pro 4.6.2 Advanced Tests on all related hardware to repair any damaged volumes and files but the Time Machine backup stops after at 97.5 MB of approximately 60+ GB of data.
I have been unable to detect a cause for the failure in the Console logs but I note that the following entry has been repeated every few seconds in the system log since about August 23rd:
Aug 26 10:55:30 Dee-Coopers-iMac mds[37]: (Error) Import: importer:0x844400 Importer start failed for 501 (kr:268435459 (ipc/send) invalid destination port)
Aug 26 10:56:00: --- last message repeated 7 times ---I had experienced the similar problem when I first upgraded to Leopard. The problem was caused by spotlight indexing my hard drive and at the same time Time Machine was trying to backup the spotlight index file. The solution was to temporary exclude most of the documents (I have a lot of pdf files) from spotlight and let it runs through the indexing process before starting Time Machine.
I don't know if my experience help you or not but it might be something worth looking into.
Good luck. -
Time Machine Backup failured (Issue 1426)
Hello at all,
well i have got a big problem with my macbook.
I reinstalled it today (incl. formatting the HD). Now i tried to backup my data (I did all updates) 10.5.8 and it failured.
Its horrible. I need all my data.
I hope there´s somebody who can help me, because i have to learn for my Bachelor.
Here some more data:
Mac OS X, 10.5.8
4 GB 667 MHz DDR2
The time Machine:
WD Ext HDD 1021 Media
1 TB
Mac OS x Extended journaled
And i have to say it was the first time ever i had to reinstall the system since february 2008 i bought my MacBook.
Please help me...
Christinmickleroy wrote:
We setup time machine backups in an office environment which is managed by a mac OS X Lion server.
I'm not familiar with the server product, but the actual backup process should be the same as on the client version.
On some occasions, a device requests an admin username and password whilst time machine is backing up.
Does it say Admin password, or could it be a password for the backup device?
Feb 1 10:01:16 pc-205 diskarbitrationd[15]: SystemUIServer [206]:24835 not responding.
Feb 1 10:01:33 pc-205 diskarbitrationd[15]: SystemUIServer [206]:24067 not responding.
Not related to Time Machine.
Feb 1 10:06:15 pc-205 sandboxd[513] ([61]): mds(61) deny file-write-data /dev/dtracehelperThat's not coming from Time Machine. Looks to be related to Spotlght (mds) trying to index something.
Feb 1 10:07:16 pc-205 mds[61]: (Error) Volume: Could not find requested backup type:2 for volume
We see that occasionally. It seems to be spurious, or at least not a significant problem.
Feb 1 10:07:37 pc-205 com.apple.backupd[436]: Backup completed successfully.
Feb 1 10:07:39 pc-205 com.apple.backupd[436]: Ejected Time Machine disk image.
Feb 1 10:07:40 pc-205 com.apple.backupd[436]: Ejected Time Machine network volume.
Yes, that's the "bottom line."
Could this be fixed by running a full backup as admin so that time machine doesn't have to backup these inaccessible files (to normal users) anymore?
No. However a backup runs, it runs as the root user, so has access to everything. -
Time Machine backup failure on 60Gb iPhoto Library on second partition
I had 1 partition on my Macbook Pro (2010). I have several users on the mac and I use fast switching for them. All users use same iPhoto Library and iTunes Media - they are situation in a separate folder in my partition root. My Time Capsule was setup to backup everything and it actually did it well.
Sometime ago I started to find a solution to avoid file permission problem - when different users add files/photos, they have permission to delete/change for them only. This caused some unwanted behavior. I read a lot of forums and basically the most appropriate solution is to create a separate partition on the same HDD and remove checkbox on it to support "Owner".
So I did it - created new partition. Then I moved iTunes and iPhoto to new partition and then I started backup again. Unfortunately, it failed. It took me 2 days to understand that it actually fails on iPhoto Library - all other staff works ok. But as soon as I allow to backup iPhoto Library, it starts backing up and shows some progress, but when 1-2 Gb (or sometimes 100-500 MB) complete it shows that "Backup failed - ... this might be temporary problem..".
I did not manage to resolve this - so I removed partition and reverted everything back by copying iTunes library and iPhoto library to external drive and then back after removing second partition. When I enabled backing up, everything worked great again - no problem.
So here is the question - why backup failed on iPhoto library when it was on second partition? Are the any ideas?Move/backup/move back/backup did not fix the problem. TM still didn't backup the missing directories.
I was finally able to convince TM to do the right thing by following the procedure described here:
http://www.nzmac.com/quick-tips/time-machine/how-do-i-reset-time-machine.html
This isn't a solution because I still don't know what caused TM to think that it backed up something that it didn't back up. But the article was suggested by a friend of mine in IT who also owns a few Macs. After following the procedure and running TM again I can see all of the previously missing files backed up on the ext drive. I also used BackupLoupe (http://www.soma-zone.com/BackupLoupe/) to browse the files that were actually copied by the last backup. I see that TM copied the directories that I knew were missing and two other directories that I did not know were missing.
At this point I think my TM backup is complete. But now I'm on the lookout for a better backup solution. Until I find it I'll need to periodically compare backup sizes to make sure that TM keeps doing its job. -
I have had to reinstall my Mavericks OS and use a Time Machine backup. Now when I open InDesign I get Error:5 , AMT subsystem failure. Does anyone have a fix for this?
I have had to reinstall my Mavericks OS and use a Time Machine backup. Now when I open InDesign I get Error:5 , AMT subsystem failure. Does anyone have a fix for this?
-
Restore encrypted Time Machine backup: password failure
hi,
I upgraded my mid 09 MBP with an SDD and created a Fusion Drive maintaining my HDD in the optical bay. After rebooting and wanting to restore from a Time Machine Backup, I'm prompted with a password request of the disk image, being the password I used to encrypt the TM when creating it.
No matter how I enter the password, it says it's not correct and I can't proceed.
Finally I created in a fresh setup of Mavericks. Once I'm in my Mac, When going to Time Machine, I see my Time Capsule drive on the network, and entering the encryption password, I can indeed access my Sparse Bundle.
I have to say that my password contains a space at the end of the password (it slipped in by copying the password by accident) and I think it might be the reason it's not accepting it as the valid password when in recovery/setup mode.. Either way, I've tried the password with and without the space so...
In Disk Utility, I've had the disk listed but the change password feature is disabled..
I've looked thru different forums, but no luck so far.
Anyone who has had the same issue or has a clue on how to either change the encryption password or how to install the full backup I have in my sparse bundle, it would be highly appreciated!
Thanks in advance.Hello:
This thread seems to answer your question:
https://discussions.apple.com/message/12949561#12949561
Barry -
Time Machine backups corrupt or external hard drive failure?
My goal today was to upgrade my MacBook Pro's HD, and to restore my system from my latest Time Machine backup which resides on an external hard drive. I installed the new hard drive, formatted it as Mac OS Extended (Journaled), and selected Restore System From Backup from Utilities. The system restore was five minutes form finishing when I received an error that the system restore could not be completed, and that I should restart my machine and try again. I did as instructed, but once the system restore process began, the screen went gray, and I was told that the Snow Leopard install could not be completed.
Before beginning the process a third time, I ran Disk Utility from the Snow Leopard install disc and attempted to verify and repair the external (Time Machine) hard drive. The Time Machine hard drive could not be verified, nor could it be repaired. I popped in the old hard drive into my MacBook Pro, booted Snow Leopard, and ran Disk Utility, and tried again repairing the Time Machine hard drive. Here is the log of the error I received:
2010-12-29 21:14:30 -0800: Verify and Repair volume “Time Machine”
2010-12-29 21:14:30 -0800: Starting repair tool:
2010-12-29 21:14:31 -0800: Checking Journaled HFS Plus volume.
2010-12-29 21:14:31 -0800: Checking extents overflow file.
2010-12-29 21:14:31 -0800: Checking catalog file.
2010-12-29 21:20:22 -0800: Invalid node structure
2010-12-29 21:20:22 -0800: The volume Time Machine could not be verified completely.
2010-12-29 21:20:22 -0800: Volume repair complete.
2010-12-29 21:20:22 -0800: Updating boot support partitions for the volume as required.
2010-12-29 21:20:22 -0800: Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
2010-12-29 21:20:22 -0800:
2010-12-29 21:20:22 -0800: Disk Utility stopped repairing “Time Machine”: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
Do these errors indicate that my Time Machine backups located in the Backups.backupdb are corrupt, or is the external hard drive corrupt and failing?
The Time Machine backups are on a Maxtor OneTouch, and from what I've read, they're prone to an early demise. I've also recently noticed that my Time Machine backups started slowing. For example, I would plug in my external hard drive and if 1.3GB needed to be backed up, it would stall at 300 MB before jumping to 700 MB, stall again, then jump to 900 MB. That could be a sign of a failing hard drive, correct? If the external hard drive is failing, I can purchase a new eternal hard drive then copy the Backups.backupdb to the new hard drive, correct?
However, if Backups.backupdb is corrupt, then from what I understand, I would have to start fresh. I would prefer to not start fresh unless there's no other option, as I would be losing almost three years worth of Time Machine backups.
Any guidance is appreciated. Thanks!ali_baba7 wrote:
2010-12-29 21:20:22 -0800: Invalid node structure
2010-12-29 21:20:22 -0800: Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
It's possible a heavy-duty 3rd-party utility such as +Disk Warrior+ can fix that. It's about $100, and there's no guarantee, but it's probably a good investment for the future.
Do these errors indicate that my Time Machine backups located in the Backups.backupdb are corrupt, or is the external hard drive corrupt and failing?
The structure of the file system is damaged.
That may have been caused by the disk beginning to fail, but there's no way to tell for sure until you erase and reformat the disk and try to use it.
I've also recently noticed that my Time Machine backups started slowing. For example, I would plug in my external hard drive and if 1.3GB needed to be backed up, it would stall at 300 MB before jumping to 700 MB, stall again, then jump to 900 MB. That could be a sign of a failing hard drive, correct?
It could, but it could also be whatever's wrong with the file structure.
If the external hard drive is failing, I can purchase a new eternal hard drive then copy the Backups.backupdb to the new hard drive, correct?
No. You can't copy corrupted backups. They're all linked together, like a database, so if anything's damaged, the whole set is suspect, and can't be copied.
There are a couple of options:
If the disk is physically ok, and the directory damage was recent, you might be able to restore from an earlier backup. But since you noticed problems some time ago, the damage may not be recent.
Or, you might be able to get up and running by just installing OSX from your SL Install disk (and the 10.6.5 "combo" update). You'll be missing whatever wasn't restored in that last 5 minutes or so. Things are restored in the same order they're listed by the Finder, so it will be the last things in the last user account. You should be able to figure out where it stopped, check or delete the very last file (likely incomplete) and selectively restore as many of the remaining things as you can, via the "Star Wars" display.
Just to make things more difficult, if the disk is failing, the more you use it, the more likely it is to get worse or fail completely.
So your safest bet may be to install OSX, then download and install the 10.6.5 "combo" update. Info and download available at: http://support.apple.com/kb/DL1324 Be sure to do a +Repair Permissions+ via Disk Utility (in your Applications/Utilities folder) afterwards. Then recover what you can. -
Hard drive failure! New hard drive/Time machine backup/iPhone questions
Hello,
I have a 2011 MacBook Pro who's hard drive failed (rather acutely too, I do use disk utility to check it's health regularly) and I bought a replacement to install (SSD!). I have a bunch of questions but have only found partial answers in searches. Maybe it's best to list them:
1. I'd like to do a fresh install of the OS X using OS X Recovery because I'm concerned my Time Machine backup is partly corrupted. I hadn't updated to Mavericks, will I be able to install Mountain Lion? If not: will this be a problem with my backup files?
2. Say the OS X Recovery works, how do I use Time Machine to restore things like my iTunes library/iMessages/email/iPhoto library etc? In other words: just the data I can't get any other way (I hope it's not too corrupted). And/or should I use my iCloud backup on a few of these (iMessages/contacts)?
3. Do I need to set up the new OS X install with the same account names/home disk name etc. for the restored backup files to function?
4. Is this going to f'up iCloud or vice versa?
5. Finally, how do I sync my iPhone to the "new" computer without erasing the iPhone (which had an iOS update since my last backup to Time Machine). Or do I have to restore the iPhone too.
6. How come Apple doesn't have a mobile theme for their website yet?
Any help would be much appreciated,
MattDo you still have the original System Reinstall DVD set that came with your Mac?
If you created that Lion external drive you have from YOUR Mac, when Lion was installed on it, and it also contains a Recovery HD partition you can use that to boot to the Recovery HD and reinstall Lion on the new drive. And or Clone that external to the new internal drive you installed.
Right since your Mac came with Snow Leopard you can't use the Online Internet Recovery system to reinstall Lion, as your system didn't originally come with Lion, but you should still be able to boot to it to do diagnosic things like using Disk Utility, going to the Net to get help and even Restoring the system from a Time Machine backup. But you will get an error if you select Reinstall Mac OS X. The firmware update is usually applied with system updates.
If you created a New Time Machine Backup when any of the Download Only version of OS X were installed on your internal drive Time Machine, the system, Copies over the files needed to boot the system from that backup drive. If it was a care over backup from when Snow Leopard was installed is might or might not be bootable. Only way to tell is to connect it and at startup hold down the Option key to get the Boot selection screen, IE The Boot Manager screen, and see if it shows up as a Boot Source. If it does thenn it contains the files needed to get to the Mac OS X Utilities, IE the Recovery HD files.
What you should do is Boot the system from either the Time Machine backup, if it is bootable, or your External that has Lion on it, The Recovery HD if that drive contains a Recovery HD, or your Original Snow Leopard reinstall DVD that came with your Mac and then try to Restore from your Time Machine backup drive.
If that fails to restore your system properly then nyou should reinstall Snow Leopard and the iLife Apps from the Original Discs then upgrade to Mt Lion which will be in the Mac App Store under your Purchases area. Then maybe you can restore your files from that Time Machine backup.
scardanelli wrote:
I've had a bunch of issues with my computer (you can look at some of my other questions on these forums) which, to my mind anyway, seemed to be finally given a diagnosis when my HD crashed. It may be paranoia but there have been enough problems that I'd rather do a clean install to be on the safe side.
I have an early 2011, shipped with Snow Leopard.
I was under the impression that Time Machine can't be used as a boot drive and the OS X Recovery is a firmware update (on my computer) or hard wired in (on later computers). I might be wrong. I was planning on using the internet recovery, the HD failed right after I got some password protected files unencrypted and onto an external drive (was that necessary?) but wasn't sure if it's a problem if it installs Mavericks.
So Setup Assistant will configure my accounts the same and I don't need to worry about that? That's a relief.
Thanks for the lengthy response. -
How do I reinstall Mavericks from a time machine backup? (Hard drive failure)
Ok, so I have a mid-2007 iMac and the hard drive finally died. It originally shipped with Leopard or something, but I had it upgraded to Mavericks. I have an external hard drive with a current Time Machine backup on it. I am about to replace the internal hard drive with a brand new (unformatted) hard drive. So here is the question: Is there a way to boot from my Time Machine backup and then reformat the drive and do a Time Machine recovery?
I have the old OS X install disks, but I don't want to have to upgrade through all of the old OS Xs. I also have a Macbook that I could create a bootable USB from--something like this (http://lifehacker.com/how-to-create-an-os-x-mavericks-usb-installation-drive-145 0280026)--and then I could reformat the drive and recover from Time Machine. But is there an easier way? Can I just boot straight from my external hard drive that has the backup on it?
Thanks for your help everyone, I'm hoping to be able to take care of all of this tonight.You can try this. OPTION boot the computer.
Boot Using OPTION key:
1. Restart the computer.
2. Immediately after the chime press and hold down the
"OPTION" key.
3. Release the key when the boot manager appears.
4. Select the disk icon labeled Recovery HD.
5. Click on the arrow button below the icon.
This should boot the Mavericks Utilities Menu.
Drive Partition and Format
1. Open Disk Utility from the Utilities menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Apply button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Security button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
When the formatting is done quit Disk Utility and return to the Main Menu. Now select the option to restore/reinstall OS X from a Time Machine backup. Follow the directions. -
Sudden Failure in Time Machine Backups
Over the last week and a half, I can no longer use Time Machine to back up my HD. I get about 2/3 through and it fails with this message in the log:
Error parsing SystemMigration.log to determine source volume of system migration.
Here is what I have tried:
Three separate drives, one of the drives is brand new
Changed the options in time machine to point to each drive
deleted the preferences entry for time machine and let it recreate itself.
Verify and repair disk with Disk Utility
Verify and Repair disk with Drive Genius 2
(both times, there was no indication of errors).
I am out of ideas, short of wiping and restoring the entire OS. Any assistance would be greatly appreciated. Thank you.Here you go!
Starting standard backup
Backing up to: /Volumes/Time Machine Backup/Backups.backupdb
Error parsing SystemMigration.log to determine source volume of system migration.
Backup content size: 121.1 GB excluded items size: 1.4 GB for volume iRob's iMac
No pre-backup thinning needed: 143.65 GB requested (including padding), 929.92 GB available
Waiting for index to be ready (101)
SystemFlippers: didn't consume all data for vers ID 1 (pBase = 0x10072d050, p = 0x10072d05d, pEnd = 0x10072d05e)
SystemFlippers: didn't consume all data for vers ID 1 (pBase = 0x103075b1c, p = 0x103075b30, pEnd = 0x103075b31)
Error: (-50) SrcErr:NO Copying /DamagedFiles/009041d6 msvcrt.dll to /Volumes/Time Machine Backup/Backups.backupdb/iRob's Rockin' iMac/2010-03-08-155222.inProgress/AE677AB7-C8AF-4C2A-966F-49E23DB4BFC4/iRob's iMac/DamagedFiles
Copied 34.6 GB of 119.7 GB, 120552 of 1394304 items
Error: (-36) SrcErr:YES Copying /Users/iRob/Library/Application Support/Backup/Backup Library/C630B3F8-02EF-4F31-83F9-184616613CD8/Personal Data & Settings - 2007.01.19-16.55.50.122.IncrementalBackup/Contents/PriorSecondaryLocations.plis t to (null)
Error: (-36) SrcErr:YES Copying /Users/iRob/Library/Application Support/Backup/Backup Library/C630B3F8-02EF-4F31-83F9-184616613CD8/Personal Data & Settings - 2007.01.19-18.47.03.227.IncrementalBackup/Contents/PriorSecondaryLocations.plis t to (null)
Error: (-36) SrcErr:YES Copying /Users/iRob/Library/Application Support/Backup/Backup Library/C630B3F8-02EF-4F31-83F9-184616613CD8/Personal Data & Settings - 2007.01.20-18.47.03.252.IncrementalBackup/Contents/PriorSecondaryLocations.plis t to (null)
Error: (-36) SrcErr:YES Copying /Users/iRob/Library/Application Support/Backup/Backup Library/C630B3F8-02EF-4F31-83F9-184616613CD8/Personal Data & Settings - 2007.01.21-18.47.13.144.IncrementalBackup/Contents/PriorSecondaryLocations.plis t to (null)
Error: (-36) SrcErr:YES Copying /Users/iRob/Library/Application Support/Backup/Backup Library/C630B3F8-02EF-4F31-83F9-184616613CD8/Personal Data & Settings - 2007.01.25-18.47.09.272.IncrementalBackup/Contents/PriorSecondaryLocations.plis t to (null)
Error: (-36) SrcErr:YES Copying /Users/iRob/Library/Application Support/Backup/Backup Library/C630B3F8-02EF-4F31-83F9-184616613CD8/Personal Data & Settings - 2007.01.26-18.47.03.172.IncrementalBackup/Contents/PriorSecondaryLocations.plis t to (null)
Error: (-36) SrcErr:YES Copying /Users/iRob/Library/Application Support/Backup/Backup Library/C630B3F8-02EF-4F31-83F9-184616613CD8/Personal Data & Settings - 2007.01.27-09.27.33.223.IncrementalBackup/Contents/PriorSecondaryLocations.plis t to (null)
Error: (-36) SrcErr:YES Copying /Users/iRob/Library/Application Support/Backup/Backup Library/C630B3F8-02EF-4F31-83F9-184616613CD8/Personal Data & Settings - 2007.01.28-08.08.20.569.IncrementalBackup/Contents/PriorSecondaryLocations.plis t to (null)
Error: (-36) SrcErr:YES Copying /Users/iRob/Library/Application S -
Time Machine backup behavior erratic, now not working at all
[ Using Lion 10.7.2 on a Macbook Pro 15" with 2.53GHz Intel Core 2 Duo processor, 4GB RAM. ]
The Macbook is connected to our home LAN, and I have been using (since September) a Synology NAS drive on the network which is set up as the Time Machine backup drive. Most of the time for these past months it has been fine; some issues initially with connectivity which were finally solved by using a static IP address for the NAS.
Recently it did the first strange thing. It had been performing incremental backups as normal, when a message came up saying the backup was unreliable and it needed to carry out a complete new backup. Anyway - no drama - I took it up and plugged it into the router to speed up the transfer (around 200GB on the drive). It worked fine and thereafter it went back to doing incremental backups normally.
Yesterday morning I noticed it was apparently running and running without progress, clicking on the bar icon revealed that TM was "Preparing Backup"; this state continued for several hours. So I stopped the backup, restarted the machine, and then last night at 22h00 I restarted it - by 08h00 this morning, ten hours later, it was still "Preparing Backup", so clearly something is wrong.
The NAS drive is accessible, ie.
- The 'Time Machine Backups' icon for the drive has appeared on the desktop
' The 'Diskstation (Time Machine)' is available in Finder under 'shared'
So this seems to be something to with Lion and/or with Time Machine.
Considering the infrastructure environment has been stable for months, the IP address of the drive is static, there appear to be no network connectivity problems... I am at a loss as to why now this irritating behaviour and, more to the point, at the moment I cannot make the Mac backup. I would be happy to do another full backup but, really, should not be necessary since this only happened (due to the recently problem) a few weeks back - and anyway what's the point of automated incremental backup if (a) it doesn't work reliably and (b) every 2-3 weeks you have to manually perform a full backup anyway??!!
Thanks in advance
AlastairAlastair Mac wrote:
thanks. unfortunately a locally attached drive isn't a option that will work well for me (too long to explain, but it just won't - personal logistics rather than technology issues).
Are you sure about that? I have a Time Capsule (2nd hand) but I've switched back to a locally attached disk with Lion. Lion's new mobile backups provide some measure of backups when not connected to the backup drive. It protects against accidental deletions, but not hardware failure. Plus, the new bootable recovery partition in Time Machine and encryption tip the balance back in favor of the local drive - for me at least.
1. does it make sense to you that, until yesterday, it was working fine and then quite suddenly it stopped working?
I will say that it isn't surprising. There are some changes in Lion that affect networked Time Machine devices. The early versions of Lion got pretty annoying. 10.7.2 seemed to be better. I had to erase my Time Machine drive a couple of times and do new backups when it decided it needed to keep rebuilding the Spotlight index. Unless you connect with Ethernet, the reindexing will never finish. In your case, I would expect a 3rd party, flaky open-source product to perform even worse.
2. in my specific situation (going around and around "preparing backup" without any progress even in 24hrs of preparing, what can i do to restart the backup process? even if it means doing a clean backup i.e. junking the old one, i would live with it as at present (touch wood) my hard drive is OK and i have no historical version recovery issues.
With Time Machine, the only quick and easy way to reset things is to erase the Time Machine volume.
3. did apple / synology reach a point in previous releases of OSX and DSM which was stable and DID work, despite the need to use Netatalk? in other words, if i soldier on patiently, is it likely this will eventually get solved? or will this be a perennial problem? in the end, if twice a year i have to intervene, it doesn't really matter PROVIDED the backup itself is intact should the HD finally die. of course, if i have to intervene every couple of days, i may as well do it all manually.
I can't really answer that. I used Netatalk briefly several years ago and it scrambled my files. It has certainly improved somewhat, but obviously isn't stable. The part that really annoys me is that the change that Apple introduced in Lion wasn't really new. Apple introduced a more secure version of the AFP protocol 9 years ago. In Lion, all they did was make that more secure protocol the default and disabled the older protocols. There are a number of hacks that have been posted (sometimes by me) about how to set a flag in Lion so that it will continue to use the older protocol.
Synology seems to have better Mac support that some NAS vendors. Still, there was no reason they had to wait so long to update their software. Developers have had access to Lion for almost a whole year.
I would expect that companies would be always trying to improve their products, but the evidence doesn't support that assumption. I don't like Netatalk's shady open source extortion practices, but then no one else has stepped up to fund a stable open-source implementation of AppleTalk. People tend to blame Apple but they published the new specifications a decade ago and no one bothered to read them. Why should they care?
Personally, I think backups are too important to rely on such flaky software. I really like Time Machine but it is pretty complicated. Apple is able to make it functional over a network, but just barely. If you are using a 3rd party NAS, my suggestion would be to use NFS instead and backup with Carbon Copy Cloner or SuperDuper!. Even if you want to continue to try using Time Machine, a Carbon Copy Cloner backup would be a good thing to have too. -
Restoring data from a Time machine backup of a potentially corrupted drive
I seem to be the queen of failing hard drives, heh. I'm on my third in a year, and will be addressing the root cause of these failures, of course, but right now, I'm wondering how safe it is to restore from my Time Machine backup. Here's the scenario:
-- Drive started throwing I/O errors, detected via SMARTReporter, about 2-3 months ago. No change in how the machine functioned, all OK.
-- I continued to back up daily to TM & Crashplan
-- While traveling for a month (and not backing up anymore, I left TM home), the machine started acting funny. Finder freezing, etc. I decided to clear some caches (by booting into safe mode) and see what happened.
-- This caused the HD to fail completely. Recovery mode, target disk mode, booting into single user mode and command-lining fixes, and DiskWarrior all failed to rebuild the directory. Failures were in multi-linked files/directories, the catalog file, etc.
-- I ordered a warranty replacment drive (and a new hard drive cable for starters).
When I got home, I borrowed another machine and just did a Verify Disk on the TM backup. It came back totally clean. So, my question is: is it safe to restore the data from my TM backup to the new drive when it arrives?Shouldn't be any problem.
Boot from your SL installer DVD (hold down the C key on startup or hold down Alt/option on start and choose the installer disc).
OK the language page (if present). From the installer screen, go to the menu bar and choose Disk Utility; depending on the OS version it may be in the Utilities menu or Tools menu.
In DU, select your internal drive in the sidebar (the top item with the makers name and serial no.). Run Repair Disk. If that comes up as disk OK, click the partition tab. Select the partiton from the drop-down above the graphic; 1 partiton is all you need. Go to the options button and ensure that the partition scheme is GUID (for Intel Macs) or APM (for G5 and earlier) and the file system to Mac OS Extended (Journalled). Name the partiton (usually Macintosh HD), click Apply.
When that's finished, select the new volume in the sidebar (indented to the right below the drive) and go to the Erase tab, select Security options and select zero data (one pass is more than sufficient). Click erase. That will take quite some time; probably measured in hours and dependant on the size of the drive.
When that's completed, close DU and continue with the installation.
Shortly into the installation process, you'll be asked if you want to migrate data from another source. Select 'from a Time Machine Backup' and follow the prompts.
See Pondini's FAQs;
http://web.me.com/pondini/Time_Machine/19.html
http://web.me.com/pondini/AppleTips/SetupAsst.html
That should leave you with the same setup as you had on the previous MB. -
TIme Machine backup grows too large during backup process
I have been using Time Machine without a problem for several months, backing up my imac - 500GB drive with 350g used. Recently TM failed because the backups had finally filled the external drive - 500GB USB. Since I did not need the older backups, I reformatted the external drive to start from scratch. Now TM tries to do an initial full backup but the size keeps growing as it is backing up, eventually becoming too large for the external drive and TM fails. It will report, say, 200G to back up, then it reaches that point and the "Backing up XXXGB of XXXGB" just keeps getting larger. I have tried excluding more than 100GB of files to get the backup set very small, but it still grows during the backup process. I have deleted plist and cache files as some discussions have suggested, but the same issue occurs each time. What is going on???
Michael Birtel wrote:
Here is the log for the last failure. As you see it indicates there is enough room 345g needed, 464G available, but then it fails. I can watch the backup progress, it reaches 345G and then keeps growing till it give out of disk space error. I don't know what "Event store UUIDs don't match for volume: Macintosh HD" implies, maybe this is a clue?
No. It's sort of a warning, indicating that TM isn't sure what's changed on your internal HD since the previous backup, usually as a result of an abnormal shutdown. But since you just erased your TM disk, it's perfectly normal.
Starting standard backup
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Ownership is disabled on the backup destination volume. Enabling.
2009-07-08 19:37:53.659 FindSystemFiles[254:713] Querying receipt database for system packages
2009-07-08 19:37:55.582 FindSystemFiles[254:713] Using system path cache.
Event store UUIDs don't match for volume: Macintosh HD
Backup content size: 309.5 GB excluded items size: 22.3 GB for volume Macintosh HD
No pre-backup thinning needed: 345.01 GB requested (including padding), 464.53 GB available
This is a completely normal start to a backup. Just after that last message is when the actual copying begins. Apparently whatever's happening, no messages are being sent to the log, so this may not be an easy one to figure out.
First, let's use Disk Utility to confirm that the disk really is set up properly.
First, select the second line for your internal HD (usually named "Macintosh HD"). Towards the bottom, the Format should be +Mac OS Extended (Journaled),+ although it might be +Mac OS Extended (Case-sensitive, Journaled).+
Next, select the line for your TM partition (indented, with the name). Towards the bottom, the Format must be the same as your internal HD (above). If it isn't, you must erase the partition (not necessarily the whole drive) and reformat it with Disk Utility.
Sometimes when TM formats a drive for you automatically, it sets it to +Mac OS Extended (Case-sensitive, Journaled).+ Do not use this unless your internal HD is also case-sensitive. All drives being backed-up, and your TM volume, should be the same. TM may do backups this way, but you could be in for major problems trying to restore to a mis-matched drive.
Last, select the top line of the TM drive (with the make and size). Towards the bottom, the *Partition Map Scheme* should be GUID (preferred) or +Apple Partition Map+ for an Intel Mac. It must be +Apple Partition Map+ for a PPC Mac.
If any of this is incorrect, that's likely the source of the problem. See item #5 of the Frequently Asked Questions post at the top of this forum for instructions, then try again.
If it's all correct, perhaps there's something else in your logs.
Use the Console app (in your Applications/Utilities folder).
When it starts, click +Show Log List+ in the toolbar, then navigate in the sidebar that opens up to your system.log and select it. Navigate to the +Starting standard backup+ message that you noted above, then see what follows that might indicate some sort of error, failure, termination, exit, etc. (many of the messages there are info for developers, etc.). If in doubt post (a reasonable amount of) the log here. -
File Sharing drops regularly, Time Machine Backups are delayed on OSX 10.7.3. Solution?
Hi there folks,
I'm having an issue with the new 10.7 server. We're running 10.7.3 Server on an Late 2006 XServe with 10GB RAM , connected to a Drobo Pro for Time Machine Backups of our 50+ users via our internal network.
Recently, Time Machine backups have been getting delayed, stating that they can't connect up to the backup drive (which is out Drobo Pro handling 16TB of space). The Drobo Pro hass not unmounted, and all the IP Addresses coming from and going to the Server handling the backups will still ping.
We've also be having trouble with Server resident drives and shared folders that people can mount using the ⌘+K shortcut or "Connect to Server" option in finder. People will choose the IP address, and finder will think for a few minutes then give an error stating that it cannot connect the the specified IP. The only way I can reestablish connection to the file sharing through a remote computer is to remote or physically login to the server, then go into System Preferences and turn "File Sharing" off, then on again. After that, the ⌘+K on a remote machine can find the drives again.
It's driving me crazy why this is ocurring. I don't know why, and people in the office are beginning to complain that they can't access certain files on the servers or are worried because their backups are not completeing.
It should also be known that a majority of the machines we have in the ofice are still running 10.6.8, with only a handful on 10.7, as we haven't had the time to make the major switchover yet.
I'm not the best when it comes to server software or Unix CLI managment (the office outsourced our Network Admin to the east coast), so I'm a bit stumped.
Does anyone have any suggestions to try? Is there a link between the number of Time Machine Users and the connection failures? Should I just tel the NetAdmin to create a script that will restart the File Sharing protocol on the server every couple of hours?
Hopefully someone will be able to help.
Thanks,
JYHASHI started having connectivity issues to my 10.6.8 server from my 10.7 client immediately after updating the client to 10.7.3. FWIW. Takes forever to connect, when it does. After just milliconds before.
Maybe you are looking for
-
After resetting the SMC the keyboard is inoperative. On the start screen appears a traslucent square with a horizontal bar in white, and a row of empty dots below (the same format as for example the brightness symbol). I cannot turn the Mac off wit
-
Download Bloomberg data to SAP
Dear all, at a customer we want to download energy prices from specific companies from Bloomberg and compare it with the prices they agreed upon with these companies. My question is, what's the best way to get this data from Bloomberg on any given ti
-
I'm moving from the US to India, will Apple TV and the movies I purchased on the apple site work with a PAL TV?
-
when I display a travel expense claim, there is a text on the top of the form saying "To print the form using a browser, right-click on it and select the print command from the context menu." How can I change this text? the thread below helps Modifi
-
Have anyone seen this exception before??? setNull() feature not implemented
java.sql.SQLException: [Microsoft][ODBC SQL Server Driver]Optional feature not implemented Have anyone seen this exception before????? I see this exception when I use the "setNull()" function in the preparedstatement class.