NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
readynas developers network
301 TopicsDowngrade to RAIDiator-x86 from ReadyNAS OS | #notsupported
This is UNSUPPORTED by NETGEAR. Do so at your own risk, without support from NTGR. You need to factory default after downgrading your NAS back to the old platform, BACKUP YOUR DATA! This downgrade will only work for legacy systems (Ultra/Ultra Plus/Pro), the new 312/314/316/516/716X models are not supported by the old firmware. If you do attempt to downgrade a new model to 4.2.x you will likely need to do a USB Boot Recovery followed by a factory default to get a working system again. Here is a pre-built image: RAIDiator-x86-4.2.31-downgrade (54.7 MB) After you do the required reboot as part of the firmware update process you will get the "corrupt root" error. If your NAS has a display on the front you will see it on this. Otherwise you can see it in the Info (far right) column in RAIDar. Once you get that error you will need to power down the system and do a factory default using the boot menu. Note: As RAIDiator-x86 is unable to mount an OS partition formatted to use the BTRFS filesystem there is no add-on trick to avoid a manual factory default. You will need to use the boot menu. If your NAS is off-site or inconvenient to physically access contact me via PM and I may be able to arrange an alternative solution. If you want to build the image on your own, you can follow the steps from this wiki article: $ wget -q http://www.downloads.netgear.com/files/GDC/RNDU2000/RAIDiator-x86-4.2.24.zip $ unzip RAIDiator-x86-4.2.24.zip $ head -n1 RAIDiator-x86-4.2.24 $ echo -n 'info::name=ReadyNASOS,version=6.0-4.2,time=1372729316,size=56387584,md5sum=5a29e74205983247ba50358a453c9ef2,arch=x86_64,descr=ReadyNAS Final Release,release_notes=http://www.readynas.com/RAIDiator_x86_4_2_24_Notes ' > newhead $ dd if=newhead conv=notrunc of=RAIDiator-x86-4.2.24 Basically, changes the ::name and ::arch in the header to match with what ReadyNAS OS 6 expects. Being able to downgrade using the image above may be of use to some who would like to try OS6 but want the ability to go back if they don't like it. More information on running ReadyNAS OS 6 on legacy ReadyNAS can be found in this thread (well worth reading if you are considering the upgrade): OS6 now works on x86 Legacy WARNING: NO NTGR SUPPORT
Flexget on Readynas Ultra [SOLVED]
For anyone who is still reading and/or trying this: http://flexget.com/wiki/InstallWizard/ReadyNAS The guide is still accurate. I got flexget to work on a readynas Ultra. The only thing I needed to do was to add this deb http://ftp.be.debian.org/debian squeeze main contrib non-free to /etc/apt/sources.list Don't forget this afterwards: apt-get update This was needed to be able to install all the dependencies needed for this step from the guide: apt-get install libc6-dev gcc libtag1-dev libssl-dev zlibc zlib1g-dev I commented the line out in sources.list afterwards, just to be safe.
How to update BIOS w/ OS6.x installed
So I decided to update the BIOS on my ReadyNAS PRO Pioneer (in order to increase the maximum memory capacity and add support for additional hardware CPU upgrades) and I noticed that people in the forum who had already installed OS6.x were struggling to perform the update. The problem they're having is that the BIOS update was packaged as an add-on for the old readynas os (Radiator 4.x) and is not compatible w/ OS6.x. Currently, their options are: a) (painstakingly) revert to Radiator 4.x in order to apply the bios update add-on and then reinstall OS6.x b) ssh into their box, extract the correct bios update image from the add-on and then manually flash the bios. I was about halfway through writing up a walk through for manual flashing when I found an article which detailed the process quite well. For detailed instructions, see the 'BIOS Upgrade' section of the following article: Replace the OS on ReadyNAS PRO *note: There is a typo in the article's instructions which I've described below. **note: This article assumes the user has a couple of packages (dmidecode and flashrom) already installed on their NAS. If you're uncertain about how to obtain these packages, see the instructions below: 1) Ensure the ssh-toggle is enabled in the OS6.x web GUI under: System > Settings > Services Then ssh into your ReadyNAS as root (in this example, my nas is located at 192.168.1.75) $ ssh root@192.168.1.75 root@192.168.1.75's password: ************** Welcome to ReadyNASOS 6.2.2 Last login: Sat Jan 3 21:53:41 2015 from 192.168.1.5 root@readynas:~# 2) add a repository where you may download the packages required in the walkthrough: # echo "deb http://ftp.us.debian.org/debian wheezy main non-free" >> /etc/apt/sources.list 3) download/install the packages # apt-get update # apt-get install dmidecode flashrom Also, there is a typo in the article's instructions which I would like to draw attention to. First, this is what the article says: warwick.ac.uk wrote: This is when you want to be connected to a UPS: # /opt/biosflash/flashrom -c W25x80 -w /opt/biosflash/RN_NV6_072610.ROM flashrom v0.9.3-r1205 on Linux 3.7.5-1.el6.elrepo.x86_64 (x86_64), built with libpci 2.2.4-pre4, GCC 4.1.2 20061115 (prerelease) (Debian 4.1.1-21), little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. No coreboot table found. Found chipset "Intel ICH8/ICH8R", enabling flash write... OK. This chipset supports the following protocols: FWH,SPI. Found chip "Winbond W25x80" (1024 KB, SPI) at physical address 0xfff00000. Flash image seems to be a legacy BIOS. Disabling checks. Writing flash chip... Erasing flash before programming... Erasing flash chip... SUCCESS. done. Programming flash... done. COMPLETE. Verifying flash... VERIFIED. Notice that when he actually flashed the new bios, he does: # flashrom -c W25x80 -w /opt/biosflash/RN_NV6_072610.ROM If you enter the above command, you'll receive an error about a non-supported chipset. To correct this, simply capitalize the x in the chipset's name. That is, change "x" to "X" and you'll be good: # flashrom -c W25X80 -w /opt/biosflash/RN_NV6_072610.ROM
Please Upgrade gcc tools!!!!
I'm trying to compile a program called ps3netsrv for NV + but the tools make gcc cpp and others are VERY outdated. In the source code I'm trying to compile I have several warning because of the gcc there is a guy on this forum who wonder why the problem had to compile and got no result, I have gotten results in MIPS and other Linux Embebed but Sparc NV + is IMPOSSIBLE because of the compilers. Please pray for the team netgear please make an upgrade of the tools. 'm No developer but I do not understand how you can have a version of gcc 3.X when the structure completely changed in later versions. Please make an update
Upgrading RN312 RAM to 4 GB (works!)
Maybe this is old news... but still: Seems that upgrading the RAM in the new Intelbased ReadyNAS series works just fine. Popping in a 4 GB module was quick and easy, and worked without further configuration. Nice! Having tried the same thing in an UltraNAS it did not work with the RAM modules I had, so this was a lot easier. I guess the RN300 series (and its siblings) are just a more modern design. Full writeup incl spec of what SODIMM module was used at http://goo.gl/zYtTiGMinecraft server addon for PRO - almost done, UI not working
Hello All, I was successful in creating a minecraft addon that had working start, stop and running scripts as well as an install bin. The problem is the UI doesn't seem to successfully start/stop even though i can run the scripts to successfully launch the java in console. I compared my handler file with other addons (transmission) for one as well as the javascript and xml file. I can't seem to figure out what's wrong - even when I enable the check box and click save, the /etc/default/services file is not being updated to enabled. what could be wrong? I've already checked my permissions, made sure those are alright, then went through and did a compare on the handlers; didn't see a problem. is there an exit code i should be omitting or returning for on start.sh?how to get iptables and nat working?
Seems some modules are missing by default, and reading around the forum here I noticed this thread: viewtopic.php?f=35&t=29947&p=165472&hilit=iptables#p165472 but there's some unanswered questions there. Is it possible to get NAT working on my Ultra 4? I tried this command, but note the errors: # iptables -t nat -I POSTROUTING -o eth0 -j MASQUERADE FATAL: Module ip_tables not found. iptables v1.4.8: can't initialize iptables table `nat': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded.
Sparc platform development envrionment using Qemu
You can now run a fully emulated Sparc platform development environment on any system capable of running Qemu. Download: readynas_compile_environment.qcow.gz # wget -q http://www.readynas.com/download/development/readynas_compile_environment.qcow.gz # gunzip readynas_compile_environment.qcow.gz # qemu-system-sparc -hda readynas_compile_environment.qcow -nographic Default root password for this package is 'a'. The compile environment is all there for most common stuff. # qemu-system-sparc -hda readynas_compile_environment.qcow -nographic (qemu) Nvram id QEMU_BIOS, version 1, machine id 0x80 CPUs: 1 invalid nvram partition length nvram error detected, zapping pram Welcome to OpenBIOS v1.0RC1 built on May 31 2007 23:50 Type 'help' for detailed information [sparc] Booting file 'disk' with parameters '' Not a bootable ELF image Not a Linux kernel image Loading a.out image... Loaded 7680 bytes entry point is 0x4000 Jumping to entry point... SILO Version 1.4.13 boot: Uncompressing image... Loaded kernel version 2.6.18 Loading initial ramdisk (3210249 bytes at 0x3000000 phys, 0x60000000 virt)... PROMLIB: obio_ranges 1 Booting Linux... PROMLIB: Sun Boot Prom Version 3 Revision 2 Linux version 2.6.18-6-sparc32 (Debian 2.6.18.dfsg.1-23etch1) (dannf@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 Fri Dec 12 16:29:52 UTC 2008 ARCH: SUN4M TYPE: SPARCstation 5 Ethernet address: 52:54:0:12:34:56 Boot time fixup v1.6. 4/Mar/98 Jakub Jelinek (jj@ultra.linux.cz). Patching kernel for srmmu[Fujitsu TurboSparc]/iommu PROM: Built device tree with 21266 bytes of memory. Power off control detected. Built 1 zonelists. Total pages: 31179 Kernel command line: root=/dev/sda2 ro PID hash table entries: 512 (order: 9, 2048 bytes) start_kernel(): bug: interrupts were enabled early Console: colour dummy device 80x25 Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 121200k/130232k available (1640k kernel code, 8880k reserved, 404k data, 136k init, 0k highmem) Mount-cache hash table entries: 512 checking if image is initramfs... it is Freeing initrd memory: 3135k freed NET: Registered protocol family 16 IOMMU: impl 0 vers 4 table 0xf3200000[262144 B] map [65536 b] sbus0: Clock 21.1250 MHz dma0: Revision 2 dma1: Revision 2 NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 2, 16384 bytes) TCP bind hash table entries: 2048 (order: 1, 8192 bytes) TCP: Hash tables configured (established 4096 bind 2048) TCP reno registered ioremap: done with statics, switching to malloc apc: power management initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) Console: switching to colour frame buffer device 128x48 /iommu@0,10000000/sbus@0,10001000/SUNW,tcx@3,800000: TCX at 0:50800000, 24-bit depth ffd54490: ttyS0 at MMIO 0x71100000 (irq = 44) is a zs Console: ttyS0 (SunZilog zs0) ffd54490: ttyS1 at MMIO 0x71100004 (irq = 44) is a zs ffd5466c: Keyboard at MMIO 71000000 (irq = 44) is a zs ffd5466c: Mouse at MMIO 71000004 (irq = 44) is a zs Floppy drive(s): fd0 is 1.44M FDC 0 is a S82078B RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize rtc_sun_init: Registered Mostek RTC driver. mice: PS/2 mouse device common for all mice TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family 17 Freeing unused kernel memory: 136k freed input: Sun Type 5 keyboard as /class/input/input0 Loading, please wait... Begin: Loading essential drivers... ... SCSI subsystem initialized esp0: IRQ 36 SCSI ID 7 Clk 40MHz CCYC=25000 CCF=8 TOut 167 NCR53C90(esp100) scsi0 : Sparc ESP100 (NCR53C90) Vendor: QEMU Model: QEMU HARDDISK Rev: 0.8. Type: Direct-Access ANSI SCSI revision: 03 Vendor: QEMU Model: QEMU CD-ROM Rev: 0.8. Type: CD-ROM ANSI SCSI revision: 03 Done. Begin: Running /scripts/init-premount ... SCSI device sda: 20971521 512-byte hdwr sectors (10737 MB) sda: Write Protect is off SCSI device sda: drive cache: write back SCSI device sda: 20971521 512-byte hdwr sectors (10737 MB) sda: Write Protect is off SCSI device sda: drive cache: write back sda: sda1 sda2 sda3 sda4 sd 0:0:0:0: Attached scsi disk sda Done. Begin: Mounting root file system... ... Begin: Running /scripts/local-top ... Done. Begin: Running /scripts/local-premount ... Done. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Begin: Running /scripts/local-bottom ... Done. Done. Begin: Running /scripts/init-bottom ... Done. INIT: version 2.84 booting INIT: Entering runlevel: 3 EXT3 FS on sda2, internal journal sunlance.c:v2.02 8/24/03 Miguel de Icaza (miguel@nuclecu.unam.mx) SunLance: using auto-carrier-detection. eth0: LANCE 52:54:00:12:34:56 Starting LVM...done. Checking filesystems...done Setting kernel variables. Mounting filesystems: nothing was mounted Initializing urandom... done. Starting portmap...done. Starting log daemons: syslogd klogd. Starting atd...done Starting inetd...done Starting cupsd...done Starting cron...done debian-sparc login: root Password: Linux debian-sparc 2.6.18-6-sparc32 #1 Fri Dec 12 16:29:52 UTC 2008 sparc GNU/Linux debian-sparc:~# (I'm actually running this directly on a ReadyNAS Pro)is there a Java VM for NV+
Is it possible to install java on the readynas NV+ I have a simple text based java application that grabs data from a webpage and loads to mysql on the readynas. It would be nice if I could schedule and run it all from the NV+ without the need to have my PC do the java part.
SickRage taken over update no longer works, use SickChill
Not sure who noticed that after an update Sickrage stopped working, if you then try to download a new version you land on the sickrage.ca page. If you install that version and want to access the GUI you are redirected to that site where you have to create a login. This page is maintained by a different person echelon, who initially added cryptocurrencyminig to both his site and to the SickRage code. This is part of a long running dispute between echelon and the people who maintaned the code the last couple of years. This group has now forked SickRage and created SickChill, less rage more chill! Myhnlo created an updated installer linking to the SickChill git repo: https://github.com/Mhynlo/readynas-sickchill/releases/tag/201810.15-ml0 Dave
