Problem with Time Machine setup on Synology DS412+

[newton]

MacBook Pro running 10.7.5 cannot backup to Time Machine for some reason (2 Mac Pros on same network are fine, one on same OS, other on SL). Have set up a specific user for TM as recommended in Synology web guide and a quota of 1.6TB. I suspect this is a permissions issue related to DSM - the Mac connects to the TM share as the TM user, however an error is displayed after connecting that there is not enough space (approx 1.6GB instead of 1.6TB - approx 250GB required). Initially it as trying to use the DSM admin user (which is used for Finder access), even after I'd changed to the TM user. Temporarily removed DSM admin from Keychain and seems to be using the TM user in OSX logs. TM settings in Sys Prefs show approx 1.6TB free, can't see what else obvious it could be! Any ideas would be appreciated. Have replicated as test user (OS X log below):

02/12/2013 20:08:21.000 kernel: AFP_VFS afpfs_mount: /Volumes/StudioX-1, pid 1113
02/12/2013 20:08:21.000 kernel: AFP_VFS afpfs_unmount: /Volumes/StudioX-1, flags 0, pid 1135
02/12/2013 20:08:21.000 kernel: ASP_TCP do_thread_read: no reqInfo found for reqID 0
02/12/2013 20:08:26.712 com.apple.backupd: Starting standard backup
02/12/2013 20:08:27.604 com.apple.backupd: Network destination already mounted at: /Volumes/StudioX
02/12/2013 20:08:44.566 com.apple.backupd: Resizing backup disk image from 1.6 GB to 1599.9 GB
02/12/2013 20:08:44.576 com.apple.backupd: Could not resize backup disk image (DIHLResizeImage returned 35)
02/12/2013 20:08:45.888 com.apple.backupd: QUICKCHECK ONLY; FILESYSTEM CLEAN
02/12/2013 20:08:47.862 com.apple.backupd: Disk image /Volumes/StudioX/Robin’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups 1
02/12/2013 20:08:47.868 com.apple.backupd: Backing up to: /Volumes/Time Machine Backups 1/Backups.backupdb
02/12/2013 20:08:59.108 com.apple.backupd: Backup content size: 228.1 GB excluded items size: 10.2 GB for volume Data
02/12/2013 20:08:59.123 com.apple.backupd: 261.44 GB required (including padding), 1.54 GB available
02/12/2013 20:08:59.124 mds: (Error) Volume: Could not find requested backup type:2 for volume
02/12/2013 20:08:59.493 com.apple.backupd: Ejected disk image: /Volumes/StudioX/Robin’s MacBook Pro.sparsebundle
02/12/2013 20:08:59.493 com.apple.backupd: Compacting backup disk image to recover free space
02/12/2013 20:08:59.742 diskimages-helper: Reclaimed 0 bytes out of 1.5 GB possible.
02/12/2013 20:09:00.753 com.apple.backupd: Completed backup disk image compaction
02/12/2013 20:09:00.754 com.apple.backupd: Starting standard backup
02/12/2013 20:09:00.784 com.apple.backupd: Network destination already mounted at: /Volumes/StudioX
02/12/2013 20:09:17.863 com.apple.backupd: Resizing backup disk image from 1.6 GB to 1599.9 GB
02/12/2013 20:09:17.874 com.apple.backupd: Could not resize backup disk image (DIHLResizeImage returned 35)
02/12/2013 20:09:19.341 com.apple.backupd: QUICKCHECK ONLY; FILESYSTEM CLEAN
02/12/2013 20:09:21.329 com.apple.backupd: Disk image /Volumes/StudioX/Robin’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups 1
02/12/2013 20:09:21.336 com.apple.backupd: Backing up to: /Volumes/Time Machine Backups 1/Backups.backupdb
02/12/2013 20:09:24.003 com.apple.backupd: Backup content size: 228.1 GB excluded items size: 10.2 GB for volume Data
02/12/2013 20:09:24.015 com.apple.backupd: 261.44 GB required (including padding), 1.54 GB available
02/12/2013 20:09:24.016 com.apple.backupd: No expired backups exist - deleting oldest backups to make room
02/12/2013 20:09:24.018 mds: (Error) Volume: Could not find requested backup type:2 for volume
02/12/2013 20:09:34.048 com.apple.backupd: Backup failed with error: Not enough available disk space on the target volume.
02/12/2013 20:09:34.318 com.apple.backupd: Ejected Time Machine disk image.
02/12/2013 20:09:34.000 kernel: AFP_VFS afpfs_unmount: /Volumes/StudioX, flags 0, pid 1249
02/12/2013 20:09:34.000 kernel: ASP_TCP do_thread_read: no reqInfo found for reqID 8
02/12/2013 20:09:34.562 com.apple.backupd: Ejected Time Machine network volume.
02/12/2013 20:10:25.817 helpd: CarbonCore.framework, Our status with coreservicesd is unusual, 2, and things likely will stop working.
02/12/2013 20:10:25.817 helpd: CarbonCore.framework: Unable to connect to coreservicesd.  Things likely won't work.  Sorry.
02/12/2013 20:10:28.830 helpd: Could not find access page in directory /Applications/Switch.app/Contents/Resources/help
02/12/2013 20:10:28.840 helpd: Could not find access page in directory /Applications/Switch.app/Contents/Resources/help
02/12/2013 20:10:29.283 com.apple.backupd: Starting standard backup
02/12/2013 20:10:29.283 com.apple.backupd: Attempting to mount network destination URL: afp://tm@DiskStation.local/StudioX
02/12/2013 20:10:30.000 kernel: ASP_TCP CheckReqQueueSize: increasing req queue from 32 to 128 entries. so 0xffffff8013e628e0 
02/12/2013 20:10:33.796 com.apple.backupd: Mounted network destination at mountpoint: /Volumes/StudioX using URL: afp://tm@DiskStation.local/StudioX
02/12/2013 20:10:33.826 com.apple.backupd: Backup canceled.
02/12/2013 20:10:33.832 mds: ERROR: _MDSChannelInitForAFP: AFPSendSpotLightRPC failed -1
02/12/2013 20:10:34.000 kernel: AFP_VFS afpfs_mount: /Volumes/StudioX, pid 1269

 

