talos-r3-xp-066

talos-r3-fed-029 talos-r3-fed-030 talos-r3-fed-031 talos-r3-fed-075 talos-r3-fed64-012 talos-r3-fed64-039 talos-r3-fed64-045 talos-r3-fed64-057 talos-r4-snow-007 talos-r4-snow-063

w32-ix-slave16 (w32-ix-slave16-mgmt isn't responding, this is one of the machines that didn't like the extra RAM in bug 672969)

talos-r3-fed-024 - still down since bug 711969

talos-r3-fed64-013

talos-r3-xp-022

talos-r3-fed64-036 talos-r3-fed64-056

talos-r4-lion-006 - nagios thinks it's up, ssh is non-responsive after the initial connection, no jobs done since Dec 18

talos-r3-fed-062 talos-r3-fed64-054

talos-r4-snow-023

talos-r3-fed64-009.build.scl1

talos-r3-fed64-042.build.scl1

talos-r3-xp-066 | as soon as I connect the CC, it began running a test talos-r3-fed-029 | dead fish | rebooted talos-r3-fed-030 | grey screen | rebooted talos-r3-fed-031 | grey screen | rebooted talos-r3-fed-075 | grey screen | rebooted talos-r3-fed64-012 | no vga sig | rebooted * talos-r3-fed64-039 | no vga sig | rebooted * talos-r3-fed64-045 | no vga sig | rebooted talos-r3-fed64-057 | grey screen | rebooted talos-r4-snow-007 | "The system bootstrapper has crashed", fs errors| re-imaged talos-r4-snow-063 | blank desktop | rebooted talos-r3-fed-024 | grey screen | rebooted talos-r3-fed64-013 | grey screen | rebooted talos-r3-xp-022 | as soon as I connect the CC, it began running a test talos-r3-fed64-036 | no vga sig | rebooted * talos-r3-fed64-056 | no vga sig | rebooted talos-r4-lion-006 | blank desktop | rebooted talos-r3-fed-062 | grey screen | rebooted talos-r3-fed64-054 | no vga sig | rebooted * talos-r4-snow-023 | offline | wouldn't respond to pwr button, pulled pwr, wait 15 sec, power on talos-r3-fed64-009 | dead fish | rebooted talos-r3-fed64-042 | no vga sig | rebooted * * some of the feds that had no vga sig also had trouble rebooting. I have noticed this before in the past and would default to re-imaging. I dug a little deeper this time and noticed the kernel would fail to mount the root fs. The error indicated the kernel couldn't recognize the root fs type and therefore would give up. Workaround: added rootfstype=ext4 to kernel args in grub This allowed the kernel to continue mounting the root fs. Since the fsck immediately preceding returned clean, I don't believe this is caused by fs corruption. It might be a bug in the kernel in regards to how it mounts the root fs on a lvm.

talos-r3-w7-002. i can add to a new bug if this one is otherwise fixed.

(In reply to Aki Sasaki [:aki] from comment #13) > talos-r3-w7-002. i can add to a new bug if this one is otherwise fixed. Sure, I'm still here.... done.