Time Machine issue

[Kiran1]

I have been using the Apple Time Machine for the past year with no issues. I got a message today that it had not been backing up and the last back up was ran on September 4. I tried to fix the issue but kept coming up with the following message:
The disk image "Kiran's Macbook Pro.sparsebundle" is in use. Try ejecting the disk image.

What does this mean and how do I fix it?
Thanks for your help.

 

[RadDave]

I have been using the Apple Time Machine for the past year with no issues. I got a message today that it had not been backing up and the last back up was ran on September 4. I tried to fix the issue but kept coming up with the following message:
The disk image "Kiran's Macbook Pro.sparsebundle" is in use. Try ejecting the disk image.

Hi Kiran - well, you've not helped us much: 1) What Apple computer are you using; 2) What OS X is installed; and 3) I'm assuming that you mean an Apple 'Time Capsule' - correct? If so, take a look HERE to see if the information helps; if not, please post back - Dave

 

[Kiran1]

I have a Macbook Pro that's a couple years old. I have Maverick installed as my OS X and yes I meant a time capsule hahaha

 

[Slydude]

@Kiran1 The fact that the error mentions sparse bundle suggests you are saving Time Machine backups to some type of network drive such as a Time Capsule or drive attached to a network device. It would help us to know exactly what the setup is as that affects the troubleshooting steps available.

If you are backing up to a Time Capsule try the following and let us know the result. Double click the sparsebundle file and see if it mounts in the Finder. If it does launch Disk Utility. The Time machine bundle should appear as a disk in Disk Utility. Select it then try to verify and repair the disk.

 

[Kiran1]

I tried the link for the firmware update and that seemed to have solved the issue. Thanks for your help!

 

[RadDave]

I tried the link for the firmware update and that seemed to have solved the issue. Thanks for your help!

GREAT! Looks like Slydude and I were replying @ the same time - glad that the firmware update solved your issue - Dave