Time Machine eject in OSX 10.9.3

After installing OSX 10.9.3 I am unable to use my LaCie external drive for Time Machine backups. I continue to receive "failure to eject" notices on my desktop. I do not see the LaCie external drive within Time Machine preferences as a backup alternative. The disk utility does not see the LaCie drive as available for repair, although it is grayed out on the screen. I have shutdown the LaCie drive and shutdown my iMac, as well as restarted it numerous times too, without effect.
...added: When I look at "select Backup Disk" in Time Machine preferences, it shows "Boot OSX" instead of the LaCie external drive. What does this mean?
Message was edited by: Bronco 01

...added: Just to check it out, I changed name of Boot OSX icon on my desktop to 3TB LaCie backup disk and selected it for Time Machine backup disk within Time Machine preferences. I then tried to backup the Time Machine unsuccessfully. I received the following error message, which makes no sense to me:
"Time Machine couldn't complete the backup to "Time Machine Backup 3TB". The backup disk needs 575.91 GB for the backup but only 97.3 GB are available. Select a larger backup disk or make the backup smaller by excluding files."
I'm back to ignorance regarding the Boot OSX designation of the LaCie external drive. Did anything I tried with the restore OSX option, which I never completed out of fear it would affect something adversely, have anything to do with this?

Similar Messages

Even via time machine the new osx lion has deleted all my latest files in iPhoto and will only revert back to an old 2009 backup?

even via time machine the new osx lion has deleted all my latest files in iPhoto and will only revert back to an old 2009 backup?... Help?!

Have you verified that the original files are missing from the Originals/Masters folder? There are time when the library might appear empty due to a damaged database file but still has the files. If you can open the library package via the Finder to see if the files are really missing or just can't be seen by iPhoto there are fixes you can try.
If the files are there make a temporary, backup copy of the library and apply the two fixes below in order as needed:
Fix #1
Launch iPhoto with the Command+Option keys held down and rebuild the library.
Select the options identified in the screenshot.
Fix #2
Using iPhoto Library Manager to Rebuild Your iPhoto Library
Download iPhoto Library Manager and launch.
Click on the Add Library button, navigate to your Home/Pictures folder and select your iPhoto Library folder.
Now that the library is listed in the left hand pane of iPLM, click on your library and go to the File ➙ Rebuild Library menu option
In the next window name the new library and select the location you want it to be placed.
Click on the Create button.
Note: This creates a new library based on the LIbraryData.xml file in the library and will recover Events, Albums, keywords, titles and comments but not books, calendars or slideshows. The original library will be left untouched for further attempts at fixing the problem or in case the rebuilt library is not satisfactory.
OT

Time machine backup between OSX versions?

Hi,
I have a 2006 Mac Pro with OSX10.7 installed, I decided to upgrade as the newest versions of OSX aren't supported. My question is could I restore my OSX 10.7 time machine backup to OSX 10.8? Or would it change the OSX version to 10.7 on the new machine? If so is there anyway to restore the time machine backup without losing OSX 10.8 or having to buy and reinstall it?
Thanks, Tom

Once you have bought a version of Mac OS X, you may re-download and re-Install it as often as you like without paying again -- provided you use the same Apple-ID to do so.
A 2006 Mac Pro cannot run 10.8, so I do not understand the rest of your query. That Mac is stuck at 10.7 as the highest it can run. If you attempt to download 10.8 to it, it should refuse to do so, offering instead the highest purchased version that can actually run on that machine.

Time machine backup from OSX 10.5 to Mountain lion doesn't want to recover.

Hi!
I have just upgraded my iMac from 2007, from the original oreparting system (10.5?) to mountain lion.
I had read a lot about the problems with loosing files so I made a complete backup of the computer using time machine.
I then updated to snow leopard as a "from scratch" installment and then upgraded to mountain lion via the app store.
I therefore had a completely blank computer with only mountain lion installed.
When I now try to take my time machine backup that I did and install it straight over, then it says:
"The operation can’t be completed because you don’t have permission to access “.localized”." or the same sentence but something else instead of localized.
Any tips on how I can try to sort this out?
Thanks!
Annika

For ALL things Time Machine see Pondinis Excellent Information Here...
http://pondini.org/OSX/Home.html
But first... Try Here > http://pondini.org/TM/E10.html
From Section E Here > http://pondini.org/TM/Troubleshooting.html

