Change Details

Just as the title says... wdqs1002.eqiad.wmnet does not come up after a routine reboot. @Joe and @Volans did the investigation. What we know sofar: * server was booting in pxe, not on HDD. Luckily pxe installation did not complete due to missing swap partition. * LV were checked and look good (no partition erased during failed install, data is still there) * RAM, disk and proc look good when checking in BIOS * post serial redirection was on the whole time, nothing strange is logged * there was something like no supported device found at reboot but went away to quikly

Just as the title says... wdqs1002.eqiad.wmnet does not come up after a routine reboot. @Joe and @Volans did the investigation. What we know sofar: * server was booting in pxe, not on HDD. Luckily pxe installation did not complete due to missing swap partition. * LV were checked and look good (no partition erased during failed install, data is still there) (check was done by dropping to shell during the pxe installation) * RAM, disk and proc look good when checking in BIOS * post serial redirection was on the whole time, nothing strange is logged * there was something like no supported device found at reboot but went away to quikly

Just as the title says... wdqs1002.eqiad.wmnet does not come up after a routine reboot. @Joe and @Volans did the investigation. What we know sofar: * server was booting in pxe, not on HDD. Luckily pxe installation did not complete due to missing swap partition. * LV were checked and look good (no partition erased during failed install, data is still there) (check was done by dropping to shell during the pxe installation) * RAM, disk and proc look good when checking in BIOS * post serial redirection was on the whole time, nothing strange is logged * there was something like no supported device found at reboot but went away to quikly