Closed
Bug 1465404
Opened 7 years ago
Closed 3 years ago
[Tracker] W10/Linux Moonshot machines that fail after reimage
Categories
(Infrastructure & Operations :: RelOps: Hardware, task)
Infrastructure & Operations
RelOps: Hardware
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: rmutter, Unassigned)
References
Details
Attachments
(3 files)
As Mark requested per email . Here the bug that tracks W10/Linux moonshots that keep failing for a reason or another. For now we've tracked the following:
T-W1064-MS-179 -> Looks like a HDD problem
T-W1064-MS-281 -> Looks like a network problem, Displays XenServer menu
T-W1064-MS-170 -> Unable to reimage, gets rebooted when it gets at Deployment kit view, freezes at boot
Reporter | ||
Updated•7 years ago
|
Summary: [TRACKING] W10 Moonshot machines that fail after reimage → [TRACKING] W10/Linux Moonshot machines that fail after reimage
Comment 1•7 years ago
|
||
T-W1064-MS-108 freezes on PXE boot
T-W1064-MS-130 Looks like HW issue, see attached pic below
T-W1064-MS-175 Java interface doesn't start up, see attached pic below.
Comment 2•7 years ago
|
||
Comment 3•7 years ago
|
||
Comment 4•7 years ago
|
||
I found that 170 and 179 are online and taking tasks.
108 is now reinstalling.
Through ILO turned off the node. SSH to moon-chassis-3.inband.releng.mdc1.mozilla.com and ran command "reset cartridge power c18". Then restarted the install.
175 is now reinstalling.
Cold booted through the ILO desktop client and then was able to kick off a new install.
Comment 5•7 years ago
|
||
I asked Van to look into opening up an HP support case for node 130 in bug 1463754.
Depends on: 1463754
Comment 6•7 years ago
|
||
With 281, it is not seeing a bootable eufi device. I asked for the cartridge be reseated in Bug 1467264.
Depends on: 1467264
Reporter | ||
Comment 7•7 years ago
|
||
Seems like T-W1064-MS-077 has issues. Tried to reimage it 2 times. Both failed. Attached log for more context.
Reporter | ||
Comment 8•7 years ago
|
||
Comment 9•7 years ago
|
||
t-w1064-ms-130 is still busted with the above mentioned problem.
t-linux64-ms-279 - tried to reimage it, to no avail.
Updated•6 years ago
|
Assignee: relops → nobody
Component: RelOps: General → RelOps: Hardware
QA Contact: klibby
Summary: [TRACKING] W10/Linux Moonshot machines that fail after reimage → [Tracker] W10/Linux Moonshot machines that fail after reimage
Comment 10•3 years ago
|
||
backlog cleanup
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•