Bug 1222578 - MicroOS enters emergency.target when rebooted by transactional-update
Summary: MicroOS enters emergency.target when rebooted by transactional-update
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Current
Hardware: x86-64 openSUSE Tumbleweed
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: openSUSE Kernel Bugs
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-10 05:22 UTC by Shung-Hsi Yu
Modified: 2024-05-21 15:38 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Shung-Hsi Yu 2024-04-10 05:22:30 UTC 
On openSUSE MicroOS 20240407, the system enters into systemd's emergency shell when reboot by transactional-update after system update (dup).

The reason that emergency shell is started seems to due to local-fs.target failing, which in turn comes from failure in boot-efi.mount with the error message:

  mount: /boot/efi: unknown filesystem type 'vfat
Comment 1 Shung-Hsi Yu 2024-04-10 05:26:20 UTC 
FWIW system seem to boot fine if powered it off and reboot again.
Comment 2 Shung-Hsi Yu 2024-04-10 05:33:50 UTC 
Looks like the root cause being kernel vs kernel module version mismatch. For example the runtime kernel is 6.8.2-1-default, but under /usr/lib/modules/ only 6.8.4-rc1-1-default exists.
Comment 3 Takashi Iwai 2024-05-21 15:38:21 UTC 
That sounds weird.  Can you reproduce the problem by transaction-update of a single kernel package 6.8.2?