Time Machine backup on OSX Leopard Server, no user logged in

Hi
I'd like to use Time Machine to do backups of a Mini running OSX Leopard Server. It has a TimeCapsule connected, which it backs up to fine, at the moment.
However, I've been wondering, if it still backs up, if no user is logged in? I've been reading a few old tips about making removable drives not dismount, when no user is logged in by adding/modifying a key in /Library/Preferences/SystemConfiguration/autodiskmount.plist, setting AutomountDisksWithoutUserLogin to true.
Is this still nescessary?
Is TimeMachine actually running when no user is logged in?
Is it a good idea to set the key, if my users homedirs is on a removable drive too?
If TimeMachine is NOT the way to do it, which way is the best/smartest?
Best regards
Nicolai

When reading my report, I forgot to mention how the external hard drive is formatted :
Hard Drive FW/USB:
Manufacturer: LaCie
Model: 0x0
GUID: 0xD04B78070AD64B
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Up to 400 Mb/sec
Sub-units:
Hard Drive FW/USB Unit:
Unit Software Version: 0x10483
Unit Spec ID: 0x609E
Firmware Revision: 0x110
Product Revision Level:
Sub-units:
Hard Drive FW/USB SBP-LUN:
Capacity: 298.09 GB
Removable Media: Yes
BSD Name: disk1
Mac OS 9 Drivers: No
Partition Map Type: APM (Apple Partition Map)
S.M.A.R.T. status: Not Supported
Volumes:
Aristotle:
Capacity: 297.97 GB
Available: 164.85 GB
Writable: Yes
File System: Journaled HFS+
BSD Name: disk1s3
Mount Point: /Volumes/Aristotle
Raf

Time Machine ejecting internal hard drive during backup

I originally posted this in the Time Machine group. It was suggested I post to the Xserve group.
We have an XSERVE running 10.6.4 server. It has 2 internal 1TB drives. The plan is to use one as the main drive and the second as a Time Machine backup. This used to work in 10.5, but since about 10.6.2 or so, it has not worked correctly.
Time machine will come on, begin the backup, and then error off with a message that the drive has been ejected. I have erased the drive, but still no joy. I have partitioned the drive, still no joy. I have verified the drive repeatedly, and all is fine. I can copy files to and from the drive until the cows come home, and all works fine, which means I do not think it is the drive itself. Activate TM, however, and it will fail before the first backup is completed. The only way to get the drive back is to do a complete power down and then power up. Needless to say, that is not a good thing for a server that we rely on.
Any ideas?
10/14/10 10:41:27 AM com.apple.backupd1230 Backup content size: 542.8 GB excluded items size: 474.1 GB for volume Server HD 10/14/10 10:41:27 AM com.apple.backupd1230 No pre-backup thinning needed: 82.46 GB requested (including padding), 930.13 GB available 10/14/10 10:41:27 AM com.apple.backupd1230 Waiting for index to be ready (101) 10/14/10 10:41:27 AM mds70 (Normal) DiskStore: Creating index for /Volumes/backup/Backups.backupdb
10/14/10 10:47:38 AM kernel FusionMPT: Notification = 22 (SAS Discovery) for SCSI Domain = 0 10/14/10 10:47:38 AM kernel Discovery condition = 0x000f0001 10/14/10 10:47:38 AM kernel FusionMPT: Notification = 18 (SAS Phy Link Status) for SCSI Domain = 0 10/14/10 10:47:38 AM kernel SAS Phy Link Status: PhyNum = 0, old link rate = 8, new link rate = 0, SASAddress = 50080007002e8c04
10/14/10 10:48:10 AM kernel SCSIPressurePathManager: Timed out waiting for inactive/error path to become active, loops = 0 10/14/10 10:48:10 AM kernel  10/14/10 10:48:10 AM kernel disk0s2: media is not present.
10/14/10 10:48:10 AM com.apple.backupd1230 Stopping backupd because the backup volume was ejected!  10/14/10 10:48:10 AM com.apple.backupd1230 Error writing to backup log. NSFileHandleOperationException:* -NSConcreteFileHandle writeData:: Input/output error 10/14/10 10:48:10 AM com.apple.backupd1230 Error writing to backup log. NSFileHandleOperationException:* -NSConcreteFileHandle writeData:: Input/output error 10/14/10 10:48:10 AM com.apple.backupd1230 Error writing to backup log. NSFileHandleOperationException:* -NSConcreteFileHandle writeData:: Input/output error 10/14/10 10:48:10 AM com.apple.backupd1230 Copied 13416 files (4.0 GB) from volume Server HD. 10/14/10 10:48:10 AM com.apple.backupd1230 Error writing to backup log. NSFileHandleOperationException:* -NSConcreteFileHandle writeData:: Input/output error 10/14/10 10:48:10 AM servermgrd64 servermgr_backup: TimeMachinePostBackupHook called. 10/14/10 10:48:10 AM servermgrd64 servermgr_backup: TimeMachinePostBackupHook done. 10/14/10 10:48:11 AM kernel jnl: disk0s2: close: journal 0xffffff8012b15d20, is invalid. aborting outstanding transactions  

