NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RAIDiator 4.1.9 (sparc) Time Machine Failing to Find Disk?
Whey hey!
I've recently updated my NV+ to RAIDiator 4.1.9 which gave me the ability to mount via AFP from the command line in OSX Lion - brilliant, I've been wanting this ability for some time now.
One thing I did notice after installing the new firmware is that Time Machine has now stopped working. This is quite odd, as it's been working under 4.1.8 forever and a day without any hiccups whatsoever. Now when I attempt to run a Time Machine backup I'm told that "Time Machine could not complete the backup. The backup disk is not available", even though I have numerous shares mounted from the ReadyNAS.
In addition to this, the NV+ can be selected with clicking "Use Disk", successfully passes authentication, then falls over with the same error again. Anyone else experiencing this? Any suggestions would be much appreciated.
Cheers,
G
I've recently updated my NV+ to RAIDiator 4.1.9 which gave me the ability to mount via AFP from the command line in OSX Lion - brilliant, I've been wanting this ability for some time now.
One thing I did notice after installing the new firmware is that Time Machine has now stopped working. This is quite odd, as it's been working under 4.1.8 forever and a day without any hiccups whatsoever. Now when I attempt to run a Time Machine backup I'm told that "Time Machine could not complete the backup. The backup disk is not available", even though I have numerous shares mounted from the ReadyNAS.
In addition to this, the NV+ can be selected with clicking "Use Disk", successfully passes authentication, then falls over with the same error again. Anyone else experiencing this? Any suggestions would be much appreciated.
Cheers,
G
19 Replies
Replies have been turned off for this discussion
- The plot thickens: As it turns out, if I unmount my guest mounts to the ReadyNAS Time Machine works just fine and dandy. It'd appear as though TIme Machine doesn't like AFP mounts to the device existing with a different username to that which Time Machine itself is using ("ReadyNAS" in this case) ... bummer.
- Is there anyway I can get TimeMachine to mount the NAS with a user other than ReadyNAS (FrontView doesn't allow entry of a different username)? Hrmmmmm ...
- I had Time Machine working great with 4.1.8 for a long time.
Upgraded to 4.1.9 yesterday. Now Time Machine broken.
ARGGHHH! - As it turns out, I ended up just using CIFS/SMB for the filsystem mounts and AFP for Time Machine. Less than I deal I know, as AFP is certainly faster, but this was the best overall solution I could find without tripping up over permissions issues.
- When will this be fixed? Have avery upset wife/daughter whose macs used to back up just fine and now cannot.
Am I doing something wrong or is this a known problem with the AFP supprot introduced in 4.1.9? garethj wrote: When will this be fixed? Have avery upset wife/daughter whose macs used to back up just fine and now cannot.
Am I doing something wrong or is this a known problem with the AFP supprot introduced in 4.1.9?
I suggest doing what I've been doing ... mount your shares over CIFS/SMB and leave Time Machine to have exclusive use of AFP. This way you wont get into the multi-user-tangle.
G- I'd suggest you open a tech support case at my.netgear.com and post your case number.
Or if you are willing to try 4.1.10 beta: http://www.readynas.com/forum/viewtopic.php?f=17&t=59222 post a thread in the beta forum if you still have the issue. - Is this a general problem with TimeMachine not working if other volumes are mounted via AFP - or is it something specific this user is doing? Would like to avoid the CIFS/SMB work around and wait for the fix in 4.1.10?
Odd that only one person has reported the problem... - I'm happy to be corrected, but I believe this is more a generic problem on the OSX side of the fence. It's my understanding that OSX won't allow multiple shares on a single device to be mapped with different usernames.
In saying that, if the ReadyNAS allowed you to specify what user you were connecting to Time Machine as (instead of forcing ReadyNAS) then this problem wouldn't exist ... - A little confused... it worked in Radiator 4.1.8 - i.e. mapping multiple drives at the same time with different user names (time machine and "normal user") and now it doesn't work in 4.1.9... no change on OSX version... what am I missing?
I came to this thread because the release notes say there have been changes in AFP functionality in 4.1.9 cf 4.1.8... and trying to understand what those changes are and whether they have anything to do with the problem you're experiencing (in which case I won't upgrade)
Thoughts?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
