NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
ReadyNAS OS 6 on Legacy models
998 TopicsOS6 now works on x86 Legacy WARNING: NO NTGR SUPPORT!
Update: It is now unofficially possible using NTGR images to update legacy hardware to os6.X See Post #3, for directions to install 6.2.1 on x86 Ultra and Pro Models. (ARM NOT SUPPORTED by this OS) Be forewarned, this requires a SYSTEM WIPE and likely voids any warranty support from NTGR Supported so far: pro 2/4/6, ultra 2/4/6, old pro / Pioneer Pro, 2100v2 Not Supported: NVX and 2100v1 Thanks go out to "HomeBrew Anonymous" for making this possible. Update 2: A firmware image to downgrade back to 4.2.26 is now available. See this thread. While this downgrade should get you a working system again on the supported firmware, be forewarned this requires a SYSTEM WIPE and NetGear also does not provide support for this downgrade. If you have issues seek help on these forums. Original Post/Gripes I have been reading these forums since Monday's announcement and there has been a resounding "ooof" regarding the fact the Ultras and Pros are unsupported for future OS improvements. To clear the air: it would appear Netgear will never support os6 on past hardware. I have almost come to grips with this, and at least they have been open and honest with their forward direction and aren't stringing us along. viewtopic.php?f=138&t=70131 The upside is our devices still work and are mostly stable and eventually we can upgrade to a new shell that has os6 support, but in the meantime our $500-1000 investment is unable to take advantage of modern features we all desire. I don't think I can add a poll here at RN forums, but I would like to garner support for a 100% unsupported home brew of the os6 on Pro6 units. If we get enough support perhaps a talented member(s) here would help release a homebrew of sorts. The 3 main caveats are: 1. Netgear will never be held responsible/your warranty is void 2. A format is required (new FS and OS) 3. Data loss is highly possible If you are still interested please post a reply to this thread.Solved141KViews9likes1274CommentsReadynas Pro Pioneer corrupt flash - no boot menu and thanks to mdgm for help...
Hi there. Recently I had a PSU issue with my Pro Pioneer, where it would take a long time to power up after being off. The NAS then wouldn't boot, and sat showing 'Readynas' on the LCD. It was not possible to get to boot menu. The reset button had no effect when the NAS was turned on. I replaced the PSU, so the server at least powers up quickly, but still no boot. I managed to obtain a VGA header for the board (XFX Low profile bracket kit - MA-BK01-LP1K), and saw an MBR error, when connecting a screen - assumed to be the internal flash being corrupted). I then managed to do a USB recovery on the server, which reflashed the image (I removed my 5 disk RAID array and replaced with a single drive, so as not to break the array). After all this, the server booted OK, but with some odd hyroglyphics on the LCD, and when accessed through the web (OS6), was unable to use the setup wizard, as the page was blank. Also, the admin page showed no information for the model number, and odd characters for the serial number. It turns out that the model number and serial numbers, etc. are contained somewhere in flash.... i approached mdgm for help on this community board, and he telneted in to my server while it was in tech mode, and totally sorted it out for me.... Luckily I had a record of my serial number from one of the logs I had downloaded from the server before the problems, and so I could give it to him... Finally reconnected my array, and everything booted up as if the PSU thing never happened... mdgm even vent updated my bios, as I had upgraded the processor to a quad core one, but had forgotten to up the bios... The NAS now identifies itself as a Pro 6 which is a bonus! I've written this to say a big thank-you to mdgm for the help he gave me, and hope that these details can help anyone in a similar situation...Solved3.1KViews2likes1Commentpure performace and connecting losses after update to V 6.4.0 on RN 2120
After automatic update to V 6.4.0 our RN 2120 v2 performace is really pure. SMB-Connections to Windows 7 Clints are not stable and User/Group rights a ignored. We need a fast hotfix for those problems because we can use our ReadyNas as fileserver at the moment? Any quick help? Andreas5.5KViews1like21CommentsOS6.2.2 - Service SMB suddenly stopped working, won't start!
PROBLEM IS SOLVED :D READ THE REPLIES. I have a ReadyNAS Ultra 2 and a ReadyNAS Ultra 6. Both running firmware 6.2.2. Antivirus is disable on both devices. Service SMB suddenly stopped working on both devices! Need help to figure out what's wrong and what to do to fix this! The last thing I remember doing before the fault was installing several addons, including Plex Media Server. I have removed all these addons, but did not work. Disabling and removing Plex Media Server did not help! Both having these services enabled and green in UI: AFP, UPnP, HTTP, HTTPS, SSH. Both with these Addons installed and active: - PHPSysInfo for Readynas v3.1.7 by Poussin. - Gateone v1.0.2 by Poussin. - BitTorrent Sync v1.4.103 by BitTorrent Inc. - Plex Media server v0.9.11.7.803 by Plex, Inc. - Anti-Virus Plus v2.0.2 by NETGEAR, Inc. - SMB Plus v1.0.1 by NETGEAR, Inc. Gets this message when I try to restart and status the SMB service via SSH. # systemctl restart smb.service Job failed. See system journal and 'systemctl status' for details. # systemctl status smb.service smb.service - Samba SMB Daemon Loaded: loaded (/lib/systemd/system/smb.service; enabled) Active: failed (Result: exit-code) since Sun, 01 Feb 2015 15:50:52 +0100; 12s ago Process: 24036 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/smb.service Same happens with WINS service: # systemctl restart winbind.service Job failed. See system journal and 'systemctl status' for details. # systemctl status winbind.service winbind.service - Samba Winbind Daemon Loaded: loaded (/lib/systemd/system/winbind.service; disabled) Active: failed (Result: core-dump) since Sun, 01 Feb 2015 17:29:50 +0100; 19s ago Process: 31034 ExecStart=/usr/sbin/winbindd $WINBINDOPTIONS (code=dumped, signal=ABRT) CGroup: name=systemd:/system/winbind.service5KViews1like6CommentsReadyNAS Pro 6 - Stuck on booting while checking fs
I have searched for similar errrors on here, but none seem to either work or be related as to my situation. My Pro 6 just started to freeze a couple days ago while it was running. I had updated it to OS6 a long while ago. Thinking it might just be a random error, I restarted the device and now it gets to the checking root fs and stops around half way (sometimes more or less). I have tried the following: OS Reinstall - Completes and boots to same percentage. Disk Tests ran fine and rebooted itself (though now this is no longer an option in the boot menu) USB Recovery ran and shutdown. Boots back to same percentage. Tech Support mode works Tried start_raids and it seemed to see every drive. Ran some mdadm commands to examine the drives and array as found in other posts on here with no glaring errors found. Running a 'smartctl -t long /dev/sda' now. Not sure what else to do to get it to boot so I can get my files (prefer it to continue being useful but can get soem other NAS and move my data as long as I can get to it). Thoughts/ideas/help? Thank you.219Views1like27CommentsReadyNas Ultra 2 - OS 6.10.7 - Only accesible via DLNA / UPNP
Hi there, I am running a ReadyNas Ultra 2, on the latest OS (6.10.7) and the device has a reserved IP address. As of yesterday, I was able to access the NAS via Windows Explorer / Mac Finder using SMB connection. However, when attempting to login via 192.160.x.xxx/admin, the NAS was refusing to accept the Username and PW, despite these not being changed in years. I therefore followed guidance on this forum to re-install the OS, to attempt to re-set PW's, without losing the stored data. Since then, I am unable to browse to the admin page, I get the error 'This site can't be reached' in Chrome, and similar errors on other browsers. I am also unable to connect via Windows Explorer / Mac Finder. I am able to access the DNLA enabled shares still via other devices on the network, and I have successfully pinged the NAS via CMD Prompt. I can also see the device when running RAIDar, RAIDar shows the status as 'Healthy', but I cannot download logs, access diagnostics as I get a PW error. Any help would be much appreciated!! Thanks4.6KViews1like34CommentsReadyNAS Ultra 6 missing model name and serial number, corrupt VPD
My ReadyNAS Ultra 6 was running stable for many years, also after upgrading to OS6. But at some point it wouldn't boot anymore and only showed 'ReadyNAS' on the display . This text is shown as soons as the NAS is powered on and is not an indicator that it is booting. Also the boot menu couldn't be selected. Since I have another NAS with the exact the same hardware that was running fine, I start swapping components to rule out hardware issues. PSU, memory, disks were put from the dective NAS to the working one and everything was working, so the problem was related to the mortherboard not starting up. The last resort was to try and fix it with USB recovery. The machine was originally shipped with Firmware v4.2.19, but before it was stuck it was already running on OS6.10.x. The first USB stick I created was with using the ReadyNAS OS6 Recovery Tool. But when booting according to the recovery procedure and pressing the backup button on the front of the NAS, nothing happened. The machine just stayed ON and didn't shut down, also not after 20 minutes. I tried several other brands and sizes of USB sticks, all with the same results. Then I moved to using the old RAIDiator 4.2 USB recovery tool. Under Windows 10 running the usbrecovery.exe to prepare the USB stick, only threw an error: "The application has failed to start because its side-by-side configuration is incorrect". The same happended when I tried to run the tool using Windows 8. Luckily I found an old version of the RAIDiator recovery tool in my archive that didn't have the executable to create the bootstick, but manual instructions on how to create the bootstick. I still used the RAIDiator 4.2 USB Recovery Tool that can be still downloaded from the Netgear website, but followed the manual instructions: 1. Get a spare USB flash drive, formatted to FAT32 on Windows XP 2. Download the recovery tool 3. Extract everything to a temporary directory, e.g. c:\Pro-Recovery 4. In DOS window (Command Prompt), go to recovery directory and issue the following command: syslinux.exe -m E: (Assume USB drive is E drive, otherwise, replace with actual driver letter of recovery drive) 5. Copy all files except syslinx.exe from C:\Pro-Recovery to USB recovery drive E: 6. Download latest RAIdiator release and copy it to USB recovery drive 7. Eject USB from Windows and put it in front USB port and remove any other USB devices from back ports 8. Press and hold backup button, turn on power, continue to hold backup button, until power LED becomes solid, hold 5 more seconds and release button. 9. OS should boot into front USB and perform internal boot device The result was still the same. The NAS only showed 'READYNAS' and nothing happended when booting with the Recovery USB stick in the front USB port. The next thing I did was instead of putting the 4.2.31 image on the USB stick (step 6), I copied the image of the latest OS 6.10.3 firmware to the stick. And finally things started rolling. After booting the NAS with USB recovery, it shuts down within a few minutes, which confirms that the internal flash is refreshed with the firmware image provided on the USB stick. The Ultra 6 is fully operational again with OS 6.10.3. Hdd are recognized and after formatting, a new volume was created. There is only one issue left and that is during the process the VPD file that sits on the internal flas has become corrupt. Now OS 6 show a blank Model Type and blank serial number. Due to the device type is unknown to the OS, also the available application page, where one can select an App to install, remains empty. I hope the Netgear staff Marc_V or JohnCM_S on this forum are able to update the VPD on my machine, this would be much appreciated. In the mean time I have bought the RN426. Of course performance of this newer machine is better, but I really would like to continue using the Ultra 6 alongside, as it is still performing well for file sharing and backups.Solved3.3KViews1like7Commentsbackup over Rsync - creating subfolders with name of shares
Sharing the solution found on this issue. I experienced the same issue as reported by Peterlilly on post "backup-over-Rsync-creating-subfolders-with-name-of-shares" "I'm doing NAS to NAS backup from my new RN102 to my old Duo." "The jobs connect and run okay; but what is happening is that the backup jobs are creating a new folder in the destination share that has the name of the source share. As these folders are empty, they then create a new full backup in that folder." To avoid this issue of subfolder "sharename" creation, I found and successfully tested this workaround: Backup job configured on the ReadyNAS x86 (OS v6.9.x) to push to an old ReadyNAS arm (OS v4.1.x): Source: Type: share Name: share:Mysharename Path: ./ Destination: Type: remote Name: remote:Serveur Rsync Host: x.x.x.x Port: 873 Path: Mysharename/ Note the ./ in source path and the trailing "/" in the destination path Enjoy NB: disclaimer - make sure you have offline backups of data, please test first, no warranty if this solution does not work or if rsync erease data893Views1like1CommentFailed firmware upgrade - am I bricked?
I was foolish and updated my ReadyNAS 2120 unit from firmware 6.2.x to 6.9.4 without reading the readme (just assumed there'd be safety checks in there by default). Now I know I was supposed to update to 6.2.4 then 6.5.x then 6.9.x, but unfortunately I did not know that up front. I rebooted the NAS and the power light comes on for a second and then shuts off. I tried doing the USB Recovery thing, but it doesn't even get to the point where I can see LEDs for the boot loader. The power LED comes on for a second and then goes off, the fans don't even spin. Is this thing now a brick? And if so can I get my data off it pretty easily? I'm familiar with flashing these sorts of things over serial line. Is there any way to connect serially and re-flash? Thanks in advance.6.4KViews1like15CommentsFan control on RadyNas Umtra 6 with OS 6
Hi, I just updated my ReadyNas Ultra 6 from OS4 to OS6 -6.9.4 to be precise. Pretty much everything is working aside from the fans who are showing as 0 RPM in the manager while they're running full speed IRL. Is there a way to get some auto control nback or am I stuck with that ? Thanks a lot for any help.4.6KViews1like19Comments