External HD/Time Machine Errors

When restarting my iMac I got a string of errors telling me that my back-up volume needed to be repaired. My iMac wouldn't recognize the external HD and the error message said the external was 'read only'. The external HD didn't show in 'Disk Utilities'. I unplugged and restarted the iMac and still have the error icon in the upper task bar. I've tried to repair permissions and repair the disk but I keep getting the error, 'disk is read only'. Should I reformat and try to restore Time Machine back-ups or take it to the shop. The iMac is now showing the external drive one my desktop and I can view old back-ups but if I try to do a back-up, it keeps telling me my external drive is 'read only'.

This is the report from Disk Utility when I run 'Verify Disk'. I'm unable to run 'Verify Disk Permissions' or 'Repair Disk Permissions'.
Verifying volume “Iomega HDD”
Checking Journaled HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Incorrect block count for file 0000000001f3dc7e
(It should be 1 instead of 0)
Incorrect block count for file 0000000001f42845
(It should be 1 instead of 0)
Incorrect block count for file 0000000001f489d3
(It should be 1 instead of 0)
Incorrect block count for file 0000000001f4a029
(It should be 1 instead of 0)
Incorrect block count for file 0000000001f4f34b
(It should be 1 instead of 0)
Incorrect block count for file 0000000001f5453d
(It should be 1 instead of 0)
Incorrect block count for file 0000000001f552a3(It should be 1 instead of 0)
Incorrect block count for file 0000000001f928d5
(It should be 2 instead of 0)
Incorrect block count for file 0000000001f9da23
(It should be 2 instead of 0)
Incorrect block count for file 0000000001fa2e92
(It should be 2 instead of 0)
Incorrect block count for file 0000000001fa89ba
(It should be 2 instead of 0)
Incorrect block count for file 0000000001faedb7
(It should be 2 instead of 0)
Incorrect block count for file 0000000001fb1b67
(It should be 2 instead of 0)
Incorrect block count for file 0000000001fb4f4e (It should be 1 instead of 0)
Incorrect block count for file 0000000001fbe608
(It should be 2 instead of 0)
Incorrect block count for file 0000000001fc253a
(It should be 2 instead of 0)
Incorrect block count for file 0000000001fc5330
(It should be 2 instead of 0)
Incorrect block count for file 0000000001fcb863
(It should be 2 instead of 0)
Incorrect block count for file 0000000001fcf4ab
(It should be 2 instead of 0)
Incorrect block count for file 0000000001fd5586
(It should be 2 instead of 0)
Incorrect block count for file 0000000001fe50ef (It should be 2 instead of 0)Incorrect block count for file 0000000001fe7501
(It should be 2 instead of 0)
Incorrect block count for file 0000000001fe9850
(It should be 2 instead of 0)
Incorrect block count for file 0000000001febbfc
(It should be 1 instead of 0)
Incorrect block count for file 0000000001fee257
(It should be 2 instead of 0)
Incorrect block count for file 0000000001ff4f92
(It should be 2 instead of 0)
Incorrect block count for file 0000000002016126
(It should be 2 instead of 0)
Incorrect block count for file 000000000201d55c
(It should be 2 instead of 0)
Incorrect block count for file 0000000002023b79(It should be 2 instead of 0)
Incorrect block count for file 000000000202a533
(It should be 2 instead of 0)
Incorrect block count for file 00000000020315b4
(It should be 2 instead of 0)
Incorrect block count for file 00000000020381d0
(It should be 2 instead of 0)
Incorrect block count for file 000000000203c6cb
(It should be 2 instead of 0)
Incorrect block count for file 0000000002045084
(It should be 2 instead of 0)
Incorrect block count for file 000000000204f9f7
(It should be 2 instead of 0)
Incorrect block count for file 0000000002056150
(It should be 2 instead of 0)
Incorrect block count for file 000000000205ec73(It should be 2 instead of 0)
Incorrect block count for file 0000000002065156
(It should be 2 instead of 0)
Incorrect block count for file 000000000243973b
(It should be 1 instead of 0)
Incorrect block count for file 0000000002440880
(It should be 1 instead of 0)
Incorrect block count for file 00000000027e20f5
(It should be 1 instead of 0)
Incorrect block count for file 0000000003ae6aff
(It should be 1 instead of 0)
Incorrect block count for file 0000000003af9c3e
(It should be 1 instead of 0)
Incorrect block count for file 0000000004ecca87
(It should be 1 instead of 0)Incorrect block count for file 0000000005695936
(It should be 1 instead of 0)
Incorrect number of thread records
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking multi-linked directories.
Checking volume bitmap.
Volume Bit Map needs minor repair
Checking volume information.
Invalid volume free block count
(It should be 95145020 instead of 95145021)
The volume Iomega HDD needs to be repaired.
Error: Filesystem verify or repair failed.
Thanks for taking a look at this. Does this mean my external drive is toast?

