Mountain Lion Compatibility

Yes it would've been tested with Mountain Lion.

Having said that before updating to Mountain Lion it wouldn't hurt to do a backup of your system. That way if you find you don't like Mountain Lion yet you could go back Lion.

Mattebury, I'll give 4.1.10 a go with ML and let you know in this post...since I noticed this morning AFP dropped off-line again with ML 10.8.2. Good stuff Apple and Netgear...

eriddler wrote:
mdgm wrote: 4.1.8 is old firmware now. Please update to 4.1.10 (http://www.readynas.com/RAIDiator_4_1_10_Notes) and see if this helps. Yep old firmware, that works just fine with 10.8.2. Not inclined to switch to 4.1.10 unless I know there aren't issues with AFP reconnect or share ownership...thanks.

Still after upgrading to 4.1.10 AFP disappears and Time Machine cannot find NAS. So that problem is not solved on that firmware. If I want to connect to NAS via AFP have to reboot Mac. Still hoping that Netgear can solve this OS X problem.

4.1.10 and 10.8.2 didn't fix the NAS visibility over WiFi issue for me. It did fix a mounted NAS share unmounting on a fast user switch or move to the Login Window.

So far no issues with one Sleep reconnect to AFP. The iMac is connected via ethernet right now, I'll switch to Wifi later today to see how that works out.

System:
Mac Mini running 10.8.2 (previously running 10.7.x, this is an upgrade install of 10.8.x)
Mac Mini is configured to never sleep
ReadyNAS Pioneer Pro running RAIDiator 4.2.21
Single NFS export from ReadyNAS
Flat network through two Netgear 5 port switches (ie all wired, no WiFi)

NFS configured to auto mount using auto_fs with "-host" rule.

Prior to 10.8 this configuration was stable. After updating to 10.8 I get server disconnection errors from the Finder. Other times I get the NFS file operation wedging and never completing but sending iTunes into an unresponsive state. Force-quit of iTunes will immediately raise the server disconnection error.

The iTunes XML library is stored on the Mac Mini's local hard drive. Only the mp3 files are stored on NFS.

Rebooting will often have NFS operations time out. Rebooting with the "/net" line in /etc/auto_master commented out, followed by uncommenting that line and running "sudo automount -vc" to re-read the configuration will allow terminal access to /net/nasname/files to work. Finder access will then work briefly before this problem comes up again.

Does anyone have suggestions on how to fix this?

PS: I would prefer to avoid having to move this data over to an iSCSI volume on the ReadyNAS. But if that is the only way to get this working I can make that switch. (Edited to add this PS.)

mrichmon, sorry not smart enough for your issue. But did want to report that I've run the iMac on WiFi all day with a couple sleeps and haven't had issues with reconnects. AFP / Mac OS X 10.8.2 / ReadyNAS Duo 4.1.10

My ReadyNAS Duo's seem to be working on ML but when I used FrontView to try to update from 4.1.9 to 4.1.10 it doesn't find any update available.http://www.readynas.com/forum/posting.php?mode=reply&f=28&t=64805#

It should find the update. Try clearing your web browser cache (such as Temporary Internet Files in Internet Explorer), close your web browser then reopen Frontview

You can do a local update if you like: http://www.ReadyNAS.com/RAIDiator_4_1_10_Notes

My confidence with D-Link routers is still shaky. I found that turning on multicast messed up Duo visibility with my wife's MacBook Pro running Snow Leopard and didn't fix my iMac on Mountain Lion. I turned it back off and things were still not totally right. But after a restart or two of the router, both Macs have been successfully making and maintaining connections to the Duo for about a week. I was about to go all DD-WRT on the D-Link. I'll wait a while longer to see if things are stable.

Edit on 6 Oct: Another week and only one instance of failing to mount the Time Machine sparsebundle on the Duo. I'm not sure why it's stable but I'm not going to mess with it.