[Wikidata-bugs] [Maniphest] [Commented On] T132387: wdqs1002 does not reboot, stops at "Scanning for devices"

2016-04-15 Thread Stashbot
Stashbot added a comment. Mentioned in SAL [2016-04-15T09:01:04Z] reenabling wdqs1002 in varnish rotation after reinstall (https://phabricator.wikimedia.org/T132387) TASK DETAIL https://phabricator.wikimedia.org/T132387 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/

[Wikidata-bugs] [Maniphest] [Commented On] T132387: wdqs1002 does not reboot, stops at "Scanning for devices"

2016-04-15 Thread gerritbot
gerritbot added a comment. Change 283485 merged by Gehel: Revert "remove wdqs1002 from varnish during reinstall / fix" https://gerrit.wikimedia.org/r/283485 TASK DETAIL https://phabricator.wikimedia.org/T132387 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emai

[Wikidata-bugs] [Maniphest] [Commented On] T132387: wdqs1002 does not reboot, stops at "Scanning for devices"

2016-04-14 Thread gerritbot
gerritbot added a comment. Change 283485 had a related patch set uploaded (by Gehel): Revert "remove wdqs1002 from varnish during reinstall / fix" https://gerrit.wikimedia.org/r/283485 TASK DETAIL https://phabricator.wikimedia.org/T132387 EMAIL PREFERENCES https://phabricator.wikim

[Wikidata-bugs] [Maniphest] [Commented On] T132387: wdqs1002 does not reboot, stops at "Scanning for devices"

2016-04-12 Thread Gehel
Gehel added a comment. Full reinstall is in progress as we needed to account for new disks anyway. TASK DETAIL https://phabricator.wikimedia.org/T132387 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Gehel Cc: gerritbot, MoritzMuehlenhoff, RobH,

[Wikidata-bugs] [Maniphest] [Commented On] T132387: wdqs1002 does not reboot, stops at "Scanning for devices"

2016-04-12 Thread gerritbot
gerritbot added a comment. Change 282946 merged by Gehel: remove wdqs1002 from varnish during reinstall / fix https://gerrit.wikimedia.org/r/282946 TASK DETAIL https://phabricator.wikimedia.org/T132387 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferen

[Wikidata-bugs] [Maniphest] [Commented On] T132387: wdqs1002 does not reboot, stops at "Scanning for devices"

2016-04-12 Thread gerritbot
gerritbot added a comment. Change 282946 had a related patch set uploaded (by Gehel): remove wdqs1002 from varnish during reinstall / fix https://gerrit.wikimedia.org/r/282946 TASK DETAIL https://phabricator.wikimedia.org/T132387 EMAIL PREFERENCES https://phabricator.wikimedia.org/

[Wikidata-bugs] [Maniphest] [Commented On] T132387: wdqs1002 does not reboot, stops at "Scanning for devices"

2016-04-12 Thread Joe
Joe added a comment. so, it could be possible that the package upgrade failed to correctly install grub to the mbr? TASK DETAIL https://phabricator.wikimedia.org/T132387 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Joe Cc: MoritzMuehlenhoff, R

[Wikidata-bugs] [Maniphest] [Commented On] T132387: wdqs1002 does not reboot, stops at "Scanning for devices"

2016-04-12 Thread Volans
Volans added a comment. @Joe FYI: I was able yesterday to get a shell in the installer and mount /dev/sda1 and there was a boot partition with 4 kernels there, so the data was not wiped out IMHO. I was also able to see the other 2 partitions and lvdisplay was showing 3 logical volumes. TA

[Wikidata-bugs] [Maniphest] [Commented On] T132387: wdqs1002 does not reboot, stops at "Scanning for devices"

2016-04-11 Thread MoritzMuehlenhoff
MoritzMuehlenhoff added a comment. The reboot was for the upgrade to Linux 4.4 TASK DETAIL https://phabricator.wikimedia.org/T132387 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: MoritzMuehlenhoff Cc: MoritzMuehlenhoff, RobH, Smalyshev, Gehel, J

[Wikidata-bugs] [Maniphest] [Commented On] T132387: wdqs1002 does not reboot, stops at "Scanning for devices"

2016-04-11 Thread Smalyshev
Smalyshev added a comment. AFAIK something to do with kernel upgrade, @Gehel should know the details. TASK DETAIL https://phabricator.wikimedia.org/T132387 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Smalyshev Cc: MoritzMuehlenhoff, RobH, Smal

[Wikidata-bugs] [Maniphest] [Commented On] T132387: wdqs1002 does not reboot, stops at "Scanning for devices"

2016-04-11 Thread Joe
Joe added a comment. Why were we rebooting this system to start with? TASK DETAIL https://phabricator.wikimedia.org/T132387 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Joe Cc: MoritzMuehlenhoff, RobH, Smalyshev, Gehel, Joe, Volans, Aklapper, A

[Wikidata-bugs] [Maniphest] [Commented On] T132387: wdqs1002 does not reboot, stops at "Scanning for devices"

2016-04-11 Thread MoritzMuehlenhoff
MoritzMuehlenhoff added a comment. It's really strange that it initiated a PXE install, both wdqs* servers were rebooted w/o problems for the keyctl security bug (and no additional BIOS config were needed). TASK DETAIL https://phabricator.wikimedia.org/T132387 EMAIL PREFERENCES https:/

[Wikidata-bugs] [Maniphest] [Commented On] T132387: wdqs1002 does not reboot, stops at "Scanning for devices"

2016-04-11 Thread Joe
Joe added a comment. So, a few points: - If the MBR was wiped, it was not wiped by the installation process (the MBR stays untouched until the very end of the install process, thanks god) - If the MBR was wiped, we can simply boot from pxe, get to the installer stops, get a shell and r

[Wikidata-bugs] [Maniphest] [Commented On] T132387: wdqs1002 does not reboot, stops at "Scanning for devices"

2016-04-11 Thread RobH
RobH added a comment. Please note: https://phabricator.wikimedia.org/T120714 This should have an entirely new partman recipe designated to accomodate the new disks installed into this system previously. TASK DETAIL https://phabricator.wikimedia.org/T132387 EMAIL PREFERENCES https:/

[Wikidata-bugs] [Maniphest] [Commented On] T132387: wdqs1002 does not reboot, stops at "Scanning for devices"

2016-04-11 Thread RobH
RobH added a comment. I've disabled the lifecycle controller completely, so its not the issue. After more testing, I think the initial load into the installer here: "server was booting in pxe, not on HDD. Luckily pxe installation did not complete due to missing swap partition." When it hi