Last edited on
2010-12-04 06:54:40 by MikeGreene
[Reverting last edit by ConradTyree [1343] to previous version [650]]
Additions:
Ok, I figured at this point I did not spend money much on this thing so I altered the [[http://www.opennas.info/ OpenNAS]] firmware header and gave it a try! I first tried the LCS8220_402-zap3a_253.bin version from 2005 which with the altered header worked.
Deletions:
Ok, I figured at this point I did not spend money much on this thing so I altered the [[http://www.opennas.info/ OpenNAS]] firmware header and gave it a try! I first tried the LCS8220_402-zap3a_253.bin version from 2005 which with the altered header worked. [[http://essaysexperts.com/ buy essay]]
Additions:
Ok, I figured at this point I did not spend money much on this thing so I altered the [[http://www.opennas.info/ OpenNAS]] firmware header and gave it a try! I first tried the LCS8220_402-zap3a_253.bin version from 2005 which with the altered header worked. [[http://essaysexperts.com/ buy essay]]
Deletions:
Ok, I figured at this point I did not spend money much on this thing so I altered the [[http://www.opennas.info/ OpenNAS]] firmware header and gave it a try! I first tried the LCS8220_402-zap3a_253.bin version from 2005 which with the altered header worked.
Additions:
**10 October 2007 - I will leave these pages up, but I got tired of this thing and gave it away. I purchased an HPMediaVault MV2010 which is MUCH better than the ADS.**
Other half complete pages:
AdsNas1
AdsNas2
AdsNas3
Deletions:
Additions:
The /var/log/messages file is [[AdsNasLog HERE]].
Deletions:
The /var/log/messages file is [[AdaNasLog HERE]].
Additions:
@@**PART I: How Can I Break This?**@@
Additions:
The /var/log/messages file is [[AdaNasLog HERE]].
The first thing I noticed is that openNAS is not as easy to use as the original ADS firmware and that it requires more setup.
Deletions:
The /var/log/messages file is HERE.
Additions:
@@====ADS NAS Drive Kit (NAS-806-EF)====@@
Deletions:
====ADS NAS Drive Kit (NAS-806-EF)====
Additions:
The /var/log/messages file is HERE.
Additions:
I found the script that the NAS ran for flashing which I modified to just do a direct flash. It was something like this:
dd if=/mnt/openNAS-0.9d.bin of=/dev/mtdblock
I was sure the NAS would be a brick once this completed. Once the dd command had completed, I typed reboot at the prompt and did the factory reset. It seems that a bug in openNAS turns the NAS power light on and then it goes out, after that "oh shit' moment I realized the lan light was flashing so it was running. Also, openNAS does not assign a static IP to the NAS, but rather uses dhcp. Last, the http server does not start. After figuring all this out, and seeing I had not turned the NAS into a brick, I telnet'd into the box (root pw:all6200). Here is what I saw:
No differences.
No differences.
Additions:
CUSTOMER=LONGSHINE <== Changed to ADS using Hexedit/2
I flashed through the web interface and once complete I pressed the reset for factory defaults. One issue I ran into was that my linksys router is 192.168.1.1 and the NAS started as 192.168.1.1. Once this conflict was cleared up I had the NAS up and running. It looked a lot like the ADS version with web interface, however, I was able to telnet into it and look around. Just for information, the default root password is all6200.
Unfortunately, like the ADS firmware this version did not support EAs. So, I decided to go one step further. Since LCS8220_402-zap3a_253.bin was from 2005, I set about to flash the NAS to openNAS-0.9d-64MB.bin (25 Feb 2007).
If the previous flash was living on the edge then the next step was even worse. The openNAS does not have the header to edit, rather you have to flash via tftp or a special serial cable. The developer did have instructions as to how to add a header:
dd if=original_firmware.bin of=header.bin bs=512 count=1
cat openNAS-0.9d.bin >> header.bin
The dd command strips the header of original_firmware.bin, which I used an ADS fireware update, to header.bin. Next, the the cat command combines the header and openNAS file. I assume one should be able to flash from this point. However, I found that with the old v4.02 firmware installed I could no longer flash, not to openNAS or back to ADS firmware. At this point I did think I was screwed!
BusyBox v1.4.1 (2007-02-25 01:26:42 CET) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
Deletions:
CUSTOMER=LONGSHINE
I flashed through the web interface and once complete I pressed the reset for factory defaults. One issue I ran into was that my linksys router is 192.168.1.1 and the NAS started as 192.168.1.1.
Additions:
A portscan showed port 24 and when I used telnet to connect the I received the [[AdsNasMsg message]] I had read about.
I flashed through the web interface and once complete I pressed the reset for factory defaults. One issue I ran into was that my linksys router is 192.168.1.1 and the NAS started as 192.168.1.1.
Deletions:
A portscan showed port 24 and when I used telnet to connect the I received the [[AdsNas1 message]] I had read about.
http://all6250.blogspot.com/
http://openwrt.org/
http://tobe.mine.nu/
http://www.uclinux.org/
http://forum.opennas.info/
http://wiki.opennas.info
ntx_libra.tgz
J1: Power pack
J2: Current supply of the non removable disk
J3: Current supply of the exhaust
J4: COM1
J5: Net socket
J6: COM2 (?)
JP1: JTAG (?)
JP2: IDE interface
SW1: In/circuit breaker
SW2: RESET tracer
LD1: Power LED
LD2: HDD-LED
LD3: Net traffic LED
In the Netronix NH-220 NAS devices the BRECIS MSP2006 MIPS32 4Km processor is blocked. Here it concerns one on 170Mhz clocked MIPS CCU. As is the case for others embedded/NAS here a MMU is missing to systems to the store management.
The CCU is accessible over a JTAG interface.
http://wiki.openwrt.org/OpenWrtDocs/Customizing/Hardware/JTAG_Cable
http://forum.opennas.info/viewtopic.php?t=188&highlight=ads
http://all6250.blogspot.com/
Load Firmware extensions
To enable the Unicode and UPNP function for the device, you have to install the "ntx_libra.tgz" file to the device before any configuration.
To install the file,
1. Insert the included CD and click the "Browse" button.
Note: The Install Menu may auto run. Click "EXIT" to close it.
2. Select your CD-Rom drive. Select Firmware Extensions Gigabit SATA NAS with USB folder. Select the "ntx_libra.tgz" file and click "Open" to browse the file.
3. Click "Apply" to perform installation.
4. It takes a few seconds to perform installing, please wait upon installation.
http://translate.google.com/translate?u=http%3A%2F%2Fforum.opennas.info%2Fviewtopic.php%3Ft%3D61%26highlight%3Dads&langpair=de%7Cen&hl=en&safe=off&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools
Additions:
A portscan showed port 24 and when I used telnet to connect the I received the [[AdsNas1 message]] I had read about.
Ok, I figured at this point I did not spend money much on this thing so I altered the [[http://www.opennas.info/ OpenNAS]] firmware header and gave it a try! I first tried the LCS8220_402-zap3a_253.bin version from 2005 which with the altered header worked.
Deletions:
A portscan shows port 24 and when I used telnet to connect the following was captured:
Ok, I figured at this point I did not spend much on this thing so I altered the [[http://www.opennas.info/ OpenNAS]] firmware header and gave it a try! I first tried the LCS8220_402-zap3a_253.bin version from 2005 which with the altered header worked.
Deletions:
[TELNET] CONNECT (nasdrive/192.168.1.2)
***
*** CONNECT TO 192.168.1.2:24
*** date 08-26-07
*** time 15:03:10
***
1452.14 1361.72
/etc/issue www.brecis.com 28 July 2003
Welcome to linux 2.4.20-br251 by BRECIS (Release 2.5.1)
Brecis linux incorporates changes from kernel.org, and uclinux.org as well
as locally derived features to provide a robust environment for the embedded
BRECIS mips chip. Almost any program that can run with less than 64k of
stack should work. Most all features of the linux kernel are provided.
The "c" runtime library originated at uclibc.org. One nice feature is
that the fork() system call works (although slowly) for this MMU-less chip.
For more information on the operating system please visit these sites:
http://www.uclinux.org
http://www.kernel.org
http://www.uclibc.org
On the CDROM distribution, see files:
README
CHANGES Accumulated change log.
RELEASE-NOTES Additional notes, and short FAQ.
uClinux/README Instructions for building/changing things.
[TELNET] INFO: DISCONNECTED
***
*** DISCONNECT
*** time 15:03:10
***
Additions:
Ok, I figured at this point I did not spend much on this thing so I altered the [[http://www.opennas.info/ OpenNAS]] firmware header and gave it a try! I first tried the LCS8220_402-zap3a_253.bin version from 2005 which with the altered header worked.
Deletions:
Ok, I figured at this point I did not spend much on this thing so I altered the OpenNAS firmware header and gave it a try!
Additions:
Ok, I figured at this point I did not spend much on this thing so I altered the OpenNAS firmware header and gave it a try!
OpenNAS - LCS8220_402-zap3a_253.bin file from
Deletions:
OpenNAS
Additions:
http://all6250.blogspot.com/
No differences.
