Reply
Apprentice
Posts: 16,075
Registered: ‎2007-09-24

ReadyNAS OS 6.1.9 | Run on existing x86 (4.2) #notsupported

There are a few threads on this, showing how to convert 6.0 firmware to run on the 4.2 platform.
I am combining the information here, so it is easier to digest.

This is UNSUPPORTED by NETGEAR. Do so at your own risk, without support from NTGR.
You need to factory default after converting your NAS to the new platform, BACKUP YOUR DATA!
ReadyNAS OS 6 will only work on 64-bit systems (Ultra/Pro), the NVX/2100v1 models are 32-bit and thus are not supported.



Here are pre-built images for the lazy:

After you upload the addon/firmware and reboot, it will update the firmware and start a factory default. Your system should be back up in less than 10 minutes running the new firmware.

If you want to build the image on your own, you can follow the steps from this wiki article:
$ 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
$ head -n1 ReadyNASOS-6.0.4-x86_64.img
info::name=ReadyNASOS,version=6.0.4,time=1364529349,size=49301504,md5sum=4086b247f29be084549f2b150ada8a70,arch=x86_64,descr=ReadyNASOS
$ echo -n 'info::name=RAIDiator,version=6.0.4,time=1364529349,size=49301504,md5sum=4086b247f29be084549f2b150ada8a70,arch=x86,descr=ReadyNASOS for 4.2!' > newhead
$ dd conv=notrunc if=newhead of=ReadyNASOS-6.0.4-x86_64.img
Basically, changes the ::name and ::arch in the header to match with what RAIDiator 4.2 expects.

More information can be found in this thread: OS6 now works on x86 Legacy WARNING: NO NTGR SUPPORT
Guide
Posts: 171
Registered: ‎2012-01-18

Re: ReadyNAS OS 6 for x86 4.2

Great info Chirpa, here is a Guide for the Lazy.

(Once your data is backed up)

OS6 in 3 Steps:
1. Download pre modified IMG (51.8 MB) (see chirpas post to see what has been changed)
2. Upgrade firmware in Frontview 4.2.X (with above file)
3. Reboot & factory default

This has been tested on Pro6s and Ultra6s.

Current Issues:
-Fans run loud, possibly fixed via console edit.
-Genie (NTGR Appstore does not work, do NOT enable)

Supported: pro 2/4/6, ultra 2/4/6, old pro / Pioneer Pro, 2100v2
Unsupported: NVX and 2100v1

Post your experiences.


Apprentice
Posts: 16,075
Registered: ‎2007-09-24

Re: ReadyNAS OS 6 for x86 4.2

Here are the change logs from NTGR's FTP site for the releases up to the most recent 6.0.4:

ReadyNAS OS V6.0.1 Release Notes:

Notes:

This is the bug fix release of software for the new ReadyNAS 100-300-500 Series products.
This software is not compatible with ReadyNAS units running 4.1.x, 4.2.x, or 5.3.x software

Changes/enhancements since previous release:

Fixed automatic snapshot for the default shares.
Fixed auto permission issue for shared folders.
Disabled Flex RAID "Add Parity" functions if smaller size disk is selected and is used for adding parity.
Reduced log size to prevent root partition becomes full.
Fixed backup Vault share name are not found in option "Includes" and "Excludes" issue.
Fixed UI crash caused by USB device eject.
Fixed IE10 compatibility issue.
Previous Version properly displays snapshot versions in Windows.

ReadyNAS OS V6.0.2 Release Notes:

NETGEAR is pleased to announce the release of ReadyNAS OS 6.0.2, the latest firmware for the following ReadyNAS network attached storage products:

ReadyNAS 102
ReadyNAS 104
ReadyNAS 312
ReadyNAS 314
ReadyNAS 316
ReadyNAS 516

The following are changes since ReadyNAS OS 6.0.1:

New features and enhancements:

None

Bug Fixes:

Fixed volume scan issue for ReadyNAS Vault.
Now able to remove apps that fail to install properly.
UPS support for forced system shutdown.
Added support for 6-bay touchpad.
Fix for backup configurations.
ReadyDROP share created by default.
LCD messages include support for UPS messages.
Fix for fan issue on RN516.
Fix for UPNP.
Fix for Wake-on-LAN.
Fix for AFP going offline during share creation.
Improve service handling when volume is deleted.
Fixed continuous loop for usage with cloud user.
Fix for eSATA.
Add additional menu options for 6-bay touchpad.
Fixed issue with ReadyCLOUD and device info.
Fix for degraded volumes.
Fix for NTP issue after reboots.
Set maximum attempts when device cannot connect to ReadyCLOUD to 10.
User no longer needs to authenticate ReadyCLOUD access if already logged in.
Fixed disk channel display show zero.
Added checks for bonded network interfaces.
Fixed unallocated buffer access.
Fix when trying to create two of the same shares.
Fix in backup jobs to when ownership is reset.
Fixed issue with Share name length.
Fix for issue when web server (Apache) can't be started correctly.
Fixed issue for ReadyCLOUD default share permissions.
Added Genie App warning message.

