Otter: Difference between revisions

From Wildsong
Jump to navigationJump to search
Brian Wilson (talk | contribs)
Brian Wilson (talk | contribs)
Line 98: Line 98:
The big deal with operating system upgrades on the Magnia's is the fan control for the CPU and System fans. Without the proper control software, the fans stay on all the time.
The big deal with operating system upgrades on the Magnia's is the fan control for the CPU and System fans. Without the proper control software, the fans stay on all the time.


==== Requests for next release (should I ever do one!) ====


# Webmin
# Support for the wireless card
# Support for the modem (unlikely as I dont have a phone line)
# Make the fans be speed controlled by default


=== Stuff you need to know ===
=== Stuff you need to know ===

Revision as of 14:01, 5 July 2007

Otter is a Toshiba Magnia SG20.

SLOW

Ubuntu 7.0.4 image made with Acronis "True Image" and the MD5 for the image

FAST -- try this one Ubuntu 7.0.4 image and the MD5 for the image

Goal

Set up as a general purpose home server, replacing as many small dedicated boxes as possible. These boxes include a gateway router, a VOIP telephone adapter, an ethernet switch, and a WiFi access point.

Along the way I am preparing an Ubuntu disk image that other people can try on their SG-20's.

I feel the computers I use should use no more energy than required to get the job done, and they should be as quiet as possible. You should have to check the LED on the front panel to see if it's on.

Using Otter as my SOHO server is part of my Carbon diet.

What I like about the SG20

  1. It came with Linux on it. It can be upgraded and hacked in many ways.
  2. Low power consumption.
  3. It's small.
  4. Has a generic Intel CPU that is fast enough for a SOHO server.*
  5. Uses generic PC components for drives and memory.
  6. Has extra goodies hidden away inside like the video slot.
  7. The serial LCD display.
  • Compare with a Via C3 which is not quite a 686 so it crashes if you try to run 686 code on it.

What I don't like

  1. Noisy slow hard drives
  2. Noisy fans
  3. No externally accessible serial port.
  4. No USB ports.

I know I could hack the daughter board to add a serial port so that I could use it as a serial console but am not willing to invest the time in populating the board to install one. Lack of USB ports is remedied on the newer SG-30.

History

06-2007-- put the Ubuntu image up on this site

03-2007-- I've had it for several years now. I used it with the stock Redhat 7.2 for about a year, then shut it down for a while. When I started writing this page, I did most of the upgrades described here.

Hardware

Disks

It had two 30 GB drives when I got it. I replaced the second hard drive with an 80 GB leftover from a laptop upgrade.

The 30 GB drive is a Toshiba MK3017. The 80 GB drive is a MHV2080AT.

These are both 4200 rpm drives; I'd like to replace one or both with 7200 rpm drives but probably won't for a while.

Memory

I pulled a 512MB PC133 DIMM out of a computer that I got dumpster diving, it works fine. It's not ECC, so I had to hookup an AGP video card and keyboard and turn off ECC in BIOS. While I was in there I set it to boot from the network. I can PXEboot from a Linux desktop system into a rescue mode.

Fans

The stock power supply fan was too noisy, so I hacked out the case a bit for more air flow. Then I put a 80 mm fan on top of the power supply and run it at a low speed.

Software

Boot from network (PXEboot)

You can bypass the hard drive and boot your Magnia from another server on your network. It's not easy, as you have to get BIOS access to switch it on, but once it's set it's set forever.

If you try "PXEboot", you need to set the network adapter in the Magnia to use LAN for booting and you need to use the WAN network port. It's an Intel Etherpro 100. The SG20 will not boot off any of the etherswitch network ports.