Similar Messages

  • Lacie external drive time machine error

    I'm using my Lacie external drive (2TB) for my time machine. And it has this problem that every time after I put my macbook to sleep, the time machine won't work, it keeps showing this message "error occurred during back up" (but it doesn't not specify what kind of error). And the time machine can't recognize the history backup from the drive.
    However, it will function again if I eject the drive and replug it in.
    It's not a major problem, but it's kinda annoying and I wanna know what's causing it.
    Thanks yall.

    Hi George,
    The one way I found to get the TM back on the rail is to access my back up disk from finder, choose the sparse disk image. Hit cmmd-delete and banish it.
    Start over again. Be sure to be connected by a wired connection as on a wireless network it will take a while. But I guess you have the HD attached via firewire or usb so it should not be a major issue.

  • HT3275 Lacie external drive/Time Machine errors

    I am using Lacie external drive with Time Machine and now have an "invalid node structure." Wants me to back up and restore...again. I have had problems in the past and have restored twice so far.  Other problems include "Incorrect number of thread records" and "Invalid directory item count." Why does this keep happening? Is it normal to keep restoring your external hard drive? Where else should I back up my hard drive?

    Terriodo wrote:
    I wonder if this is a problem with Time Machine or my external hard drive.
    Hard to tell, unfortunately.  As posted earlier, that can be caused by lots of things.
    Our Lacie hard drive is backing up everything that is on our computer. Meaning there isn't anything getting backed up that has been deleted. But it is annoying to erase the darn thing every couple of weeks and load it all on again.
    My advice would be to get another drive.  Since you have a desktop Mac, get a desktop drive, with it's own power supply.  Plug it (and your Mac) into a same good-quality surge suppressor;  or, better, U.P.S. (battery backup) system. 
    It's always prudent to keep secondary backups.  See Time Machine - Frequently Asked Question #27 for an explanation and some suggestions. 
    That recommends using a different app, but in your situation, you might want to use both drives with Time Machine temporarily; you'll have to switch back and forth manually via the TM Preferences panel (Mountain Lion allows multiple destinations, but Snow Leopard doesn't).  If the new drive works fine, but the old one doesn't, that will implicate the LaCie, or it's connections, etc. 
    If you determine it's ok, then use one (probably the desktop) with Time Machine, and the Rugged with another app.  Consider taking it off-site, as mentioned in #27.
    If it's not ok, replace it.
    I am running 10.6.8 and have Lacie 1T Rugged external hard drive connected by firewire on my Mac desktop.
    I have a smaller version of that drive, as do several folks here.  It gets good reviews, but like any drive, won't last forever.  If it's over about 3 years old, it could be starting to develop a problem.

  • HT3275 Time Machine error. Unable to complete backup. An error occurred while copying files to the backup volume. Tried restarting, remounting external WD drive. Still cannot backup.

    Time Machine quit backing up files. Bought a new WD external drive. Worked for awhile, then quit backing up. Tried restarting computer, remounting drive. Message: Time Machine Error. Unable to complete backup. An error occurred when copying files. Suggestions?

    Thanks so very much for your help!! I'm boggled by it and now just about ready to dump the whole idea of Time Machine and backup using a cloning program. Maybe TM is only guaranteed to work well with Time Capsule these days?
    Today there again was no backup. I did as you suggested, looked into Console. It showed many lines of "(Error) DiskStore: No block in wakeup" and also repeatedly "(Warning) DiskStore: Ignored bogus fetch...".
    So I created a marker and attempted to initiate a backup, keeping Console open and refreshed. Here's what I got:
    8/19/13 5:18:40.385 PM Console:  Marker - Aug 19, 2013 5:18:40 PM
    8/19/13 5:19:48.844 PM com.apple.backupd: Starting standard backup
    8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.508 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:38ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.510 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:40ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:20.000 PM kernel: USBF:          58091.976          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:20:51.000 PM kernel: USBF:          58122.985          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:21:22.000 PM kernel: USBF:          58153.992          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:21:53.000 PM kernel: USBF:          58185.  2          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:22:24.000 PM kernel: USBF:          58216. 14          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:22:55.000 PM kernel: USBF:          58247. 25          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:23:26.000 PM kernel: USBF:          58278. 41          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:23:57.000 PM kernel: USBF:          58309. 51          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:24:28.000 PM kernel: USBF:          58340. 59          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:24:59.000 PM kernel: USBF:          58371. 68          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:25:30.275 PM xpchelper: for uid: 501 -- timeout while waiting on FSEvents flush; clearing cache.
    8/19/13 5:25:30.000 PM kernel: USBF:          58402. 82          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:26:01.000 PM kernel: USBF:          58433. 96          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:26:32.027 PM com.apple.backupd: Backing up to: /Volumes/TMBackups/Backups.backupdb
    8/19/13 5:26:32.000 PM kernel: USBF:          58464.112          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:27:02.653 PM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TMBackups/Backups.backupdb/David’s iMac size:37
    8/19/13 5:27:02.657 PM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TMBackups/Backups.backupdb/David’s iMac size:37
    8/19/13 5:27:03.000 PM kernel: USBF:          58495.121          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:27:12.668 PM com.apple.backupd: Backup failed with error: 2
    During this 9-minute timeframe Finder also was inoperative - according to Activity Monitor: "Not Responding".
    I'm thinking it's the standalone Buffalo backup drive not waking up, and so everything comes to a screeching halt. Do you also think I should abandon TM and just do manual backups every day using a clone program?

  • Time Machine Error Unable to complete backup. An error occurred while ...

    Hi,
    I've looked all around the forums for the answer to this one and I'm still unable to get it. So I'm getting this error "Time Machine Error Unable to complete backup. An error occurred while linking files on the backup volume". This started happening after I turned off and on FileVault. I was having a problem with it and turning it on an off got rid of that problem, but created this one. I've noticed that when I shut down the computer and filevault accesses the TM hard drive, it can back up.....but then when I'm logged on, or I want it to back up I get the error. I've tried fixing the drive, removing the in progress file and resetting the PRAM (i think that's what it was called). I'm starting to run out of options and have no other drive to back all this info on to reformat it.
    I really don't want to loose all my stuff.
    Please help!
    Daria

    nautical_stars wrote:
    Hi,
    I've looked all around the forums for the answer to this one and I'm still unable to get it. So I'm getting this error "Time Machine Error Unable to complete backup. An error occurred while linking files on the backup volume". This started happening after I turned off and on FileVault.
    Usually this message happens when you replace an external disk that was being backed-up by Time Machine with another one of the same name.
    Since File Vault works by making a sparse image of your home folder, and it's treated as a volume just as a HD is, that's probably what's happening here: the new sparse image has the same name as the old one, but isn't the old one.
    First, consider whether you really need File Vault. It doesn't work well with Time Machine: you can't see or restore individual items in your home folder, and it only gets backed-up when you log out.
    If you have a lot of other things, say photos, videos, and/or music that don't need to be encrypted, perhaps there's an easier way to secure our sensitive data. You can create an encrypted disk image via Disk Utility (in your Applications/Utilities folder), then copy the sensitive documents into it. Then the rest of your home folder is backed-up normally, and individual items can be viewed and restored in the usual fashion.
    But if you do continue using FileVault, you may have to use TM to delete all backups of it, via the instructions in item #12 of the Frequently Asked Questions *User Tip* at the top of this forum. That should then allow the new version of your encrypted home folder to be backed-up by TM.

  • Time Machine Error "Unable to complete backup"

    I have not backed up my hard drive for about 30 days. When I plug my external hard drive in, Time Machine "prepares backup" for a while, then gives me the following message:
    *Time Machine Error*
    Unable to complete backup. An error occurred while copying files to the backup volume.
    I tried unplugging and re-plugging, rebooting my computer, trashing the ".inprogress" backup file and restarting. It did not help. While it time machine is preparing the backup, my computer runs crazy slow, with the rainbow pinwheel spinning for about 5-10 seconds just about every time I click the mouse, in any program.
    Per someone's suggestion, I put "sudo grep backupd /var/log/system.log" into terminal, and this is what came up:
    "No pre-backup thinning needed: 4.98 GB requested (including padding), 70.16 GB available
    Waiting for index to be ready (906 > 0)
    Unable to rebuild path cache for source item. Partial source path:
    Indexing a file failed. Returned -12 for: /Applications/iChat.app, /Volumes/Time Machine Backups 1/Backups.backupdb/My Computer (2)/2011-01-13-113417.inProgress/CB0D491E-EF04-48A0-9AE9-32AE43E9209C/Macintosh HD/Applications/iChat.app
    Aborting backup because indexing a file failed.
    Stopping backup."
    This time, it was apparently iChat, but in each of the three times I've tried to backup and gotten this error message, a different file has been the culprit for the indexing error.
    Any suggestions?

    orchestr wrote:
    Indexing a file failed. Returned -12
    see [this_|http://web.me.com/pondini/TimeMachine/C3.html] user tip by Pondini.
    JGG

  • Time Machine Error. Unable to complete backup. An error occurred while copy

    I purchased my iMac 24" in February.
    After I had set up the machine I configured an IceCube Firewire 300 GB (Seagate) Hard Drive as a backup volume and flicked the switch in Time Machine. All went as expected. I even restored my whole hard drive from the Time Machine volume about a month ago after I repartitioned the boot volume to set up Boot Camp. No problems.
    About a week ago I purchased a 500GB WD HDD and set it up inside the IceCube enclosure (I remembered to make it the "Master" disk too!!). I partitioned it with Disk Utility with a GUID Mac OS X (Journaled) partition for my Leopard boot partition, and as MS-DOS FAT32 for my Boot Camp external partition. I used Carbon Copy Cloner to copy all the Windows files across from Boot Camp to the new FAT32 partition and set up Time Machine to make a backup of the Leopard boot partition.
    After several hours Time Machine stopped with the error message above. ("Time Machine Error. Unable to complete backup. An error occurred while copying files to the backup").
    I have spent days formatting the new WD drive, repairing permissions on the boot drive, excluding large files and cache files from the backup in Time Machine to no avail. Every time I get the same message. I even set up another 200GB firewire drive to see if it was anything to do with the enclosure of WD HDD. Same result!!
    I have searched these forums for any ideas, and have done wide searches with Google but nothing has worked.
    I can not understand why my Mac worked perfectly with Time Machine before I installed the new Western Digital Hard Drive.
    What have I missed?

    I keep getting the Time Machine backup error too, like many others. Was fine until just the other day, now, nothing. Although my husband's backs up just fine. I assume it's the 10.5.3 bug everyone else has. I've tried reselecting the drive, running the disk utility, shutting everything on and off... help!
    Here's the console log- anyone know what this means?
    Jun 10 08:37:27 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Starting standard backup
    Jun 10 08:37:27 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Network mountpoint /Volumes/Library not owned by backupd... remounting
    Jun 10 08:37:27 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Network volume mounted at: /Volumes/Library-1
    Jun 10 08:37:43 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Disk image /Volumes/Library-1/Tiffany Danko’s Computer (2)_001b63baf698.sparsebundle mounted at: /Volumes/Backup of Tiffany Danko’s Computer (2)
    Jun 10 08:37:43 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Backing up to: /Volumes/Backup of Tiffany Danko’s Computer (2)/Backups.backupdb
    Jun 10 08:37:48 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Failed to create progress log file at path:/Volumes/Backup of Tiffany Danko’s Computer (2)/Backups.backupdb/Tiffany Danko's computer (2)/2008-06-09-065427.inProgress/.Backup.234797868.792920.log.
    Jun 10 08:37:48 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Event store UUIDs don't match for volume: Macintosh HD
    Jun 10 08:37:48 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Error: (-36) Creating directory 77B4FA27-3E65-4B81-897C-610DEE7BB187
    Jun 10 08:37:48 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Failed to make snapshot.
    Jun 10 08:37:53 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Backup failed with error: 2
    Jun 10 08:37:58 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Ejected Time Machine disk image.
    Jun 10 08:37:59 Tiffany-Dankos-computer-2 /System/Library/CoreServices/backupd[1683]: Ejected Time Machine network volume.

  • Question on Time Machine error log

    I have a program (Time Machine Error Log) that keeps track of the message log entries that occurr after you do a Time Machine backup.
    I am getting two messages each time Time Machine completes a backup.
    Here are the two message from the last log:
    Jan 13 17:39:29 xxxxxx-iMac.local com.apple.backupd[36854]: Error: Error Domain=NSOSStatusErrorDomain Code=-36 "The operation couldn’t be completed. (OSStatus error -36.)" (ioErr: I/O error (bummers)) deleting backup: /Volumes/Time Machine Backups/Back
    Last Successful Backup Message:
    Jan 13 17:39:37 xxxxxx-iMac.local com.apple.backupd[36854]: Backup completed successfully.
    How can there be an error reported stating "deleting backup", then a message stating "Backup completed successfully"?
    If I didn't check the log, I wouldn't know that there was a problem, because the Time Machine preferences pane tells me the last backup time, and the next backup time, indicating all went well.
    I just need some verification that my backups are completing successfully.
    Thank
    Len

    There is a lot of rubbish messages that TM produces.. if the final message is that all is good, then I would say all is good.. it is pretty quick to decide when something isn't good.
    But I would say.. there is only one way to know a backup is good. Restore it.
    You don't need to test restore over current drive.. plug in an external drive and restore.
    You can do a verify.. hold the option key whilst clicking the TM icon in the top menu area.. and the option verify will appear.. click that. It really doesn't test more than files are readable though, AFAIK.
    Do a disk image occasionally.. Disk Utility can create an image.. but superduper even free download version can do a full disk image. Makes me feel safer knowing that I have a backup TM doesn't actually have anything to do with.

  • Is there a solution for Time Machine error?

    I got an error in Time Machine saying backup had failed, a couple of days ago. Spent the next day or two trawling the web and found thousands of postings from people with the same error, but no solution.
    (At least, some people had a solution - they were using PC-formatted hard drives.)
    I've been using Time Machine for a few weeks, and it has only now taken a dislike to my external hard drive, which is connected by FireWire.
    Is there a solution to this problem, or should I revert to using SuperDuper, which I was using successfully before?
    I haven't put in lots of information about the apps I'm running, because this is a general query rather than a specific one. If there's a solution, I'll use it; otherwise I'll wipe the drive and go back to using SuperDuper.

    OisinOg wrote:
    Pondini - Thank you for your slightly hostile reply.
    On the contrary. The statement was: +"found thousands of postings from people with the same error, but no solution."+ I don't know where you found thousands of posts -- there are many here, but certainly not thousands. If you're talking about, say, a Google search, if you actually look at them, many are duplicates, unrelated to your problem, or unrelated to Macs at all -- and there are a number of solutions that seem to have fixed many of the real ones.
    The error message was the standard one: "Time Machine Error - Unable to complete backup. An error occurred while creating the backup directory."
    There's most likely another, better message in your logs. Thus the suggestion about Time Machine Buddy. You can also use the Console app (in your Applications/Utilities folder). Click on Show Log List, then navigate in the sidebar to your system.log (or system.log.0.bz2, etc. for previous ones). You can filter for backupd to get the same TM messages as the widget, but I prefer to view the full log at the date/time in question, as messages from other concurrent processes may have a clue.
    I've gone through the suggestions in some of the helpful replies to those thousands of postings, by wiping my drive, erasing it and reformatting it, first in two partitions using the GUID method in Disk Utility, then in a single partition. But Time Machine still doesn't want to back up to it.
    Sounds a bit like a problem communicating with the drive. The logs may clarify that.
    The hard drive of my computer is 250GB; the external drive is 300GB. Both are SATA drives; the external is connected by FireWire.
    How full are they?
    Thanks for your suggestion of downloading the Time Machine Buddy widget; I'll give it a last try tonight.
    What is the difference between a SuperDuper clone and a Time Machine backup?
    The initial backup of both copies almost everything on your HD, excluding only some caches, temp files, etc., although you can exclude other things. This takes quite a while, of course. Thereafter, only the items that changed are backed-up.
    SuperDuper (and CarbonCopyCloner, which I use, and other, similar apps) are most often used to make bootable "clones" identical copies of your HD -- if your HD fails, you can boot and run from them immediately. With TM, once your HD is repaired/replaced, you restore your system to it from your TM backup.
    Score one for the clones, but TM has it's advantages, too (which is why many of us run both).
    First is, CCC and SD look at every file and folder on your HD to see what changed. This is quite time-consuming and CPU-intensive, so most of us run it once a day (or less often), usually automatically at, say, 3 am. TM, however, runs hourly, but uses an internal File System Event Log of changes, so it is far quicker and less intrusive. There are exceptions, but most users rarely even notice the backups unless they see the icon revolving. On my small system, for example, TM rarely runs over 30 seconds; CCC is at least 15 minutes.
    Second, not only does TM keep previous versions of changed files, but it manages the space and backups for you. It keeps those hourly backups for 24 hours; except the first of the day becomes a daily backup which is kept for a month; one per week becomes a weekly backup that is kept for as long as there's space (it will fill the drive/partition). But it's smart enough, as it deletes the old weeklies, that it won't delete it's copy of anything that still exists on your HD.
    There isn't room to have two 250GB sections on a 300GB drive. I suppose I could get another 250GB drive - I have an IDE enclosure somewhere - but I don't fancy the expense right now.
    Your CCC or SD partition only needs to be as large as your HD, although in a pinch it only needs to be somewhat larger than what's actually used on your HD. If you don't have room for both on the one drive, an even better solution might be to get a pair of smaller portable HDs for CCC/SD. Use one daily for, say, a week, then take it to your safe deposit box, workplace, relative's house, etc. and start with the other. Now you're also protected against fire, flood, theft, direct lightning strike on your power lines, etc.

  • HT201250 Time Machine Error

    Just bought a new 1 TB external hard drive specifically for a Mac and time machine error: unable to complete backup. An error occurred while copying files to the backup volume. messages keeps appearing.  Tried to restart and that didn't help.  Please advise.

    Hello, I don't use TM myself.
    Have you looked through Pondini's extensive TM help site?
    http://Pondini.org/TM/FAQ.html
    http://pondini.org/TM/Troubleshooting.html
    I can't imagine anything TMwise not covered.

  • Time Machine Error - Backup Requires 2,211,365.5 GB!

    Hello - I have searched the posts and nothing seems to touch on this specifically - I have been using Time Machine successfully for months and this has only started to happen in the last few days.
    I have a white Macbook, 10.5.6 with an upgraded 150GB hard drive. I do backups sporadically (once or twice a week), as I don't want to keep my Macbook connected to a hard drive and I find using the airdisk feature on my AEBS takes too long and slows down the network. This has been working fine for me for months, but now I get the following message:
    Time Machine Error
    This backup is too large for the backup volume. The backup requires 2211365.5 GB but only 125.5 GB are available.
    I tried reformatting my disk (250GB hard drive) and the problem still arises. There are no external drives or anything connected to the Macbook at the time.
    Can anyone help? I don't want to go out and buy a Hard Drive with a 3million GB capacity!
    Thanks
    Ian

    ChunTzu wrote:
    If TM is seeing a ridiculous amount of info to backup like that (2 million gigs is probably not a real number I am guessing) it probably means you have file structure problems that are causing TM to count a folder infinitely in some kind of loop... like maybe a file link to itself that kind of thing.
    A disk check usually repairs these sorts of problems and should alleviate your issue.
    I believe you are correct and I would add that this case might require stronger medicine such as DiskWarrior to repair the directory structure, if that it the issue.

  • Time Machine Error - again again..

    Hi,
    I also get this one...
    Time Machine Error
    Unable to complete backup. An error occurred while
    copying files to the backup volume.
    I haven´t tried with Time Machine Buddy - but here is a few facts, that maybe could help me find a solution.
    My total backup size is approx. 300GB (on USB connected 1TB external disk)
    When i exclude the movie folder in iTunes (113GB) it works fine - when i include it, I get the above error...
    Whats wrong - corrupt file in the movie folder?? How do i locate it?? Foldersize to big???
    Best regards...

    Hello j:
    Welcome to Apple discussions.
    There is probably a corrupt file in the movie folder. Try TM Buddy. That gives you a log (almost real time) of what is happening when TM does a backup.
    Barry

  • Time Machine Error sparse bundle could not be accessed

    Issue: Time Machine Error "the backup disk image "/volumes/data/.sparsebundle" could not be accessed (error -1).
    Background: I have an '07 iMac with an external WD 1TB hard drive to store video, pictures and music as well as a 1TB Time Capsule to use for my Time Machine back ups.  Once I converted to Lion, I started getting the "sparsebundle...counld not be accessed" error message.  The Apple support line directed me to take the issue up with my local Apple store (or else they would have charged me $50).  I went to the local Apple store and was directed to erase my sparsebundle and start over.  My iMac apparently values the sparsebundle as it would not let me delete it...it would just hang up.  I finally had to erase the file from the Time Capsule and start over (based upon some recommendations I found within the Apple Support Communities).  I did that two days ago and it looked like I was in the clear.  I have about a day's worth of backups and now just started getting the same error message as I did before.  I am a casual computer user with limited trouble shooting skills.  Does anyone have any ideas, tips or suggestions as to the source of the problem and how to properly trouble shoot the issue?

    Dirty of Apple.. this is a bug.. that is caused by your upgrade to Lion.
    We see loads of issues. Did you upgrade install? I am not sure that that is some of the issue.
    Anyway the solution is to restart the TC.. just pull out the plug and reboot it.
    Like windows.. first support question. Did you turn it off and on again??
    Read C17
    http://pondini.org/TM/Troubleshooting.html
    You need to use the 5.6 utility so download and install that.
    http://support.apple.com/kb/DL1482
    Go to the disk page and disconnect all users.. same thing as pulling the plug really.

  • Time machine error: The backup disk image could not be mounted

    Time Machine worked OK for several months. Now I get this error every 10 minutes or so.
    I unplugged Time Machine capsule and "Change Disk" in Time Machine options.
    Nothing helps, I continue to get this error.
    I cannot Enter Time Machine either. "Connecting to Server, Connecting to backup" does not work.
    Help please because I will probably have to archive and reinstall Leopard. I need the backups,
    Christine

    Christ1ne,
    Before you reformat the disk, consider these causes of this error.
    *_"The Backup Disk Image Could Not Be Mounted" (Console - “Failed to mount disk image”)_*
    First, it is important to distinguish this error message from another, similar Time Machine error that states “The backup volume could not be mounted”. This is important as the causes and cures for these two errors can be very different.
    Consider each topic below separately. When one option does not resolve your issue, then move on the next one.
    *Unmount the Backup Disk Image* (TC)
    If, for some reason, you have manually mounted the Time Machine backup disk image (sparsebundle), or Time Machine failed to eject it after the previous backup, subsequent backups may fail. (Console - “Failed to mount disk image”… “Backup failed with error: 21”)
    Eject the backup disk image (white drive icon) by either clicking the little Eject icon to the right of the disk image in the Finders’ Sidebar, or Ctrl-Click the drive icon on the desktop and select “Eject” from the contextual menu. Now try backing up again or launching Time Machine to view previous backups.
    *“Disconnect All Users…”:*
    If your Time Machine backup drive (“Backup of Users Computer”) is mounted on your desktop or in the Sidebar of the Finder window. then Time Machine may think the drive is already in use. Alternatively, if the Time Capsule hard disk has been recently accessed by a Windows machine, it may not have fully relinquished control. Do the following:
    Open Airport Utility and select the Time Capsule on the left.
    Click “Manual Setup”.
    Select “Disks” at top of window.
    Click “Disconnect All Users…” at bottom of window.
    Close the Airport Utility.
    Now try Backing up again.
    One poster reported: “I got it resolved. Apparently it had to do with one of the files being open on the disk from the drive. I had browsed the disk with one of my windows boxes here and it must have left one of the folders "open". Anyway, I rebooted the TC and we are good to go now.”
    *Proper Computer Name* #
    Make sure your computer has a proper name. Go to System Preferences --> Sharing. Time Machine needs to differentiate your computer from others on your network (i.e. "Bills MacBook" or "Office iMac"). If the "Computer Name" field is blank, create a name. Realize that if this step is necessary, you will likely have to start the Time Machine backup process over again and do another full initial backup.
    According to this article, [http://support.apple.com/kb/TS1760], Time Machine may experience problems if your computer name includes certain characters. Make sure the computer name only includes ASCII characters from the following set.
    (0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ)
    Once a change in the computer name occurs, you should stop and restart Sharing on the affected computer. Uncheck and then recheck Sharing in the Services list on the left.
    # Try removing the apostrophe from the disk images name (sparsebundle).
    *A Stalled .inProgress Files:* #
    It may be that the previous backup attempt was ungracefully interrupted leaving remains that Time Machine can’t deal with.
    Stop any current backup attempt. Choose “Stop Backing Up” from the Time Machine menu.
    Open the Time Machine Preferences and turn “OFF” Time Machine.
    Open your Time Machine drive.
    Open the folder labeled “Backups,backupdb”.
    Now open the folder containing backups of the computer in question.
    Are there any “.inProgress” files there. Delete them by dragging the file to the Trash. Or Ctrl-Click the file and select "Move to Trash" from the contextual menu. (Give this time as deleting a large file on an external disk can take a while.)
    Turn Time Machine back “ON”. Now try backing up again.
    NOTE: If the above procedure becomes impossible to perform, try accessing the disk image from another Mac. Some have discovered that attempting a repair from another computer succeeds where the original computer failed.
    Let us know if any of the suggestions above helped to resolve your issue.
    Cheers!

  • Time Machine Error with brand new WD My Book Studio Edition

    I have a brand new iMac and just bought a new WD My Book Studio Edition 500 gb HD for specific use with my Time Machine. The iMac has a 500 HD is about 3 months old and the WD HD is brand new. I am getting an error when I try to activate and back up with Time Machine that says, " Time Machine Error. This backup is too large for a backup volume. The backup requires 524.4 gb but only 465.5 gb are available. To select a larger volume, or make the backup smaller by excluding files, open System Preferences and choose Time Machine."
    I copied the files from the Time Machine to my hard drive to make as much space as possible. I have a capacity of 465.44 GB and 28.48GB of free space on my MacHD. I have a capacity of 465.64 GB and 465.49 GB of free space on my WD. It is formatted Mac OS Extended (Journaled) the way it was originally sold. I have not tried to reformat. Not too sure about how to. But I have tried all of these scenarios.
    I have tried the following and nothing works to get Time Machine backing up at all:
    1. I have changed the preferences in Time Machine Options to a smaller file size excluding the applications folder (appx. 12 GB),
    2. I have zapped the P-RAM,
    3. I have reset the index in the Spotlight by putting my Macintosh HD and Time Machine in the Privacy section, let it reindex and then pulled it out, and
    4. I have deleted the preferences in Macintosh HD>Library>Preferences>com.apple.TimeMachine.plist.
    Nothing is working and I bought the HD when I was home visiting in the states and I live in Bogota, Colombia. Quite hard to return HD.
    Can anyone help me?
    Thanks,
    Marsh64

    You have a nearly full 500 GB hard drive and you are trying to use TM with a 500 GB hard drive - but the way TimeMachine works, your TimeMachine hard drive should be at least twice the size of your backup data. In other words, to use TM effectively you should have bought a 1 TB external drive.
    With a 500 GB drive for backups, you need to determine exactly what has to be backed up and what can be left out. If you open the TimeMachine preferences you'll see that there's an Options button. Click it and you can select folders to exclude from backing up. For example, you might decide that you don't need to back up your music because it is all on your iPod anyway and the Mac OS and your applications are all on CD so those can be left out. By carefully paring the list down you may be able to get your backup data down under 250 GB and if so, then TimeMachine will do the job for you.
    Another solution would be to drop TimeMachine as your backup solution and simply use a program such as SuperDuper! or CarbonCopyCloner (CCC) to perform your backups. There are advantages and disadvantages to each backup method. As you mull your options, don't be afraid to ask more questions.

Maybe you are looking for

  • Cost of Replacing Screen?

    I just applied some light pressure to the upper left corner to tilt the screen back and it CRACKED! Just a hairline fracture and there was no effect on the picture, but it's over an inch long and now I am absolutely terrified that it is a sign of thi

  • Struts PgFlow error using a RowSet control in WL 8.1 SP1

    I created a RowSet Control within an existing WAR and setup a PgFlow process to CRUD my linked datasource.           When i run or view the pageflow it builds and deploys fine and I am able to view the generated main grid.jsp containing all my data i

  • Does IDoc get triggered when GR occured for a particular po

    Hi Friends, Say a GR occured for a particular PO,so i want to track this GR in Action Code that GR has occuredand no other details is needed except that. so,my question is "Does IDoc get triggered when GR has occured for a particular Purchase Order".

  • Watermarks in Lightroom 4

    Hi. I have Lightroom 4 and was able to get my text watermark to export on my photos until I changed the resolution. Now, even after changing the resolution back, it still won't export the watermark. I've tried deleting and recreating the watermark an

  • Call an other servlet to run in the background?

    I have a servlet which is use to save some forms and after redirect to a thankyou page and send an thankyou email. I don't know whats happen with the email server (they did some modifications and now it is work very slowly). I want to split the servl