Differences

This shows you the differences between two versions of the page.

--- hardware:apama [2016/07/30 23:39] – Added SMART data checking info dgalloway
+++ hardware:apama [2020/01/30 15:55] (current) – djgalloway
@@ Line 1: / Line 1: @@
-====== apama{001,002} ======
+====== apama{001,002} (RETIRED) ======
 https://opendcim.engineering.redhat.com/devices.php?DeviceID=7792
+This hardware was retired on 30JAN2020 to make room for new [[hardware:vossi]] (rex replacements after LA office closure).
 ===== Summary =====
 apama001 and apama002 are two nodes in an HP SL4540 Gen8 chassis.  Both nodes are running Xenial because the systems [[http://h20564.www2.hp.com/hpsc/doc/public/display?docId=mmr_kc-0111501|RSOD]] when running rpm-based distros.  It's possible to get past it by messing with grub but not worth it.  See Quirks below for more info.
-Both hosts are serving as OSD nodes for the [[services:longrunningcluster]].
+apama001 is running RHEL and the plan is to use it as a docker host.  apama002 is an OSD node in the [[services:longrunningcluster]].
 The iLOs are accessible but the java KVM is mostly useless since our lack of Enterprise License causes it to quit after POST.
@@ Line 25: / Line 27: @@
 ===== Quirks =====
-I was able to install Fedora23 on apama001 but still got Red Screen of Death and "Illegal Opcode" after grub tries to boot the OS.  Something about rpm-based distros doesn't like searching for the root partition using UUID.
+I was able to install Fedora23 on apama001 but still got Red Screen of Death and "Illegal Opcode" after grub tries to boot the OS.  <del>Something about rpm-based distros doesn't like searching for the root partition using UUID.</del>  **See UPDATE below**
 What fixed it was finding the proper root drive and manually booting to it in a grub rescue prompt.  See below.
@@ Line 56: / Line 58: @@
 There's probably a permanent fix that can be applied in grub.cfg but haven't looked into it.
+**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.
+<code>
+[root@apama001 ~]# diff /etc/grub.d/10_linux.orig /etc/grub.d/10_linux
+c109
+< 	sixteenbit="16"
+---
+> 	sixteenbit=""
+# Then,
+grub2-mkconfig -o /boot/grub/grub.cfg
+</code>
+-----
+To open a Java KVM successfully, log into the iLO web UI in another tab.  Then browse to %%https://apama{001|002}.ipmi.sepia.ceph.com/html/java_irc.html?lang=en%%
 ===== Checking Disk SMART data =====