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.

Similar Messages

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.

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?

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 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

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.

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.

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.

My Seagate external 250GB hard drive ejects improperly without command. I am trying to use Time Machine to backup my macbook via usb cable... I keep getting the message that the disked ejected improperly... Any solutions...

My Seagate external 250GB hard drive ejects improperly without command. I am trying to use Time Machine to backup my macbook via usb cable... I keep getting the message that the disked ejected improperly... Any solutions...

You are not alone. Thousands have this problem, on various models of Macs. Short answer, it has something to do with the disk going to sleep (possibly?). You can't do anything about it and Apple won't address the problem. Maybe you should buy a time capsule. Just keep giving them money and use their proprietary equipment.
For a more complete answer, see this thread (all 65+ pages of it with NO SOLUTION IN SIGHT... except for some 3rd party solutions that sometimes work, sometimes don't): Disk Drive ejecting itself

Disk not ejected properly while making a backup through time machine

Hi everyone. I'm trying to make a backup by using time machine on an external hard drive LaCie of 2 TB. However, after storing 5 to 10 GB the backup stops and I get a message window saying that the disk has not been properly ejected and that I have to eject the disk before turn it off. Then I thought it was a format problem, I went to the disk utility and I chose the Mac OS extended (journaled) format and the GUID partition table since my Mac is intel-based. I started the backup again and I got the same message window saying that I desconected improperly my external drive. The strange thing is that in both cases the backup seems to be okay at the beginning and stores 5 to 10 GB, more or less, then it stops and the message window shows up. Then I went further, I thought I could fix the problem by completely erasing the disk; I went to the disk utility and in the erase tab I chose the Zero Out Data option in the security options. The system starts erasing the external hard drive, but after a while other message window shows up saying that there was an error eliminating the disk because of a POSIX reports, that the operation could not be completed and that memory could not be assigned. Does anyone know what's going on? What am I doing wrong? Thank you in advanced for your support.

Most likely, there's a damaged/corrupted file on your Mac that Time Machine is choking on.
Erase the disk (quick erase is almost always fine) and start over.
If the backup fails, See #C2 in Time Machine - Troubleshooting. It will show you how to locate the message(s) that describe the problem, then help you fix it. If that doesn't help, post back with details, including all the messages, your setup (especially the destination for the backups), what you've done, and the results.
EDIT: I should add, sometimes when Time Machine has a problem, it force-ejects the drive.

External Hard Drive ejects during Time Machine Backup

I've read through all the troubleshooting pages that I thought had anything to do with this problem, but none of my error messages seemed to match. This is my first backup with Time Machine onto my external hard drive, and it never gets past about 60GB before deciding that the drive has improperly ejected itself and aborting the backup. The error message from my Time Machine Buddy is below:
Starting standard backup
Backing up to: /Volumes/Untitled/Backups.backupdb
Ownership is disabled on the backup destination volume. Enabling.
Backup content size: 147.2 GB excluded items size: 5.1 GB for volume Macintosh HD
No pre-backup thinning needed: 170.49 GB requested (including padding), 930.54 GB available
Waiting for index to be ready (101)
Copied 56.0 GB of 142.1 GB, 112101 of 886988 items
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Device not configured
Error: (-50) SrcErr:NO Copying /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/ge ms/net-ssh-1.1.4/lib/net/ssh/proxy/errors.rb to /Volumes/Untitled/Backups.backupdb/Eugenio Vargas Computer/2011-05-17-161101.inProgress/E6F5C3CB-75B8-41C4-B52E-138235EB4B34/Maci ntosh HD/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/ gems/net-ssh-1.1.4/lib/net/ssh/proxy
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Device not configured
Error: (-50) SrcErr:NO Copying /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/ge ms/net-ssh-1.1.4/lib/net/ssh/proxy/http.rb to /Volumes/Untitled/Backups.backupdb/Eugenio Vargas Computer/2011-05-17-161101.inProgress/E6F5C3CB-75B8-41C4-B52E-138235EB4B34/Maci ntosh HD/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/ gems/net-ssh-1.1.4/lib/net/ssh/proxy
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Device not configured
Error: (-50) SrcErr:NO Copying /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/ge ms/net-ssh-1.1.4/lib/net/ssh/proxy/socks4.rb to /Volumes/Untitled/Backups.backupdb/Eugenio Vargas Computer/2011-05-17-161101.inProgress/E6F5C3CB-75B8-41C4-B52E-138235EB4B34/Maci ntosh HD/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/ gems/net-ssh-1.1.4/lib/net/ssh/proxy
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Device not configured
Error: (-50) SrcErr:NO Copying /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/ge ms/net-ssh-1.1.4/lib/net/ssh/proxy/socks5.rb to /Volumes/Untitled/Backups.backupdb/Eugenio Vargas Computer/2011-05-17-161101.inProgress/E6F5C3CB-75B8-41C4-B52E-138235EB4B34/Maci ntosh HD/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/ gems/net-ssh-1.1.4/lib/net/ssh/proxy
Indexing a file failed. Returned 200 for: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/ge ms/net-ssh-1.1.4/lib/net/ssh/proxy, /Volumes/Untitled/Backups.backupdb/Eugenio Vargas Computer/2011-05-17-161101.inProgress/E6F5C3CB-75B8-41C4-B52E-138235EB4B34/Maci ntosh HD/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/ gems/net-ssh-1.1.4/lib/net/ssh/proxy
Aborting backup because indexing of file failed.
Other details:
My external drive is a WD 1TB drive. The partition for the Time Machine Backup is formatted as Mac OS Extended (Journaled), as is my Macintosh HD. The Partition Map Scheme on the external drive is GUID Partition Table.
I have tried reformatting the external drive for good measure, but this doesn't seem to solve any problems. I also tried searching for the file that the error message says NO Copying for (/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/g ems/net-ssh-1.1.4/lib/net/ssh/proxy/...) but I'm unable to find the files. I can get as far as /System/Library/Frameworks, but can find no folder in Frameworks titled Ruby.
Please help.

The Ruby folder is probably hidden. That is why you don't see it.
You may want to add System/Library/Frameworks to the exempted sync list until you can figure out which file is causing this. You can do this by opening Time Machine Preferences ( > System Preferences > Time Machine) and clicking on Options…
After that click the small + key and browse to the folder you want to exempt from the sync. In your case: Macintosh HD > System > Library > Frameworks
Next hit the exclude button with the Frameworks folder highlighted.
Try your backup again and see if it fails.

Time Machine Disk Self-ejects, and more

I'm using a 1 TB FreeAgent GoFlex external USB drive as my Time Machine back up. Half the time it works perfectly, other times it suddenly ejects itself and I get a message about how the disk was ejected improperly. If I pop out the USB cable, then plug it back in, the disk remounts and goes on as before. Other times it will begin backing up, and seems to get stuck in "back up" mode. It keeps evaluating the main hard drive until it's time to shut down for the day. I can't make it stop. If I go ahead and shut down, the computer quits everything down to the bare desktop, then locks up. If I shut down while not stuck in "evaluating" the computer shuts down normally.
How do I make the disk quit self ejecting?
How do I keep it from getting stuck "evaluating" the disk?

I have a similar problem which only recently developed with my Seagate FreeAgent Desktop Classic. The drive ejects only during TM backups. Here's the message from the TM widget:
Starting standard backup
Backing up to: /Volumes/TM/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
No pre-backup thinning needed: 309.2 MB requested (including padding), 365.05 GB available
Unable to rebuild path cache for source item. Partial source path:
Error: (-39) SrcErr:YES Copying (null) to (null)
Copied 8845 files (84.6 GB) from volume Macintosh HD.
No pre-backup thinning needed: 534.6 MB requested (including padding), 280.31 GB available
Stopping backup.
Error: (-43) SrcErr:NO Copying /Users/angeloferraro/Library/Preferences/Macromedia/Flash Player/#SharedObjects/EC6L7AJD to (null)
Copied 8625 files (184.9 MB) from volume Macintosh HD.
Copy stage failed with error:11
Stopping backupd because the backup volume was ejected!
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
Backup failed with error: 27
have reformatted the external drive which has not helped.
No problem if TM is switched off. No disk errors with Apple's native disk utility, however Seagate's drive manager reports that "the selected drive failed its most recent diagnostic test" but does not provide any further information.
Have sent an email to seagate and awaiting their reply. Drive still under warranty.

I got a macbook pro 2008 and can not back up using time machine. it eject my external hard drive everytime. does someone has a fix???

i got a macbook pro 2008 and can not back up using time machine. it eject my external hard drive everytime. does anybody has a fix???

Does your external hard drive have it's own power supply? It should.
Is your external hard drive formatted with the NTFS file system? It won't work.
It needs to be formatted either with Mac OS Extended or FAT32.
(There are drivers available to add NTFS support to OS X but their quality is unknown, especially the "free" ones.)

I have a Seagate Freeagent 1TB external drive that ejects it's self in the middle of the time machine backup, then disappears and can't be found unless I turn it off and back on again

I have a Seagate Freeagent 1TB external drive that ejects it's self in the middle of the time machine backup, then disappears and can't be found unless I turn it off and back on again. Any ideas?

Hmmm.. sorry to jump in but...
I Wish I had seen this before I got mine.
Mine has been doing this auto eject stuff too.
I think I just plugged it in and TM let me select it but is it possible
I should have reformatted it with DU first, like with all the WD drive problems ?
Is it too late for that ?
Or just try to return it or get rid of it ?
TIA

Time Machine backups cause error message "Disk No Ejected Properly"

I have a 2011 iMac using OS X version 10.9.4. I have had to change the external hard drive used with my Time Machine to get more storage. Every time the Time Machine backs up (every hour), I get the message "Disk Not Ejected Properly" Eject "FreeAgent GoFlex Drive" before disconnecting or turning it.
I am concerned about any damage that is happening because of this message. I researched this on this forum and other users had a similar problem. I tried 2 of the easier solutions: 1) make sure none of the boxes are checked in System Energy Saver (ie. put hard disks to sleep when possible, etc.) and 2) buy and connect a USB hub that has it's own power supply to keep the external hard drive powered constantly. Neither of these solutions has worked for me. I still get the message. So I have two questions. First, is damage being done to my computer because it "thinks" that I did not properly eject the disc. And, second, is there anything else I can do to stop this message besides not using the freeagent disc?

I had the same problem. it turned out to be a cable issue. Contact seagate for replacement cable.
http://www.seagate.com/support-all/

Time Machine "ejects improperly".

Similar Messages

Maybe you are looking for