Closed Bug 913046 Opened 11 years ago Closed 11 years ago

please run hardware diagnostics on t-w864-ix-109

Categories

(Infrastructure & Operations :: RelOps: General, task)

x86_64
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: markco)

References

Details

(Whiteboard: reimaging)

It's hitting some issues that appear to be related to memory or graphics. If it passes diagnostics, please reimage.
colo-trip: --- → scl3
Running memtest
Whiteboard: Running memtest
Host passed diagnostic test. Going to reimage.
Whiteboard: Running memtest → reimaging
Reimage finished.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
The reimage was not successful on this machine, and it's giving an error when another reimage is attempted. Moving this to relops to have one of the windows admins take a look at it.
Assignee: server-ops-dcops → relops
Status: RESOLVED → REOPENED
Component: Server Operations: DCOps → RelOps
Product: mozilla.org → Infrastructure & Operations
QA Contact: dmoore → arich
Resolution: FIXED → ---
Assignee: relops → mcornmesser
What appears to be happening is during the MDT deployment an unexpected reboot is occurring. This reboot causes Litetouch to enter an odd suspended state. This state is what is preventing another deployment from taking place. After the unexpected reboot and manually log in Litetouch picks back up and continues the deployment, and if the machine is reset then it will allow another deployment to start. I am looking into what is causing the unexpected reboot.
During the gpupdate step of the MDT install a reboot was being triggered. I am assuming that this was occurring during the the users gpo being applied and the root password being set. After item level targeting was being applied that would not allow the root password to be touched until the GPO key MDT step the questioning reboot stopped. Double testing to make sure it wasn't a fluke. Will resolved the bug if the retest works as well.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.