Open Stock Firmware LS-XHL
Why a new page for the XHL?
Unfortunately to open the firmware of a XHL depends on the release of the firmware currently running on the machine.
The XHL firmware above release 1.10 do NOT contain telnetd or sshd anymore. So acp_commander can not enable telnet access due to the lack of the executable.
If you have firmware 1.10 or lower, you should be able to follow the hints in Open_Stock_Firmware to get telnet access. But with firmware 1.20 or above luck is not on your side.
Attention: What ever you do, you do it on your own risk
What to do first in case of upgrading from 1.10?
If you want to upgrade the firmware from 1.10 to something newer, you should take care of some things before, or you will loose the ability to get telnet access to your XHL.
The assumption is, that you have a share called share.
- You already should have acp_commander.jar. If not: http://downloads.nas-central.org/TOOLS/ALL_LS_KB_ARM9/ACP_COMMANDER/acp_commander.jar.
- Save some executables from the 1.10 firmware:
mkdir /mnt/disk1/share/xhl cd /mnt/disk1/share/xhl mkdir bin cp /bin/su bin/ mkdir -p usr/local/bin mkdir -p usr/local/sbin cd /mnt/disk1/share/xhl/usr/local/sbin cp /usr/local/sbin/telnetd . cp /usr/local/sbin/sshd . cd /mnt/disk1/share/xhl/usr/local/bin cp /usr/local/bin/ssh* . mkdir -p etc/init.d cd /mnt/disk1/share/xhl/etc/init.d cp /etc/init.d/sshd.sh .
Now you are prepared to upgrade to 1.20 or higher.
How to get telnet working in 1.20 or higher
The assumption is, that your XHL is already running firmware 1.20 or higher and that you are aware of handling command line executables and stuff like this, if you are used to a Unix flavor. For the windows noobs I will add some windows hints also.
- Disable the XP/Vista/7 firewall or you will get sockettimeout errors.
- Start a command line via "Start" - "Run" - "cmd.exe". Everything else is done within the command line window.
- Ensure you have a valid java installation by checking the version:
- Change to the place where you placed acp_commander.jar (I assumed it is on c:\tmp\xhl\) via:
- Get into an interactive acp_commander session (all commands will be executed as root in interactive mode):
java -jar acp_commander.jar -t <XHL IP address> -ip <XHL IP address> -pw <password of the web admin user> -s
- In interactive mode you should do the following (attention: cd does not work in interactive mode!):
cp /mnt/disk1/share/xhl/usr/local/sbin/telnetd /usr/local/sbin/ ln -s /usr/local/sbin/telnetd /usr/sbin/telnetd cp /mnt/disk1/share/xhl/usr/local/sbin/sshd /usr/local/sbin chmod 4555 /bin/su echo "telnet stream tcp nowait root /usr/sbin/telnetd /usr/sbin/telnetd" >> /etc/inetd.conf chmod 644 /etc/profile reboot
Now your XHL should reboot. After a minute or so, you should be able to telnet to your XHL using the user admin (the same admin you use to access the web configuration of your XHL).
I haven't found a way to let root login via telnet, but you can simply call
after logged in as user admin, to switch to user root.
The installation of the addons.tar is identical to the non-XHL LS-PRO except that /bin/su will get overridden by a version within the addon.tar which is not working properly. So you have to get into the acp_commander interactive mode again after the installation of addon.tar. Do the following:
java -jar acp_commander.jar -t <XHL IP address> -ip <XHL IP address> -pw <password of the web admin user> -s cp /mnt/disk1/share/xhl/bin/su /bin/ chmod 4555 /bin/su
Now you should have telnet access to your XHL. Have fun!
How to get the executables from release 1.10 if you already upgraded to 1.20?
Get the firmware release 1.10 from Buffalo: http://www.buffalo-technology.com/support/getfile/?lsxhl-110.zip
Unpack the zip and unzip hddrootfs.img then. Use the password:
Now you can copy the extracted executables to your XHL share.
Alternatively you can download this file: http://downloads.buffalo.nas-central.org/Users/kenatonline/xhl-110-telnet-ssh-clearaddon.tar.gz
It contains the executables and a patched (unnecessary binaries removed) addons.tar which you can copy into your acp_commander directory. The excutable "su" is still part of this, in case you already used the addons.tar from acp_commander (via automatic download). It also contains the optware bootstrap file for the Marvell Kirkwood feed.
How to convert the data partition from XFS to EXT3?
At least with firmware release 1.20, the firmware can handle a ext3 formatted root filesystem as well as a ext3 formatted data partition without "patching" anything serious.
The information of the format of the root filesystem and the data partition seems to be stored in non-volatile ram. There are two applications handling the reading and writing to this storage, named dumpnf and setnf.
If one looks into the initrd.buffalo, he can find a dirctory /root/.nas_features which contains preconfigured information for different linkstation models.
For the following operations you should login as root (su -).
To ensure to take the right information we dump the current content of the storage to a file:
dumpnf > /etc/nas_feature
Now edit the file /etc/nas_feature and change the following setting:
Now one can format the data partition (/dev/disk1_6 aka. /mnt/disk1), but do not forget to save the data before, because you will loose everything on this partition.
umount /mnt/disk1 mkfs.ext3 -m 0 /dev/disk1_6 mount -t ext3 /dev/disk1_6 /mnt/disk1
Now you should restore your saved data.
The last thing we have to do, is saving the changed settings into the non-volatile ram:
setnf < /etc/nas_feature
Atfer a reboot, one should check with:
that he gets this:
rootfs on / type rootfs (rw) /dev/root on / type xfs (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw) /dev/ram1 on /mnt/ram type tmpfs (rw) /dev/sda1 on /boot type ext3 (rw,data=ordered) usbfs on /proc/bus/usb type usbfs (rw) /dev/disk1_6 on /mnt/disk1 type ext3 (rw,data=ordered)
The last line is the important one. It says the format is ext3. Voila.
To change the root filesystem from xfs to ext3 is analog to the former stuff, but one has to get into EM mode to access the partition sda2.
The setting to change is:
Because I decided to change only the filesystem of my data partition to ext3, I do not explain the change of the root filesystem in detail.