After days of searching and trying different "solutions" I still cannot get Time Machine to successfully back up to my server.  I recently switched from an connected esata drive.  I tried a drobo but found it worked just fine but was extremely slow.  I have a 2008 Mac Pro running Mavericks with 7.5TB of data on it and it was going to take 2 weeks + to back up which is unacceptable if i have have a hard drive fail in my raid array. When i first got the free version of unraid running as a test the backup started fine.  I decided since it was working to upgrade to the plus.  Here is where it quit.  I bought the license on a sunday evening and wend to bed while i waited for my key to be emailed to me.  When i woke up the next morning time machine had failed after 400GB.  I decided it would be a good point to upgrade the key and add more drives so i could do a complete backup.  I now get messages that says time machine couldn't back up to "Time Machine" and when I click on details the failure message says "The backup dis image "/Volumes?Time Machine-2> Mac Pro.sparesbundle" could not be access (error (null))"Anyone got any help for someone who knows very little about computer programing?

I had a similar problem using version 5. Version 6 has been working well for the last month. I skipped versions b7 and b8.

 

/Volumes?Time Machine-2> Mac Pro.sparesbundle

 

Why is there a ? after /Volumes? Keep the name alpha-numeric (- and _ are ok) to avoid name issues.

I have similar issues with unRIAD 6.0-beta10a.

 

After the upgrade from beta10 --> beta10a followed by the required reboot my Mac transferred approx. 350GB of data and stopped then. TM was asking me to start over again in order to improve the reliability of the backup.

 

My wife's Mac was doing fine and transferred 40GB without any hassle.

 

We both are running Mac OSX 10.9.5. and the dedicated TM shares are both on one single disk /mnt/disk1/ with exactly the same settings. Only difference is the amount of data....

 

At the same time when unRAID brought these errors:

Sep 30 16:52:32 Tower cnid_metad[5573]: set_dbdir: mkdir failed for /mnt/user/TMO/.AppleDB/
Sep 30 16:52:32 Tower afpd[18673]: read: Connection reset by peer
Sep 30 17:17:39 Tower afpd[23390]: transmit: Request to dbd daemon (volume TMO) timed out.
Sep 30 17:21:11 Tower afpd[23390]: transmit: Request to dbd daemon (volume TMO) timed out.

 

...my Mac was showing this:

30.09.14 16:52:28,751 xpcd[165]: Info.plist does not contain an XPCService dictionary: /System/Library/Frameworks/Security.framework/XPCServices/SecurityAgent.xpc
30.09.14 16:52:31,000 kernel[0]: ASP_TCP CheckReqQueueSize: increasing req queue from 32 to 128 entries. so 0xffffff803be50a08 
30.09.14 16:52:35,270 xpcd[25]: Info.plist does not contain an XPCService dictionary: /System/Library/Frameworks/Security.framework/XPCServices/SecurityAgent.xpc
30.09.14 16:52:35,280 UserEventAgent[11]: com.apple.backupd-auto launchd job disabled
30.09.14 16:52:43,000 kernel[0]: outputPacket: data connection is closed, dropping packetDropping packet
30.09.14 17:17:33,293 xpcd[165]: Info.plist does not contain an XPCService dictionary: /System/Library/Frameworks/Security.framework/XPCServices/SecurityAgent.xpc
30.09.14 17:17:46,197 DashboardClient[7736]: CGSGetWindowBounds
30.09.14 17:18:36,248 quicklookd[10170]: Warning: Cache image returned by the server has size range covering all valid image sizes. Binding: VariantBinding [0x1003] flags: 0x8 binding: BundleBinding [0xf03] URL: file:///Library/PreferencePanes/Flash%20Player.prefPane bundle identifier: (null) request size:256 scale: 1
30.09.14 17:22:40,962 xpcd[165]: Info.plist does not contain an XPCService dictionary: /System/Library/Frameworks/Security.framework/XPCServices/SecurityAgent.xpc
30.09.14 17:22:41,001 syncdefaultsd[10364]: *** -[iADomainCache init]: IA domains cache couldn't be read.
30.09.14 17:22:41,001 syncdefaultsd[10364]: -[iAPluginManager allAListPlugins] [546] -- *** warning: we're on the slow path.

The TM backup was again breaking up this night - please see the pic1 of the error message that I received (apologize, it's in german - it's saying that I have to restart with a new backup in order to increase the reliability).

 

I removed the share and defined it completely new. Please see pic2 - this is all according to what I read here. TM backup is running now but I doubt that the steps I took will yield success. Error messages are coming up again:

Oct 1 09:52:43 Tower afpd[17725]: transmit: Request to dbd daemon (volume TMO) timed out.
Oct 1 10:01:05 Tower afpd[17725]: transmit: Request to dbd daemon (volume TMO) timed out.
Oct 1 10:01:05 Tower afpd[17725]: afp_createfile("29b"): CNID error

Any idea/guidance?

Try reiserfsck check. See check disk fileesystems in my sig.

I was able to back up two mac mini servers to UNRAID utilizing two TM shares, each with their own share, without issue. The difference I had was the TM was open (connected as guest) and I used a cache drive. (6.0 beta10a)

This is a XFS drive, so Reiserfsck is not available. However, I don't see why a file system check would be n eeded. I completely define a new share and still:

Oct 2 21:05:11 Tower afpd[10709]: transmit: Request to dbd daemon (volume TMO) timed out.
Oct 2 21:08:44 Tower afpd[10709]: transmit: Request to dbd daemon (volume TMO) timed out.
Oct 2 21:26:17 Tower afpd[10709]: transmit: Request to dbd daemon (volume TMO) timed out.
Oct 2 21:39:26 Tower afpd[10709]: transmit: Request to dbd daemon (volume TMO) timed out.
Oct 2 22:04:02 Tower sshd[15933]: Accepted password for root from 192.168.178.30 port 50632 ssh2
Oct 2 22:04:33 Tower sshd[15933]: Received disconnect from 192.168.178.30: 11: disconnected by user
Oct 2 22:07:38 Tower afpd[10709]: transmit: Request to dbd daemon (volume TMO) timed out.
Oct 2 22:07:38 Tower afpd[10709]: afp_createfile("2737"): CNID error
Oct 2 22:10:33 Tower afpd[10709]: transmit: Request to dbd daemon (volume TMO) timed out.

Jbartlett, you’ve got Time Machine running stably on v6b10a with a cache drive? I haven’t had a single error since updating to b10a but I had read previously not to use a cache for TM. If that works now too, that would be awesome, since my only complaint would be speed to the array.

 

EdgarWallace, maybe this would help? https://discussions.apple.com/thread/6214730

Thanks a lot barakthecat. I immediately executed the steps that were explained in your link. All the

07.10.14 18:01:37,465 xpcd[162]: Info.plist does not contain an XPCService dictionary: /System/Library/Frameworks/Security.framework/XPCServices/SecurityAgent.xpc

spam is now gone....let's see if this is having an impact on my Time Machine issues.

 

Anyhow, I have decided to do a new install as soon as Yosemite will go public instead of migrating the OS.

 

Use xfs_repair to check the disk,

This is what I see:

root@Tower:~# xfs_repair -n /dev/sdj
Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!

attempting to find secondary superblock...
...

 

This is my second try. It will run forever now; I have stopped it. I do believe that this isn't any good?