Limitations & Known Issues:

Disk encryption is not supported in this release.
The 6-bay products refer to a "backup button" on the device. The button is labeled "Ok".

ReadyNAS OS V6.0.3 Release Notes:

NETGEAR is pleased to announce the release of ReadyNAS OS 6.0.3, the latest firmware for the following ReadyNAS network attached storage products:

ReadyNAS 102
ReadyNAS 104
ReadyNAS 312
ReadyNAS 314
ReadyNAS 316
ReadyNAS 516
ReadyNAS 2120

The following are changes since ReadyNAS OS 6.0.1:

New features and enhancements

Supports ReadyNAS 2120

Bug Fixes:

Fixed volume scan issue for ReadyNAS Vault.
Now able to remove apps that fail to install properly.
UPS support for forced system shutdown.
Added support for 6-bay touchpad.
Fix for backup configurations.
ReadyDROP share created by default.
LCD messages include support for UPS messages.
Fix for fan issue on RN516.
Fix for UPNP.
Fix for Wake-on-LAN.
Fix for AFP going offline during share creation.
Improve service handling when volume is deleted.
Fixed continuous loop for usage with cloud user.
Fix for eSATA.
Add additional menu options for 6-bay touchpad.
Fixed issue with ReadyCLOUD and device info.
Fix for degraded volumes.
Fix for NTP issue after reboots.
Set maximum attempts when device cannot connect to ReadyCLOUD to 10.
User no longer needs to authenticate ReadyCLOUD access if already logged in.
Fixed disk channel display show zero.
Added checks for bonded network interfaces.
Fixed unallocated buffer access.
Fix when trying to create two of the same shares.
Fix in backup jobs to when ownership is reset.
Fixed issue with Share name length.
Fix for issue when web server (Apache) can't be started correctly.
Fixed issue for ReadyCLOUD default share permissions.
Added Genie App warning message.

Limitations & Known Issues:

Disk encryption is not supported in this release.
The 6-bay products refer to a "backup button" on the device. The button is labeled "Ok".

ReadyNAS OS V6.0.4 Release Notes:

NETGEAR is pleased to announce the release of ReadyNAS OS 6.0.4, the latest firmware for the following ReadyNAS network attached storage products:

ReadyNAS 102
ReadyNAS 104
ReadyNAS 312
ReadyNAS 314
ReadyNAS 316
ReadyNAS 516
ReadyNAS 2120

The following are changes since ReadyNAS OS 6.0.3:

New features and enhancements

None

Bug Fixes:

Fix issue with Available Apps not appearing for new registrations.

Limitations & Known Issues:

Disk encryption is not supported in this release.
The 6-bay products refer to a "backup button" on the device. The button is labeled "Ok".
WebDAV is not supported in this release.
ReadyNAS 2120 browser display needs to be wider than 1024 pixels to display properly.
ReadyNAS OS V6.0.5 Release Notes:

NETGEAR never posted them.
ReadyNAS OS V6.0.6 Release Notes:

Bug Fixes:

Fixed for HTTPS port conflict with other services (ReadyDLNA, NFS).
Fixed an issue with volume deletion when Vault and DLNA services are active.
Fixed an issue with ReadyDLNA TiVo setting options.
Fixed an issue that may prolonged system reboot time.

Limitations & Known Issues:

Drag and drop in Browse page only support files, doesn't support folders yet.
No AFP/FTP auto permissions set for new files and folders. Newly added files and folders only can be written by the owner, others only have read permission.
Plex Media Server's default temp folder is installed in /temp should be changed to data volume manually.
Dropbox service needs to be re-enabled and re-authorized after volume deletion.
Users cannot change the genie+ marketplace account associated with the ReadyNAS after the initial genie+ marketplace. If you need to change genie+ marketplace accounts, please contact technical support at support.netgear.com
Downgrading from 6.0.6 to previous versions is not allowed.
Apprentice
Posts: 16,075
Registered: ‎2007-09-24

Re: ReadyNAS OS 6 for x86 4.2

