This is something to do with linux 5 kernel api
You need to manually downgrade systemd - well - that's what I did.
when you boot with grub or refind - edit default entry and change the
init=/bin/init to init=/bin/bash
That will bypass systemd starting up and drop you straight into a shell.
mount -o remount /
mount /usr
mount /var
mount /dev/sdc1 /mnt
dpkg -i /mnt/systemd_241-7~deb10u3_amd64.deb
On a system that works or download a previous version somehow.
dpkg -l systemd
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
ii systemd 245.5-2 amd64 system and service manager
root@leet:/home/wozza# apt-cache policy systemd
systemd:
Installed: 245.5-2
Candidate: 245.5-2
Version table:
*** 245.5-2 500
500 http://ftp.iinet.net.au/debian/debian bullseye/main amd64 Packages
100 /var/lib/dpkg/status
241-7~deb10u3 500
500 http://ftp.iinet.net.au/debian/debian stable/main amd64 Packages
root@leet:/home/wozza# apt-get download systemd=241-7~deb10u3
Get:1 http://ftp.iinet.net.au/debian/debian stable/main amd64 systemd amd64
241-7~deb10u3 [3,495 kB]
Fetched 3,495 kB in 11s (321 kB/s)
W: Download is performed unsandboxed as root as file
'/home/wozza/systemd_241-7~deb10u3_amd64.deb' couldn't be accessed by user
'_apt'. - pkgAcquire::Run (13: Permission denied)
root@leet:/home/wozza# ll systemd_241-7~deb10u3_amd64.deb
-rw-r--r-- 1 root root 3495428 Jan 31 15:11 systemd_241-7~deb10u3_amd64.deb
root@leet:/home/wozza# mount /dev/sdc1 /mnt
root@leet:/home/wozza# cp systemd_241-7~deb10u3_amd64.deb /mnt/
root@leet:/home/wozza# cd /mnt/
root@leet:/mnt# mkdir unpack
root@leet:/mnt# cd unpack/
root@leet:/mnt/unpack# dpkg-deb -R ../systemd_241-7~deb10u3_amd64.deb .
worst comes to worse can copy the files across from unpack directory -
good luck.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1876486
Title:
Kernel panic booting after 18.04 to 20.04 upgrade
Status in libseccomp package in Ubuntu:
New
Bug description:
Upgraded Ubuntu 18.04 to 20.04. Following the upgrade, booting was not
possible. The error messages is:
/sbin/init: symbol lookup error: /lib/systemd/libsystemd-shared-245.so:
undefined symbol: seccomp_api_get
[ 4.608900] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x00007f00
See also attached photograph of screen during boot.
Upgrade followed steps from here:
https://help.ubuntu.com/community/FocalUpgrades/Kubuntu
With the excpetion that The -d flag was used for the do-release-upgrade:
sudo do-release-upgrade -d -m desktop
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Prior to upgrade: Ubuntu 18.04.4
After upgrade (but never booted): Ubuntu (Kubuntu) 20.04
Note that Ubuntu had originally be installed, but kubuntu-desktop was
recently installed to change to Kubuntu, but no booting problems were
experienced before updating to 20.04.
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in
Unknown -- Package version may have changed when upgrading to 20.04.
3) What you expected to happen
Boot without kernel panic.
4) What happened instead
Could not boot. Even selecting safe mode from grub could not boot. Had to
restore system from backups. Will not attempt upgrade again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
