riri wrote:20.10.08 22:41:58 /System/Library/CoreServices/backupd Network mountpoint /Volumes/TimeMachine not owned by backupd... remounting
There's an ownership problem somewhere. A few questions:
1) Is the Mac account you set this up with an Admin account?
2) Do you have an account on your NAS that EXACTLY matches the username and password of the Mac account used to set up the Spasrebundle on the NAS?
3) Please telnet to your NAS and cd to the directory where your TimeMachine share is located (eg. cd /share/MD0_DATA
for TS-409, but don't confuse it with the link to TimeMachine at /share/). Do an ls -alF
, you should see something like:
- Code: Select all
drwxrwxrwx 3 admin everyone 4096 Aug 7 15:00 TimeMachine/
4) Does the TimeMachine share have both the administrators
groups with Full Access assigned to it? See Network Share Management->Access Control
20.10.08 22:42:00 kernel AFP_VFS afpfs_mount: /Volumes/TimeMachine-1, pid 329
20.10.08 22:42:00 /System/Library/CoreServices/backupd Network volume mounted at: /Volumes/TimeMachine-1
In fact, it looks like a volume called "TimeMachine" has already been mounted (perhaps under a different user?) and it tried to mount it a second time as "TimeMachine-1". This really messes up TM (which of course has been set up to use "TimeMachine" and not "TimeMachine-1"), which is why I recommend Fast User Switching be disabled. If there is already a "TimeMachine" volume mounted that can't be ejected ie. it is locked by something, best cure is to simply reboot the Mac.
20.10.08 22:42:00 /System/Library/CoreServices/backupd Creating disk image /Volumes/TimeMachine-1/Nati_001ff3522c3c.sparsebundle
So TM tries to create its own Sparsebundle...
20.10.08 22:42:48 /System/Library/CoreServices/backupd Error 45 creating backup disk image
20.10.08 22:42:48 /System/Library/CoreServices/backupd Failed to create disk image
Which fails, because this Sparsebundle (should!) already exists and is locked...
20.10.08 22:42:53 /System/Library/CoreServices/backupd Backup failed with error: 20
So the backup fails because it cannot write to the Sparsebundle...
20.10.08 22:42:54 kernel AFP_VFS afpfs_unmount: /Volumes/TimeMachine-1, flags 0, pid 363
20.10.08 22:42:54 /System/Library/CoreServices/backupd Ejected Time Machine network volume.
TM ejects "TimeMachine-1" (normal when a TM session completes)...
20.10.08 22:44:28 /System/Library/CoreServices/backupd Network mountpoint /Volumes/TimeMachine not owned by backupd... remounting
20.10.08 22:44:29 kernel AFP_VFS afpfs_mount: /Volumes/TimeMachine-1, pid 369
20.10.08 22:44:29 /System/Library/CoreServices/backupd Network volume mounted at: /Volumes/TimeMachine-1
Looks like the backup process started again a few minutes later.
Are you connecting to the NAS share via SMB or AFP, out of interest?
Actually, TM is connecting to your NAS via the AFP protocol, according to the logs.
If you want to use AFP, does your NAS have the very latest firmware installed? Apparently, Apple tightened up on AFP security (or made some other changes) with Leopard which became problematic for the QNAP NASes, which a recent firmware update fixed.
Anyway, something for you to think about.