I just updated my ACER laptop from Leap 15.6 to 16.0 using the opensuse-migration-tool and I didn’t see any problems reported during the upgrade.
It’s a dual-boot machine with Windows 11 and on the first reboot, I got the familiar window offering the boot possibilities. Windows booted normally but when, instead, I select “openSUSE 16.0” it boots into “emergency mode” and prompts me to enter root password for system maintenance. It also suggests running “journalctl -xb” which I did but haven’t been able to work out what’s wrong. Any ideas gratefully received
Yea, you should have provided the output of journalctl … otherwise, everyone is just guessing at a possible issue. 
My command line knowledge is now so rusty that I haven’t been able to work out how to transfer that output to a working machine. I redirected it to a file but can’t work out how to copy it from there to a usb stick, so that I can share it. I plug in the usb drive but lsblk doesn’t show it, so can’t get any further.
Unfortunately, I’ve never duel-booted a machine (do have a Windows-only dedicated machine) , so …
When you select “openSUSE 16” (Win boot menu), do you then see an openSUSE boot screen, like GRUB? Or does the Windows-specific boot loader screen only offer a direct-boot to openSUSE?
No the machine starts with the GRUB bootloader screen which offers
openSUSE 16.0
Advanced options for openSUSE16.0
openSUSE 16.0 memtest
Windows Boot Manager
UEFI firmware
I’ve just checked the boot options (for /boot/vmlinuz-6.12.0-160000.35-default) that are invoked when openSUSE 16.0 is selected - they are:
splash=silent preempt=full quiet mitigations=auto security=selinux enforcing=1 selinux=1ia32_emulation=1
Quite unbelievably (to me, anyway), the issue went away when I deleted an immutable file named .foo my home directory. No idea where the file came from either!
Hmmmm. I would have been inquisitive about a file like that: Immutable. Where it came from.
It could be an app saved its settings in it, but a strange method to do it.
I would have checked if it was a plain text or executable type. If executable, might be malicious. If text, I would have read its content. Personally, I’ve never seen a “.foo” immutable file.
@mkmacvean Likewise, I do note you have enforcing=1 in your output?
What does sestatus show?
Perhaps some relabeling was interuppted?
Check the Forum Side panel for the link the the SELinux Portal and run the command to check the log for potential clues.
It was an empty file and slowly it’s dawning on me that it must have been created when I was investigating how to prevent accidental deletion of a certain set of files - so not malicious. Unfortunately, I hadn’t documented this in my system log, so had to rely on my ageing memory!!
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.