Intuition - Home of Wiki2Touch

I will soon post a complete and detailed description on how to get the box working again after a unsuccessfull firmware flash burned the box. To be able to do that I used resources from Flipstars FAQ and his Wiki. You can reach it here:

http://flipstar.net/myfaq/

http://nas-2000.org/

While the NAS 2000 (Icy Box IB-NAS2000, build by raidsonic: http://www.raidsonic.de/) is not the same as the HDD DUAL NAS they do share the same chipset and a lot of the same features. The firmware is also *not the same* but you can easily see that the firmware comes from the same source.

So having a look at the NAS 2000 device is very usefull. For instance, Flip’s ssh integration works also on the DUAL HHD NAS.

The telnet daemon can be legally enabled by the web frontend. The option to do so is *not* visible in the menu but the corresponding page ist existing. To get the page displayed log into you’re NAS device using the web frontend. Assuming that the device has the IP address 192.168.0.13 you can then call the telnet setup page. While logged on chance the URL to

http://192.168.0.13/html/telnet/telnet.html

The next display looks weird, but you if you check the checkbox and press the button telnet is enabled for you. Of course you can disable telnet here, too.

What is following now can be the end of you’re NAS. So be carefull and warned!

After the first “hack” of the firmware ended in a dead box I was more carefull the this time. In the file hddapp.tgz (part of the firmware; this is not a .tgz file but a bzip2 compressed .tar file) the folder “webroot/nav/telnet”, along with the only file “telnet.xml” in it, is missing. On the device the folder is “/usr/webroot/…”. I guess you can image what is the contents of “telnet.xml” once you had a look in a file from on of the other folders. As the webserver is loading the file dynamically you can experiment directly on you’re device. Telnet is working for you!

After adding the “missing” folder and file you can enable/disable telnet comfortably from the “Network Service” menu:

BTW: Every time I enable telnet I also set a password for the root account.

I made myself a new image and flashed. So the option is there after a reset.

My first approach was to modify the firmware. If you google for “dual hdd nas firmware” you should find the proper file (CentriNAS_V2_3_3a.tar.gz). With the help of Linux (using “Parallels”) I was able to change the firmware. My third try was to big and the device was more or less death after the flash process (see the other article).Shortly after the NAS was working again I found that the telnet port was open a short period after the device has booted (no, I don’t mean the bootloader). To get connected simply shutdown the device, enter

ping -o 192.168.0.13; telnet 192.168.0.13

and start the device. One or two minutes later you can log in as “root”. The password is blank.

Edit the “/etc/inetd.conf” file and remove the comments so you can log out and in as long as the device is not rebooted.

The telnet daemon is originally started but then stopped by the configuration program. But you can’t use the web interface to change this.

But well, that’s not true…

After the switch to MAC OS X in needed a new NAS. The old system, a Netgear SC101, is using driver which are only available for windows. Beside the missing drivers for Mac OS (and Linux, too) the SC101 is awfull slow, especially in raid 1 (mirror) mode. Further, the features are limited (hmm, yes, it’s only a NAS).

But I wanted a box with embedded Linux, easy expandable or modificable.

That’s what I got from eBay. NIB but not much more information. Based on a SL3316 by Storelink it is build around an ARM9 processor, has an IDE controller (two channels), 10/100 ethernet connector and an USB port (looks like 1.1). You can find more specs here: http://www.storlinksemi.com/products-sl3316.htm

After powering up you can use your webbrowser to configure the device. In case you can not (remember MAC OS X) run the enclosed “setup.exe” (which does not much more than to hand you the ip address) try ping 192.168.0.255 (or whatever your broadcast address is). The web interface is not very nice but my goal was to get into the “engine room”.

To bad at this point: telnet (or ssh) aren’t working in the first place.

Finally a picture of the board. There is also a seriell connector but I don’t have a proper cable.