Mountain Lion won't let me create a new Time Machine backup

Question

Level 1

0 points

Mountain Lion won't let me create a new Time Machine backup

Hi,

today I upgraded to Mountain Lion, and everything seemed fine with the system, until I had to check Time Machine.

I already had many problems when upgrading to Lion since I'm using a Western Digital 4Tb Sharespace to save my backups. But now, in Mountain Lion, when i tried to backup, it simply didn't let me. I decided to start fresh, as I didn't need the old copies, but now, with everything deleted (and the RAID re-created for this purpose, so perfectly new) when it is going to mount the drive, it says that the disk is not available.

Checking the console it says "error 19", but I cannot find what that error exactly means, just some wonderings and roundabouts for other people's problems (which aren't exactly mine)

Any solution? Is it Mountain Lion, or Sharespace's Firmware?

Thanks

Mac Pro, OS X Mountain Lion, Sharespace 4Tb NAS

Posted on Jul 25, 2012 5:55 PM

Reply

Answer 1

Linc Davis

Level 10

209,649 points

Jul 25, 2012 6:16 PM in response to Lord-Enzo

If you have more than one user account, these instructions must be carried out as an administrator.

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad. Click Utilities, then Console in the page that opens.

Select "system.log" from the file list. Copy the words "Starting standard backup" (without the quotes) on this page and paste into the String Matching text field. Note the timestamp of the last message shown. Clear the text field and scroll back in the log to that time. Post the messages timestamped from then until the end of the backup, or the end of the log if that's not clear.

Post the log text, please, not a screenshot. If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.

Some personal information, such as the names of your files, may be included — edit that out, too, but don’t remove the context.

Reply

Answer 2

Lord-Enzo Author

Level 1

0 points

Jul 25, 2012 6:32 PM in response to Linc Davis

Nothing just searching for "Starting standard backup" only these two:

Jul 26 00:39:40 MacPro-Enzo.local com.apple.backupd[2759]: Starting automatic backup

Jul 26 00:39:42 MacPro-Enzo.local com.apple.backupd[2759]: Backup failed with error: 19

