Difference between revisions of "Server Build Checklist"

From FreekiWiki
Jump to navigation Jump to search
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
__NOTOC__
 +
 
==Preliminaries==
 
==Preliminaries==
 
'''Check for blown caps''' - Examine all of the capacitors<br>
 
'''Check for blown caps''' - Examine all of the capacitors<br>
Line 10: Line 12:
 
==='''RAID & LVM Setup  (Build ONLY)'''===
 
==='''RAID & LVM Setup  (Build ONLY)'''===
  
'''Install Debian Squeeze''' - Boot to network and install Debian Squeeze to local disks, choose hostname, leave domain name as “fglan”<br>
+
'''Install Debian Wheezy''' - Boot to network and install Debian Wheezy to local disks, choose hostname, leave domain name as “fglan”
 +
 
 
===='''Setup Software RAID'''====
 
===='''Setup Software RAID'''====
*Debian Wiki Guide to Software RAIDs: http://wiki.debian.org/DebianInstaller/SoftwareRaidRoot
+
 
 
'''Partition Disks:'''
 
'''Partition Disks:'''
 
*Create small partition (400-500M) on each device
 
*Create small partition (400-500M) on each device
Line 24: Line 27:
 
*'''For 2-3 disks:'''Setup RAID1, with number of devices equal to number of disks
 
*'''For 2-3 disks:'''Setup RAID1, with number of devices equal to number of disks
 
*'''For 4+ disks:'''Setup RAID6, with number of devices equal to number of disks
 
*'''For 4+ disks:'''Setup RAID6, with number of devices equal to number of disks
 
+
<br>
 
'''Configure LVM''' - configure larger RAID1 or RAID6 array as LVM volume
 
'''Configure LVM''' - configure larger RAID1 or RAID6 array as LVM volume
 
*Create Logical Volume Group with same name as hostname
 
*Create Logical Volume Group with same name as hostname
 
*Select Large RAID array as LVM Volume
 
*Select Large RAID array as LVM Volume
**create volume (4G) named root (mounted at /, ext3 filesystem)
+
**create volume (4G) named root (mounted at /, ext4 filesystem)
 
**create volume (1G) named swap (use as swap)
 
**create volume (1G) named swap (use as swap)
**create volume (remaining) named srv (mounted at /srv, ext3 filesystem)<br><br>
+
**create volume (remaining) named srv (mounted at /srv, ext4 filesystem)<br><br>
 +
*Debian Wiki Guide to Software RAIDs: http://wiki.debian.org/DebianInstaller/SoftwareRaidRoot
 
*Wikipedia RAID article: http://en.wikipedia.org/wiki/RAID
 
*Wikipedia RAID article: http://en.wikipedia.org/wiki/RAID
  
 
==Diagnostics & Databases==
 
==Diagnostics & Databases==
* Confirm that the server can boot from the local disk(s),
+
* '''Boot from local disk(s)'''
* Test any USB ports (front and back),
+
* '''Test USB ports''' (front and back),
* Test the video ports (front and back),
+
* '''Test video ports''' (front and back),
* Test network ports (at terminal: <code>ifconfig eth0 up</code>,<code>ifconfig eth1 up</code>, then <code>tail -f /var/log/syslog</code>, and when you plug and unplug the ethernet cable, you should see reasonable printouts. Ctrl-C to stop the <code>tail</code> command.),
+
* '''Test network ports''' - at terminal: <code>'''ifconfig eth0 up'''</code>, <code>'''ifconfig eth1 up'''</code>, then <code>'''tail -f /var/log/syslog'''</code>, and when you plug and unplug the ethernet cable, you should see reasonable printouts. Ctrl-C to stop the <code>'''tail'''</code> command.<br><br>
* '''QC Only:''' Remove any SATA/SAS drives and give them to your Instructor,
+
**'''QC Only:''' Remove any SATA/SAS drives and give them to your Instructor<br><br>
* Run printme:
+
'''Run printme:'''
** Boot from network,
+
*Boot from network
** Select printme from the network boot menu,
+
** Select printme from the network boot menu
** Log in as guest,
+
** Log in as guest
** Open a terminal,
+
** Open a terminal
** Run printme,
+
** Run printme
** Record whether it's Tower or Rackmount and its size (1U, 2U, 3U, etc.), multiple power supplies, if it's using hardware raid, and anything else noteworthy.
+
** Answer all questions and record anything else noteworthy in the notes section<br><br>
* Fill out the Server Specs sticker based on whether you are doing Build or QC:
+
'''Fill out the Server Specs sticker''' based on whether you are doing Build or QC:
** '''BUILD:'''
+
* '''For BUILD:'''
*** Put System ID on server specs sticker,
+
** Put System ID on server specs sticker
*** Processor speed (GHz) and type (Xeon, Opteron),
+
** Number of physical processors and number of cores ''per'' processor
*** Number of physical processors and number of cores per processor,
+
** Processor speed (''GHz'')  
*** Number and type (DDR, DDR2) of RAM slots,
+
** Circle processor type (''Xeon, Opteron, Core 2, Other'')
*** Number of RAM sticks with their type, speed, and size,
+
** Total amount of included RAM
*** Number of hard drive bays and their interfaces (IDE, SCSI, SATA),
+
** Total number of RAM slots on board
*** Do ''not'' print!  Instead, put your Volunteer ID on a piece of tape on the system.
+
** Number of included RAM sticks with their speed and size
** '''QC:'''
+
** Circle type of RAM (''DDR, DDR2, DDR3'')
*** Confirm the accuracy of information already on the Specs sticker,
+
** Circle type of DIMM (''ECC, FB-DIMM, etc.'')
*** The total amount of installed RAM,
+
** Number of hard drive bays  
*** The number, type, and size of installed hard drives (IDE & SCSI only),
+
** Circle hard drive bay type (''IDE, SCSI, SATA, SAS'')
*** Print the printme, and tape it to the top of the system.
+
** Number and size of included hard drives
* Have your Instructor look over the printme,
+
** Record anything notable, like Hardware RAID support, in the notes section
 +