By default, ReadyCloud keeps a connection open to NETGEAR, even if you have the cloud services disabled. Their 'discovery' tool on readycloud.netgear.com uses this to find NAS's without using RAIDar. From the YouTube videos, it looks like two-way traffic here, where you can control your NAS behind a firewall via this site. So if you are the cautious/paranoid folk, or you don't plan on using Remote/other Cloud services, you can remove them to stop the NAS from phoning home (required by Gov/DoD/JPL/etc)... (this will break Remote/Replicate/ReadyDrop)
# apt-get remove leafp2p readydrop rdbroker remote replicate
The following packages will be REMOVED:
leafp2p rdbroker readydrop remote replicate
Do you want to continue [Y/n]?
Removing remote ...
Removing leafp2p ...
Removing rdbroker ...
Removing readydrop ...
Removing replicate ...

If you also want to remove the other bundled applications, if you have no plans on using them:
# apt-get remove plexmediaserver-ros6 vault rnp2-installer
The following packages will be REMOVED:
plexmediaserver-ros6 rnp2-installer vault
Do you want to continue [Y/n]?
Removing plexmediaserver-ros6 ...
Removing rnp2-installer ...
Removing vault ...
Aspirant
Posts: 26
Registered: ‎2015-07-11

Re: ReadyNAS OS 6 for x86 4.2 #notsupported

Hi chirpa.
A question:
Could removing these packages you mentioned (leafp2p readydrop rdbroker remote replicate) cause anything to break?
Other than the mentioned gui functions, of course Smiley Happy

brgds
Royan
Apprentice
Posts: 16,075
Registered: ‎2007-09-24

Re: ReadyNAS OS 6 for x86 4.2 #notsupported

Of course it could. Basic functionality wouldn't change, but the GUI may expect a response from those daemons yet not receive it, causing weird activity. There isn't a lot of proper error handling happening. Don't expect anything on the Cloud tab to work. Also note that upon firmware upgrades, all that junk gets re-installed again, for that reason, I've seen people use a boot script to remove the items.
Aspirant
Posts: 26
Registered: ‎2015-07-11

Re: ReadyNAS OS 6 for x86 4.2 #notsupported

Ok, thanks.

That's mostly what I tought.
Well, I'll see. Maybe I'll remove them, maybe not.
I have the itch, but as both the Nas and disks are brand new, maybe I've done enough for now.

brgds
Royan
Apprentice
Posts: 16,075
Registered: ‎2007-09-24

Re: ReadyNAS OS 6 for x86 4.2 #notsupported

I've been told the 6.0.5 release coming soon has a lot of memory leak fixes, seems like it should have been the initial release.
Apprentice
Posts: 16,075
Registered: ‎2007-09-24

Re: ReadyNAS OS 6 for x86 4.2 #notsupported

You can now run ReadyNASOS6 as a Virtual Machine: viewtopic.php?f=35&t=70699
Apprentice
Posts: 16,075
Registered: ‎2007-09-24

Re: ReadyNAS OS 6 | Run on existing x86 (4.2) #notsupported

[ Edited ]

Some handy utilities for scripting...

# rnutil -h
Usage: rnutil COMMAND [OPTIONS]
event_push push a system event to the UI
get_disk_info print a list of all attached disks and disk information
notify_ups notify command called from upsmon
check_ups_drv check and possibly start network ups drivers
powerbtn handle power button events from acpid
disk_chan disk event helper for udev
set_mtu network interface mtu helper for udev
create_bond create bond
rn_shutdown shutdown readynasd and system gracefully
rn_lcd LCD display
remote_access start a remote access session for tech support
volume_util perform volume operations
mkhomedir_helper home subvolume creator for PAM
disk_event_handler handler for disk events
hotplug_event notifier for hotplug events
md_event notifier for MD RAID events
start_raids start all MD RAID arrays
rn_dbgrw debug utils
shutdown_eda shutdown all attached EDA500
list list all personalities
help print this help text
# rn_nml -h
Simple NML CLI. Return NML on stdout.
(C) NETGEAR Inc, 2012-

Usage: rn_nml -h ... help
Usage: rn_nml [-v] -I debpkg ... install debian package
Usage: rn_nml [-v] -i debpkg ... install debian package (w/o check signature)
Usage: rn_nml [-v] -g obj ... call NML-GET for obj.
Usage: rn_nml [-v] -s obj:opt ... call NML-SET for obj. (!! NOTE IMPLEMENTED !!)
Usage: rn_nml [-v] -a obj:opt ... call NML-ADD for obj.
Usage: rn_nml [-v] -S AppName ... call NML-CMD to start and enable app
Usage: rn_nml [-v] -K AppName ... call NML-CMD to stop and disable app
options:
-v ... verbose

