LS Pro Debootstrap Howto
This article describes the procedure to install Debian on a Linkstation Pro or Kurobox Pro by creating a minimal installation on a Linux workstation and transferring it to a Linkstation. Access via serial cable is not required.
To run this procedure you will need a computer with some form of Linux installed on it, preferably Debian or a variant of it such as Ubuntu. The CPU architecture isn't relevant, so if you have another Linkstation with Debian on it that will work fine. Before you start, you need to install two packages: debootstrap and some form of HTTP or FTP server. If you don't have a server installed, I recommend vsftpd.
For these instructions to work your Pro you must be running at least a 2.6.16 kernel, or else the chroot command will not work. I recommend using the latest upstream Linux kernel instead of a Buffalo or Marvell modified one; you can follow these instructions to install a recent one. It is a good idea to adjust the size of your partitions before following this procedure, as the /dev/sda2 partition is very small by default. I suggest making it at least 5 GB. You also need to be using a modified initrd in order to boot the custom distribution.
Create the Stage 1 image
On your Linux workstation, pick a directory that you will stage the Debian install in. For my example I will use /tmp/debian. Become root and use debootstrap to create a minimal Debian installation in this directory:
su mkdir /tmp/debian debootstrap --foreign --arch armel lenny /tmp/debian
Now make a tarball from the installed files:
cd /tmp/debian tar cvzf ../debian.tar.gz *
Move the tarball to wherever your FTP server serves files from, for example /home/ftp.
Unpack the image and complete the debootstrap process
Now boot your Pro in EM mode and telnet to it. I'm assuming that you want to overwrite the installed system on /dev/sda2. If that's not what you want, don't run the mkfs command. Instead, choose another directory to install to.
I use the ext3 filesystem for this example because it's very likely that your kernel has support for it. If you'd like to use a different filesystem, it's up to you to determine whether the kernel you're using supports it.
Make a new filesystem on /dev/sda2 and mount it. Download the tarball from your FTP server, and unpack the minimal Debian image. Then chroot into it and complete the bootstrap process:
mke2fs -j /dev/sda2 mount -t ext3 /dev/sda2 /mnt/disk1 cd /mnt/disk1 wget ftp://ip.of.ftp.server/debian.tar.gz tar xvzf debian.tar.gz chroot /mnt/disk1 /debootstrap/debootstrap --second-stage
The last step may take a while, but you now have a full Debian system installed on your Linkstation. Don't reboot yet, though... we don't have a working system!
Configure the system and install additional software
There are two files that need to be configured before the system will run correctly, /etc/fstab and /etc/network/interfaces. The first describes the layout of filesystems on your disk; the second, as the name implies, configures network interfaces.
After mounting the proc filesystem, you can use chroot to enter the system and modify the configuration files:
mount -t proc proc /mnt/disk1/proc chroot /mnt/disk1 /bin/bash vi /etc/fstab vi /etc/network/interfaces
My suggested /etc/fstab file contains the layout you wound up with if you followed the instructions above.
/dev/sda1 /boot ext3 noatime 1 2 /dev/sda2 / ext3 noatime 0 1 /dev/sda5 none swap sw 0 0 /dev/sda6 /srv ext3 noatime 0 0
/srv is the location recommended by the FHS for data stored on the system by and for services such as FTP and Samba. Your partition may be formatted as XFS; if this is the case I recommend changing it to ext3, as XFS has known bugs on the ARM9 platform.
This /etc/network/interfaces will bring up the network device using DHCP.
auto lo eth0 iface lo inet loopback iface eth0 inet dhcp
You also need to install micro_evtd, which keeps the watchdog timer in the LS Pro happy, adjusts the fan speed for you, and such. The binaries and configuration files for micro_evtd are provided by lb_worm and stored in the downloads area.
cd / wget http://buffalo.nas-central.org/download/Users/goat/micro_evtd-20080531.tar.gz tar xvzpf micro_evtd-20080531.tar.gz rm micro_evtd-20080531.tar.gz
Next, update the package lists and install sshd so that you can access the Pro over the network after the install is done, and udev, the dynamic /dev manager:
apt-get update apt-get install ssh udev invoke-rc.d ssh stop
If you have a serial cable attached and wish to login via that, open /etc/inittab and ensure it has a line that looks like:
T0:23:respawn:/sbin/getty -L ttyS0 115200
Finally, change the root password, set the hostname for the next boot, exit the chroot, unmount the disk, and reboot. Your new system is ready!
passwd echo 'LS-GL' > /etc/hostname exit umount /mnt/disk1/proc /mnt/disk1 reboot
On reboot, it probably is a good idea to turn recommends off.
as root do -- echo "APT::Install-Recommends 0;" >/etc/apt/apt.conf.d/99recommends
Then you will need the following.
*DATA BACKUP - NO ONE BUT YOU CAN BE BLAMED IF YOU FORMAT, MOVE, LOOSE OR DESTROY DATA AND DO NOT HAVE A BACKUP. *BACKUP OF the WORKING /boot partition (files).
* The debootstrapped debian armel lenny tar file you made (or other method of storing it). * Enough free disk space to place the new rootfs on. * micro_evtd-20080531.tar.gz There is a debian package of this, but it needs to be configured from the last time i looked at it. *be able to get into and out of safe mode.
* The files below. * I suggest you give the root filesystem 2GB or the larger 5GB as stated above. For a linkstation 2gb should be fine. However, it is probably safer to give it 5GB.
My hard is paritioned disk looks like this. I am using ext3 for my data and rootfs file systems.
Device Boot Start End Blocks Id System /dev/sda1 1 37 297171 83 Linux /dev/sda2 38 281 1959930 83 Linux /dev/sda4 282 38913 310311540 f W95 Ext'd (LBA) /dev/sda5 282 318 297171 82 Linux swap / Solaris /dev/sda6 319 38913 310014306 83 Linux
See the custom partitions page for how to get this kind of a setup. (it is referenced above).
My Fstab looks like # /etc/fstab: static file system information. # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 #none /dev/pts devpts gid=5,mode=20 0 0 tmpfs /tmp tmpfs size=10M,mode=1777 0 0 /dev/sda1 /boot ext3 defaults,noatime 1 2 /dev/sda2 / ext3 defaults,noatime,errors=remount-ro 0 1 /dev/sda5 none swap sw 0 0 /dev/sda6 /mnt/disk1 ext3,acl defaults,noatime,nodiratime 0 0 (you may not want nodiratime)
Either get them this way or download them from ---lenny_REQ.tar
*lenny_REQ.tar md5sum c3bfb83fdeeb7020d6644af11245a1cf sha1sum 5cb463e7ee6861d4d862546fc3f34e02fc60b0b4 sha256sum lenny_REQ.tar f6044746e9dec3c42fc9fb013193aabaa8fe320504a9714b0077f9713a981420
*1 lb_worm's new initrd / image. md5sum 885b1b61f0f00a9459c434dd47ef32f5 sha1sum ac844bd0c7bdab225b846b57a407a53cc74437ea sha256sum 9281ab4ade3139d4dbc7e1b2c87f226f000641092f5c4bd047b5534959161ca2
*2 [http://buffalo.nas-central.org/download/Users/davy_gravy/kernelpackages/2.6.26- update_full_debian.tgz You should use a a new kernel (2.6.26)]
uImage-2.6.26 md5sum a2ec665585d248ba63fb043f6d59ae37 sha1sum 2ffc50231d4141bcbb1d82d6b1504fe1411acb2b sha256sum 9c86038c3cf48d2667d62bdaabe3b745ea050eb86710c732cd15c91af80610da
*3 modules from the kernel. (get from either the bundle i have made or from davey's lenny distribution).
lb_worm's image does not require to change the bootloader, but there comes no kernel with that image. So take a kernel from one of davy_gravy's packages.
Once you have all of this.
Reboot / get into EM mode. I suggest you copy the files to another computer (so you can pick up the pieces). Rename the boot_options to the correct name, rename initrd.buff... to the correct name remove the link from the current kernel to the uImage2.6.26 (2.6.26 kernel). mount /dev/sda2 untar the lenny armel tar / other file / files to it. extract the modules.tar / modules to /lib/modules (move to the appropriate place).
Reboot. And hope it works ! Oh and if you find that the linkstation is rebooting and beeping you can disable the watchdog microapl -a system_set_watchdog 255 . Others have reported that decreasing or turning off the polling will also fix the problem.