NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
geggog
Jul 01, 2012Aspirant
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
- geggogAspirantAdmittedly I can't comment on 4.1.8 vs 4.1.9, as I never tried to set up this configuration on 4.1.8.
What I can tell you is that whenever I have active mounts on my ReadyNAS NV+ (as guest), Time Machine will fail. As soon as I unmount my guest AFP mounts, Time Machine starts working as you'd expect it to. - ReadyNASUserAspirantIf you have active mounts logged in as any other user than guest does timemachine work on 4.1.9?
- geggogAspirantI never really wanted to run the NAS is user mode, but the question does beg further investigation.
I'll try it out tonight when I get home from work. - mdgm-ntgrNETGEAR Employee RetiredShare Security mode is EOL and not available on any newer ReadyNAS models. Share mode doesn't work well with new OSes.
Take a look at How to Migrate to User Security Mode
What version of RAIDiator did you update from?
Note that it's possible that your issues could be related to the ownership issue introduced in 4.1.9. You may wish to downgrade to 4.1.8 or update to 4.1.10 beta, then fix the ownership via Shares > Share Listing > Sharename > CIFS, click on Advanced Options tab, set the user and group you want to own the share, click Set Permission for existing... and click Apply. I think this tab isn't available in Share mode so you would need to change to User mode to use it.
In 4.1.9 Netatalk (provides AFP service) was updated to Netatalk 2.2.3 which has improved compatibility with Mac OS X Lion. - geggogAspirantRightio, this is all good stuff to know. As it turns out, I'm due to receive my new Ultra 4 Plus in a few days, so I'll make sure to configure this to user mode and will report back with how I get on ... there's no real point in investing time into the NV+ when I'm just about to retire it.
I'll report back with how I get along. - mdgm-ntgrNETGEAR Employee Retired
geggog wrote: As it turns out, I'm due to receive my new Ultra 4 Plus in a few days, so I'll make sure to configure this to user mode and will report back with how I get on ...
With the Ultra 4 Plus, I suggest you put one disk in the NAS and do a factory default (wipes all data, settings, everything). I would suggest you update to 4.2.16 (http://www.readynas.com/RAIDiator_x86_4_2_16_Notes) if the unit comes with 4.2.15 or older firmware; then update to the latest firmware. After verifying the updates have been successful, then I'd suggest you power down, put the rest of the disks in and do a factory default (wipes all data, settings, everything) via the Boot Menu (http://www.readynas.com/kb/faq/boot/how_do_i_use_the_boot_menu) which will give you a clean setup on the latest firmware.
Do note that you can't migrate your array from the NV+ to the Ultra 4 Plus due to the different RAID format, so it's best to buy new disks from theHCL for your NAS. - geggogAspirant
mdgm wrote: With the Ultra 4 Plus, I suggest you put one disk in the NAS and do a factory default (wipes all data, settings, everything). I would suggest you update to 4.2.16 (http://www.readynas.com/RAIDiator_x86_4_2_16_Notes) if the unit comes with 4.2.15 or older firmware; then update to the latest firmware. After verifying the updates have been successful, then I'd suggest you power down, put the rest of the disks in and do a factory default (wipes all data, settings, everything) via the Boot Menu (http://www.readynas.com/kb/faq/boot/how_do_i_use_the_boot_menu) which will give you a clean setup on the latest firmware.
Do note that you can't migrate your array from the NV+ to the Ultra 4 Plus due to the different RAID format, so it's best to buy new disks from theHCL for your NAS.
Excellent, thanks for the above info, it's genuinely appreciated. Tell me, what's the rational for upgrading to 4.2.16 before going to the latest firmware? Why wouldn't I go directly to the latest stable release? Not that I'm overly fussed about going to the intermediate version, just curious as to why. - mdgm-ntgrNETGEAR Employee Retired4.2.16 added GPT support and is the most thoroughly tested firmware for updates from previous firmware which used MBR partitioning on the disks. On update from 4.2.15 or earlier to 4.2.16+ the partitioning of the disks is converted from MBR to GPT. An update to 4.2.21 direct should work, but with some older firmware (e.g. 4.2.19) a firmware update from firmware prior to 4.2.16 hanged. It doesn't hurt to update to 4.2.16 first then to the latest firmware.
- geggogAspirantFair enough... thanks again.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!