coreos / coreos/bootupd

Failure on RAID1 bootloader update

Open
#1,059 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
196
Forks
55
Avg merge
3d 2h
Merged PRs (30d)
14

Description

I use universalBlue Aurora and I've noticed that I'm getting a noisy startup where bootupd tries to update the bootloader, but is failing with the following logs:

Running as unit: bootupd.service
error: Failed to update EFI: Failed to mount "/dev/nvme0n1p1": Subprocess failed: ExitStatus(unix_wait_status(8192))
mount: /boot/efi: fsconfig() failed: /dev/nvme0n1p1: Can't lookup blockdev.
       dmesg(1) may have more information after failed mount system call.

dmesg doesnt mention anything meaningful

Currently I'm on a Lenovo Thinkpad, it has an OEM Raid1 setup with Intel RST.

My blkid:

/dev/nvme0n1: TYPE="isw_raid_member"
/dev/md126p2: UUID="677b7145-fc97-4fb2-93a9-fff1b4ded0a2" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="d7110fce-5560-4c6d-8cca-5ca025ac1edf"
/dev/md126p3: LABEL="fedora_aurora" UUID="9e9f309f-5014-4386-b5c0-f4903e979634" UUID_SUB="df7a423d-974c-455c-9361-4409b051b65c" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="03a655f8-aad8-45b0-97a7-569c85f3ad7c"
/dev/md126p1: UUID="E722-FBB9" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="fe375d77-9242-4944-b2ef-fcc29b4ac2aa"
/dev/nvme1n1: TYPE="isw_raid_member"
/dev/zram0: LABEL="zram0" UUID="6c5d0ff8-386c-4532-92f1-c2b11c694dd3" TYPE="swap"

bootupd version: 0.2.32

bootupd status:

Running as unit: bootupd.service
Component EFI
  Installed: grub2-efi-ia32-1:2.12-40.fc43.x86_64,grub2-efi-x64-1:2.12-40.fc43.x86_64,shim-ia32-15.8-3.x86_64,shim-x64-15.8-3.x86_64
  Update: Available: grub2-1:2.12-40.fc43,shim-15.8-3
Detected: BIOS: unknown
Boot method: EFI

Is there anything I can do to fix this? is this even the right place to report?

Contributor guide

No contributing guide indexed for this repository

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

No source file or test is named; start by reproducing the bootupd.service EFI update and reviewing bootupd status alongside the provided mount, blkid, and dmesg output. Done means determining why the EFI partition cannot be mounted on this Intel RST RAID1 layout and whether bootupd can update it successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, rust
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.