NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
readynas developers network
303 Topics
More on CPU specs of the ReadyNAS Pro
Hi all, Does anyone know what FSB speeds the ReadyNAS Pro motherboard supports. I have three "servers" that I'm trying to consolidate. I figured that the file server (which is actually the slowest machine) would be replaced by the NAS but I'm actually trying to merge some other services onto the box which much luck so far.. One feature I'm working on porting is my Tivo transcoder. Essentially I have a small system that pulls programs off my Tivo, transcodes them and uploads (via WiFi/ethernet) to my portable media player. It means when I get home my media player syncs with my now-playing list so I can watch TV on the train too and from work. Since I work miles and miles away, I don't have time to watch TV at home so it's the only way I can watch TV.. I have the package working on the NAS, and I'm working on the integration with the front end (like managing black-lists and so on). I'd like to bump the speed of the processor but obivously the newer energy efficient <65W intel chips all seem to be 1333MHz FSB. Is this supported on this NAS? I know the warranty is void with this type of fiddling, but that is a risk I'm happy to take.. I also understand you wouldn't recommend an upgrade like this, but I would really like to know if it were possible.. I'll make all the code (mplayer is the driver behind the transcoding) available to anyone if interested.. but it is important to realise this is a Series 1 Tivo and an Archos 705/605 media player, not a common combination..19KViews0likes284Comments
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)
Installing Selfoss on ReadyNAS Pro 2
As you know, Google will close its Reader tomorrow and users are migrating to different RSS readers and aggregators. Selfoss (http://selfoss.aditu.de/) is one of these alternatives. It is opensource, lightweight and have very nice interface. And it could be installed to ReadyNAS server. This is how it is done: Install requirements (PHP 5.3 with sqite and gd modules) Easiest way is to buy PHP addon from ReadyNASXtras (http://readynasxtras.com/readynas-x86-add-ons/php-53-x86), but it is not too hard to install these requirments via shell: Add debian squeeze source to /etc/apt/sources.list: deb http://www.readynas.com/packages 4.2.23/ #deb http://archive.debian.org/debian etch main deb http://ftp.debian.org/debian squeeze main (thanks to chirpa for this trick https://www.readynas.com/forum/viewtopic.php?t=62906#p352609) apt-get update apt-get install debian-archive-keyring (otherwise you'll have to confirm signature of each squeeze package) apt-get install php5 php5-sqlite php5-gd Download and unpack Selfoss. I've used /c/webroot/selfoss folder. Set owner of this folder. It should be same user as starting apache: chown -R admin:admin /c/webroot/selfoss Configure apache. Config located in /etc/frontview/apache/httpd.conf. I've created /etc/frontview/apache/addons/selfoss.conf, which is imported automatically: Include /etc/apache2/mods-available/php5.load Include /etc/apache2/mods-available/php5.conf PHPIniDir /etc/php5/apache2 Alias /selfoss /c/webroot/selfoss <Location /selfoss> Options +FollowSymLinks +SymLinksIfOwnerMatch </Location> Fix php timezone warnings. ReadyNAS using non-standard timezone format which issue warnings in php. Simply edit this setting in /etc/php5/apache2/php.ini: date.timezone = {your timezone} Configure Selfoss Copy defaults.ini into config.ini. Uncomment "RewriteBase /selfoss" line in .htaccess. Restart apache killall /usr/sbin/apache-ssl /usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.conf Open https://{ReadyNAS host}/selfoss, add RSS sources or import OPML. Open https://{ReadyNAS host}/selfoss/update to load feeds. Add cron job to update feed as described in selfoss readme. That's it.Running VirtualBox VM host on ReadyNAS Pro
What is VirtualBox? So, I got bored while laundry was going... and decided to see how well a virtual OS would run on the Pro. My first choice of VM was VirtualBox, just cause I'm familiar with it after using it for ages, plus its open and free :) Eventually, I may look into VMWare as well. After a bit of messing around, got it installed. Since the system is based off of Debian, was easy to get VirtualBox itself there (deb package). The trickiest part was getting the kernel modules required installed (see end of post). In the end, I've got Windows 2003 R2 running on my Pro, interacting with it via RDP, and I am happy with the performance. I've added an extra 1GB memory (for a total of 2GB). I assigned 1GB of ram to my virtual OS, which still leaves the default configuration of 1GB for the NAS itself (which is more than enough still, 800MB+ is always cached). I made a 10GB virtual disk to install the OS on. If I need more space later for extra applications, I can just add another virtual drive to that installation. And since I always like a bit extra security, I went a bit beyond the usual, and also have TrueCrypt running full disk encryption in the virtual OS. So no one can even boot and read the data in that OS without my bootup password. I don't really have any screenshots to show, just a standard Windows installation. Here is a few of the steps I used while creating the VM on the console: VirtualBox 3.1 has changed the CLI configuration. Until I update this how-to, please reference this: http://www.uhleeka.com/blog/2009/12/vir ... 9-04-host/ # Creating the Virtual Machine. $ VBoxManage createvm -name "Windows2003" -register $ VBoxManage modifyvm "Windows2003" -memory "1024MB" -acpi on -boot1 dvd -nic1 nat $ VBoxManage createvdi -filename "/c/backup/VirtualBox/Windows2003.vdi" -size 10000 -register $ VBoxManage modifyvm "Windows2003" -hda "/c/backup/VirtualBox/Windows2003.vdi" $ VBoxManage registerimage dvd /c/backup/VirtualBox/Windows2003Ent.iso $ VBoxManage modifyvm "Windows2003" -dvd /c/backup/VirtualBox/Windows2003Ent.iso $ VBoxHeadless -startvm "Windows2003" & # Connected via Remote Desktop at this point. # After the installation, first page requires Ctrl-Alt-Del, so I sent the keycodes. $ VBoxManage controlvm "Windows2003" keyboardputscancode 1d 38 53 # System is up and running, time to install GuestAdditions for better video, etc. $ wget http://download.virtualbox.org/virtualbox/2.2.2/VBoxGuestAdditions_2.2.2.iso $ VBoxManage registerimage dvd /c/backup/VirtualBox/VBoxGuestAdditions_2.2.2.iso $ VBoxManage controlvm "Windows2003" dvdattach /c/backup/VirtualBox/VBoxGuestAdditions_2.2.2.iso With the OS booted up and just sitting at the desktop, top reports: top - 16:17:10 up 1 day, 17:58, 1 user, load average: 0.00, 0.01, 0.00 Tasks: 93 total, 1 running, 92 sleeping, 0 stopped, 0 zombie Cpu(s): 0.7%us, 0.2%sy, 0.0%ni, 99.2%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 2072432k total, 2020100k used, 52332k free, 6120k buffers Swap: 1048536k total, 144k used, 1048392k free, 784620k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10297 root 20 0 1104m 1.0g 4720 S 4 52.5 57:31.53 VBoxHeadless 12792 root 20 0 46092 9520 1720 S 1 0.5 59:54.51 motion 12196 root 20 0 9196 7688 980 S 0 0.4 0:57.72 wastesrv 1 root 20 0 1948 600 508 S 0 0.0 0:01.30 init Ad-hoc installation of VirtualBox. Should work for RAIDiator 4.2.4. Download links for the kernel modules, for those who don't want to go through the mess of compiling them. $ mkdir /lib/modules/`uname -r`/misc $ cd /lib/modules/`uname -r`/misc $ wget http://www.readynas.com/contributed/chirpa/modules/virtualbox/pro/vboxdrv.ko $ wget http://www.readynas.com/contributed/chirpa/modules/virtualbox/pro/vboxnetflt.ko $ echo "deb http://download.virtualbox.org/virtualbox/debian etch non-free" >> /etc/apt/sources.list $ wget -q http://download.virtualbox.org/virtualbox/debian/sun_vbox.asc -O- | apt-key add - $ apt-get update $ apt-get install virtualbox-2.1 $ /etc/init.d/vboxdrv start Or, if you want to compile the kernel modules yourself: envyious:/c/backup# echo "deb http://download.virtualbox.org/virtualbox/debian etch non-free" >> /etc/apt/sources.list envyious:/c/backup# wget -q http://download.virtualbox.org/virtualbox/debian/sun_vbox.asc -O- | apt-key add - envyious:/c/backup# apt-get update && apt-get install build-essential ... Setting up build-essential (11.3) ... envyious:/c/backup# wget -q http://www.readynas.com/download/GPL/RNDP6xxx_4.2.4_WW_src.zip envyious:/c/backup# unzip -q RNDP6xxx_4.2.4_WW_src.zip -d ./GPL envyious:/c/backup# cd GPL/linux-x86-2.6/ envyious:/c/backup/GPL/linux-x86-2.6# make && make prepare ... envyious:/c/backup/GPL/linux-x86-2.6# ln -s /c/backup/GPL/linux-x86-2.6/ /usr/src/linux envyious:/c/backup/GPL/linux-x86-2.6# KERN_DIR=/usr/src/linux envyious:/c/backup/GPL/linux-x86-2.6# apt-get install virtualbox-2.1 ... Setting up virtualbox-2.1 (2.1.4-42893_Debian_etch) ... Adding group `vboxusers' (GID 101) ... Done. Messages emitted during module compilation will be logged to /var/log/vbox-install.log. Success! Starting VirtualBox kernel module: done. envyious:/c/backup/GPL/linux-x86-2.6# cd envyious:/c/backup/GPL/linux-x86-2.6# VBoxManage list vms VirtualBox Command Line Management Interface Version 2.1.4 (C) 2005-2009 Sun Microsystems, Inc. All rights reserved. Install of VirtualBox 2.2.2, before Sun updates the Debian Repository... # wget -q http://www.readynas.com/download/GPL/RNDP6xxx_4.2.4_WW_src.zip # unzip -q RNDP6xxx_4.2.4_WW_src.zip -d ./GPL # cd GPL/linux-x86-2.6/ # make && make prepare # ln -s /c/backup/GPL/linux-x86-2.6/ /usr/src/linux # export KERN_DIR=/usr/src/linux # apt-get install libfontconfig1 libglib2.0-0 libice6 libsdl1.2debian libsm6 libx11-6 libxcursor1 libxext6 libxi6 libxmu6 libxrandr2 libxrender1 libxslt1.1 libxt6 python2.4 # wget -q http://download.virtualbox.org/virtualbox/2.2.2/virtualbox-2.2_2.2.2-46594_Debian_etch_i386.deb # dpkg -i virtualbox-2.2_2.2.2-46594_Debian_etch_i386.deb Setting up virtualbox-2.2 (2.2.2-46594_Debian_etch) ... Recompiling VirtualBox kernel module: done. Starting VirtualBox kernel module: done.16KViews0likes441CommentsReadyNAS OS 6.0.6 | VirtualBox Image #notsupported
Are you a developer that wants to create and test new add-ons, but don't have systems available to develop on/break? Are you pondering upgrading your first generation x86 system to the new OS, but want to test it out first? Are you just jealous that Synology DSM can be run in a VM, and ReadyNAS can't? Well here is how you can create a VirtualBox HDD to run ReadyNASOS virtually! For the lazy, a pre-made appliance to download and import, all ready to go! ReadyNASOS-6.0.6-x86_64.ova (68 MB) (First boot does install, will take ~1 minute. First time setup wizard will show. Has 2x8GB data disks in RAID1.) This VM is no longer updated by the #notsupported team, as NTGR now provides an official VirtualBox image themselves: Installing ReadyNAS OS on VirtualBox These steps were run on a RAIDiator-x86 4.2.22 system, any Debian system should work, other platforms may need tweaking; your mileage may vary! And of course, it has to be said, don't expect any support from NETGEAR with this. $ wget -q ftp://downloads.netgear.com/files/GDC/READYNAS-100/ReadyNASOS-6.0.4-x86_64.zip; unzip -q ReadyNASOS-6.0.4-x86_64.zip $ apt-get -y install syslinux-common; apt-get -y install syslinux mtools $ mkdiskimage RNOS6.raw 512 8 32; losetup --offset 16384 /dev/loop0 RNOS6.raw $ mkdosfs /dev/loop0; syslinux /dev/loop0; mount /dev/loop0 /mnt $ dd if=ReadyNASOS-6.0.4-x86_64.img bs=16k skip=1|tar -C /mnt -x $ echo -e 'default Normal\nlabel Normal\nkernel kernel\nappend initrd=initrd.gz reason=normal' > /mnt/syslinux.cfg; umount /mnt; losetup -d /dev/loop0 (losetup creates loopback device at first partition offset. installing syslinux-common (for mkdiskimage) first, because it will conflict with syslinux if installed at the same time. mtools provides mkdosfs.) Now you have the raw disk image. Next you need to create a .VMDK file, to properly reference the RAW file, example: # Disk DescriptorFile version=1 encoding="windows-1252" CID=fffffffe parentCID=ffffffff isNativeSnapshot="no" createType="monolithicFlat" # Extent description RW 327680 FLAT "RNOS6.raw" 0 # The Disk Data Base #DDB ddb.virtualHWVersion = "8" ddb.longContentID = "deadbeefcafedeadbeefcafeffffffff" ddb.uuid = "60 00 C2 9c c1 a4 a8 2b-9f d1 65 f2 1e b1 9d 09" ddb.geometry.cylinders = "325" ddb.geometry.heads = "16" ddb.geometry.sectors = "63"ddb.uuid.image="71222d44-9672-4482-941c-149c2ee0dfc4" ddb.uuid.image="71222d44-9672-4482-941c-149c2ee0dfc4" ddb.uuid.modification="de4161f9-152e-442e-ad6e-aa559179bd3e" ddb.uuid.parent="00000000-0000-0000-0000-000000000000" ddb.uuid.parentmodification="00000000-0000-0000-0000-000000000000" ddb.geometry.biosCylinders="325" ddb.geometry.biosHeads="16" ddb.geometry.biosSectors="63" Another option is to install the qemu-utils package, and run this command, to convert the raw image into a single VMDK file: qemu-img convert -f raw RNOS6.raw -O vmdk RNOS6.vmdk Now load up VirtualBox, create a VM, give it this disk to boot from, and a few more 'data' disks to install to. Put the E1000 NIC in Bridge mode. You can discover the NAS via RAIDar, and possibly readycloud.netgear.com. Default admin/root password is 'password'. You can login via the console in the VM as root. Open https://IP/admin, and access Dashboard. The system model shows as 'VirtualBox Simulation'.14KViews0likes50Comments
HowTo: Install VBox Synology DSM 4.2.3202 onto x86 ReadyNAS
XPENOLOGY DSM 4.2.3202 -------------------- OS: SYNOLOGY, DSM 4.2.3202 VIRTUAL MODEL: DS3612xs Are you worried that the new ReadyNAS 100,300, and 500 series means EOL for you current x86 ReadyNAS? Are you worried that features of ReadyNAS OS6 will never make it into your current x86 ReadyNAS? Is your system running fine, so you don't really have the need or desire to spend hundreds of dollars to upgrade? Then, thanks to VBox, give your older ReadyNAS product the same capabilities (if not more) as the new ReadyNAS line. Netgear and QNAP have better hardware, but Synology has many times more free apps and a better graphical web browser interface. Synology User Manual: http://www.synology.com/support/download.php?lang=enu&b=12%20bays&m=DS3612xs Modified Firmware Image: http://kuai.xunlei.com/d/heVkBwKQPAA.cFJR954 http://pan.baidu.com/share/link?shareid=352918&uk=1193824219 You must have an operational VBox Host Server installed onto your ReadyNAS for this to work. *** Setup a Synology VBox Guest running on your ReadyNAS VBox Server 1. Create Guest VM: A. General[Basic]: Synology, Linux, Linux 2.6 (64 bit), 512MB B. [Do not add a virtual hard drive] at this time: <Create> C. System[Motherboard]:Base Memory[512MB], [x]Hard Drive, [x]CD/DVD-RPM, [x]Floppy, Chipset[PIIX3] D. System[Processor]: [x]Enable PAE/NX E. Display[Remote Display]: [x]Enable Server, 12MB Video Memory F. Storage: Controller [IDE], Type [PIIX3] 1. Attach Primary/Master: Flash Image ~ DS3612xs_3202-Repack.vdi \-> create DS3612xs_3202-Repack.vdi using VBOX: $ VBoxManage convertfromraw --format VDI DS3612xs_3202-Repack.img DS3612xs_3202-Repack.vdi 2. Attach Secondary/Master: VBoxGuestAdditions.iso G. Storage: Controller [SATA], Type [AHCI], Port Count [6] Create and Attach 6 Virtual Disks: SynologyVirtualDisk1 .. 6 These Virtual Disks will hold your Synology operating system. Synology can also link to remote shares. This means you can remote link to your ReadyNAS Shares. H. Network: Adapter 1/2 -> [x],[Bridged], [x] eth 0/1, [Deny] Advanced: [Intel PRO/1000 MT Desktop] MAC: Set MAC to match the mac address of the DS3612xs_3202-Repack.vdi image [00113208D62A/B] I. Optional: You can also tie a VBox VM to a Physcal HD. The VBox VM will take control and reformat as if it were directly connected to a PC running the installed OS. 1. Example in Windows: Open DOS Window as Administrator \-> C:\ VBoxManage internalcommands createrawvmdk -filename "C:\Users\Downloads\NAS\Synology\DS3612xs\synoHD.vmdk" -rawdisk \\.\PhysicalDrive1 -register OPTIONAL: (The '-register' option should have done this part) VBoxManage storageattach Synology --storagectl "SATA" --port 0 --device 0 --type hdd --medium "C:\Users\Downloads\NAS\Synology\DS3612xs\synoHD.vmdk" 2. Example in Linux: Must provide the actual /dev/sdx. In this example sda was used \-> $ VBoxManage internalcommands createrawvmdk -filename ~/.VirtualBox/Machines/Ubuntu.vmdk -rawdisk /dev/sda -register 2. <Start> Synology VM 3. Download and install the Synology Assistant (Windows PC App) 4. Run the Synology Assistant. It will scan and display the IP of any Synology NAS devices running on your network. 5. <Click> on the displayed Device then <Click> on the above [Connect] Icon to go to a web portal. 6. Load the "DS3612xs_3202-Repack.pat" file from your PC when asked. This is a modified version designed to work with VBox.USB to UART Bridge VCP Drivers for CP210x
I've just begun looking at using my ReadyNAS Pro 6 as a potential home automation controller for the Z-Wave devices dotted around my home. I have an Aeon Labs Z-Stick S2 controller connected to my Mac (OSX) and talking to some test devices fine. I'm using the OSX drivers from http://www.silabs.com/products/mcu/Page ... ivers.aspx and they are working fine. But i'd like to move my Z-Stick over to the ReadyNAS Pro and communicate with the Z-Wave network from PHP using the compiled libopenzwave much in the same way as is done on the Raspberry Pi project and codebase at http://code.google.com/p/lights-control/ I found an old thread on here where WhoCares? had compiled the cp210x drivers for the old NV+ (which i still have powered off in my cupboard!). Would anybody with ReadyNAS x86 compiling skills be able to assist in getting the cp210x drivers packaged up for use with Frontview to kick off this z-wave journey? 8)Downgrade 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
HOW TO: Hosting multiple websites
G'day Guys, For some time I've wanted to host multiple websites from a single ReadyNAS unit...I haven't had the time to investigate it. 1. Backup all the .conf files in /etc/frontview/apache 2. Backup all the .conf files in /etc/frontview/apache - so you can restore the originals if you screw something up !!! 3. Edit /etc/frontview/apache/Virtual.conf Original file <VirtualHost _default_:80> SSLEngine off RewriteEngine on RewriteRule ^/admin/(.*)$ https://%{SERVER_NAME}/admin/$1 [R,L] </VirtualHost> Modified file NameVirtualHost *:80 <VirtualHost *:80> SSLEngine off RewriteEngine on RewriteRule ^/admin/(.*)$ https://%{SERVER_NAME}/admin/$1 [R,L] </VirtualHost> 4. Create a new my-virtual.conf file in /etc/frontview/apache/addons, this way it will be auto loaded without modifying any other files. The example below has definitions for two websites....add/remove as required. my-virtual.conf <VirtualHost *:80> ServerName www.example.com DocumentRoot /path/to/example.com <Directory /path/to/example.com> Options Indexes Order allow,deny Allow from all </Directory> <Location /index.html> SetHandler none Order Allow,Deny Allow from all </Location> SSLEngine off </VirtualHost> <VirtualHost *:80> ServerName www.domain.net DocumentRoot /path/to/domain.net <Directory /path/to/domain.net> Options Indexes Order allow,deny Allow from all </Directory> <Location /index.html> SetHandler none Order Allow,Deny Allow from all </Location> SSLEngine off </VirtualHost> 5. shutdown apache, killall apache-ssl 6. restart apache, apache-ssl -f /etc/frontview/apache/httpd.conf 7. All done :D CAVEATS 1. Toggling the state of HTTP within Frontview rewrites Virtual.conf so the above changes will be lost. ReadyNAS Team 1. It would be nice if the above changes could be made to the format of /etc/frontview/apache/Virtual.conf, so that changes aren't overwritten 2. I currently have to add the Location element to undo a global definition within httpd.conf. It would be awesome if this was removed from httpd.conf and added to Virtual.conf as... NameVirtualHost *:80 <VirtualHost *:80> <Location /index.html> SetHandler server-status Order Deny,Allow Deny from all </Location> SSLEngine off RewriteEngine on RewriteRule ^/admin/(.*)$ https://%{SERVER_NAME}/admin/$1 [R,L] </VirtualHost> Cheers, David13KViews0likes129Comments
