Time Machine using OSX Mavericks

mdgm wrote:
Dave, if you try 4.1.13 RC1 does that help?

Just installed it and after a power off reboot of both the ReadyNAS and MacBook I am now fully connected and "Preparing Backup..." :)

Update: The backup completed successfully and I was then able to delete a file out of my Downloads folder and recover it from the Time Machine backup so all seems well with the 4.1.13 RC1 for me...

I just get the "There was a problem while connecting to server "ReadyNAS". The server may not exist or is currently unavailable moment. Check the server name or IP address and your network connection and try again"

This is the same problem that I get... does anyone have a way to troubleshoot this, or a fix?

g262 have you updated to 5.3.10 beta?: http://www.readynas.com/forum/viewtopic.php?f=148&t=72267

O.K. just to help make it clear let's list the firmware that addresses Time Machine Support on Mavericks:

ReadyNAS OS: 6.1.4 or later. If you are running older firmware you should be automatically prompted to update when you next open the Dashboard.
RAIDiator-x86: 4.2.25 or later: http://www.readynas.com/forum/viewtopic.php?f=1&t=74129
RAIDiator-arm: 5.3.10 beta or later: http://www.readynas.com/forum/viewtopic.php?f=148&t=72267
RAIDiator (Sparc): 4.1.13 or later: http://www.readynas.com/forum/viewtopic.php?f=1&t=74130

Thanks now it is running in Mavericks and on other machines in the network
i hate to write this
but Netgear have a messy old site and forum-software
Allright you know the pages and the site Yourself but

make it structured please

Svendus

I received the following error after updating to RAIDiator 5.3.10-T3, when trying to access the time machine settings in Dashboard.
7061010006
Code: 7061010006

As a follow up: after the install it would not complete booting and it would not respond to the power button, It said booting.... installing add-on. Had to unplug and force a restart. After a successful reboot I had the above error. I also could not access my previous shares.

I down graded to 5.3.9 as I thought my problem was with the beta. Had the same boot problems and still can not access my shares. below is the log from the NAS

Mon Nov 4 05:46:28 EST 2013 System is up.
Mon Nov 4 05:46:25 EST 2013 The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume.

media
Scotts_Data
backup
Kirstens_Data

Mon Nov 4 05:45:31 EST 2013 Your ReadyNAS device has been updated with a new firmware image. (5.3.9)
Mon Nov 4 05:45:24 EST 2013 Volume scan failed to run properly.
Sun Nov 3 06:26:25 EST 2013 314: ERROR: mysql failed while loading RNP2DB-V25.sql.
Sun Nov 3 06:26:12 EST 2013 Volume scan failed to run properly.
Sat Nov 2 21:14:08 EDT 2013 System is up.
Sat Nov 2 21:14:06 EDT 2013 The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume.

media
Scotts_Data
backup
Kirstens_Data

Sat Nov 2 21:13:19 EDT 2013 Volume scan failed to run properly.
Sat Nov 2 19:54:28 EDT 2013 Detected increasing uncorrectable errors[865] on disk 3 [WDC WD20EARX-00PASB0, WD-WCAZA8334391]. This often indicates an impending failure. Please be prepared to replace this disk to maintain data redundancy.
Sat Nov 2 19:50:42 EDT 2013 Reallocated sector count has increased in the last day.

Any help would be appreciated. How can I get the unit to do a volume scan now that it is up?

Skywalker wrote:
This sounds to me like a Bonjour issue. You're running 4.1.13-RC1, right? Can you load up Bonjour Browser and check if there are two AFP service advertisements for the ReadyNAS -- one using just the hostname, the other with "(AFP)" appended?

yes, I just updated to 4.1.13-RC1 trying to solve this problem a few days ago.

I only have it once under AFP. i attached a screenshot of the bonjour browser that shows where else it's show up as well.