No, it is not always at the same point/file/bytes transferred. It will vary from a few GB (say 3GB) to quite a few GB (say 30GB). I would add amongst the things I have done was to:
Perform numerous Disk Utility Checks. Never any errors found.
Erased the backup drive on multiple occasions. Double checked the GUID and format.
Partitioned the drive and tried backing up to a new partition. (No joy there either)
Copied lots and lots of data from the root disk to said partitions to test them. All went fine.
It really is Time Machine that is causing the issue. I can use the drive all day long as long as TM does not run. When it does, I eventually get a failure message that the drive has been ejected.
While I have not tried making a partition on the home drive (I'd rather not, lots of data there, make users mad, and since TM is not working, I have no backups at present), I do limit the data that is being backed up to JUST that of the system. /Users is being excluded at the moment. So I doubt there is anything out of the ordinary in the system. And, yes, I did a disk check on the root disk and all is fine there too.

How to remove old backup files from time machine? Lion OSx

Hi everyone,
I am just wondering how to efficiently and safely remove the old backup files from time machine? I tried once with command, but it damaged my extra-disk... Does Lion OSx have fixed that?
Many thanks
Hong

Blue-
Time Machine will automatically delete back-ups as the need for space arises. If you want to delete a certain file (application, document, whatever) and have it gone for good you can do that as well.
The best place on the web for information about Time Machine is...
http://pondini.org/TM/Home.html
...it covers everything!
Clinton

Time Machine ejects my Ext Drive

Hi,
I hooked up an external (1.5TB) drive to my MacBook and ran time machine. It said backing up 103GB. Everything went fine until about 14GB and somehow ejected my ext drive. The drive disappeared. I unhooked and put the drive back. Ran TM again. This time it was backing up about 1KB a minute or so. And soon spit my drive again - showing a failure to back up.
I am not willing to reformat my ext drive because I have put a lot of video files on it.
Any suggestions?
Thanks

Wobbles wrote:
Hi,
I hooked up an external (1.5TB) drive to my MacBook and ran time machine. It said backing up 103GB. Everything went fine until about 14GB and somehow ejected my ext drive. The drive disappeared. I unhooked and put the drive back. Ran TM again. This time it was backing up about 1KB a minute or so. And soon spit my drive again - showing a failure to back up.
I am not willing to reformat my ext drive because I have put a lot of video files on it.
That may be a problem. How is this drive formatted? Was it previously used on Windoze?
The most common cause of an initial Time Machine failure is the drive not being set up properly. Check it via the instructions in item #C1 in the Time Machine - Troubleshooting post at the top of this forum.
As mentioned there, if the formatting is correct, see item #C2 for other possibilities.
There is another consideration here; since you already have other data on that disk, you really should partition it, so TM has it's own, exclusive space. Otherwise you're likely to have conflicts later on. See item #3 in the Frequently Asked Questions post at the top of this forum.

Time Machine "ejects improperly".

I have a March 2009 iMac 10.10.3, and used a Seagate Free Agent Extreme external drive as my Time Machine. It functioned flawlessly.
I purchased a January 2015 iMac 10.10.3, and used the same drive as my Time Machine.
After a short time I began to get a message, “not ejected properly”, and backups ceased
I could restart the drive by disconnecting the power and reconnecting it after a short time. Backups would then proceed for a day or so and the problem would repeat.
A call to Apple support stated that many drives were having the same problem. The blame was placed upon the Seagate provided USB cable. I replaced the cable but the problem remains. It was also suggested that I have the drive tested??
It is odd that the Time Machine functions on 10.10.3 of the old iMac, but not on 10.10.3 of the new iMac. Could there be a problem with the code associated with the running of the Time Machine?
Any ideas?
Thanks

I'm quite sure if there was corruption going on, Apple would continue displaying the message every time. It does warn you with actual hard drives, but with USB sticks and cards, writing should always be cached anyway.
Whatever the case, the warning does nothing to alleviate the problem anyway - casual users don't care/pay attention/know what's going on anyway and advanced users eject properly.

Time Machine Ejecting Second HD and Failing to Backup

Hey everyone, first time posting after many years of getting great tips and help here!
So I've been dealing with this error for the last 3 days. Basically, I have a 13in Macbook Pro with a Second 2TB HD in place of the DVD drive.
When I run Time Machine, somewhere in the backup process it ejects the 2nd HD and fails to backup. I have done the following:
- Tried backing up to my 6TB firewire drive, used exclusively for Time Machine. Didn't work.
- Tried backing up to a 4tb USB3 drive, used exclusively for Time Machine. Didn't work.
- Reinstalled OS X, tried Time Machine on a new installation, didn't work.
- Tried using console to isolate a problematic file and tried to exclude it from the backup, didn't work and another file immediately became problematic. Here's an example of the error.
- Formatted ALL my drives, reinstalled and restored everything. Still the same error -
11/27/14 12:37:46.859 PM com.apple.backupd[180]: Error: (-36) SrcErr:YES Copying /Volumes/Production HD/Komplete/Damage Library/Samples/Damage 001.nkx to (null)
What's strange is that the drive works perfectly fine and when I try to back it up using Carbon Copy Cloner it does so without a glitch.
Any one have any insight on what could possibly be going on here? Below are the details:
MacBookPro9,2
Mac OS X Yosemite 10.10
16GB
System Drive: Samsung SSD 830
Data Drive: Samsung Seagate Momentus SpinPoint ST2000LM003 2TB
Time Machine Drive: WD My Book 1230 Media
Any help would be greatly appreciated! Not sure what to try at this point.

Start with Section C in the 1st linked article.
Time Machine Troubleshooting
Time Machine Troubleshooting Problems

Do you have Time Machine in Mac OSX Server 10.6?

Do you?
How does it work? Does it back up the data every hour, or is is possible to do it more often?

Time Machine is variously incompatible with the creation of backups of the Mac OS X Server box itself; while the basic TM configuration might (does?) work, but the advanced configuration won't work. Well, you'll probably get copies of what was once an "advanced" configuration, but whether you can restore and resume use of those can be problematic at best.
You need take explicit steps to gain consistent and restorable archives of various Mac OS X Server configurations.
Have a look around the forums for existing discussions of (for instance) shutting off dovecot to get a snapshot of the mail store.

How to prevent Time Machine from ejecting volume?

I just set up a Buffalo Cloustor NAS (which is working very nicely, thank you) and one of its features is that it plays nice with Time Machine backups. I also recently took advantage of a MacUpdate promo on Back-In-Time. BIT works fine as long as the NAS backup volume is mounted but for some reason Time Machine ejects that volume when it's finished its backups. I've seen similar problems in threads of non-Lion version of OSX but they seemed to be troubles with USB or FW drives rather than an Ethernet NAS. I'd rather keep the NAS volume mounted so I can use this 3rd party app.
Here is a copy of the console messages filtered on "time machine" for the relevant time period:
3/24/12 7:11:03.180 PM
com.apple.backupd
Disk image /Volumes/cloudshare/Mini2009’s Mac mini.sparsebundle mounted at: /Volumes/Time Machine Backups
3/24/12 7:11:03.196 PM
com.apple.backupd
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
3/24/12 7:12:37.276 PM
com.apple.backupd
Ejected Time Machine disk image.
3/24/12 7:12:37.678 PM
com.apple.backupd
Ejected Time Machine network volume.
Is there a way of telling Time Machine to not eject when finished? I'm comfortable writing stuff using Terminal if that's what it takes.
Thanks!
-Tod

BordeauxQuill wrote:
If it is useful to anyone else, these are Western Digital My Passport Studio 640GB drives.
Yup, you're the 3rd or 4th to report it with various models of WDs (one fellow had 3 of them!), and a few weeks ago someone had some Iomegas, I think, too.
This confusion may well also explain some weird stats in Get Info I noticed last week (such as the drive apparently having used more bytes than its capacity, as I recall).
Quite likely.
Thank you for your support. I shall come back and mark the thread resolved when I have reformatted the drive.
Cool. Also double-check the contents of the one you don't erase; you may find some extra stuff there.

I have an iMac OS X 10.6.8 and have problems with the backup Disk for Time Machine disconnecting itself with the message that I ejected it improperly.. It ejected itself - why?

I have an iMac OS X 10.6.8 and have problems with the backup drive to Time Machine ejecting itself and so does not automatically backup the way it is meant to do. It is connected with an USB cable to my iMac. What could cause this - malfuntioning drive?

The "iLife" apps are not part of any Mac operating system install and are a separate purchase.
Once you get past 10.6.6 you can purchase and download iPhoto, GarageBand and iMovie. iWeb and iDVD have been discontinued.
Snow Leopard 10.6.6 and higher include the App Store application which is what you use to purchase Lion.

Ejecting Time Machine disk will prompt to choose its partitions

By clicking to eject the TM disk my Mac asks which partition I'd like to eject. Of course, if really present, those partitions were automatically created by the Mac itself, not by me, thus asking me which one sounds useless to me!
Besides, Disk Utility shows only one partition, while others seem to be undisclosed.

I connected the backup drive, let it performing a backup, turned the TM feature off, launched Disk Utility, selected the icon of the drive (not the volume), clicked on Repair Disk (btw Repair Permissions button was greyed out), waited several minutes for the operation to complete and got the drive led stuck flashing. Tried to eject the disk and got the same prompt window, remounted the disk with Disk Utility, reactivated Time Machine, ejected the disk and the window didn't prompt.
For now it worked! Thank you.
PS
I rewrote the whole procedure, in case someone reading this topic should not exactly understand what to do before and after what you suggested.

Time machine osx server backup to multiple drives?

Hello,
I've just discovered Time Machine for Mac OSx Server. It can act as a centralizad point for the backups of all the computers in the network, how cool!
I know that Time Machine "client" can back a system up to multiple drives. My question is, can I do something similar with Time Machine "server" so I can have more than one storage product onto which I can back up all the systems? That would be very interestin if I want to implement a off-site backup from all my systems.
I would love to hear your inputs.Thanks in advance,
Regards,

I don't know. If the TM preference pane is scriptable then you could do it with an AppleScript. Unfortunately, TM is not designed to also schedule different backup times. For example, assume you could automate drive switching, you still need to tell TM to backup to one drive at some time then backup to another drive at a different time.
I suppose the latter could be done via a cron job as long as you did not use TM preferences to turn TM on in which case it will backup each hour automatically.
It seems to me you'd be better off using a different backup utility that would allow you to schedule such backups. For example:
1. Retrospect Desktop (Commercial)
2. Synchronize! Pro X (Commercial)
3. Synk (Backup, Standard, or Pro)
4. Deja Vu (Shareware)
5. Carbon Copy Cloner (Donationware)
6. SuperDuper! (Commercial)
7. Intego Personal Backup (Commercial)
8. Data Backup (Commercial)
9. SilverKeeper 2.0 (Freeware)
10. Tri-Backup (Commercial)
Others may be found at VersionTracker or MacUpdate.
Visit The XLab FAQs and read the FAQ on backup and restore. Also read How to Back Up and Restore Your Files.
Not all of the above will backup over a network, but most can backup to any mounted device including a network drive except SuperDuper!.
In an enterprise setting your best choice of the above is Retrospect. There are a few other enterprise level backup utilities (costly) that you can track down at VersionTracker or MacUpdate. BRU is an example.
Oh, and if you know how to use the command line you can use the Unix tools, ditto and rsync.
Message was edited by: Kappy

Time Machine eject in OSX 10.9.3

Similar Messages

Maybe you are looking for