639499 - re-image talos-r3-xp-002

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P3)

Description

[Armen [:armenzg]]

It seems that newly re-imaged XP machines have a smaller space than expected.

The machines believe they have 5.37 GB for the C drive but in reality it should have 128.85GB according to disk manager.

I have checked the ref machine and it has the expected usable space.

I noticed this initially in bug 639486.

Comment 1

[Zandr Milewski [:zandr]]

Where do you want to keep track of the ones you find? this bug or that one?

(I reimaged xp-001 on Saturday)

Comment 2

[Armen [:armenzg]]

This one. We could DUPE that one to this one as it is more complete.

Comment 4

[Zandr Milewski [:zandr]]

FWIW, VNC to either -001 or -002 gets me a black screen (actually *crashes* Chicken of the VNC, but Screen Sharing works)

Comment 5

[Armen [:armenzg]]

It WFM. I have had that problem before.
I would use Remote Desktop to work around it.

Comment 6

[Zandr Milewski [:zandr]]

Reimaged talos-r3-xp-005, it's now in the same state

Comment 7

[Zandr Milewski [:zandr]]

This looks to be sorted by the new snapshots. Closing, but I'll check each machine as I image them.

Comment 8

[Dustin J. Mitchell [:dustin] (he/him)]

Opening this back up to re-image -005 and -001.  I'm loaning -002 out, so I'll open a separate bug to re-image that one.

Comment 9

[Zandr Milewski [:zandr]]

To be clear, since apparently I wasn't, these machines were reimaged at the time of comment 7.

Comment 10

[Dustin J. Mitchell [:dustin] (he/him)]

Having now checked the hosts in question, -005 has the right sized C:, but -001 and -002 do not.

Rather than loan BenWa a machine with a tiny C drive, I'll loan -005 out to him, and keep this bug open for -001 and -002.

Sorry to be the bearer of bad news :(

Comment 11

[Zandr Milewski [:zandr]]

Reimaged and renamed -001 and -002. Disk space confirmed.

Comment 12

[Dustin J. Mitchell [:dustin] (he/him)]

These two need to be set up.  Same problem as in bug 668031: OPSI doesn't do the right thing.

Also, talos-r3-xp-002 is currently inaccessible, and has been added to bug 673604 for a reboot.

Comment 13

[[e-mail] (:bhearsum)]

I'll try to take care of these this week.

Comment 14

[[e-mail] (:bhearsum)]

Didn't get a chance to do these, passing to Aki, who is on buildduty next week.

Comment 15

[Armen [:armenzg]]

I needed a staging slave so I grabbed talos-r3-xp-001 and did the following on staging-opsi:
> opsi-admin -d method deleteClient talos-r3-xp-001.build.mozilla.org
and rebooted the slave.

I didn't install any packages. I tried to install winxp-graphic-driver but it failed.

That's all I needed from the slave and I am leaving it alone.

Comment 16

[Aki Sasaki (not active)]

I'm looking at the wiki pages and it's not really clear what needs to be done.

(In reply to comment #12)
> These two need to be set up.  Same problem as in bug 668031: OPSI doesn't do
> the right thing.

Does this mean that https://wiki.mozilla.org/ReferencePlatforms/Test/WinXP#Post-cloning_Setup_for_Pool is no longer accurate?

If so, what needs to be done?

Comment 17

[Chris Cooper [:coop] (he/him)]

I used 001 yesterday and it is up-to-date with OPSI now. 002 still needs OPSI setup to be returned to staging.

Comment 18

[Chris AtLee [:catlee]]

tried setting it up with opsi, and now VNC doesn't work

Comment 19

[Armen [:armenzg]]

VNC seems to be reachable now.

Comment 20

[Armen [:armenzg]]

I am loaning talos-r3-xp-002 to BenWa in bug 679066.

We will have to reimage once he is done with it.