NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
os6
15 TopicsMigrating gracefully from ReadyNAS OS4 to OS 6 (Settings, Data)
I have a ReadyNAS Ultra 4 running RAIDiator 4.2.31 , and I am looking to move to a ReadyNAS OS 6 device as gracefully as possible. My current NAS is not damaged or dead, so no emergencies - I just want to minimize the amount of work I need to do to make the move happen. My current plan is to back up all the data onto an external drive, move the drives to the new chassis (which will wipe them), and then restore the data. So far, this part is fine. My question comes down to the settings - if I back up the settings on RAIDiator 4.2.31 (IP, Shares, Users & Security, etc.), can I restore them onto to OS 6 device? Is there another graceful way of migrating all my settings, so that I do not need to re-create them all by hand and reset permissions? Thank you!870Views0likes2CommentsReadyNAS "Admin Page" is offline
Upgraded to firmware 6.7.5 through the web interface and now the unit is not responing via the browser at all. SMB share is still working Tried Rebooting Tried Reset via reset pin on back and selecting OS Reinstall - same issue Raidar Diagnostic will not connect, but raidar says unit is healthy ! I cannot download the logs because login is not working, I know the password before someone suggests password recovery. Looking at USB recovery but cannot get the tool to recognise any firmware to make a usb for me. Format USB to Fat32 and put these in root Reboot machine and hold backup for 30 seconds. Machine says booting from usb, then after a few minutes, resets and does FW Upgrade. But the firmware is still 6.7.5 ?? How to do it? What am I doing wrong? I know the issue is network adapter related because "\\192.168.1.101\folder" is working fine, but "\\192.168.1.147\folder" comes up with network error do i want to diagnose? If I factory reset it with different disks in it, can I the set it to x-raid and put back the original disks without losing data? Will factory reset put the original firmware back in or will it use 6.7.5 ? I really want to get this working again :( Many thanks for any help6.4KViews0likes26CommentsNo detection of "bad" power supply on ReadyNAS 4200V2 with OS6.7.5
Having recently seen a couple of posts from users with 3200's and 4200's with power supply issues, I ran an experiment and unplugged one of the supplies on my 4200V2 running OS6.7.5. While is beeped loudly, there was no message in the log that a power supply had failed. I don't have email alerts turned on, but my suspicion is that it would not have sent one, either. Pulling the supply completely silenced it, but there was still no entry in the log. It made no difference if this was done with power on or it was booted that way. I know OS6 is not officially supported, but it sure would be nice if it did properly detect this, as many with this type of unit administer them remotely. Do the newer rack-mount units with redundant supplies provide proper notification? I only ran this unit briefly with OS 4.2.x, but I am sure that it logged a power supply failure if one was not plugged in to a power source. I don't know if it complained if a supply was pulled completely (I suspect not, as that would be an intentional act).2.3KViews0likes0CommentsCan't all be bad .img files
ReadyNAS OS 6 Software Version 6.7.4 Every single version I download and then try mounting the .img file in Win7 ir Win10 gives me a "The disc image file is corrupted" error. They can't all be bad so I'm missing sometihing basic. They all unzip fine, just can't mount htem. Thanks in advance for your help!Solved3.3KViews0likes2CommentsReadyNAS 2120 crash every little
Hello, We have about a dozen NAS ReadyNAS, half are model 2120 and 2120v2. These models give us problems that make them unusable every little time: balance, defrag ... that last up to 22 days and with a load higher than 10 in the system, so the NAS are not operational. We need to know what is the necessary configuration so that no problems (job scheduling, firmware version...) These NAS worked correctly until they reached a particular firmware version: what is the reason they are no longer functional? Greetings.5.4KViews0likes16CommentsAuto clean "Recycle bin" on OS6.6 ?
I have looked though this post: https://community.netgear.com/t5/Using-your-ReadyNAS/Can-Recycle-Bin-be-enabled-for-CIFS-and-OS-6-1-2-on-a-314/td-p/856707 And I have successfully enabled the "recycle bin" on my NAS, it works fine excpet I have to empty it manually. I have crated a 'clean_recycle_bins' script and a 'recycle.conf' file according to the post, but when I try to run this scrip using " /frontview/bin/clean_recycle_bins start", I get this : "Can't locate Frontview.pm in @INC (you may need to install the Frontview module) (@INC contains: /frontview/lib /etc/perl /usr/local/lib/arm-linux-gnueabi/perl/5.20.2 /usr/local/share/perl/5.20.2 /usr/lib/arm-linux-gnueabi/perl5/5.20 /usr/share/perl5 /usr/lib/arm-linux-gnueabi/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at /frontview/bin/clean_recycle_bins line 8. BEGIN failed--compilation aborted at /frontview/bin/clean_recycle_bins line 8." So I guesee I am missing some frontview module files right? Where can I get them?Solved7KViews0likes18CommentsUpdating motherboad BIOS from OS6 -- can't get it to work
There is an older post, now closed (why does Netgear do this when future changes really can need a subject to be resurrected?) at How to update BIOS w/ OS6.x installed on updating some of the legacy machines (Pro6, Ultra6, Ultra4, Ultra2) motherboard BIOS if you made the switch to OS6 without first updating the BIOS and can no longer use the .bin package to do the upgrade. I can't get it to work. The forum poster may have been wrong when he said pars of the referenced article are wrong. The author in the referenced article does not seem to assume that you have flashrom and dmidecode installed as the forum posting states, the process given includes extracting them from the .bin package and moving flashrom and the .ROM files to /opt/flashrom. Dmidecode is not moved, but I can't see where it's needed, anyway. But, try as I might, I cannot still get the instructions to work. Bash complains -bash: /opt/biosflash/flashrom: No such file or directory in spite of the fact that flashrom is there and executable: flashrom -rwxr-xr-x+ 1 root root 280765 Jan 13 2011 flashrom. It makes no difference what directory I am in when I do this (making appropriate change to the path, of course). I can't even copy, move, or delete flashrom unless I use flashrom* instead of flashrom. That sounds a lot like there is an unprintable charachter at the end, but why then do ls, find, and cat all work without the * appended? I can do as I please with the non-executable files in the same directory, and I can I can do with it what I please (except, of course, execute it) it if I chmod it to non-executable. lsattr shows all dashes for the file. I tried using a newer version of flashrom that I installed with apt-get to do the ROM update, but it has a problem of it's own. It needs to be configured for the archetecture, and that fails on the Pro6, which is where I need it (error has been reported). I'm no Linux wiz, and Google has not been my friend here. No suggested solutions found in a search have helped. Anybody here have any clues/suggestions?Solved6.6KViews1like11CommentsRsync difference OS6 v OS 4 Security ?
I seem to be encountering another difference between how OS6 works compared to OS 4. I know I can achieve my objective by using another protocol or swapping source / destination around, but that isn't really the point, so could I ask for some help please. I am creating a third version of my data on an RN104. Having examined the 3 versions I have identified a few differences which I want to correct at an individual folder level using Rsync. I have successfully created and run an rsync job transferring data from a local share on a Duo to a remote rsync server on a Duo. The job was created and ran first time with no issues. I then amended the job, simply changing the destination IP address and attempted to transfer data from the first Duo to my RN104. The job fails, for unknown reason, with the backup job log containing the following sending incremental file list rsync: read error: Connection reset by peer (54) rsync error: error in rsync protocol data stream (code 12) at io.c(759) [sender=3.0.6] I have downloaded the logs on the RN104 and system.log shows the following (IP address and destination folder edited out) Mar 07 22:59:26 NAS_104 rsyncd[7702]: name lookup failed for 172.16.x.xx: Name or service not known Mar 07 22:59:26 NAS_104 rsyncd[7702]: connect from UNKNOWN (172.16.x.xx) Mar 07 22:59:26 NAS_104 rsyncd[7702]: rsync to [Destination] from UNKNOWN (172.16.0.50) Mar 07 22:59:26 NAS_104 rsyncd[7702]: ERROR: module is read only Mar 07 22:59:26 NAS_104 rsyncd[7702]: rsync error: syntax or usage error (code 1) at main.c(999) [Receiver=3.1.1] I successfully tested the connection both on an anonymous basis and using the admin user / password Any idea what is going on ? Does rsync need to be read/write, and if so how do you configure it, or is the RN104 denying access because it doesn't recognise the source NAS.Solved2.2KViews0likes2CommentsOS6 on legacy Pro 6
Was going to reply to an existing thread, but it won't let me... ReadyNas Pro 6. Running with 4GB RAM and a Core 2 Duo E7600 (3.06 GHz) in it. Now that Plex have decided to stop new releases for OS4, I'll finally need to make the jump to OS6. So: Backup Download the prep4tor6 bin Upload it like an add-on, but don't reboot Download R4toR6 bin Upload it using the ReadyNAS web gui firmware update After you upload the addon/firmware and reboot, it will update the firmware and start a factory default. What is the latest version to use? In the directory the most recent ones I see are: R4toR6_6.5.1.bin R4toR6_latest-beta.bin R4toR6_latest.bin Are these right? Or is there "Get this particular version that's best for a Pro 6 and don't get a later version as it doesn't work as well" or something?4.4KViews0likes4CommentsWhat btrfs data compression format is used in NAS OS 6?
I was looking at the options for btrfs, and I can't remember what Netgear mentioning what type of data compression is used in their boxes. I've heard of both zlib (faster compresion) and LZO (more compression) being used in btrfs systems. I'm not as interested in the space-saving end as I am in the transfer speed of otherwise non-compressed data (not precompressed AV media for example). What does OS 6 use?3.2KViews0likes3Comments