** '''Do ''not'' print!''' Instead, put your Volunteer ID on a piece of tape on the system<br><br>
 +
* '''For QC:'''
 +
** Confirm the accuracy of information already on the Server Specs sticker
 +
** Number and size of included hard drives
 +
** Circle whether an OS is installed (''none if hard drives removed!'')
 +
** Write the '''System ID#''' on a Server Tag sticker (small labels marked '''S1, S2, etc.''') and stick it to the front of the chassis.
 +
** '''Print the printme''' - Write the number from the Server Tag in the upper right-hand corner of the printme, and give it to your instructor.<br><br>
 +
 
 
* Move the system to the Server Build KVM and run Memtest, if it hasn't already been done.
 
* Move the system to the Server Build KVM and run Memtest, if it hasn't already been done.
 
* Consult your Instructor for a new project!
 
* Consult your Instructor for a new project!
 
<noinclude>[[Category:Server_Build]]</noinclude>
 
<noinclude>[[Category:Server_Build]]</noinclude>

Latest revision as of 11:30, 15 May 2013


Preliminaries

Check for blown caps - Examine all of the capacitors
Check battery - Confirm that the CMOS battery is at least 3 volts
Boot Process - Ensure that the server boots properly in the following ways:

  • Boots from CD - use an Ubuntu Live CD, leave Ubuntu running for next step
  • Boots automatically after power loss - while still in Ubuntu from the previous step, unplug all power cords (and the keyboard for the next step) from the server to simulate a sudden power loss. It should reboot automatically - if not, check BIOS settings.
  • Boots without keyboard - the server may report a "Keyboard failure" error - this is okay as long it boots successfully without human intervention, such as "press key X to continue..."


RAID & LVM Setup (Build ONLY)

Install Debian Wheezy - Boot to network and install Debian Wheezy to local disks, choose hostname, leave domain name as “fglan”

Setup Software RAID

Partition Disks:

  • Create small partition (400-500M) on each device
    • primary partition at the beginning of the drive
    • use as “physical volume for RAID”
    • set as bootable
  • Create large partition (all remaining space) on each device
    • primary, not bootable

Setup RAID for small partitions: RAID1 (bootable) with the number of devices equal to number of disks
Setup RAID for large partitions:

  • For 2-3 disks:Setup RAID1, with number of devices equal to number of disks
  • For 4+ disks:Setup RAID6, with number of devices equal to number of disks


Configure LVM - configure larger RAID1 or RAID6 array as LVM volume

Diagnostics & Databases

  • Boot from local disk(s)
  • Test USB ports (front and back),
  • Test video ports (front and back),
  • Test network ports - at terminal: ifconfig eth0 up, ifconfig eth1 up, then tail -f /var/log/syslog, and when you plug and unplug the ethernet cable, you should see reasonable printouts. Ctrl-C to stop the tail command.

    • QC Only: Remove any SATA/SAS drives and give them to your Instructor

Run printme:

  • Boot from network
    • Select printme from the network boot menu
    • Log in as guest
    • Open a terminal
    • Run printme
    • Answer all questions and record anything else noteworthy in the notes section

Fill out the Server Specs sticker based on whether you are doing Build or QC:

  • For BUILD:
    • Put System ID on server specs sticker
    • Number of physical processors and number of cores per processor
    • Processor speed (GHz)
    • Circle processor type (Xeon, Opteron, Core 2, Other)
    • Total amount of included RAM
    • Total number of RAM slots on board
    • Number of included RAM sticks with their speed and size
    • Circle type of RAM (DDR, DDR2, DDR3)
    • Circle type of DIMM (ECC, FB-DIMM, etc.)
    • Number of hard drive bays
    • Circle hard drive bay type (IDE, SCSI, SATA, SAS)
    • Number and size of included hard drives
    • Record anything notable, like Hardware RAID support, in the notes section
    • Do not print! Instead, put your Volunteer ID on a piece of tape on the system

  • For QC:
    • Confirm the accuracy of information already on the Server Specs sticker
    • Number and size of included hard drives
    • Circle whether an OS is installed (none if hard drives removed!)
    • Write the System ID# on a Server Tag sticker (small labels marked S1, S2, etc.) and stick it to the front of the chassis.
    • Print the printme - Write the number from the Server Tag in the upper right-hand corner of the printme, and give it to your instructor.

  • Move the system to the Server Build KVM and run Memtest, if it hasn't already been done.
  • Consult your Instructor for a new project!