I used the "Trinity Rescue Kit", build 279 and was able to ssh into the Magnia. I hacked the TRK startup scripts to allow this; by default it will require entering a new root password from the Magnia console (which is not hooked up, that's the whole point of the netboot.)

Having network booting means that I have another option when the system won't boot from its internal drives. I can netboot, then use ssh to log into the machine and see what happened when it booted, see if it properly detected the hard drives and peripherals and so on.

For example, right now my Magnia is not bootable from the hard drive but I can see this by typing 'dmesg' after booting with TRK.

Probing IDE interface ide0...
hda: TOSHIBA MK3017GAP, ATA DISK drive
hdb: FUJITSU MHV2080AT, ATA DISK drive

This means that it's seeing both drives; I had to change the jumpers on the 80 GB drive from Master to CSEL (cable select) mode by adding a jumper before the Magnia could see it. I just added this drive from a laptop that I upgraded.

Using the TRK, I can mount /dev/hda1 (where I installed Ubuntu) and edit critical system files. The problem turned out to be in the configuration of the network interfaces. I installed Ubuntu onto the 30 GB drive using a VMWare virtual machine and it set up the ethernet interface wrong.

It was finding the network card as '/dev/eth2' instead of '/dev/eth0' so it was not working.

Using an Ubuntu system as a PXEboot server

Ubuntu

I have installed Ubuntu 7.04 Feisty Fawn (upgraded from 6.10 actually).

The big deal with operating system upgrades on the Magnia's is the fan control for the CPU and System fans. Without the proper control software, the fans stay on all the time.


Stuff you need to know

  1. Default IP address on the LAN is 192.168.123.101
  2. Set for DHCP on the WAN port.
  3. Login via ssh, not telnet.
  4. Usernames and passwords: superuser: root / admin regular user: sshuser / user
  5. Firewall is set to accept no connections from outside (WAN).

Set up for image

hda1 3.0 GB /     ext3   The root filesystem
hda2 500 MB       SWAP

This is the /etc/fstab file contents

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/hda1       /               ext3    defaults,errors=remount-ro 0       1
/dev/hda2       none            swap    sw              0       0

Installing Ubuntu from the TIB image

Stuff you need to do this installation

  • A desktop PC
  • Either Windows with Acronis True Image installed or a True Image rescue cd (in which case you don't need Windows) You can download the 15-day trial version (or buy the commercial) of True Image Backup. This is a Windows program, most of the people using SG20's are Windows users and are learning Linux. (If you don't have Windows, get a friend to install the program and make a CDROM for you.)
  • a 2.5 to 3.5 hard drive adapter like this one from Newegg for $6

step by step

  1. Install True Image on the Windows desktop machine.
  2. Download the Ubuntu image (link near top of this page) onto the desktop
  3. Shut down your desktop and SG20
  4. Take the first drive (the one on the right as you look from the front) out of your SG20 and connect it to the desktop using the adapter.
  5. Boot the desktop and start True Image or boot the desktop from the TIB cdrom.
  6. Follow instructions there to restore from the Ubuntu image onto the SG20 hard drive. You want to restore the entire drive from this image.
  7. Power off the desktop
  8. You should be able to unhook the desktop's primary hard drive and connect the SG20 drive in its place and boot from it
  9. You can login as root and partition the remaining space if you want. (see next section.
  10. You could also delete a directory I left around accidentally. At the command prompt type rm -rf /var.old
  11. Shut down again (type "shutdown")
  12. Put the drives back where they belong. Boot the SG20 and it should now be running Ubuntu Server 7.0.4

partitioning remaining space

I left the rest of the drive unused to make it easier to deal with using Acronis True Image as the backup program. The image will wipe the entire hard drive, so after you get the system running you will need to add a partition to use the rest of the drive.

From a command line you'd do something like this. I usually put the new partition at /home and so I have some extra steps in here to copy any existing files under /home to the new partition. otherwise you will not have access to them after mounting the new partition there. (The new partition will block access to the old files underneath /home)

At the root command prompt # you type the parts in bold.

# fdisk /dev/hda   to make space available you must add a partition
n  create a new partition
p  make it a primary partition
3  partition number will be three
the program now prompts for start and size, just accept defaults by hitting 'enter' key'
w   write the new partition table to disk
# reboot  you should reboot so new partition table can take effect
# mkfs.xfs /dev/hda3   make a filesystem on the new partition
# cd /                 change to the root of the file tree
# mv /home /home.OLD   move the existing directory tree aside
# mkdir /home create a place to mount the new partition
# mount /dev/hda3 /home  mount it
# mv /home.OLD/* /home   Move files from old space to new space
add an entry to /etc/fstab so that it will mount after rebooting
# echo "/dev/hda3 /home xfs defaults 0 2" >> /etc/fstab
# rmdir /home.OLD get rid of old directory

more packages

My installation includes the options for DNS and LAMP services. DHCP is turned on. So is ssh.

I suggest you bring the system up disconnected from the Internet, and change these passwords before connecting it. Connect via ssh and use the command

sudo passwd sshuser
sudo passwd root

If you need an ssh client for Windows, I recommend 'putty'.

Other packages that I added

I enabled the 'universe' packages by uncommenting the appropriate line in /etc/apt/sources.list then I added some other things

I recommend the use of the XFS filesystem over EXT3 for large (> 1 GB) partitions. I keep the root filesystem on EXT3 because it makes things easier when using recovery tools. (Grub works better on EXT3, too.)

I also added the packages necessary to compile the lcd/fan control program.

Other changes

Change VERBOSE=no to VERBOSE=yes in /etc/default/rcS so that more information is logged at boot.

Add ons

Firewall

I briefly looked at "Shorewall" and decided it was too complex. "Firestarter" requires an X client.

I eventually gave up on canned packages and wrote a simple set of rules myself.

I put the script in /usr/local/sbin/firewall.sh and call it from /etc/network/interfaces so that it gets loaded when the system brings up the network interface. I also wrote a script /usr/local/sbin/firewall-off.sh that simply turns the firewall rules off, opening the machine up again.

LCD and Fans

The 'lcd' program is available in source code form from the SG20 group area on groups.yahoo.com. I compiled it and hacked in settings for the SG20 (it was written for an SG30) and installed it, now I get proper readings on the lcd display and I can control the fans! THANKS Hans-Michael and Eric! It uses the lm-sensors and smartmonctl packages.

I added a Fahrenheit option to the command line, see /etc/default/lcd Source code is in /usr/src/lcd-2.2/

The lm-sensors package adds the ability to read the system sensors. The standard Ubuntu 2.6 kernel + lm-sensors will give you output like this:

# sensors
via686a-isa-6000
Adapter: ISA adapter
CPU core:  +1.76 V  (min =  +0.06 V, max =  +3.10 V)   
+2.5V:     +2.48 V  (min =  +2.36 V, max =  +2.61 V)   
I/O:       +3.36 V  (min =  +3.12 V, max =  +3.45 V)   
+5V:       +5.03 V  (min =  +4.73 V, max =  +5.20 V)   
+12V:     +11.59 V  (min = +11.35 V, max = +12.48 V)   
CPU Fan:  5720 RPM  (min =    0 RPM, div = 2)          
P/S Fan:  5578 RPM  (min =    0 RPM, div = 2)          
SYS Temp:  +15.6°C  (high =  +146°C, hyst =  +133°C)   
CPU Temp:  +16.2°C  (high =  +146°C, hyst =  +133°C)   
SBr Temp:  +24.8°C  (high =  +141°C, hyst =   +54°C)

The smartmontools package talks to the hard disk drives, and can get the drive temperature if the drive has a sensor. I have two drives, the Toshiba drive does not have any sensor but the newer Fujitsu drive does.

I added code to lcd to allow running the firewall scripts (on and off) from the front panel button, and code that will show the current ip addresses.

Web server

Apache is running but nothing special is installed.

Database server: mysql username and password: root/admin (set with "mysqladmin password admin")

Printing services

I installed cupsys to allow the system to work as a print server. This was one of my primary goals for this system, to allow printing from any of my computers on my little Canon inkjet printer.

This also requires USB support. If you have an SG-30, fine. I happen to have an SG-20 which does not have built in USB ports so I got a PCMCIA card. I plugged in a pair of USB headphones to try the USB card out and the Magnia froze up, so I might end up not using the USB printer after all. Oh well. :-(

I modified /etc/cups/cupsys.conf so that its built-in web server listens on all ethernet addresses, not just localhost. Connect with a browser to port 631, http://mymagnia:631/ for example. You should consider editing /etc/cups/cupsys.conf file to allow connections only from your local network.

Support for Windows clients with Samba

I installed Samba so that you can share file and print services with Windows clients. I installed 'swat' so that you can change the Samba configuration using a web browser. I installed 'inetd' since swat runs as an inetd service. Connect to it with a web browser. It runs on port 901. So for example, http://mymagnia:901/

Update: I installed swat but did not test it so I did not notice the xinetd package was missing. Ray Day reports that you can get swat going by doing the following:

# apt-get install xinetd
# update-inetd --enable swat
# cd /etc/xinetd.d
# nano swat
# default: off 
# description: SWAT is the Samba Web Admin Tool. Use swat \
#              to configure your Samba server. To use SWAT, \
#              connect to port 901 with your favorite web browser.
service swat
{
       port    = 901
       socket_type     = stream
       wait    = no
       only_from = 192.168.2.7
       user    = root
       server  = /usr/sbin/swat
       log_on_failure  += USERID
       disable = no
}

The IP address following "only_from" is the IP of my windows PC. Either put your own desktop computer's ip address or leave the line out to allow unrestricted access.

Ctrl X and say 'Y' to save. Then do:

# /etc/init.d/xinetd restart

Now you can go to http://192.168.x.x:901/ What ever your SG20 IP is. Put in your name and password and you are in.

DHCP

I installed and configured the dhcpd server package. It assigns numbers in the range 192.168.123.101-199. This is set in the file /etc/dhcpd.conf