08-13-2010 12:06 PM - edited 11-01-2010 04:46 AM
I've written a small howto on how to enable SSH the BlackArmor 220 NAS:
This modification has been tested on the Blackarmor 220 only. Please let me know if it works on other models, too.
08-31-2010 02:37 PM
the deobfuscation helped me to modify the sg1000-1000.0391.img for the NAS 110.
I modified the etc/inetd.conf within the .img by but the file was not taken over after
the firmware update. I had to delete the file from the sg1000-1000.0391.img/backup_list
so it was no longer kept after the firmware update. I don't think that this is a good solution
which should be posted. But i do not found a hint for a pre_setup and post_setup beeing
called anywhere. I am not into this admin stuff and cannot calculate the sideeffects of my
changes so how would you force the changes in /etc/inetd.conf to be made without modifying
the backup_list file. Within one of the rc pre nfs runlevel startup scripts ?
anyway many thanks for the hints from Berlin but not Tegel.
09-01-2010 02:01 PM - edited 09-01-2010 02:10 PM
Did you try to upload my service pack file to your NAS 110? As it does not contain any model-specific data, it should get accepted by the web interface and patch /etc/inetd.conf for you. It also contains pre/post-setup scripts which you can modify according to your needs (e.g. to change other config files).
09-02-2010 04:52 AM - last edited on 09-02-2010 07:07 AM by MrMatthew
Just wanted to say thanks for jumpstarting this effort. It will be great when we can get an entirely different Linux distribution onto this thing; think FreeNAS. Yum.
In the meantime I'll check this out and see if i can't get some development tools on this thing. If I can get netatalk onto the 220 it won't be such a pain[Edit: Please do not evade the word filter] with my Macs.
09-02-2010 06:12 AM
Apparently this Buffalo NAS uses the same distribution, with the same CPU:
Tried running nano but I was missing some libraries.
09-02-2010 08:06 AM
I have 220 with FW 2000.631. Please let me know if your SP is applicable to this FW version. I am very entusiastic to create a small community to improve our NASes.
09-02-2010 11:02 AM
I've used Qemu+Debian (armel) to compile extra packages for the BA220:
It shouldn't be a big problem to install Debian or any other linux distribution on the NAS. Having someone figuring out the serial port pinout (3.3V CA-42 cable) would help to monitor the boot process.
My BA220 went into production use some weeks ago and therefore I'm not able to alter the system anymore.
09-02-2010 11:06 AM
I use BA220/2000.631 as well and it works for me (to be more precise, the SP has been developed on this FW ;-) ). As the image does not contain any device or model-specific files I _think_ it should for other systems, too.
09-18-2010 12:14 AM
I have the pinouts figured out on my 440. I just want some directions on creating and loading my own altered firmware. Help would be much appreciated.
Pin 6 - black (Gnd)
Pin 1 - yellow (TX)
Pin 4 - green (RX)
Pin 9 - red VCC (3.3V)
Baud rate 115200
I used this part http://www.acroname.com/robotics/parts/S27-USB-SER
09-18-2010 03:29 AM - edited 09-18-2010 03:30 AM
thank you very much for sharing this information. With your kind permission, I've added the pinout to my seagate BA page.
If you reboot the NAS, you should see lots of debug output from the u-boot bootloader. You can interrupt the boot process and alter the u-boot settings if you press any key directly after resetting the device.
As a first step, I recommend to try to boot a linux system via NFS. You only have to alter the u-boot, and not flash and on-disk data. If anything goes wrong, you can easily revert to the original settings. Search for 'seagate dockstar NFS' on the web, the process should be very similiar.
It would be interesting to know the output of the u-boot 'printenv' command.