William H. Magill1
Level 2 (210 points)
Mac OS X

Q: iTunes 12.1.0.50 - attempting to backup an iPad Air - IOS 8.2 fails

This is a continuing problem.

 

iTunes 12.1.0.50 - attempting to backup an iPad Air - IOS 8.2 - fails - displaying the following in an error pop-up:

   "iPad <name> cannot be synced because there is not enough free space to hold all of the selected items (1MB needed 1,0618 MB available)"


At best, this is clearly a bogus error message (or Apple flunked 6th grade arithmetic) especially as iTunes itself shows 1.27GB Free.

 

Note: 12.1.0.50 is the latest iTunes provided by Apple/update. 12.1.1. is not provided by Apple update mechanisms.  OSX 10.10.2 Security Update 215-003,

Feedback has been submitted -- again.  (Submitted under both iTunes and iPad.)

iMac, OS X Yosemite (10.10.2), iMac Core i7 2.93GHz 4GB

Posted on Mar 27, 2015 6:28 AM

Close
William H. Magill1

Q: iTunes 12.1.0.50 - attempting to backup an iPad Air - IOS 8.2 fails

  • All replies
  • Helpful answers

  • by Brett L,

    Brett L Brett L Mar 30, 2015 6:40 AM in response to William H. Magill1
    Community Specialists
    Mar 30, 2015 6:40 AM in response to William H. Magill1

    Good day William,

     

    If you are having an issue with being unable to back up your iPad, I would suggest that you troubleshoot using the steps in this article - 

     

    If you can't back up or restore your iPhone, iPad, or iPod using iTunes - Apple Support

     

    Thanks for using Apple Support Communities.

     

    Safe computing,

     

    Brett L 

  • by William H. Magill1,

    William H. Magill1 William H. Magill1 Mar 30, 2015 7:51 AM in response to Brett L
    Level 2 (210 points)
    Mac OS X
    Mar 30, 2015 7:51 AM in response to Brett L

    Please note: the issue here is the fact that Apple has failed sixth-grade arithmetic.  The error message states:

                   "1MB needed 1,0618 MB available"

    Clearly, 1,0618 MB is larger than 1MB!


    Yes, there are work-arounds that sometimes work (as evidenced by the number of different work-arounds suggestions in the article you mention).

    However, there is minimally, a problem with the error message -- it is completely bogus -- which lends one to believe that any problem which might exist is clearly Apple's issue which they are not addressing.


    For what it's worth, this is undoubtedly related to the infamous "other" problem which Apple has been attempting to address now for the past several IOS updates.