Closed
Bug 798519
Opened 12 years ago
Closed 12 years ago
reimage all pandas in chassis 2
Categories
(Infrastructure & Operations :: DCOps, task)
Infrastructure & Operations
DCOps
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hwine, Unassigned)
References
()
Details
(Whiteboard: [reit-panda])
Please reimage all boards in panda chassis 2 with the image described in bug 769428 [this is bug 1 of 4 similar]
Updated•12 years ago
|
colo-trip: --- → scl1
Updated•12 years ago
|
Comment 1•12 years ago
|
||
We imaged 12 SD cards and inserted them into panda chassis 2. Jake is taking a look at the nodes now. Van
Comment 2•12 years ago
|
||
Update: They're booting up but they're also PXEbooting which they're not supposed to do. Jake is trying to figure out why but a new image may need be built. FYI, we took the image from comment 15 of bug 769428 and ran with comment 1's instruction. dd if=panda_final_2gb.img of=<device> bs=32M Van
Reporter | ||
Comment 3•12 years ago
|
||
Question: is there any harm other than a longer boot time caused by the "dual boot"? If not, we'd like to proceed with six of these images in chassis 3 (bug 797629) while the issue for chassis 2 is worked out. See bug 797629 for more details.
Comment 4•12 years ago
|
||
=> Question: is there any harm other than a longer boot time caused by the "dual boot"? If you're asking me, I don't know have an answer because I had no participation in building the image. => If not, we'd like to proceed with six of these images in chassis 3 (bug 797629) while the issue for chassis 2 is worked out. See bug 797629 for more details I am a little confused about this statement. So you want me to image 6 of the SD cards in chassis 3 to this non-working/not working as intended image(according to Jake)?
Comment 5•12 years ago
|
||
(In reply to Hal Wine [:hwine] from comment #3) > Question: is there any harm other than a longer boot time caused by the > "dual boot"? Hal: this isn't a "dual boot" issue. The boot loader was defaulting to PXE boot because the kernel on the card was corrupt and failing a CRC check. ## Booting kernel from Legacy Image at 80200000 ... Image Name: Linux-3.2.0+ Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4772120 Bytes = 4.6 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... Bad Data CRC ERROR: can't get kernel image! I downloaded the image as indicated in 769428 comment 15 but change the block size to 1M. This seemed to fix the issue. I'm re-imaging all the cards for chassis 2 now.
Reporter | ||
Comment 6•12 years ago
|
||
Jake - AWESOME! As you will see from the email that I sent before I got your update, we're keen to get access to a panda-for-android in a chassis ASAP. Thanks!
Comment 7•12 years ago
|
||
Jake comnpleted chassis 2.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Assignee: server-ops → server-ops-dcops
Updated•10 years ago
|
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•