user@coreOS:~$ sudo bootupctl adopt-and-update
Running as unit: bootupd.service
No components are adoptable.
user@coreOS:~$ sudo bootupctl status
Running as unit: bootupd.service
Component BIOS
Installed: grub2-tools-1:2.06-123.fc40.x86_64
Update: Available: grub2-tools-1:2.12-28.fc42.x86_64
Component EFI
Installed: grub2-efi-x64-1:2.06-123.fc40.x86_64,shim-x64-15.8-3.x86_64
Update: Available: grub2-efi-x64-1:2.12-28.fc42.x86_64,shim-x64-15.8-3.x86_64
No components are adoptable.
CoreOS aleph version: 40.20240728.3.0
Boot method: EFI
user@coreOS:~$ sudo bootupctl update
Running as unit: bootupd.service
Installing for i386-pc platform.
/usr/sbin/grub2-install: error: cannot find a GRUB drive for . Check your device.map.
error: Failed to update BIOS: Failed to run "/usr/sbin/grub2-install" "--target" "i386-pc" "--boot-directory" "/boot" "--modules" "mdraid1x part_gpt" ""
henry@coreOS:~$ sudo /usr/sbin/grub2-install --target i386-pc --boot-directory /boot --modules mdraid1x part_gpt
Installing for i386-pc platform.
/usr/sbin/grub2-install: error: cannot find a GRUB drive for part_gpt. Check your device.map.
user@coreOS:~$ sudo cat /boot/grub/device.map
cat: /boot/grub/device.map: No such file or directory
ignition-file: (setup with mirrored disks)
variant: fcos
version: 1.5.0
boot_device:
mirror:
devices:
- /dev/nvme0n1
- /dev/nvme1n1
hricky
(Hristo Marinov)
May 5, 2025, 9:09am
2
Hello @user24837924 and welcome to !
Could you please try to explain in more detail what you are trying to achieve, provide the output of the sudo rpm-ostree status
command and the full Butane configuration you used to provision the machine. Also, is this bare metal, virtual machine, or cloud deployment?
when I login: i get the following message:
Fedora CoreOS 42.20250410.3.2
Tracker: https://github.com/coreos/fedora-coreos-tracker
Discuss: https://discussion.fedoraproject.org/tag/coreos
Last login: XXXX
[systemd]
Failed Units: 1
custom-bootupd-auto.service
so I tried to find out what was wrong:
user@coreOS:~$ sudo systemctl status custom-bootupd-auto.service
× custom-bootupd-auto.service - Bootupd automatic update
Loaded: loaded (/etc/systemd/system/custom-bootupd-auto.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf, 50-keep-warm.conf
Active: failed (Result: exit-code) since Sat 2025-05-03 20:34:03 CEST; 1 day 16h ago
Duration: 388ms
Invocation: 57d0a4b347bd4f7db1f7bded2bddfd2c
Process: 3798 ExecStart=/usr/bin/bootupctl update (code=exited, status=1/FAILURE)
Main PID: 3798 (code=exited, status=1/FAILURE)
Mem peak: 10.5M
CPU: 97ms
May 03 20:34:03 coreOS systemd[1]: Started custom-bootupd-auto.service - Bootupd automatic update.
May 03 20:34:03 coreOS bootupctl[3798]: Installing for i386-pc platform.
May 03 20:34:03 coreOS bootupctl[3798]: /usr/sbin/grub2-install: error: cannot find a GRUB drive for . Check your device.map.
May 03 20:34:03 coreOS bootupctl[3798]: error: Failed to update BIOS: Failed to run "/usr/sbin/grub2-install" "--target" "i386-pc" "--boot-directory" "/boot" "--modules">
May 03 20:34:03 coreOS systemd[1]: custom-bootupd-auto.service: Main process exited, code=exited, status=1/FAILURE
May 03 20:34:03 coreOS systemd[1]: custom-bootupd-auto.service: Failed with result 'exit-code'.
Additional info:
user@coreOS:~$ sudo rpm-ostree status
State: idle
AutomaticUpdatesDriver: Zincati
DriverState: active; periodically polling for updates (last checked Mon 2025-05-05 10:39:32 UTC)
Deployments:
● fedora:fedora/x86_64/coreos/stable
Version: 42.20250410.3.2 (2025-04-30T17:43:22Z)
BaseCommit: baea63252b3d3836668ff0dba57d9f368b591e1387b223293953f2c3f08794cc
GPGSignature: Valid signature by B0F4950458F69E1150C6C5EDC8AC4916105EF944
LayeredPackages: docker-compose restic tailscale
fedora:fedora/x86_64/coreos/stable
Version: 42.20250410.3.1 (2025-04-28T23:24:51Z)
BaseCommit: e057a84658cd114c1fa8a944d8fe3de93f5413c0fbe3f1fabc737cc04bbd749b
GPGSignature: Valid signature by B0F4950458F69E1150C6C5EDC8AC4916105EF944
LayeredPackages: docker-compose restic tailscale
variant: fcos
version: 1.5.0
passwd:
users:
- name: user
groups:
- wheel
- sudo
- docker
ssh_authorized_keys:
- ssh-rsa XXXXXXX
storage:
files:
- path: /etc/hostname
mode: 0644
contents:
inline: coreOS
- path: /etc/vconsole.conf
mode: 0644
contents:
inline: KEYMAP=de
- path: /etc/zincati/config.d/55-updates-strategy.toml
contents:
inline: |
[updates]
strategy = "periodic"
[updates.periodic]
time_zone = "Europe/Berlin"
[[updates.periodic.window]]
days = [ "Mon", "Tue", "Wed", "Thu", "Fri", "Sat", "Sun" ]
start_time = "02:30"
length_minutes = 60
links:
- path: /etc/localtime
target: ../usr/share/zoneinfo/Europe/Berlin
systemd:
units:
- name: rpm-ostree-countme.timer
enabled: false
mask: true
- name: custom-bootupd-auto.service
enabled: true
contents: |
[Unit]
Description=Bootupd automatic update
[Service]
ExecStart=/usr/bin/bootupctl update
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
boot_device:
luks:
tang:
- url: https://example.org:443
thumbprint: XXXXXXX
mirror:
devices:
- /dev/nvme0n1
- /dev/nvme1n1
This is a baremetal installation
TLDR: I want to update the bios and find out why this is not working automatically.
siosm
(Timothée Ravier)
May 5, 2025, 1:02pm
4
Thanks,
is there a expected date, when updates will be possible with a RAID setup?