Mountain Lion Compatibility

Oh, just found another thing: Printer is not working either... Lost connection it says. I can print from a windows box though... :S

hundleton1 wrote:
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 ?

Sounds a lot like my problems as well. To me it seems that AFP is not working correctly or Apple changed a whole lot in AFP when ML was released.... Either way, I was hoping for some information on when Netgear will release an update that takes care of the problems...

I don't think much has changed in ML in regards to AFP. Lion changed a fair bit. Have you tried opening a support case?

As for the service disappearing from Finder this sounds like a Bonjour issue which doesn't appear to be specific to ML. Having said that I've heard of there being wireless issues (at least with 10.8.0). Is your Mac connected to your network via ethernet or wireless? If wireless can you see if you still get the issue if still connected via ethernet?

Interesting... I cannot connect via NFS if I'm logged into ML as "root" but **CAN** if I'm logged in as another user.

This is extremely frustrating!!!

For a small company with several MACS - we started by upgrading ONE machine to Mountain Lion - This is the boss' machine!!! This machine can no longer connect to the NAS!!
I upgraded RAIDiator to the latest version. No change
He can see the NAS but he cannot connect.

What can I do??? This is important!!
I verified all of the certificates that were in the keychain - heck, I put them ALL to always authorize because I could not see which one was for the NAS, that didn't change anything (I put all the certificats back to what they were)

Maybe I need a netgear certificat??

Any help would be greatly appreciated!!!!
please .... help!!

ReadyNAS NV+ v1
Micrologiciel: RAIDiator 4.1.9 [1.00a043]

Why would you upgrade the machine your boss uses first?

What happens when your boss tries to connect exactly? Do you get an error message? Do you see the list of AFP shares on the NAS (assuming you are connecting via AFP).

Also I don't recommend 4.1.9 due to an ownership issue. I would have suggested sticking with 4.1.8

I've read this entire thread, along with the other TM specific ones, and I'm still trying to figure out whether the ReadyNAS is ML-compatible or not. So I figured I would give it a shot myself. Before I continue, let me just say that the ReadyNAS is just a backup box to me. All I care about is TM, ReadyDLNA, and rsync (which is not from the Macs). TM worked for me on the combination of 4.1.8 and Lion/Snow Leopard. I have a Sparc NV and two Macs - one is a laptop connecting via wireless and the other communicates to the ReadyNAS via a gigE switch. I figured this was a pretty good combo for testing, so I updated both of the Macs to ML (I have not upgraded to 10.8.1 yet). I upgraded the ReadyNAS to 4.1.9 and factory defaulted it because that's how I roll. ReadyDLNA and rsync worked fine, so let's specifically talk about TM. Maybe I should have posted this is the TM sub-forum but this seems to be the ML thread that's getting the most attention. Anyway, I specifically did not upgrade to the 4.1.10 T3 beta because I don't share out the backup or media shares with CIFS or AFP. I do know that AFP is used for TM, but that share is specifically designed for that purpose and I suspected that it does not have the ownership issues that are fixed by the beta. So this is what I found...

First of all, my laptop on wireless was immediately able to find the ReadyNAS as a TM destination. However, I couldn't actually select it as a backup destination without getting the errors described in this link -> http://www.trollop.org/2012/07/12/os-x-10-8-mountain-lion-time-machine-netatalk/. I was able to fix this, as other folks suggested, by checking the box that advertises AFP with Bonjour. I never had to do that with TM on SL or Lion. But after that I was able to get a full backup of the laptop, along with several incremental ones, and was able to go into the backups and restore some test files. So far, so good.

But the wired machine on the switch couldn't even see the ReadyNAS as a backup destination. That was actually the one I tried first because I thought it would be easier. Even after the laptop was working, no wired success. But then I remembered that the laptop just uses the built-in firewall (which is set to block everything except essential services - Bonjour is considered by Apple to be essential) and that I use a custom IPFW script for the wired machine because I use it as a server. I went back to the wired machine and stopped IPFW, and then I could see the ReadyNAS. I didn't go through the motions to set it all the way up but I'm confident it would work. I know most people aren't firewalling ports the old-school way like me - the only reason I mention it is because my custom setup permits inbound Bonjour, so it must take more than just Bonjour to make TM work. I think that's an ML change because TM on Lion worked fine with my firewall settings. Maybe after you discover/set up the backup destination Bonjour can take it from there, whether you mounted it manually or not. But I want to make sure this works properly without having to mess around with it. I've never had the issues that some have had with sparsebundle corruption, and I'm hoping to keep it that way. I saw some SSDP packets in the mix, and I tried permitting both Bonjour and SSDP but that didn't seem to help. I'll update this post if I get a chance to do some more packet captures.

