hardware:apama
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| hardware:apama [2016/03/01 21:58] – created dgalloway | hardware:apama [2020/01/30 15:55] (current) – djgalloway | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== apama{001, | + | ====== apama{001, |
| https:// | https:// | ||
| + | |||
| + | This hardware was retired on 30JAN2020 to make room for new [[hardware: | ||
| ===== Summary ===== | ===== Summary ===== | ||
| - | apama001 and apama002 are two nodes in an HP SL4540 Gen8 chassis. | + | apama001 and apama002 are two nodes in an HP SL4540 Gen8 chassis. Both nodes are running Xenial because the systems [[http:// |
| - | As of this writing, they need to be reinstalled with (probably*) Fedora | + | apama001 is running RHEL and the plan is to use it as a docker host. apama002 is an OSD node in the [[services: |
| - | The iLOs are currently not accessible. Probably not cabled or switch port config required. | + | The iLOs are accessible |
| - | //* Fedora because it's good to have multiple OSes running OSDs in the same cluster.// | + | The systems were updated |
| ===== Hardware Specs ===== | ===== Hardware Specs ===== | ||
| + | | ^ Count ^ Manufacturer | ||
| + | ^ Chassis | ||
| + | ^ Mainboard | ||
| + | ^ CPU | 2 | Intel | Xeon(R) CPU E5-2407 0 @ 2.20GHz | ||
| + | ^ RAM | 12 DIMMs | Not Specified | ||
| + | ^ HDD | 1x | HP | MM0500GBKAK | ||
| + | ^ HDD | 25x | HP | MB3000GBKAC | ||
| + | ^ SSD | 0 | ||
| + | ^ NIC | 2 | Intel | I350 Gigabit Network Connection | ||
| + | ^ NIC | 1 | Mellanox | ||
| + | ^ BMC | 1 | HP | iLO | | Firmware 1.13 | | ||
| + | |||
| + | ===== Quirks ===== | ||
| + | I was able to install Fedora23 on apama001 but still got Red Screen of Death and " | ||
| + | |||
| + | What fixed it was finding the proper root drive and manually booting to it in a grub rescue prompt. | ||
| + | |||
| + | < | ||
| + | grub> ls (hd0, | ||
| + | |||
| + | vmlinuz-4.2.3-300.fc23.x86_64 System.map-4.2.3-300.fc23.x86_64 config-4. 2.3-300.fc23.x86_64 initramfs-4.2.3-300.fc23.x86_64.img initramfs-0-rescue-ba8d c4c42e5a4ec483a635961112dfd8.img vmlinuz-0-rescue-ba8dc4c42e5a4ec483a635961112d fd8 initrd-plymouth.img | ||
| + | |||
| + | grub> set root=(hd0 <tab> | ||
| + | Possible partitions are: | ||
| + | |||
| + | Device hd0: No known filesystem detected - Sector size 512B - Total size 488386584KiB | ||
| + | |||
| + | Partition hd0,msdos1: Filesystem type ext* - Last modification time | ||
| + | grub> set root=(hd0, | ||
| + | grub> linux / | ||
| + | grub> initrd / | ||
| + | grub> boot | ||
| + | </ | ||
| + | |||
| + | For CentOS, this had to be modified a bit: | ||
| + | |||
| + | < | ||
| + | grub> set root=(hd0, | ||
| + | grub> linux / | ||
| + | grub> initrd / | ||
| + | grub> boot | ||
| + | </ | ||
| + | |||
| + | There' | ||
| + | |||
| + | **UPDATE 2NOV2016** | ||
| + | \\ Turns out this isn't a UUID or disk issue at all. Changing the boot mode to not use 16-bit fixes it. | ||
| + | < | ||
| + | [root@apama001 ~]# diff / | ||
| + | 109c109 | ||
| + | < sixteenbit=" | ||
| + | --- | ||
| + | > sixteenbit="" | ||
| + | |||
| + | |||
| + | # Then, | ||
| + | grub2-mkconfig -o / | ||
| + | </ | ||
| + | ----- | ||
| + | To open a Java KVM successfully, | ||
| + | |||
| + | ===== Checking Disk SMART data ===== | ||
| + | < | ||
| + | # If needed... | ||
| + | wget http:// | ||
| + | dpkg -i hpacucli_9.40.1-1._amd64.deb | ||
| - | **Per node** | + | # Then... |
| - | * 48GB RAM | + | smartctl |
| - | * 2x Intel(R) Xeon(R) CPU E5-2407 0 @ 2.20GHz | + | </ |
| - | * 1x 500GB HP HDD | + | |
| - | * 26x 3TB HP HDD | + | |
hardware/apama.1456869538.txt.gz · Last modified: by dgalloway
