I have installed Debian testing on a hard drive connected to my Linutop1. I use it as my primary home server as a NAS with apache, sshd and other basic stuff. See Tutorials/Debootstrap for a nice install guide.
More than one drive
I want to connect more than one disk to it, but this is far from ideal. The Linutop will choose a random disk to boot from, making server usage extremely unreliable. I am seriously hoping the Linutop guys will fix this, this isn't actually cheap hardware.
- Rob Wonders: Can you Label the Partitions?
- (not an Linutop user just interested). On other systems with 2.6 kernel, rather than use device names (which change) or UUID's which are long and hard to remember, I use partition labels, normally -L <PARTITION-NAME> (mkreiserfs is -l though). Then in fstab(5) LABEL=<PARTITION-NAME> instead of /dev/disk/by-lable/<PARTITION-NAME>. This relies on udev being set up, to make the devices probably...
- Just an idea, I've done it with swap, ext2, ext3, reiserfs & vfat. It lets me move disks around on my server & play systems. Rob 2007/11/12
- I would still need /boot, /etc and an MBR on all drives, right? Henrik 15:21, 14 November 2007 (CET)
- Did you get that to work yet? I tried copying just /boot to my other disk (just one partition on each) and running this in the GRUB shell: setup --stage2=/boot/grub/stage2 -- KevinLyda 17:53, 2 January 2008 (CET)
- User:jcurl: With Ubuntu Hardy 8.04.1 and the Linutop2 this is immediately obvious as it mounts the internal flash and tries to boot from that (and doesn't work). I've just added an entry Tutorials/Debootstrap#Linutop2_and_Ubuntu_Hardy to the installation page and I've got it working on my Linutop2 so it boots reliably. The kernel said the internal flash was /dev/sda and my USB stick was /dev/sdb and comes on line a few seconds after initramfs starts its thing.
Random USB disconnects
Lately, my Linutop has disconnected my USB primary drive, resulting in a unavailable box. The console shows "scsi 1:0:0:0: rejecting I/O to dead device". I need to unplug/plug the power on the Linutop and harddrive to make it available again.
I have no idea why this happens, I am suspecting that high i/o during updatedb makes the USB chipset choke.
No battery backup for clock
Upon boot or restart, the clock is reset to 1-1-1970. This is not very ideal, since an ext2 filesystem with default options will force a fsck on every boot. Use "tune2fs -i 0" and install ntpd to remedy this.