Mountain Lion Compatibility

[mdgm]

Upgraded to ML and Time Machine no longer works for Ready NAS NV v2.

Please open a support case.

I haven't upgraded to ML yet, but I understand that if you right click on an app icon and use the 'open with' command, there is an option to authorise an 'unauthorised' app to run - you only need to do this once.

Yes. This trick works well.

[dgerson76]

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

SAME ISSUE. Can someone please help?

Macbook air/ML.
Ultra2+ with latest firmware and latest Remote software.

Shares eventually mount but can't see anything past the 1st level of folders.

This was working perfect prior to last firmware and readynas remote software.

HELP!

[sircoolio]

I'm having an issue accessing the WebDAV service on my ReadyNAS Pro, which is running the latest production firmware, from a Mountain Lion machine. Accessing the ReadyNAS WebDAV share on Lion and Snow Leopard works great, but the machine running ML fails to connect. I can ping the webdav server from the ML machine, but not connect via WebDAV. I can also access the ReadyNAS shares from AFP without an issue (in my limited testing). I've been scouring console for the error, but can't seem to find the failure.

Reading up on the issue on the Apple Support forums, it appears Apple made a change that requires a server (e.g. ReadyNAS) change? https://discussions.apple.com/thread/41 ... 0&tstart=0

Anyone else having this problem?

[sphardy]

sircoolio - this is not necessarily a Server change that needs to be implemented, but a client change.

The ReadyNAS issues a self-signed certificate to enable SSL support (i.e. the "S" in "HTTPS", and self-signed as those do not cost you anything)

Web browsers always warn you before accessing services over HTTPS where the certificate is self-signed and allow you to set the certificate as trusted to avoid future warnings. Finder doesn't have such a feature and has previously always defaulted to trusting the certificate. It appears that security hole has been closed in ML by now defaulting to not trusting self-signed certificates. But as there is no mechanism to ask to trust the certificate built into Finder you must therefore you must use the KeyChain app on your client to first trust the certificate - once done Finder should connect as before

The alternative is to make a server change and buy & install a certificate from a trusted authority (eg Comodo, verisign etc) - you can read how here: http://url.sphardy.com/Romarm

I've just tested connecting to my NAS with trusted certificate installed over HTTPS from Finder on my ML MacBook - works just fine as shown below:

[GJSchaller]

I ran into an issue with mine, and the initial steps (Enabling AFP) didn't seem to work for me. Then again, my NAS hung in the middle of a backup, which may have corrupted something... in either case, here's the steps I took to fix the issue, and it seems to be backing up now.

1) Follow the steps here, to delete any old backups: viewtopic.php?f=71&t=60831

2) While there, also delete the .AppleDB and .AppleDouble folders (from SSH, do a "rm -rf .AppleDB" and "rm -rf .AppleDouble" command)

When you are done, the only files in the /c/.timemachine directory (or the home folder you've designated as your backup) should be:

.AppleVolumes
.com.apple.timemachine.supported

Once I did this, my TimeMachine backup ran without issues.

[Josc73]

Strange, when I check my /c/.timemachine directory I haven't got .AppleVolumes or .com.apple.timemachine.supported? What will happen if it is empty?

/Joakim

[GJSchaller]

Remember that files beginning with a . are hidden - they should be there, or the Time Machine functionality won't work!

Depending on how you're accessing the folder, you may need to enable the view of hidden files, and or do a "ls .*" to see them.

[Josc73]

Ah, thanks Geoffrey! Soory, I'm a bit of a noob when it comes to command prompt administration....

I have tried to do a completly fresh backup and then yet another one a couple of minutes later, but I still have the same problem: The first one runs, the second on gets the error "The backup disk is not available". If I then turn off AFP on my ReadyNAS and then turn it on AND connect to the Time Machine-share on the ReadyNAS I am able to connect again and TM runs flawless. Why?

/Joakim

[GJSchaller]

That one is beyond me... I haven't had any issues since I cleared those files. Sorry. :-/

[mdgm]

What version of RAIDiator are you running Josc73?

[Josc73]

I have upgraded to 4.1.10-T3 in an attempt to fix the issue. But, it didn't....

[ipaul81]

After upgrading to Mountain Lion I can no longer Search for my files through Spotlight. Is anyone else having this issue? Was working fine in SL and Lion for me even though initially there were some problems when Lion first came out. I have a ReadyNas Ultra 2 Plus running 4.2.21

[ipaul81]

After upgrading to Mountain Lion I can no longer Search for my files through Spotlight. Is anyone else having this issue? Was working fine in SL and Lion for me even though initially there were some problems when Lion first came out. I have a ReadyNas Ultra 2 Plus running 4.2.21

Tried again this morning and now it works. Weird. I haven't changed any setting so not sure what fixed it.

[Sylvia]

OK well after a great run with Lion, it appears Mountain Lion has broken my .timemachine
I have 2 mac's that used to work fine but now, no go.
Pro6

Is this a reported "Known" issue?

[DavidB]

Spotlight "not working" at first may have been because it was busy rebuilding indices?
Anyway, I have my own issue:

I installed ML and then tried to access the NAS (a v1 NV+) only to be told by ML that the fileserver was not supported. Realised I hadn't updated RAIDiator in a while, and updated to 4.1.9. Success! At first glance everything works fine, but I have been getting some hard-to-debug lockups lately.

For instance I'll be copying batches of movie files from local disk to the NAS using Finder. Once I get up to 3 or 4 concurrent copies something will go crazy, and Finder will lock up with the spinning wheel. Leaving the machines to sort themselves out had no effect. First time this happened I ended up rebooting (via hard reset) the ML machine.
BTW this is a MacBook Pro connected by gigabit to the same Airport Extreme as the NV+. In case it's relevant, both machines have auto-negotiated Ethernet frame sizes (to 1500 bytes).

Then yesterday I was using Quicktime Player to convert some AVIs on the NAS to m4v files on local disk (for transfer to an iPad). In Snow Leopard I could queue up multiple files and it would do them in turn. In Mountain Lion it does them in parallel. I had two runnning and the machine was quite busy, but I went on to start more so I could walk away from the machine for a while. I started the third conversion and guess what happened? The spinning wheel, and Quicktime Player was no longer responding. Finder was a bit iffy too (at least one window was referencing the folder on the NAS).
Sighing, I started shutting down other apps so I could restart the machine. And then instead I decided to unplug the gigabit (also turned Airport off so it wouldn't fail over to it). Came back a while later and the NAS was unmounted, Quicktime Player was gone, and the machine was behaving normally. Reconnected the cable, remounted the NAS, and did AVI conversions one by one with no problems (although I didn't get them all finished by the end of the day as I had hoped to).

So, it smells like the NAS is failing with too many concurrent connections under load. Note that this setup has worked fine previously, and this machine (primarily being a photography workstation) regularly transfers huge amounts of data around during backups without missing a beat. This failure is new behaviour: the recent changes being a fresh ML install and a RAIDiator update. Recent backups (across various USB and Firewire disks) that don't touch the NAS have been fine (literally terabytes of data have been transferred in recent weeks due to disk reorganisations).

I'm setting up some more tests to try to isolate the issue (including testing concurrent access from another machine), but it's hard to get any detail when it locks up and it's obviously very disruptive to my work. Has anyone else seen similar issues?