[Markverhyden]

I've never run into something like that before. A few suggestions if you have not already looked at them.

1. Boot into recovery mode>disk utilities, and run Repair Disk and Repair Disk Permissions.

2. There is a Time Machine plist in the root Library. Rename to .old and reboot.

3. There is a CLI utility called tmdiagnose. Run that, via sudo, and see if there are any pointers in the log files.

What is interesting is the machine seeing 1.5 gb rather than 1.5 tb. Have you tried changing the size of the store a little bit?

 

[newton]

Thanks for the quick reply Mark, haven't tried all of those (didn't know about the TM diagnose mode). I think it is just something silly as there's no obvious problem I can see, so hopefully a resize or some more configuration troubleshooting on the Mac will do it. Is the last bit of quite a big job by my standards, just my luck!

 

[anonymous Mac Tech]

I really would recommend not using a user with "admin" anywhere in the name. Newer versions of OSX are finicky about that. With the volume size issue, it could be a corrupt directory structure issue on that volume where TM is getting incorrect volume size info. Just like Mark said, run Disk Utility to repair the volume and permissions. I'd try DiskWarrior on the volume as much it is a much more potent directory structure repair utility.

 

[newton]

Thanks AMT. Didn't know that about admin users, doesn't seem to have caused an issue in this case so far but I'll bear that in mind.

Got it fixed eventually - I noticed in the logs that TM kept trying to resize the sparsebundle and failing. Since there hadn't been a successful backup so far then I thought I'd try deleting it - TM created a new one and worked straight away.

Thanks again for the help guys.