Mountain Lion Compatibility

Has anyone got NFS or RSYNC working from ML to a ReadyNAS?

I have a ReadyNAS Pro 6 with firmware 4.2.21 and can't connect with either (share does not exist on server).

10.8 = No connection
10.7.4 = OK
10.6.8 = OK

@NerdyMike: I am able to connect from ML to a ReadyNAS running 4.2.21.

Do you have share restrictions setup?

What is the process you are using to connect? What error message do you receive?

@Chewbacca - I've tried connecting via the GUI (nfs://IP.Of.Netgear.ReadyNas) and via command line. I get the useless error of "can't find share" - but I'm not onsite for the specific wording right now.

Before my server upgrade from 10.6.8 to 10.8 it worked fine, after no nfs or rsync (I use a script that runs rsync and it fails with the same message).

I did have the share restricted to just the server IP (which I checked & double checked) and then I turned that off and "default read/write" access on.

I can see the share is published OK from the 10.8 server but can't access it via either. (other protocols like AFP are not turned on due to the old file name bug to do with direct RSync backups from HFS+ volumes...)

I can head back onsite for further testing if you want me to look into anything.

kolz wrote:
READYNAS REMOTE NO LONGER WORKS you connect.. it sees the shares, asks you to select which shares you want to mount, then the connecting to 5.x.x.x. dialog continues forever. The NAS shows up in Finder but non of the shares do and the connecting dialog still shows :( :oops: :oops:

Having the same problem with readynas remote here. Works fine on Lion based Macs. But not on a fresh out of the box mountain lion based mac. :x

Im also having massive problems since mountain lion, no Time machine and the NAS keeps disappearing from Shared devises in finder, this seem more often to happen when im trying to transfer files it disappears and kills the transfer. have performed a full reset of the Readynas and setup from scratch but still problems

I Hvae a ReadyNAS Duo V1 with latest firmware

Any ideas ?

I tried enabling Time Machine and also had some problems. Before I enabled it, I had 2 shares: "media" and "backup". After enabling it, visiting my machine in the Finder showed two folders "ReadyNAS" (the Time Machine account name), and "warren" (my account name). Neither of these could be opened. After later disabling Time Machine backups, my original shares came back.

On top of all this, my machine has locked up several times. First Chrome will lock up, then when I try to force quit the app, the entire system will freeze. I can't confirm that enabling Time Machine caused this, but I didn't see the behavior before doing so.

I'm running RAIDiator 4.1.9 [1.00a147] on an X6. My mac runs OS X 10.8 (12A269).

mmyfc.office wrote:

kolz wrote: READYNAS REMOTE NO LONGER WORKS you connect.. it sees the shares, asks you to select which shares you want to mount, then the connecting to 5.x.x.x. dialog continues forever. The NAS shows up in Finder but non of the shares do and the connecting dialog still shows :( :oops: :oops: Having the same problem with readynas remote here. Works fine on Lion based Macs. But not on a fresh out of the box mountain lion based mac. :x

+1, please fix.

Remote not working with ML is a known issue and will be addressed. No ETA on an update at this time.

OH NO!!! Brand new iMac and am dissapointed that my Readynas NV+ is not Mountain Lion not compatible. Does anyone have any idea how long it usually takes to get this type of compatibility issue resolved?

Still having problem with my ReadyNAS Duo and ML...

If I disable AFP under standard file protocols and directly re-enable it will work once:

Starting manual backup Attempting to mount network destination URL: afp://ReadyNAS@nasse.local/ReadyNAS Mounted network destination at mount point: /Volumes/ReadyNAS using URL: afp://ReadyNAS@nasse.local/ReadyNAS Disk image /Volumes/ReadyNAS/JockesMBP.sparsebundle mounted at: /Volumes/Time Machine Backups Backing up to: /Volumes/Time Machine Backups/Backups.backupdb Using file event preflight for Macintosh HD Will copy (752.2 MB) from Macintosh HD Found 23513 files (1.27 GB) needing backup 2.9 GB required (including padding), 312.82 GB available Copied 31698 files (1.02 GB) from volume Macintosh HD. Using file event preflight for Macintosh HD Will copy (122.1 MB) from Macintosh HD Found 993 files (122.1 MB) needing backup 1.53 GB required (including padding), 311.61 GB available Copied 2723 files (145.3 MB) from volume Macintosh HD. Created new backup: 2012-08-31-090343 Starting post-backup thinning No post-back up thinning needed: no expired backups exist Backup completed successfully. Ejected Time Machine disk image: /Volumes/ReadyNAS/JockesMBP.sparsebundle Ejected Time Machine network volume.

No problems there right? Well, next backup generates this:

Starting manual backup Backup failed with error: 19

Why can it work only once?? I have searched and searched but it seems like no one else has this problem after upgrading to ML. I have two different Mac's at home and both behaves the same after the upgrade...