Difference between revisions of "Talk:Hacking"
|Line 197:||Line 197:|
== Cross Toolchain ==
== Cross Toolchain ==
Is there any interest in setting up a cross toolchain as the linkstation owners have done (http://linkstationwiki.
Is there any interest in setting up a cross toolchain as the linkstation owners have done (http://linkstationwiki./Articles/GeneralCrossToolchain)? Or, I wonder if I could use their cross toolchain to make binaries for my TS
== Files missing from GPL archive ==
== Files missing from GPL archive ==
Revision as of 13:05, 25 October 2006
Scott by any means please post your kernel modules, as I was able to produce modules that allow me to mount an nfs export, but when I try to do any operation over them this mount gets stuck. And if you can, please include your .config with the modules.
--Yvasilev 19:23, 18 Aug 2005 (CEST)
Just downloaded European 2.00 firmware. Extracted, added Dropbear and NFS like described in this Wiki. The ~var symlink was not overwritten when extracted using the same tar command as suggested for Dropbear. Still, one could always extract with -w as well, do not extract the /var stuff, but extract it to another folder later on and move it manually. Re-compressed, installed new firmware. File system still there without problems. Only remaining problem:
- admin@TERASTATION:/etc$ /etc/init.d/nfs-common start
- /etc/init.d/nfs-common: modprobe: command not found
- Starting NFS common utilities: statd/etc/init.d/nfs-common: start-stop-daemon: command not found
Therefore on client side:
- [root@linuxbox ~]# mount 192.168.13.8:/mnt/array1 /mnt/terabackup/
- mount to NFS server '192.168.13.8' failed.
Two additional comments:
- after extracting the NFS stuff, etc/exports needs to be edited. The default exports only to 192.168.1.1, but you probably want to adjust it to export to either your box (change IP there) or your whole network (/mnt/array1 192.168.1.0/255.255.255.0(rw,root_squash) or similar).
- You need to edit linkstation_version.txt to show a newer version number, otherwise you won't be able to upgrade. (Or add /force to the NASUpdater.exe command line)
I tried this twice. After the first time, I had to reinitialize the drives in order to restore the file system so that I could boot. This, the second time, I poked around the file system a little more and realized untarring it, using tar xvzf all-nfsd.tar.gz, overwrote my /var directory. It was overwritten because I *think* it was a symlink to /mnt/ram/var [http:/ls-lR/1.04/ file list]. I can't be certain because I'm running 1.12, but recreating the link seems better - I see the expected stuff in /var (e.g. /var/log/messages). I have no idea if the file system is normal because I haven't rebooted.
Anyone have any input? Is there a way for tar not to clobber that link?
I started up the portmapper and nfs, but I can't mount:
[root@mymachine ~]# mkdir -p /mnt/terastation/array1 [root@mymachine ~]# mount -t nfs 192.168.11.150:/mnt/array1 /mnt/terastation/array1 Segmentation fault
- nmap shows nfs and rpcbind are up.
- mymachine, running Fedora Core 4, nfs mounts stuff from an NSLU2 running Unslung 5.5 w/o issues.
- showmount -e 192.168.11.150 shows the export
Does anyone have any ideas of what else I can try? TIA
--Bluefedora 14:40, 27 Nov 2005 (CET)
One issue is that /var/lib/nfs/rmtab is a directory instead of a file. If you look in the syslog, you will see a message like:
Feb 11 20:21:01 terastation rpc.mountd: could not open /var/lib/nfs/rmtab for locking
Unfortunately, this does not fix the problem. even after a reboot, mount request still segfault.
However, now it appears to work by examining the terastation syslog:
Feb 11 22:29:55 terastation rpc.mountd: authenticated mount request from client:616 for /mnt/array1 (/mnt/array1)
There are no other errors. This makes me wonder if there is a compatibility issue with the NFS version on my FC4 box and the one installed from sf.net.???
--cctjon Sat Feb 11 22:33:29 MST 2006
I think individual problems and requests for help belong into the discussion part, not into the article! CCRDude 13:37, 13 Feb 2006 (CET)
In my over zealous hacking attempts, I have managed to kill the code in my flash. Is there a way to restore the flash code?
- The TeraStation has a JTAG interface. It's part of the regular PowerPC debugging interface CN11. This 16pin interface is quite common for embedded PowerPCs, but I've forgotten it's name and don't have any useable links.
- Unfortunately we don't have any JTAG-borderscan information, and without you will not be able to use the JTAG interface.
- Sorry, but it looks like you're hossed. How did you destroy your flash anyway?
- Come to think of it: unless you also destroyed the bootloader, you should be able to access it. Either from the serial port or even from the network. I've no further infrmation on this either.
- You could ask buffalo, they have now at last learned how to use mdadm with a hacked firmware to recover a hossed raid.
- --Bg 08:31, 4 April 2006 (CEST)
It was actually kinda stupid. I have two TeraStations, a TeraStation 1T and a TeraStation Pro 1T. I got the latest firmware for the Pro to add the AD support. I 'accidentally' applied the update to the non-pro box. After the TeraStation rebooted, it shutdown with the Diag light flashing. According to TeraStation docs:
Five time continuous blinking(every four seconds) Flash ROM Error
The box is no longer accessible from the net. I thought I may be able to find some info on the root disk so I put it in a USB enclosure and mounted it using Suse. Of course there was nothing I could do because the kernel doesn't appear to load/execute from the flash. I haven't performed the console mod yet. Do think this might provide some useful output? Or should I just admit my stupidity and send the box back to buffalo for repair?
-- Update -- I performed the console mod and now I can see the boot messages (boot text). It appears the problem is that it's not loading an IDE driver ('cause the Pro doesn't use IDE?). Any Ideas? --Sjcook 14:52, 19 April 2006 (CEST)
Terrastation Root password.
I have just installed the Terastation 2.03 firmware from http://homepage.ntlworld.com/itimpi/buffalo.htm I currently have telnet access, and wish to install SSH, although I do not have root accesss. sudo does not work because there is no /etc/sudoers file, and I can't add anything to /etc/ due to my permissions. Does anyone know the default root password for 2.03? Thanks.
- No, but feel free to crack it. It's btw. a lot easier to just make a modivied firmware image.
- --Bg 14:52, 6 April 2006 (CEST)
is the root loging account should be "myroot" with a blank password.
Hi, have just bought a Terastation and LinkTheater, like the idea of modding the TS for all these extra features, wondering if anyone has thought of testing it using a virtual PC (I have dd'ed the partitions of an old PC onto virtual disks created with QEMU (http://fabrice.bellard.free.fr/qemu) and then run the old machine as a virtual one within vmplayer (http://www.vmware.com/products/player) ) ? Is this something that anyone has considered - or does anyone have a copy of the linux partitions ? (A little nervous of opening the TS up as I now have data on it!) Thanks.
--Chris 12:36, 13 April 2006 (CEST)
Unfortunatly there is no HowTo for installing the LundFTPD. I tried to get it working but had no success. I downloaded and installed the precompiled Binary. Afer configuring the .conf file a litte bit i tried to start he deamon with /etc/init.d/lundftpd start - nothing happened (also no logfile action). when i tried to start the lundftpd manually with lundftpd -v a "segmentation fault" appeared.
Maybe there are some dependencies but i do not know which (there is no lundftpd readme.txt). If someone get the ftpd working please explain how (in the "hacking" page of this wiki).
I tried it with: Terastion 1TB, Disk Firmware 1.12 (Dave's hacked version)
Half Dead Terastation
Please read, and either laugh or cry.. After updating the firmware of my terastation to get root access to my box I started playing around. I found a heap of binaries that could be used with the terastation, so without looking through I untared everything.. (it all the packages looked useful) The downfall was that I replaced glibc and I get this error when i telnet to the box in.telnetd: /lib/libc.so.6: version `GLIBC_2.3' not found (required by /lib/libwrap.so.0) SMB, apache, have also stopped working although FTP is good and healthy.
The only thing I can see possible now is for me to find an LPR exploit or try getting serial access.
I read through the documentation serial port guide on this site, although I am still wondering what exactly I need to do from a step-by-step persepctive.. Do I need to buy any resistors or jumpers? if so what type? etc.. Could anyone please help me out.
you crashed the diskfirmware, thats not an essential problem. i had an equal problem. after disconnecting the harddisks and playing with the firmware toy a bit the whole raid array was renewed therefore also the diskfirmware deleted. after this you can flash again and everything will work again regards, ringgh0st
Your 100% right!. I was so scared that if I rebooted my terastation it would render it unusable by not being able to boot. I also realised there was a factory reset button on the back of the unit as well.
User Space NFS Daemons
I just spent the day hacking my Terastation Pro to support NFS. While it works perfectly now it was such a pain I felt I should post my solution here to save others some suffering.
First off don't bother with the kernel space version of NFS. I tried the posted modules in the articles section, all-nfsd.tar.gz, and they were nothing but trouble. The Terastation Pro kernel is a different build of the same 2.4.20 kernel used in the original Terastation, so the kernel symbol table is slightly different. As such the modules will not load easily.
No big deal right? We know the symbols are still there, the names simply changed a little bit. Just modify the symbol names in the old modules to reflect the new symbol names, all the information you need is in /proc/ksyms. I did this and I was able to load the modules, start the NFS server, and even mount an exported filesystem. Unfortunately, there seems to be a problem, the nfsd threads on the Terastation will die when handling getattr RPCs. That's just no good, don't bother with this approach there are easier ways.
Terasation: 2.4.20_mvl31-ppc_linkstation Terastation Pro: 2.4.20_mvl31-ppc_terastation
Next I opted to try the user space NFS daemon approach. After some experimentation I settled on the pre-packaged ppc version debian shipped some time back. Don't go with the version SuSE shipped it seg faults as as soon as a client mounts. Since it was a pain to round up a working ppc version of all these binary here's a pre-packaged tarball of everything you'll need to get NFS working on a Terastation Pro. These binaries should work fine on an original Terastation as well but I have not been able to test that.
Just untar this in to the root of your Terastation, configure your /etc/exports file, and start the service with the init script.
cd / wget http://www.undeadscientist.com/terastation/nfs-terastation-pro.tgz tar -xzvf nfs-terastation-pro.tgz vi /etc/exports /etc/init.d/nfs-user-server start
Then just mount it on whatever clients you see fit. There was one client side issue I ran in to which is worth mentioning, and that is you may need to explicity mount it as an NFS V2 client. This is due to an issue with the debian build of the user space NFS daemons.
mount -o nfsvers=2 -t nfs 192.168.1.5:/mnt/array1 /mnt
--Abarrow 16:29, 10 May 2006 (CEST) Thanks for the instructions! I also tried to kernel space version on my original Terastation with no luck. I then followed your instructions, and it worked a treat. So, I can confirm that the user space version of NFS works fine on an original Terastation.
--Entropy The user-land nfs referenced above has a 2Gb file size limit because it only speaks the v2 protocol.
I just finish setting this up and it seems to be working, at least nfs service started and if I scan the machine, looks like portmapper, nfs and mountd are running, but I can not get mount to work. I get an access denied when I try to mount. (I am mounting from a Solaris Box- Solaris 9)
Here's a snippet: root@AMS-2811:/# mount -o nfsvers=2 10.24.6.155:/test /test mount: 10.24.6.155:/test on /test - WARNING unknown option "nfsvers=2" nfs mount: 10.24.6.155:/test: access denied root@AMS-2811:/#
Is there any interest in setting up a cross toolchain as the linkstation owners have done (http://linkstationwiki.net/index.php?title=Articles/GeneralCrossToolchain)? Or, I wonder if I could use their cross toolchain to make binaries for my TS.
-- Kimbotha 15:05, 25 October 2006 (CEST): Changed link as linkstationwiki.org link seemed broken. Yes I am interested in having a cross toolchain for the Terastation. Am going to try and build one for myself if I can.
Files missing from GPL archive
I received the Software#GPL_Software from Buffalo but it seems that they left out the hhl-host-rpmconfig* file that contains all the macros used to crossbuild their software.
Does anyone know where I can get a MontaVista 3.1 hhl-host-rpmconfig* file?
Webmin installation on Terastation
I just managed to install Webmin on my Terastation. It was pretty simple, really. Just download the GZIP, unzip/untar into /root then run "./setup.sh /usr/local/webmin". I found it needed to go into /root to make some of the perl scripts to work. The only thing I had to change from the default was the location of PERL. It installs itself as another web server (<your terastation address>:10000). I'm still having a bit of trouble getting it to restart after a reboot, but once it is running you can look around in your system, adjust Samba settings, look at printers, log files, cron files, etc.