build:debian:redhook
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
build:debian:redhook [2010/11/13 15:05] SLUUG Administration |
build:debian:redhook [2010/11/13 15:15] (current) SLUUG Administration |
||
|---|---|---|---|
| Line 62: | Line 62: | ||
| /dev/hda 153936 153936 0 100% /target/media/cdrom0 | /dev/hda 153936 153936 0 100% /target/media/cdrom0 | ||
| - | ====Disk Array==== | ||
| - | |||
| - | On budlight, we have recently (May 2009) added a Clariion DAE (http://support.dell.com/support/edocs/stor-sys/dae/fcdae/fchardwr.pdf). The enclosure has an EMC label on it, but the documentation we have is for the same device rebranded and resold through Dell. We have it connected to budlight via a QLogic ql2100 HBA. The Clariion has 10 bays, each with a 36G FCAL drive. | ||
| - | |||
| - | To make budlight see the drives in the DAE, we needed to install the qlogic-firmware package. | ||
| - | |||
| - | <code root> | ||
| - | # apt-get install firmware-qlogic | ||
| - | </code> | ||
| - | |||
| - | After a reboot, budlight saw /dev/sd[a-j] | ||
| - | |||
| - | We have assembled the drives into a RAID-5 array with one hot spare. This should give us roughly 300G, which is a huge increase in available storage. | ||
| - | |||
| - | The assembly command is: | ||
| - | |||
| - | <code root> | ||
| - | # mdadm --create /dev/md0 --level=5 --raid-devices=9 --spare-devices=1 /dev/sd[a-j]1 | ||
| - | </code> | ||
| - | |||
| - | /proc/mdstat will show the progress of building the array. This is what it looks like when it is fully built: | ||
| - | |||
| - | <code root> | ||
| - | Personalities : [raid6] [raid5] [raid4] | ||
| - | md0 : active raid5 sdi1[8] sdj1[9](S) sdh1[7] sdg1[6] sdf1[5] sde1[4] sdd1[3] sdc1[2] sdb1[1] sda1[0] | ||
| - | 279302144 blocks level 5, 64k chunk, algorithm 2 [9/9] [UUUUUUUUU] | ||
| - | |||
| - | unused devices: <none> | ||
| - | |||
| - | </code> | ||
| - | |||
| - | After /proc/mdstat shows that md0 is fully assembled, we'll update mdadm.conf: | ||
| - | |||
| - | <code root> | ||
| - | # mdadm --detail --scan >> /etc/mdadm/mdadm.conf | ||
| - | </code> | ||
| - | |||
| - | In order to gain flexibility with the EMC DAE, we will need to install some additional packages: | ||
| - | |||
| - | <code root> | ||
| - | # apt-get install lvm2 dmsetup | ||
| - | </code> | ||
| - | |||
| - | This will allow us to create LVMs which can be resized as needed out of the logical RAID-5 device on the Clariion. | ||
| - | |||
| - | Label /dev/md0 as a physical volume: | ||
| - | |||
| - | <code root> | ||
| - | # pvcreate /dev/md0 | ||
| - | </code> | ||
| - | |||
| - | Create the volume group: | ||
| - | |||
| - | <code root> | ||
| - | # vgcreate sluug /dev/md0 | ||
| - | </code> | ||
| - | |||
| - | Create a 40G logical volume in the sluug VG called 'rsnapshot': | ||
| - | |||
| - | <code root> | ||
| - | # lvcreate -L 100G -n rsnapshot sluug | ||
| - | </code> | ||
| - | |||
| - | Format the rsnapshot volume and mount it: | ||
| - | |||
| - | <code root> | ||
| - | # mke2fs -j /dev/mapper/sluug-rsnapshot | ||
| - | # mkdir /rsnapshot | ||
| - | # mount /dev/mapper/sluug-rsnapshot /rsnapshot | ||
| - | </code> | ||
| - | |||
| - | Revel in the newly available space: | ||
| - | |||
| - | <code root> | ||
| - | df -h /dev/mapper/sluug-rsnapshot | ||
| - | Filesystem Size Used Avail Use% Mounted on | ||
| - | /dev/mapper/sluug-rsnapshot | ||
| - | 40G 177M 38G 1% /rsnapshot | ||
| - | </code> | ||
| - | |||
| - | And add the following to /etc/fstab: | ||
| - | |||
| - | <code root> | ||
| - | /dev/mapper/sluug-rsnapshot /rsnapshot ext3 defaults 0 0 | ||
| - | </code> | ||
| ===== Package Selection ===== | ===== Package Selection ===== | ||
| Line 153: | Line 68: | ||
| This system is intended to be a server, and should never run any X programs. Any GUI-type administration should be done over HTTPS. So we did not install any X server or X client programs. | This system is intended to be a server, and should never run any X programs. Any GUI-type administration should be done over HTTPS. So we did not install any X server or X client programs. | ||
| + | ===== Networking ===== | ||
| - | ===== Networking ===== | + | [TODO: Adjust these values for RedHook when available] |
| Make sure that the network settings are all correct. Review the settings in ''/etc/network/interfaces''. It should look something like this (for Bud at Primary.Net): | Make sure that the network settings are all correct. Review the settings in ''/etc/network/interfaces''. It should look something like this (for Bud at Primary.Net): | ||
| Line 181: | Line 97: | ||
| Ensure that you can connect to some Internet hosts to make sure that your configuration is correct. If you run into problems, try these troubleshooting steps: | Ensure that you can connect to some Internet hosts to make sure that your configuration is correct. If you run into problems, try these troubleshooting steps: | ||
| - See if you can ping another system on the same subnet. | - See if you can ping another system on the same subnet. | ||
| - | * NOTE: The firewalls on Bud and BudLight don't allow responding to ping, so don't try pinging them. | + | * NOTE: The firewall on RedHook doesn't allow responding to ping, so don't try pinging it. |
| - See if you can ping the default gateway. | - See if you can ping the default gateway. | ||
| - See if you can ping the DNS server. | - See if you can ping the DNS server. | ||
| Line 187: | Line 103: | ||
| - See if you can look up a name (using ''dig'' or ''nslookup'') and get an IP address back. | - See if you can look up a name (using ''dig'' or ''nslookup'') and get an IP address back. | ||
| - See if you can connect to an Internet service (using ''ssh'', ''wget'', or some other program). | - See if you can connect to an Internet service (using ''ssh'', ''wget'', or some other program). | ||
| - | |||
| ===== Hostname ===== | ===== Hostname ===== | ||
| + | |||
| + | [TODO: Adjust this section for redhook] | ||
| Ensure that the hostname is correct: | Ensure that the hostname is correct: | ||
| Line 197: | Line 114: | ||
| If it is not, change it: | If it is not, change it: | ||
| <code rootshell> | <code rootshell> | ||
| - | hostname bud | + | hostname redhook |
| </code> | </code> | ||
| Line 371: | Line 288: | ||
| See the general [[todo | TODO]] page for more work to be done. | See the general [[todo | TODO]] page for more work to be done. | ||
| - | |||
| - | |||
| ===== Credits ===== | ===== Credits ===== | ||
| - | James Pattie led the installation effort, 2005-02-19. | + | Lee Lammert led the inital installation effort, 2010-11-13, assisted by Jeff Muse and Don Ellis. |
| - | + | ||
| - | Lots of other folks helped in the decision-making and installation process. | + | |
| - | + | ||
| - | John House and Craig Buchek were the primary documentors. | + | |
| - | + | ||
| - | Craig Buchek and Jeff Muse led the installation effort on the production servers, 2005-07-30. | + | |
| - | + | ||
| - | Lee Lammert led the effort to move the systems to Primary Networks, 2006-01-16. | + | |
| - | + | ||
| - | Craig Buchek rebuilt Bud with Debian 4.0 on 2007-05-30. Installation took about 2 hours, 1 hour of which was correcting a networking issue due to incorrectly documented network settings. | + | |
| - | Craig Buchek rebuilt Bud with Debian 4.0r3 on 2008-03-02. Installation of the OS took about 30 minutes, with good documentation. | + | Don Ellis was the primary documentor. |
| - | See [[http://www.howtoforge.com/perfect_setup_debian_etch | this HowtoForge document]] for an excellent step-by-step guide to installing Debian 4.0, with screenshots. | + | See [[http://www.howtoforge.com/perfect-server-debian-lenny-debian-5.0-with-bind-and-dovecot-ispconfig-3 | this HowtoForge document]] for an excellent step-by-step guide to installing Debian 5.0, with screenshots. |
build/debian/redhook.1289682312.txt.gz · Last modified: 2010/11/13 15:05 by SLUUG Administration
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