Details
-g shares ... get share list
-a share:/volname/sharename ... add share 'sharename' under volume 'volname'
# /frontview/bin/avdu -h
Anti-Virus Definition file Update
(C) NETGEAR Inc, 2012-
Usage: /frontview/bin/avdu [options...]
options:
-h ... show this help
-v n ... verbose. n=0..3.
-V ... debug curl
# /frontview/bin/avdu -v 3 -V
avdu.c:117(3) [curl]* Connected to avdl.ctmail.com (216.163.188.32) port 80 (#0)
avdu.c:117(3) [curl]* Server auth using Basic with user '0001E241P1281I072105'
avdu.c:117(3) [curl]< GET /csav/deffiles/def5/antivir-hit.ini HTTP/1.1
Authorization: Basic MDAwMUUyNDFQMTI4MUkwNzIxMDU6
Host: avdl.ctmail.com
avdu.c:117(3) [curl]< HTTP/1.1 200 OK
avdu.c:291(3) Start downloading definition file (201305180140)
avdu.c:117(3) [curl]* Connected to avdl.ctmail.com (216.163.188.32) port 80 (#0)
avdu.c:117(3) [curl]* Server auth using Basic with user '0001E241P1281I072105'
avdu.c:117(3) [curl]< GET /csav/deffiles/def5/antivir-z-201305180140.zip HTTP/1.1
Authorization: Basic MDAwMUUyNDFQMTI4MUkwNzIxMDU6
Host: avdl.ctmail.com
avdu.c:117(3) [curl]< Content-Length: 29237024
avdu.c:117(3) [curl]< Content-Type: application/zip; charset=binary
avdu.c:303(3) Done downloading definition file (201305180140) rc=0 http_status=200
avdu.c:502(2) Successfully download definition file (201305180140)
avdu.c:330(3) Start installing virus definition file (201305180140)
avdu.c:356(3) Success installing virus definition file (201305180140)
avdu.c:519(2) Successfully installed new definition file (201305180140)


They may start hiding stuff as more people poke around via SSH. They apparently didn't like me running 'strings' on the fvdropbox binary and finding command line arguments. As of 6.0.5, they stripped out the command line arguments seen below, though they still work.

chirpa wrote:
Looking at the /frontview/bin/fvdropbox binary, it uses the curl library to call dropbox.com APIs directly. Maybe there is an atomic timestamp issue, that it thinks the remote files are newer, so it downloads them again each time the service starts. It then uses inotify to find changed files, and upload them.

# strings /frontview/bin/fvdropbox
DropBox utitlity and sync server
This probram use 'parson' (a light json parser and reader) by Krzysztof Gabls, under MIT license.
See http://kgabis.github.com/parson/ for 'parson'.
# %s -h ... show this help
# %s [-v 0..3] ... start service
# %s [-v n] [-V] [-d] ... start service
# %s [-v n] [-V] -- cmd args... ... run utility command
-v n ... verbose. n=0..3.
-d ... debug service without started by systemd
info ... Get user info. (call /account/info API.)
... File listing. (call /metadata API.)
put [-f] local_path remote_path
... Upload file. (call /file_put API.) (Up to 150MB)
-f : forces update. otherwise update if newer.
get [-f] remote_path local_path
... Download file. (call /files (GET) API.)
-f : force download. otherwise download if newer.
sync [-c cursor] remote_folder local_folder
... Download all if newer. Then upload all if newer.
... Get file/directory info. (call /metadata API.)
-l : with list=true (default: list=false)
upload [-f] local_path remote_path
... Upload file. (call /chunked_upload API.)
... Create a folder (call /create_folder API.)
... Delte folder or file (call /delete API.)
This program should be started by systemd.
# /frontview/bin/fvdropbox -v 2 -V -d -- info
display_name=my name
quota=24561844224
email=my@email.addr
If you change the "-v 2" to "-v 3", you can see all the debug values. Scary that they don't verify the SSL certificate either, someone could hijack api.dropbox.com via DNS cache poisoning, and get your info. They call HTTPS with plaintext oauth secret key in the URL.
dbox_utils.c:84(debug) [curl]* 	 SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
box_utils.c:84(debug) [curl]< GET /1/account/info?oauth_consumer_key=REDACTED&oauth_token=REDACTED&oauth_signature_method=PLAINTEXT&oauth_signature=REDACTED&oauth_timestamp=REDACTED&oauth_nonce=REDACTED HTTP/1.1
Apprentice
Posts: 16,075
Registered: ‎2007-09-24

Re: ReadyNAS OS 6.0.5 | Run on existing x86 (4.2) #notsuppor

Updated conversion firmware image to 6.0.5.
nkd Aspirant
Aspirant
Posts: 11
Registered: ‎2013-05-08

Re: ReadyNAS OS 6.0.5 | Run on existing x86 (4.2) #notsuppor

get invalid checksum when I upload the add on, any ideas?
Apprentice
Posts: 16,075
Registered: ‎2007-09-24

Re: ReadyNAS OS 6.0.5 | Run on existing x86 (4.2) #notsuppor

Did you get to the point to Perform System Update, or did it give error before that? The screenshot in the first post is from my attempt using the image on a 4.2 box.
nkd Aspirant
Aspirant
Posts: 11
Registered: ‎2013-05-08

Re: ReadyNAS OS 6.0.5 | Run on existing x86 (4.2) #notsuppor

I am on 4.2 right now. I did as instructed. tried to flash the prep file first but it keeps saying invalid checksum detected, install aborted.
Apprentice
Posts: 16,075
Registered: ‎2007-09-24

Re: ReadyNAS OS 6.0.5 | Run on existing x86 (4.2) #notsuppor

Okay, prep addon, not firmware image itself. I uploaded another copy of the addon, can you try new link above?
nkd Aspirant
Aspirant
Posts: 11
Registered: ‎2013-05-08

Re: ReadyNAS OS 6.0.5 | Run on existing x86 (4.2) #notsuppor

same thing. exactly what it says ,"Invalid checksum detected in the update file, install aborted."
Apprentice
Posts: 16,075
Registered: ‎2007-09-24

Re: ReadyNAS OS 6.0.5 | Run on existing x86 (4.2) #notsuppor

Sorry, one more time. Download again.
nkd Aspirant
Aspirant
Posts: 11
Registered: ‎2013-05-08

Re: ReadyNAS OS 6.0.5 | Run on existing x86 (4.2) #notsuppor

that worked. now flashing, hopefully this method actually works. Previous method had me blinking blue light everytime. Lets see what happens.
Apprentice
Posts: 16,075
Registered: ‎2007-09-24

Re: ReadyNAS OS 6.0.5 | Run on existing x86 (4.2) #notsuppor

Using the prep addon first automates the factory default process. So installing that addon, then the firmware, it will reboot,update,factory default. Otherwise without the addon, only the firmware image, would seem to hang after the update, requiring a manual factory default with the boot menu (physical access).
nkd Aspirant
Aspirant
Posts: 11
Registered: ‎2013-05-08

Re: ReadyNAS OS 6.0.5 | Run on existing x86 (4.2) #notsuppor

It reboots to update the firmware but goes back to frontview and older firmware. Says firmware updated failed, verifying flash! Thanks.
Apprentice
Posts: 16,075
Registered: ‎2007-09-24

Re: ReadyNAS OS 6.0.5 | Run on existing x86 (4.2) #notsuppor

Give this one a try, its 6.0.4 image. If it works, you can do Check for Update once its up and running to get to 6.0.5: https://mega.co.nz/#!2c0WDAjD!CkSzb3I88 ... k2WDa1zQB0

Maybe the 6.0.5 one has quirks still.
nkd Aspirant
Aspirant
Posts: 11
Registered: ‎2013-05-08

Re: ReadyNAS OS 6.0.5 | Run on existing x86 (4.2) #notsuppor

will do and report back.
nkd Aspirant
Aspirant
Posts: 11
Registered: ‎2013-05-08

Re: ReadyNAS OS 6.0.5 | Run on existing x86 (4.2) #notsuppor

Do I need to flash the prep file again? or the first one should be good? cuz it is giving me an error saying failed to extract file, lol.
Apprentice
Posts: 16,075
Registered: ‎2007-09-24

Re: ReadyNAS OS 6.0.5 | Run on existing x86 (4.2) #notsuppor

I'd run it again, no harm. It just drops a startup script on the drive for v6 to run.
nkd Aspirant
Aspirant
Posts: 11
Registered: ‎2013-05-08

Re: ReadyNAS OS 6.0.5 | Run on existing x86 (4.2) #notsuppor

Sweet your script automated the process. I did actually factory reset it after flashing the initial method from another post, but it just did not work. Much appreciated.

Also is the readycloud working on this. When I set it up via readycould it tells me to press the back button on the unit but never works. I was able to set it up using the local ip.
Discussion Stats
Top Contributors
User Kudos Count
1