Difference between revisions of "Airplane"
(→Updating: currently latest version ships with 5.x key) |
(6 hours later, can now snapshot root fs) |
||
Line 1: | Line 1: | ||
A generously donated HP ProLiant DL380p Gen8.<br /> | A generously donated HP ProLiant DL380p Gen8.<br /> | ||
− | + | =Hypervisor= | |
− | + | ==Proxmox VE== | |
A.k.a PVE, an open source type 2 hypervisor based on QEMU/KVM and LXC. [https://pve.proxmox.com/wiki/Main_Page wiki]<br /> | A.k.a PVE, an open source type 2 hypervisor based on QEMU/KVM and LXC. [https://pve.proxmox.com/wiki/Main_Page wiki]<br /> | ||
Apparently takes ~36GB to install, while using ~1.7GB ¯\_(ツ)_/¯.<br /> | Apparently takes ~36GB to install, while using ~1.7GB ¯\_(ツ)_/¯.<br /> | ||
− | + | ===Installation=== | |
# put their ISO on a flash drive | # put their ISO on a flash drive | ||
− | # boot from the | + | #* Alternatively, load an URL to the .iso in iLO's virtual media's CD/DVD-ROM URL field and skip step 3. |
+ | #** The target URL may have to be on the LAN. | ||
+ | # boot from the selected media | ||
# get lucky, else try again | # get lucky, else try again | ||
#* if it ends in <code>can't find cdrom</code> | #* if it ends in <code>can't find cdrom</code> | ||
Line 16: | Line 18: | ||
#* the <code>[firmware bug] ... Corrupted Hw-PMU ... (MSR 38d is 330)</code> message is a negligible warning.[https://forum.proxmox.com/threads/firmware-bug-the-bios-has-corrupted-hw-pmu-resources.12469/] | #* the <code>[firmware bug] ... Corrupted Hw-PMU ... (MSR 38d is 330)</code> message is a negligible warning.[https://forum.proxmox.com/threads/firmware-bug-the-bios-has-corrupted-hw-pmu-resources.12469/] | ||
# continue the installation process | # continue the installation process | ||
− | #* | + | #* If both SAS drives are visible, make a ZFS RAID1 from them. |
#* consider using the hostname <code>airplane</code> | #* consider using the hostname <code>airplane</code> | ||
# upon completion, | # upon completion, | ||
#* the server boots into PVE even if its boot priority is set to USB first | #* the server boots into PVE even if its boot priority is set to USB first | ||
− | #** It won't do this the next time, change boot order if you want to boot from hdd next time. | + | #** It won't do this the next time, change boot order or remove the instalation media if you want to boot from hdd next time. |
#* a web based interface is reachable via <code>https://airplane:8006</code> | #* a web based interface is reachable via <code>https://airplane:8006</code> | ||
#* it is reachable via SSH | #* it is reachable via SSH | ||
#** Address this before exposing this device to The Internet! | #** Address this before exposing this device to The Internet! | ||
− | + | ===Updating=== | |
Without a subscription, apt tries to get the enterprise packages anyway.<br /> | Without a subscription, apt tries to get the enterprise packages anyway.<br /> | ||
Line 36: | Line 38: | ||
[https://forum.proxmox.com/threads/error-401-updating-the-system.34567/#post-174403] | [https://forum.proxmox.com/threads/error-401-updating-the-system.34567/#post-174403] | ||
− | + | =Storage= | |
This server takes 2.5" SAS and SATA drives in G8 (8th generation) trays, and breaks compatibility with G7 and earlier trays.[https://serverfault.com/questions/401976/are-new-hp-gen8-servers-compatible-with-g7-drives]<br /> | This server takes 2.5" SAS and SATA drives in G8 (8th generation) trays, and breaks compatibility with G7 and earlier trays.[https://serverfault.com/questions/401976/are-new-hp-gen8-servers-compatible-with-g7-drives]<br /> | ||
it has 2 "boxes" with 4 bays each, currently bays 1-4 are occupied, bays 5-8 are missing trays, $7.5-8 seems like a typical price (missing chip/LED?). (3D print? [https://www.thingiverse.com/thing:2665391])<br /> | it has 2 "boxes" with 4 bays each, currently bays 1-4 are occupied, bays 5-8 are missing trays, $7.5-8 seems like a typical price (missing chip/LED?). (3D print? [https://www.thingiverse.com/thing:2665391])<br /> | ||
(microserver gen8 tray != proliant gen8 tray)<br /> | (microserver gen8 tray != proliant gen8 tray)<br /> | ||
− | == | + | ==ZFS RAID1== |
− | + | Consists of LD 1 and LD 2, created by proxmox at installation.<br /> | |
− | == | + | ==BTRFS JBOD== |
− | + | Managed in proxmox, created with <code>mkfs.btrfs -d single /dev/sdc /dev/sdd</code>.<br /> | |
− | + | ==SAS/SATA controller== | |
+ | On-board Smart Array P420i SAS/SATA controller.<br /> | ||
− | + | ===Box 1=== | |
− | ==== | + | ====Bay 1==== |
− | + | HP SAS 146GB hard drives (15K rpm)<br /> | |
− | + | Logical Drive 1<br /> | |
− | + | <code>/dev/sda</code><br /> | |
− | |||
− | ====Errors | + | ====Bay 2==== |
+ | HP SAS 146GB hard drives (15K rpm)<br /> | ||
+ | Logical Drive 2<br /> | ||
+ | <code>/dev/sdb</code><br /> | ||
+ | |||
+ | ====Bay 3==== | ||
+ | WD SATA 249GB hard drive<br /> | ||
+ | Logical Drive 3<br /> | ||
+ | <code>/dev/sdc</code><br /> | ||
+ | |||
+ | ====Bay 4==== | ||
+ | WD SATA 160GB hard drive<br /> | ||
+ | Logical Drive 4<br /> | ||
+ | <code>/dev/sdd</code><br /> | ||
+ | |||
+ | ===Errors=== | ||
* Cache Module Status, Failed | * Cache Module Status, Failed | ||
** Persists after fixing (previous) logical drive 02's error, [https://community.hpe.com/t5/ProLiant-Servers-ML-DL-SL/Cache-Module-Status-failed/td-p/6925472 may be a capacitor issue]. | ** Persists after fixing (previous) logical drive 02's error, [https://community.hpe.com/t5/ProLiant-Servers-ML-DL-SL/Cache-Module-Status-failed/td-p/6925472 may be a capacitor issue]. | ||
− | + | ===Array Configuration Utility=== | |
The configuration utility is reachable at boot (<code>F5</code>)<br /> | The configuration utility is reachable at boot (<code>F5</code>)<br /> | ||
There is also a commandline utility equivalent for linux known as <code>ssacli</code>, previously known as <code>hpacucli</code>, setup instructions can be found [https://serverfault.com/a/924919 here].<br /> | There is also a commandline utility equivalent for linux known as <code>ssacli</code>, previously known as <code>hpacucli</code>, setup instructions can be found [https://serverfault.com/a/924919 here].<br /> | ||
− | Passing all drives directly to the hypervisor | + | Passing all drives directly to the hypervisor (HBA) does not seem supported,<br /> |
− | + | the simplest way to achieve this effect seems to be to make Logical Drives consisting of 1 Physical Drive each in the array controller.<br /> | |
+ | It is currently unknown if this results in direct passthrough (is the [[Airplane#ZFS RAID1|RAID]] portable?).<br /> | ||
− | + | =Fans= | |
This server was named for the sound it makes at liftoff.<br /> | This server was named for the sound it makes at liftoff.<br /> | ||
It can run quietly in normal usage yet currently does not, this should be addressed...<br /> | It can run quietly in normal usage yet currently does not, this should be addressed...<br /> | ||
− | [https://wiki.archlinux.org/index.php/fan_speed_control#Fancontrol_(lm-sensors) Fancontrol] | + | [https://wiki.archlinux.org/index.php/fan_speed_control#Fancontrol_(lm-sensors) Fancontrol] cannot find any PWM controls.<br /> |
− | + | =VM setup= | |
− | + | ==Web interface== | |
# Upload an ISO via <code>Datacenter > airplane > local</code> where you can click the <code>upload</code> button and pick a file on your computer. | # Upload an ISO via <code>Datacenter > airplane > local</code> where you can click the <code>upload</code> button and pick a file on your computer. | ||
#* If a suitable ISO is already on the system you can skip this step. | #* If a suitable ISO is already on the system you can skip this step. | ||
Line 81: | Line 99: | ||
# The console tab emulates a display connected to the machine, where you can set up your OS. | # The console tab emulates a display connected to the machine, where you can set up your OS. | ||
− | + | =LXC setup= | |
− | + | ==Web interface== | |
# This step is similar to the first of [[Airplane#VM setup|VM setup]], except you click the <code>template</code> button and select a template for a system or turnkey container to download. | # This step is similar to the first of [[Airplane#VM setup|VM setup]], except you click the <code>template</code> button and select a template for a system or turnkey container to download. | ||
#* for more templates, see [https://pve.proxmox.com/wiki/Linux_Container#pct_container_images PVE's wiki about <code>pveam</code>] | #* for more templates, see [https://pve.proxmox.com/wiki/Linux_Container#pct_container_images PVE's wiki about <code>pveam</code>] |
Revision as of 19:39, 6 January 2019
A generously donated HP ProLiant DL380p Gen8.
Contents
Hypervisor
Proxmox VE
A.k.a PVE, an open source type 2 hypervisor based on QEMU/KVM and LXC. wiki
Apparently takes ~36GB to install, while using ~1.7GB ¯\_(ツ)_/¯.
Installation
- put their ISO on a flash drive
- Alternatively, load an URL to the .iso in iLO's virtual media's CD/DVD-ROM URL field and skip step 3.
- The target URL may have to be on the LAN.
- Alternatively, load an URL to the .iso in iLO's virtual media's CD/DVD-ROM URL field and skip step 3.
- boot from the selected media
- get lucky, else try again
- if it ends in
can't find cdrom
- explicitly booting from USB (
F11
) may help- Issue, keyboard doesn't work unless it's a cold boot (no
F11
on attached keyboard when rebooting)
- Issue, keyboard doesn't work unless it's a cold boot (no
- explicitly booting from USB (
- the
[firmware bug] ... Corrupted Hw-PMU ... (MSR 38d is 330)
message is a negligible warning.[1]
- if it ends in
- continue the installation process
- If both SAS drives are visible, make a ZFS RAID1 from them.
- consider using the hostname
airplane
- upon completion,
- the server boots into PVE even if its boot priority is set to USB first
- It won't do this the next time, change boot order or remove the instalation media if you want to boot from hdd next time.
- a web based interface is reachable via
https://airplane:8006
- it is reachable via SSH
- Address this before exposing this device to The Internet!
- the server boots into PVE even if its boot priority is set to USB first
Updating
Without a subscription, apt tries to get the enterprise packages anyway.
Commenting out the single line in /etc/apt/sources.list.d/pve-enterprise.list
and running
echo "deb http://download.proxmox.com/debian/pve stretch pve-no-subscription" > /etc/apt/sources.list.d/pve-install-repo.list
should fix that.
If not already present, it may also be necessary to run this,
wget http://download.proxmox.com/debian/proxmox-ve-release-5.x.gpg -O /etc/apt/trusted.gpg.d/proxmox-ve-release-5.x.gpg
Storage
This server takes 2.5" SAS and SATA drives in G8 (8th generation) trays, and breaks compatibility with G7 and earlier trays.[3]
it has 2 "boxes" with 4 bays each, currently bays 1-4 are occupied, bays 5-8 are missing trays, $7.5-8 seems like a typical price (missing chip/LED?). (3D print? [4])
(microserver gen8 tray != proliant gen8 tray)
ZFS RAID1
Consists of LD 1 and LD 2, created by proxmox at installation.
BTRFS JBOD
Managed in proxmox, created with mkfs.btrfs -d single /dev/sdc /dev/sdd
.
SAS/SATA controller
On-board Smart Array P420i SAS/SATA controller.
Box 1
Bay 1
HP SAS 146GB hard drives (15K rpm)
Logical Drive 1
/dev/sda
Bay 2
HP SAS 146GB hard drives (15K rpm)
Logical Drive 2
/dev/sdb
Bay 3
WD SATA 249GB hard drive
Logical Drive 3
/dev/sdc
Bay 4
WD SATA 160GB hard drive
Logical Drive 4
/dev/sdd
Errors
- Cache Module Status, Failed
- Persists after fixing (previous) logical drive 02's error, may be a capacitor issue.
Array Configuration Utility
The configuration utility is reachable at boot (F5
)
There is also a commandline utility equivalent for linux known as ssacli
, previously known as hpacucli
, setup instructions can be found here.
Passing all drives directly to the hypervisor (HBA) does not seem supported,
the simplest way to achieve this effect seems to be to make Logical Drives consisting of 1 Physical Drive each in the array controller.
It is currently unknown if this results in direct passthrough (is the RAID portable?).
Fans
This server was named for the sound it makes at liftoff.
It can run quietly in normal usage yet currently does not, this should be addressed...
Fancontrol cannot find any PWM controls.
VM setup
Web interface
- Upload an ISO via
Datacenter > airplane > local
where you can click theupload
button and pick a file on your computer.- If a suitable ISO is already on the system you can skip this step.
- Click
Create VM
at the top right and go through the wizard, select your ISO on the OS tab and fill in specs as needed (try to be conservative). - After clicking
Finish
, your VM should appear to the left underDatacenter > airplane
, clicking it will bring you to a summary, and allow you to start it via the button at the top. - The console tab emulates a display connected to the machine, where you can set up your OS.
LXC setup
Web interface
- This step is similar to the first of VM setup, except you click the
template
button and select a template for a system or turnkey container to download.- for more templates, see PVE's wiki about
pveam
- for more templates, see PVE's wiki about
- This step is again similar to the second of VM setup, with the added requirement of providing a password.
- By default it wants you to provide a static IP, switching this to DHCP may be advantageous.
- See steps the third and fourth steps of VM setup.