oxidecomputer / oxidecomputer/omicron

Failure to mupdate with `20.0.0-0.ci+gitd097cc7a272`

Open
#10,607 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
572
Forks
97
Avg merge
2d 12h
Merged PRs (30d)
96

Description

Mupdate fails with installinator restarting, the console shows the following

MPIO Firmware Version: 0x01.0x00.0x1e.0x00
cpu0: microcode has been updated from version 0xb002141 to 0xb002162
Oxide Helios Version helios-3.0.24018 64-bit

------> Sending IPCC command 0x15 (BOOTSTAGE), attempt 1/10
Additional data length: 0x10
Additional data length: 0x0

------> Sending IPCC command 0x15 (BOOTSTAGE), attempt 1/10
Additional data length: 0x10
Additional data length: 0x0

------> Sending IPCC command 0x15 (BOOTSTAGE), attempt 1/10
Additional data length: 0x10
Additional data length: 0x0

------> Sending IPCC command 0x15 (BOOTSTAGE), attempt 1/10
Additional data length: 0x10
Additional data length: 0x0

------> Sending IPCC command 0x15 (BOOTSTAGE), attempt 1/10
Additional data length: 0x10
Additional data length: 0x0

------> Sending IPCC command 0x15 (BOOTSTAGE), attempt 1/10
Additional data length: 0x10
Additional data length: 0x0

------> Sending IPCC command 0xe (KEYLOOKUP), attempt 1/10
Additional data length: 0x3
Additional data length: 0x1

------> Sending IPCC command 0x15 (BOOTSTAGE), attempt 1/10
Additional data length: 0x10
Additional data length: 0x0
NOTICE: Starting Oxide boot
NOTICE:     Phase 1 wants: b304d76703323cb0935703d8affbe970b29cbc961e04dbb0118ffc11f4ac12ba
NOTICE: TRYING: boot sp
NOTICE:     in image: b304d76703323cb0935703d8affbe970b29cbc961e04dbb0118ffc11f4ac12ba
NOTICE: received offer from SP -- 
NOTICE:     v2 flags 0x1
NOTICE:     data size 0x9eb1c31 image size 0x7d000000 target size 0x100000000
NOTICE:     dataset rpool/ROOT/ramdisk
NOTICE:  image name recovery d097cc7/d847a32 2026-06-11 01:11
WARNING: failed ramdisk write at offset 0x3f89e003%) 122KiB/s                
WARNING: failed ramdisk write at offset 0x3fa9e00

------> Sending IPCC command 0x6 (BOOTFAIL), attempt 1/10
Additional data length: 0x2a
Additional data length: 0x0
WARNING: Could not find a valid phase2 image on sp

------> Sending IPCC command 0x6 (BOOTFAIL), attempt 1/10
Additional data length: 0x2b
Additional data length: 0x0

panic[cpu0]/thread=fffffffffc0c43e0: Could not find a valid phase2 image on sp

Warning - stack not written to the dump buffer
fffffffffc0ca260 boot_image:oxide_boot_locate+18a ()
fffffffffc0ca290 genunix:boot_image_locate+a1 ()
fffffffffc0ca2d0 genunix:main+137 ()
fffffffffc0ca2e0 unix:_locore_start+88 ()

This showed up updating london16 and london15 (gimlet and a cosmo)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the mupdate and installinator path using the reported 20.0.0-0.ci+gitd097cc7a272 logs, focusing on the failed ramdisk writes and missing phase2 image. Reproduce the update on the affected london16 or london15 hardware if available. Done means the update completes without installinator restarting or panicking with a missing phase2 image.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.