So here's what I recommend for success with TM on Mountain Lion and a Sparc ReadyNAS: upgrade the ReadyNAS to 4.1.9 or better as needed, advertise AFP with Bonjour, and make sure your network gear in the middle is not interfering with the connectivity required to discover the ReadyNAS and mount the TM share. I would always recommend directly connecting the ReadyNAS to the Mac to temporarily take the network out of the equation. One other thing, I know this post is way too long but I did come across the tmdiagnose command, which looks like it's made for gathering TM issues for a support case with Apple. But perhaps someone here might get some use out of it. Do a man tmdiagnose for more details.

RAIDiator 4.1.8 should work with ML too. I'd go with 4.1.8 or 4.1.10-T3 on Sparc ReadyNAS due to the ownership issue on 4.1.9. 4.1.10-T3 would work better with Lion/ML due to an update to the AFP/Time Machine service, but 4.1.8 should still work.

I've got a Sparc Duo and I recently updated from Snow Leopard to Mountain Lion. The Duo was on 4.1.9. I didn't have any trouble with Time Machine. I have run into an issue with mounted shares unmounting when going to the Login Window or fast user switching to another user. I updated the Duo to 4.1.10-T3 and this still happens. I've seen some discussion about this type of issue in the Apple Support forums (https://discussions.apple.com/thread/4144656?start=0&tstart=0). The unmount is immediate. The Console has these entries:

9/8/12 9:47:01.000 PM kernel[0]: AFP_VFS afpfs_unmount: /Volumes/media, flags 0, pid 82705
9/8/12 9:47:01.000 PM kernel[0]: AFP_VFS afpfs_unmount : We are the last mnt/sbmnt using volume /Volumes/media 0xffffff807b01b008
9/8/12 9:47:01.000 PM kernel[0]: AFP_VFS afpfs_unmount : We are the last volume using socket /Volumes/media 0xffffff807b01b008
9/8/12 9:47:01.000 PM kernel[0]: AFP_VFS afpfs_unmount : afpfs_DoReconnect sent signal for unmount to proceed

Could be a ML bug. The Time Machine share does not unmount when going to the Login Window.

Well, the Login Window/user switch unmount behavior is pretty consistent. Interestingly, sleeping (without going to the Login Window) does result in a reconnection to the share after a couple of failed attempts:

9/9/12 5:29:37.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect started /Volumes/media prevTrigger 0 currTrigger 1
9/9/12 5:29:37.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/media
9/9/12 5:29:37.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: posting to KEA EINPROGRESS for /Volumes/media
9/9/12 5:29:37.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/media
9/9/12 5:29:37.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/media
9/9/12 5:29:37.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/media failed 49.
9/9/12 5:29:37.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/9/12 5:29:38.303 PM com.apple.backupd-helper[85431]: Not starting Time Machine backup after wake - less than 60 minutes since last backup completed.
9/9/12 5:29:38.478 PM ntpd[84088]: ntpd exiting on signal 1
9/9/12 5:29:38.566 PM configd[17]: network changed: v4(en0-:192.168.0.2) DNS- Proxy- SMB-
9/9/12 5:29:38.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/media
9/9/12 5:29:38.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/media failed 65.
9/9/12 5:29:38.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 2 seconds and then try again
9/9/12 5:29:38.967 PM configd[17]: network changed: v4(en0+:192.168.0.2) DNS+ Proxy+ SMB+
9/9/12 5:29:38.511 PM KernelEventAgent[63]: tid 00000000 received event(s) VQ_NOTRESP (1)
9/9/12 5:29:39.250 PM KernelEventAgent[63]: tid 00000000 type 'afpfs', mounted on '/Volumes/media', from '//[xxxx@yyyy]_afpovertcp._tcp.local/media', not responding
9/9/12 5:29:40.999 PM KernelEventAgent[63]: tid 00000000 found 1 filesystem(s) with problem(s)
9/9/12 5:29:40.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/media
9/9/12 5:29:40.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 8 /Volumes/media
9/9/12 5:29:41.865 PM KernelEventAgent[63]: tid 00000000 received event(s) VQ_NOTRESP (1)
9/9/12 5:29:41.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/media
9/9/12 5:29:41.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: get the reconnect token

It's interesting that the wired Ethernet connection seems to go down then back up while resuming from sleep. FWIW, I did a clean ML install and brought my files and stuff over via Migration Assistant as that seemed to be the common advice for updating from Snow Leopard to Lion.