NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
RN104 not accessible anymore from MacBook Pro OS Ventura 13.4.1
Hi everyone, in march 2023 I bought the new Mac Book Pro 14" M2 with OS Ventura installed. For the first month everything worked fine with my ReadyNas 104. It was reachable both from browser and as a network share. I suppose that last update to 13.4.1 has changed something. As an absurd fact I can reach it remotely, but not on local network, it says that my Mac is not on the same LAN, but that's not true. Any other device (iPhones iPads, Samsung Tv, other Macs) still works fine with NAS Thanks for answering Pale77
Time Machine won't delete old backups automatically as it should on ReadyNAS 626 with firmwar 6.10.8
Haven't had much luck with this RN626 ReadyNAS since I purchased it a couple of years ago for the following tasks: • to run six surveillance cameras, • and back up six Macs in the household with Time Machine. Three months in, Netgear removed Milestone Arcus—causing me to have to buy another Mac to run the cameras. And Time Machine has never been able to delete old backups to free up allocated space as it should. I've tried several ways to increase the sparse bundles, but nothing seems to work. The drives either go read-only, or I'm no longer able to gain access to them, my only way out being to wipe everything and start again after reseting the unit—which I've done several times now and getting fed up with having to do so. I've recently set one of the computers (the MacMini that now deals with surveillance) to back up to the shared Time Machine facility on the NAS, instead of it's own Private Time Machine, to see if that will make any difference. As far as Time Machine allocation goes, I always set them larger than the hard drives they're backing up. i.e. The MacMini has a 500GB SSD, and the private Time Machine allocation was 2,500GB. The new Shared Time Machine space that it backs up to additionally for testing purposes is set at 5,000GB. And if it helps to know, the ReadyNAS has 6x4TB HDs configured in a RAID 5 array with currently 12TB of free space. If anyone can shed some light here I'd be most grateful. Thanks, Phil
Does running the Antivirus service slow down Time Machine backups?
After the recent Mac OS update to Catalina 10.15.6, I began to experience major issues with Time Machine. Backups would take forever to run, and the "Cleaning Up" process even longer. I ended up completely deleting the backup, and starting a new one from scratch. Does running the Antivirus service on the ReadyNAS cause other processes to slow down? I use my ReadyNAS primarily for storage of things I don't access very often, and for Time Machine. I'm beginning to wonder if running the Antivirus service is even necessary. I'd like to hear from other folks about their experiences with antivirus on the Readynas, and performance.Saving Microsoft Word files to ReadyNAS from MAC
Apologies for not adding to the existing thread on this subject here, but it's closed, marked as Solved. There is still an issue saving from Microsoft Word for Mac to a ReadyNAS SMB Share. Roling back the Word version, or using .doc files is a workaround as discussed in the previous thread, but it felt to me as if there is most likely a Samba misconfiguration on the ReadyNAS. The issue only occurs when 'Enhance MacOS' is enabled in the SMB service settings. This setting is automatically enabled if SMB Timemachine is used. Eventually, I found this article on the Microsoft forums: https://answers.microsoft.com/en-us/msoffice/forum/all/cant-save-to-network-volume/cb960d44-0be3-4697-ad81-b8e1f49308f9 which contains a suggested update to the smb.conf file that fixes the issue. I'm no expert in Samba, so I couldn't tell which config setting gets it all going, but I've updated my conf file on the NAS and Microsoft Word for Mac can now save to the share. The smb.conf extract is below. I've added this to /etc/smb.conf, at the end of the existing [Global] section, before the #includes. I realise this may well get overwritten, as on the ReadyNAS smb.conf is automatically generated. When that happens, I'll find a better place to put it. Perhaps in /etc/frontview/samba/smb.conf.defaults. Not sure, more trial and error needed. Not sure if the ReadyNAS devs read these forums. But if so, any chance of getting the config fixed in a future release please? Good luck Nick [Global] # # PREREQUISITES TO FUNCTION WITH OSX # min protocol = SMB2 ea support = yes # # NOT NEEDED WITH OSX/LINUX # disable netbios = yes dns proxy = no smb ports = 445 name resolve order = host bcast # # GENERAL COMPATABILITY WITH OSX SMB # adds alternate data streams (ADS) support # vfs objects = catia fruit streams_xattr # # STORAGE OF OSX METATDATA & RESOURCE FORK # in Netatalk compat xattr & ._ AppleDouble File # fruit:metadata = netatalk fruit:resource = file # # FILE LOCKING # no cross protocol locking # fruit:locking = none # # # MAP NTFS ILLEGAL CHARS TO UNICODE # fruit:encoding = private # # SMB2+ AAPL EXTENSIONS # file metadata - Unix mode, FinderInfo, resource fork size, permissions # fruit:aapl = yes readdir_attr:aapl_rsize = yes readdir_attr:aapl_finder_info = yes readdir_attr:aapl_max_access = yes fruit:nfs_aces = yes # # OSX COPYFILE # fruit:copyfile= yes # # PERFORMANCE TWEAKS # note - error with smb2 leases # smb2 leases = yes kernel oplocks = no use sendfile = yes # # FILE CLEANUP # delete veto files = true unix extensions = yes fruit:posix_rename = yes # # PARAMETERS IN SAMBA VERSION > 4.3.11? # testparm does not check fruit parameters # fruit:model = MacSamba fruit:veto_appledouble = yes fruit:zero_file_id = yes fruit:wipe_intentionally_left_blank_rfork = yes # ## END OF ADDED CONFIGS #Catalina, Time Machine, and my ReadyNAS
I thought I'd share my recent experience with Time Machine and my ReadyNAS 314. I finally took the plunge, and upgraded my Mac from Mojave to Catalina. Suprisingly, the upgrade went off without incident, except that Time Machine stopped working. I was getting various errors, such as "Remote disk not available", etc. I noticed that the upgrade changed the name of the backup on the ReadyNAS from <mybackup>.sparsebundle to <mybackup>.backupbundle. After reviewing some online disucssions of other users, I tried de-selecting ReadyNAS as the destination for my TM backup, then selecting it again. This appeared at first to fix the problem. The backups started running again, but then would fail. I gave up after several attempts to salvage the existing backup. Fortunately, Time Machine is not my only backup strategy. My first thought was to force TM to create a new backup. So I used a trick that has worked in the past. I edited the file com.apple.TimeMachine.MachineID.plist, changing the key VerifcationState from "1" to "2". (I made a backup copy of this file before I edited it!) A value of 2 tells TM that a verification has failed. At first, this appeared to work. TM reported that it needed to begin a new backup. However, it ran for about twenty minutes, then died. Here's what I finally did: Used SSH to access the directory on the NAS (default /data/.timemachine/ReadyNAS Used the command rm -rf *.sparsebundle which forced the recursive deletion of all files/folders without any warnings or prompts Deselected/reselected the ReadyNAS (on my system, the volume is called timemachine) Let Time Machine begin a new backup. The initial backup, as expected, took several hours. However, subsequent backups have run very quickly, and without errors. I hope this information might be useful to other users who have (or are planning to) upgrade(d) from an earlier version of Mac OS-X to Catalina.
Backup OS6
I am trying to setup backup jobs to pull files from my Mac OSx machine, from the User, Library, and Application folders, but Permissions are a real bear. The User Folder backup job fails regularly, mostly with "Permission denied!" messages, and mostly on user/library/application support/ files, on many, many .plist files, as well as on many other file-types. Of course, the Mac crowd says there's certainly not anything wrong with their permissions, that I must elevate the permissions of the backup program. I think this is a classic case of, "it's the other guys fault," which, of course, leaves the frustrated user in the middle, watching two guys point fingers at each other, neither offering any real help. Can anyone offer answers, thoughts, or other wisdom that might point me in the right direction? Thanks
Time Machine
I got a ReadyNas Pro with frimware 6.10.1; my timemachine was setup with an old Firmware. Was working with no problems at all. Today my older IMac hadn't done it's backup. I tried to see if Timemachine was being advertised on the network, nothing. I looked at backup-> timemachine. I stop the serviced and then restarted the service. I got a crasy error. Can not enable time machine. only supported with authentication type is local user. How can this be? Been using this with a server for years. Now, I can't enble Time machine because I'm not using a local authentication.Cannot log into server to give Time Machine access (ReadyNAS RN212)
What is my "name and password for the server" so that Time Machine can access it? The username and password I created when enabling Time Machine isn't working. I've also tried my ReadyNAS cloud credentials and the default NAS admin / password. See uploaded screenshot for reference.