And this one when trying to force the backup (hitting Backup now from the menu bar icon, as I didn't want to wait the 120 seconds after changing the disc in the System Preferences):

Jul 26 00:42:34 Mac-Pro.local com.apple.backupd[2759]: Starting manual backup

Jul 26 00:42:34 Mac-Pro.local com.apple.backupd[2759]: Backup failed with error: 19

And, just in case, some of the things that the log outputs when configuring Time Machine:

Jul 26 00:41:13 Mac-Pro.local UserEventAgent[11]: com.apple.backupd-auto launchd job disabled

Jul 26 00:41:13 Mac-Pro.local UserEventAgent[11]: com.apple.backupd-wake launchd job disabled

Jul 26 00:41:13 Mac-Pro.local UserEventAgent[11]: com.apple.backupd-attach launchd job disabled

Jul 26 00:42:21 Mac-Pro kernel[0]: AFP_VFS afpfs_mount: /Volumes/WD_Backup, pid 2800

Jul 26 00:42:21 Mac-Pro kernel[0]: AFP_VFS afpfs_mount : succeeded on volume 0xffffff80d6ce1008 /Volumes/WD_Backup (error = 0, retval = 0)

Jul 26 00:42:21 Mac-Pro.local UserEventAgent[11]: com.apple.backupd-auto launchd job enabled

Jul 26 00:42:21 Mac-Pro.local UserEventAgent[11]: com.apple.backupd-wake launchd job enabled

Jul 26 00:42:21 Mac-Pro.local UserEventAgent[11]: com.apple.backupd-attach launchd job enabled

Jul 26 00:42:22 Mac-Pro kernel[0]: AFP_VFS afpfs_unmount: /Volumes/WD_Backup, flags 0, pid 2806

Jul 26 00:42:22 Mac-Pro kernel[0]: AFP_VFS afpfs_unmount : We are the last mnt/sbmnt using volume /Volumes/WD_Backup 0xffffff80d6ce1008

Jul 26 00:42:22 Mac-Pro kernel[0]: AFP_VFS afpfs_unmount : We are the last volume using socket /Volumes/WD_Backup 0xffffff80d6ce1008

Jul 26 00:42:34 Mac-Pro.local com.apple.backupd[2759]: Starting manual backup

Jul 26 00:42:34 Mac-Pro.local com.apple.backupd[2759]: Backup failed with error: 19

Reply

Answer 3

Linc Davis

Level 10

209,649 points

Jul 25, 2012 6:59 PM in response to Lord-Enzo

You're backing up to a third-party NAS, or trying to. If it doesn't work, your only recourse is to the NAS vendor. I suggest that you stop trying to use the NAS with Time Machine and back up to locally attached external storage devices instead.

Reply

Answer 4

Pondini

Level 8

38,863 points

Jul 25, 2012 7:05 PM in response to Lord-Enzo

Lord-Enzo wrote:

Hi,

today I upgraded to Mountain Lion, and everything seemed fine with the system, until I had to check Time Machine.

I already had many problems when upgrading to Lion since I'm using a Western Digital 4Tb Sharespace to save my backups.

Were you able to back up to it in Lion? If not, or if you didn't try, your NAS may need a firmware upgrade. Check with WD.

Reply

Answer 5

Lord-Enzo Author

Level 1

0 points

Jul 25, 2012 7:16 PM in response to Pondini

Yes, I was perfectly able (what I mean is that I had problems at the moment of upgrading, with all the Netatalk changes introduced in Lion). I just won't let me log in now, either with my Mac Pro or my MacBook Pro (both upgraded to Mountain Lion).

I can see the files in the "normal" shares, but Time Machine cannot access the Time Machine specific share when trying to mount it to start backing up. It finds it when selecting the device from a list to configure the service, and even checks the user/password correctly, but when trying to mount the drive, it just says that the disk is not available, and the Console gives me the previous error.

Reply

Answer 6

Pondini

Level 8

38,863 points

Jul 25, 2012 7:19 PM in response to Lord-Enzo

That sounds like it's unable to mount the sparse bundle.

Have you tried repairing it, per #A5 in Time Machine - Troubleshooting? The Verify Backups option probably won't work; use the long procedure.

Reply

Answer 7

Lord-Enzo Author

Level 1

0 points

Jul 25, 2012 7:22 PM in response to Pondini

No, as there is no sparsebundle, I'm starting fresh.

That's when I tried the MBP, thinking that maybe some old .plist or something might be messing around, I tried with the laptop because I've never done a TM backup with it, but it do not connect either, same error

Reply

Answer 8

Pondini

Level 8

38,863 points

Jul 25, 2012 7:31 PM in response to Lord-Enzo

Lord-Enzo wrote:

No, as there is no sparsebundle, I'm starting fresh.

Oh, sorry, I missed that in your original post. 😟 (It's been a looooong day here.)

I don't know much about NASs, but at least some models of WDs have a reset button and default login. You might try that.

Otherwise, all I can suggest is check with WD.

Reply

Answer 9

Lord-Enzo Author

Level 1

0 points

Jul 25, 2012 7:33 PM in response to Pondini

I think I'm going to post it in the WD forum, but last time (upgrade to Lion) they weren't very helpful!

Thanks for your help!!

😁

Reply

Answer 10

Jul 25, 2012 8:37 PM in response to Lord-Enzo

I had the same problem, and found this great blog that resolved my issue, give it a try http://www.trollop.org/tag/afp/ .

Reply

Answer 11

Lord-Enzo Author

Level 1

0 points

Jul 26, 2012 10:28 AM in response to Efthymakis

You also have a WD Sharespace?

I tried what you said, but with no success... There are different things to do in here:

If I try to do the backup in a specifically created share, it will display this error:

Destination does not support lock stealing. (error 45)

The backup destination could not be set.

But, actually, the system does the copies in another directory, which is hidden by default "/DataVolume/.timemachine/" with a special user created for that purposte (WD_Backup is called). This is the way this NAS does things, so I don't really know how to mount the drive manually, as I don't know where it is located.

Using the command "showmount" it does not show any mounts available other than the ones I created myself.

Also, discovered by Bonjour, I can see "Alexandria" (which is the name of the drive) and "Alexandria-Backup" which the one (supposedly) used for backups, but the system won't let me log in that drive (it will only let the Time Machine application log in that mount).

I've posted this also in the WD-Community. If I get an answer I will keep you posted. Thank you for your help.

Reply

Answer 12

Jul 26, 2012 10:43 AM in response to Lord-Enzo

yes, i too have a WD Sharespace, but the procedure should work for any remote backup device.

By default the WD Sharespace creates a hidden share called 'WD_Backup' and a user called 'wd_backup' with a default password of 'backup'.

Using the example in the blog : sudo tmutil setdestination afp://user:pass@host/share

...and assuming the following (all default settings with the exeption of the WD Sharespace Server name) -

Server Name: TimeMachine

Volume Name: DataVolume

User: wd_backup

Password: backup

you should execute the following at the terminal:

sudo tmutil setdestination afp://wd_backup:backup@TimeMachine/WD_Backup

In addition, you can validate you are using the correct UserID/Password, by:

- Launching the Finder and click on 'Go' from the menu

- Click on 'Connecto to Server...'

- in the Server Address field, enter: "afp://TimeMachine/WD_Backup" and click 'Connect'

- you'll be prompted to enter the UserID and Password to the share; assuming you have not changed either, the default is UserID: wd_backup and Password: backup.

If your machine cannot resolve the TimeMachine Server name, then replace "TimeMachine" with the IP address of your WD Sharespace Server.

..this will mount a drive to the WD_Backup folder, underwhich you will find the <machine_name>.sparcefile that TM uses to store your backup. All this is covered in the WD Sharespace User Guide on page 46 under the TimeMachine configuration section.

Reply

Answer 13

Pondini

Level 8

38,863 points

Jul 26, 2012 10:51 AM in response to Lord-Enzo

Lord-Enzo wrote:

. . .Destination does not support lock stealing. (error 45)

The backup destination could not be set.

That means it's not fully compatible with Time Machine on Mountain Lion. See if WD has an update.

Reply

Answer 14

Jul 26, 2012 11:13 AM in response to Lord-Enzo

Backup works here on a Toshiba external 2.5" 750gig USB drive but it did not see previous backups. That's ok because I'll just back the whole thing up again, 10 gigs of applications and data. And there really isn't much wrong with Mountain Lion that I'd want to uninstall it other than some of the new features taking a bit of time figuring out and one app needing an upgrade to work in 10.8.

Reply

Answer 15

Lord-Enzo Author

Level 1

0 points

Jul 26, 2012 11:20 AM in response to Efthymakis

Hi Efthymakis,

it worked like a charm withing Terminal! Thank you very much

Mac-Pro: /Users/Enzo

→ sudo tmutil setdestination afp://WD_Backup:backup@192.168.1.150/WD_Backup

But, I have to tell you: I've never been able to mount the share in which the sparsebundle is located manually. I've read page 46 of the manual (I've actually read every possible PDF issued by WD about the Time Machine & Sharespace solutions) but it never mounts anything in the Finder (never tried through Terminal).

I know this becasue I've had some sparesbundles corrupted, and I never could get the files to inspect them, because I couldn't mount the drive. With your instructions I haven't been able either, it says that the drive does not exist.

However, if entering "afp://wd_backup:backup@192.168.1.150/WD_Backup" instead of "afp://192.168.1.150/WD_Backup" it gets to mount it from the Finder window (cmd+K). I have tried this while writing this post, because as you were so sure that it worked (even though for me the "straightforward" solution does not work) I decided to try this last thing!

Right now is backing everyting, so thank you very much for all your help!

Reply