Well I guess I spoke too soon.
After upgrading my NV+ (v1) firmware to 4.1.13 RC1, I was able to connect from my Mavericks machine and start the Time Machine backup. However I haven't been able to get the backup to complete yet. It will say "Backing up X of X GB" for a while, then switch to "Waiting to Complete First Backup", and this message remains permanently. The machine will periodically try to complete a backup, but a "backup failed' message will pop up in the notifications area.

I used the Dashboard widget "Time Machine Buddy" to get this log:

Property list invalid for format: 200 (property lists cannot contain NULL)
Property list invalid for format: 200 (property lists cannot contain NULL)
Property list invalid for format: 200 (property lists cannot contain NULL)
Property list invalid for format: 200 (property lists cannot contain NULL)
Property list invalid for format: 200 (property lists cannot contain NULL)
Property list invalid for format: 200 (property lists cannot contain NULL)
Property list invalid for format: 200 (property lists cannot contain NULL)
Starting manual backup
Attempting to mount network destination URL: afp://ReadyNAS@boxy._afpovertcp._tcp.local/ReadyNAS
Mounted network destination at mount point: /Volumes/ReadyNAS using URL: afp://ReadyNAS@boxy._afpovertcp._tcp.local/ReadyNAS
Creating disk image /Volumes/ReadyNAS/CTD-MBP.sparsebundle
Failed to hide extension on /Volumes/ReadyNAS/CTD-MBP.sparsebundle, error: Error Domain=NSCocoaErrorDomain Code=4 "The file “CTD-MBP.sparsebundle” doesn’t exist." UserInfo=0x7fac69e0b610 {NSURL=file:///Volumes/ReadyNAS/CTD-MBP.sparsebundle/, NSFilePath=/Volumes/ReadyNAS/CTD-MBP.sparsebundle, NSUnderlyingError=0x7fac69e0c230 "The operation couldn’t be completed. No such file or directory"}.
Disk image /Volumes/ReadyNAS/CTD-MBP.sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to /dev/disk2s2: /Volumes/Time Machine Backups/Backups.backupdb
Ownership is disabled on the backup destination volume.  Enabling.
Forcing deep traversal on source: "Macintosh HD" (device: /dev/disk0s2 mount: '/' fsUUID: 56AAB96C-1D3D-341E-8EB8-D9FA032D35B4 eventDBUUID: 7CAC1349-6F85-46EC-9A3A-643DBD1824FE)
Total content size: 169.46 GB excluded items size: 107.96 GB for volume Macintosh HD
Found 748090 files (61.49 GB) needing backup
73.79 GB required (including padding), 114.85 GB available
Waiting for index to be ready (100)
Copied 65952 items (4 GB) from volume Macintosh HD. Linked 0.
Error writing to backup log.  NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Not a directory
Error writing to backup log.  NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Input/output error
Backup canceled.
[SnapshotUtilities mountPointForVolumeRef] FSGetVolumeInfo returned: -35
Failed to eject volume (null) (FSVolumeRefNum: -108; status: -35; dissenting pid: -1)
Failed to eject Time Machine disk image: /Volumes/ReadyNAS/CTD-MBP.sparsebundle

Is anyone else seeing this behavior? Thanks!

vrspectre wrote:
I only have it once under AFP. i attached a screenshot of the bonjour browser that shows where else it's show up as well.

So the _adisk record (for TimeMachine) isn't even showing up. Can you make sure you have TimeMachine support enabled? If so, maybe try disabling it and then re-enabling it.

Skywalker wrote:
So the _adisk record (for TimeMachine) isn't even showing up. Can you make sure you have TimeMachine support enabled? If so, maybe try disabling it and then re-enabling it.

Ahhhhh... Thanks for this suggestion. I had installed 4.1.13 RC1 and my Mac Mini running Mavericks still couldn't find my Duo Time Machine. After disabling Time Machine support in Frontview and re-enabling it, the mac found the ReadyNAS. Now it is happily backing up to the ReadyNAS Duo.

BTW, thank you, thank you, thank you for continuing to support the Sparc-based Duo. I just upgraded it to a pair of 2TB WD Red disks and I expect to keep using it for a long time. It's still doing a great job.