Today full-upgrade failed and I have no clue how to deal with it. The Summary looked very harmless to me.
# apt full-upgrade
Upgrading:
at-spi2-common busybox libauthen-sasl-perl libbinutils libsframe3
at-spi2-core gir1.2-atk-1.0 libavahi-client3 libbrotli1 libxdamage1
avahi-daemon gir1.2-packagekitglib-1.0 libavahi-common-data libctf-nobfd0 pci.ids
avahi-utils guestfs-tools libavahi-common3 libctf0 python3-brotli
binutils libatk-bridge2.0-0t64 libavahi-core7 libgprofng0 supermin
binutils-common libatk1.0-0t64 libavahi-glib1 libjs-underscore
binutils-x86-64-linux-gnu libatspi2.0-0t64 libavahi-gobject0 libpackagekit-glib2-18
Summary:
Upgrading: 33, Installing: 0, Removing: 0, Not Upgrading: 0
Download size: 13,6 MB
Space needed: 1.415 kB / 606 GB available
Continue? [Y/n] Y
Get:1 https://ftp.debian.org/debian unstable/main amd64 at-spi2-common all 2.59.1-1 [174 kB]
Get:2 https://ftp.debian.org/debian unstable/main amd64 gir1.2-atk-1.0 amd64 2.59.1-1 [26,5 kB]
Get:3 https://ftp.debian.org/debian unstable/main amd64 libatk-bridge2.0-0t64 amd64 2.59.1-1 [70,2 kB]
Get:4 https://ftp.debian.org/debian unstable/main amd64 libatk1.0-0t64 amd64 2.59.1-1 [53,0 kB]
Get:5 https://ftp.debian.org/debian unstable/main amd64 at-spi2-core amd64 2.59.1-1 [62,8 kB]
Get:6 https://ftp.debian.org/debian unstable/main amd64 libatspi2.0-0t64 amd64 2.59.1-1 [82,0 kB]
Get:7 https://ftp.debian.org/debian unstable/main amd64 libavahi-gobject0 amd64 0.8-18 [39,8 kB]
Get:8 https://ftp.debian.org/debian unstable/main amd64 libavahi-glib1 amd64 0.8-18 [30,4 kB]
Get:9 https://ftp.debian.org/debian unstable/main amd64 avahi-utils amd64 0.8-18 [47,6 kB]
Get:10 https://ftp.debian.org/debian unstable/main amd64 avahi-daemon amd64 0.8-18 [84,8 kB]
Get:11 https://ftp.debian.org/debian unstable/main amd64 libavahi-core7 amd64 0.8-18 [109 kB]
Get:12 https://ftp.debian.org/debian unstable/main amd64 libavahi-client3 amd64 0.8-18 [49,2 kB]
Get:13 https://ftp.debian.org/debian unstable/main amd64 libavahi-common3 amd64 0.8-18 [45,2 kB]
Get:14 https://ftp.debian.org/debian unstable/main amd64 libavahi-common-data amd64 0.8-18 [113 kB]
Get:15 https://ftp.debian.org/debian unstable/main amd64 libgprofng0 amd64 2.45.90.20260201-1 [821 kB]
Get:16 https://ftp.debian.org/debian unstable/main amd64 libctf0 amd64 2.45.90.20260201-1 [92,2 kB]
Get:17 https://ftp.debian.org/debian unstable/main amd64 libctf-nobfd0 amd64 2.45.90.20260201-1 [160 kB]
Get:18 https://ftp.debian.org/debian unstable/main amd64 binutils amd64 2.45.90.20260201-1 [282 kB]
Get:19 https://ftp.debian.org/debian unstable/main amd64 binutils-x86-64-linux-gnu amd64 2.45.90.20260201-1 [1.063 kB]
Get:20 https://ftp.debian.org/debian unstable/main amd64 libbinutils amd64 2.45.90.20260201-1 [549 kB]
Get:21 https://ftp.debian.org/debian unstable/main amd64 binutils-common amd64 2.45.90.20260201-1 [2.545 kB]
Get:22 https://ftp.debian.org/debian unstable/main amd64 libsframe3 amd64 2.45.90.20260201-1 [84,5 kB]
Get:23 https://ftp.debian.org/debian unstable/main amd64 busybox amd64 1:1.37.0-9 [485 kB]
Get:24 https://ftp.debian.org/debian unstable/main amd64 libpackagekit-glib2-18 amd64 1.3.4-3 [118 kB]
Get:25 https://ftp.debian.org/debian unstable/main amd64 gir1.2-packagekitglib-1.0 amd64 1.3.4-3 [27,5 kB]
Get:26 https://ftp.debian.org/debian unstable/main amd64 guestfs-tools amd64 1.52.3-3.1 [4.799 kB]
Get:27 https://ftp.debian.org/debian unstable/main amd64 libauthen-sasl-perl all 2.2000-1 [50,2 kB]
Get:28 https://ftp.debian.org/debian unstable/main amd64 libbrotli1 amd64 1.2.0-1 [308 kB]
Get:29 https://ftp.debian.org/debian unstable/main amd64 libjs-underscore all 1.13.7~dfsg+~1.13.0-6 [84,4 kB]
Get:30 https://ftp.debian.org/debian unstable/main amd64 libxdamage1 amd64 1:1.1.7-1 [16,0 kB]
Get:31 https://ftp.debian.org/debian unstable/main amd64 pci.ids all 0.0~2026.01.31-1 [278 kB]
Get:32 https://ftp.debian.org/debian unstable/main amd64 python3-brotli amd64 1.2.0-1 [330 kB]
Get:33 https://ftp.debian.org/debian unstable/main amd64 supermin amd64 5.2.2-7.1 [559 kB]
Fetched 13,6 MB in 1s (24,1 MB/s)
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs... Done
Extracting templates from packages: 100%
(Reading database... 359723 files and directories currently installed.)
Preparing to unpack .../00-at-spi2-common_2.59.1-1_all.deb...
Unpacking at-spi2-common (2.59.1-1) over (2.59.0-1)...
Preparing to unpack .../01-gir1.2-atk-1.0_2.59.1-1_amd64.deb...
Unpacking gir1.2-atk-1.0:amd64 (2.59.1-1) over (2.59.0-1)...
Preparing to unpack .../02-libatk-bridge2.0-0t64_2.59.1-1_amd64.deb...
Unpacking libatk-bridge2.0-0t64:amd64 (2.59.1-1) over (2.59.0-1)...
Preparing to unpack .../03-libatk1.0-0t64_2.59.1-1_amd64.deb...
Unpacking libatk1.0-0t64:amd64 (2.59.1-1) over (2.59.0-1)...
Preparing to unpack .../04-at-spi2-core_2.59.1-1_amd64.deb...
Unpacking at-spi2-core (2.59.1-1) over (2.59.0-1)...
Preparing to unpack .../05-libatspi2.0-0t64_2.59.1-1_amd64.deb...
Unpacking libatspi2.0-0t64:amd64 (2.59.1-1) over (2.59.0-1)...
Preparing to unpack .../06-libavahi-gobject0_0.8-18_amd64.deb...
Unpacking libavahi-gobject0:amd64 (0.8-18) over (0.8-17+b1)...
Preparing to unpack .../07-libavahi-glib1_0.8-18_amd64.deb...
Unpacking libavahi-glib1:amd64 (0.8-18) over (0.8-17+b1)...
Preparing to unpack .../08-avahi-utils_0.8-18_amd64.deb...
Unpacking avahi-utils (0.8-18) over (0.8-17+b1)...
Preparing to unpack .../09-avahi-daemon_0.8-18_amd64.deb...
Unpacking avahi-daemon (0.8-18) over (0.8-17+b1)...
Preparing to unpack .../10-libavahi-core7_0.8-18_amd64.deb...
Unpacking libavahi-core7:amd64 (0.8-18) over (0.8-17+b1)...
Preparing to unpack .../11-libavahi-client3_0.8-18_amd64.deb...
Unpacking libavahi-client3:amd64 (0.8-18) over (0.8-17+b1)...
Preparing to unpack .../12-libavahi-common3_0.8-18_amd64.deb...
Unpacking libavahi-common3:amd64 (0.8-18) over (0.8-17+b1)...
Preparing to unpack .../13-libavahi-common-data_0.8-18_amd64.deb...
Unpacking libavahi-common-data:amd64 (0.8-18) over (0.8-17+b1)...
Preparing to unpack .../14-libgprofng0_2.45.90.20260201-1_amd64.deb...
Unpacking libgprofng0:amd64 (2.45.90.20260201-1) over (2.45.90.20260125-1)...
Preparing to unpack .../15-libctf0_2.45.90.20260201-1_amd64.deb...
Unpacking libctf0:amd64 (2.45.90.20260201-1) over (2.45.90.20260125-1)...
Preparing to unpack .../16-libctf-nobfd0_2.45.90.20260201-1_amd64.deb...
Unpacking libctf-nobfd0:amd64 (2.45.90.20260201-1) over (2.45.90.20260125-1)...
Preparing to unpack .../17-binutils_2.45.90.20260201-1_amd64.deb...
Unpacking binutils (2.45.90.20260201-1) over (2.45.90.20260125-1)...
Preparing to unpack .../18-binutils-x86-64-linux-gnu_2.45.90.20260201-1_amd64.deb...
Unpacking binutils-x86-64-linux-gnu (2.45.90.20260201-1) over (2.45.90.20260125-1)...
Preparing to unpack .../19-libbinutils_2.45.90.20260201-1_amd64.deb...
Unpacking libbinutils:amd64 (2.45.90.20260201-1) over (2.45.90.20260125-1)...
Preparing to unpack .../20-binutils-common_2.45.90.20260201-1_amd64.deb...
Unpacking binutils-common:amd64 (2.45.90.20260201-1) over (2.45.90.20260125-1)...
Preparing to unpack .../21-libsframe3_2.45.90.20260201-1_amd64.deb...
Unpacking libsframe3:amd64 (2.45.90.20260201-1) over (2.45.90.20260125-1)...
Preparing to unpack .../22-busybox_1%3a1.37.0-9_amd64.deb...
Unpacking busybox (1:1.37.0-9) over (1:1.37.0-7)...
Preparing to unpack .../23-libpackagekit-glib2-18_1.3.4-3_amd64.deb...
Unpacking libpackagekit-glib2-18:amd64 (1.3.4-3) over (1.3.4-1)...
Preparing to unpack .../24-gir1.2-packagekitglib-1.0_1.3.4-3_amd64.deb...
Unpacking gir1.2-packagekitglib-1.0 (1.3.4-3) over (1.3.4-1)...
Preparing to unpack .../25-guestfs-tools_1.52.3-3.1_amd64.deb...
Unpacking guestfs-tools (1.52.3-3.1) over (1.52.3-3)...
Preparing to unpack .../26-libauthen-sasl-perl_2.2000-1_all.deb...
Unpacking libauthen-sasl-perl (2.2000-1) over (2.1900-1)...
Preparing to unpack .../27-libbrotli1_1.2.0-1_amd64.deb...
Unpacking libbrotli1:amd64 (1.2.0-1) over (1.1.0-2+b9)...
Preparing to unpack .../28-libjs-underscore_1.13.7~dfsg+~1.13.0-6_all.deb...
Unpacking libjs-underscore (1.13.7~dfsg+~1.13.0-6) over (1.13.7~dfsg+~1.13.0-5)...
Preparing to unpack .../29-libxdamage1_1%3a1.1.7-1_amd64.deb...
Unpacking libxdamage1:amd64 (1:1.1.7-1) over (1:1.1.6-1+b3)...
Preparing to unpack .../30-pci.ids_0.0~2026.01.31-1_all.deb...
Unpacking pci.ids (0.0~2026.01.31-1) over (0.0~2025.12.16-1)...
Preparing to unpack .../31-python3-brotli_1.2.0-1_amd64.deb...
Unpacking python3-brotli (1.2.0-1) over (1.1.0-2+b9)...
Preparing to unpack .../32-supermin_5.2.2-7.1_amd64.deb...
Unpacking supermin (5.2.2-7.1) over (5.2.2-7)...
Setting up pci.ids (0.0~2026.01.31-1)...
Setting up libxdamage1:amd64 (1:1.1.7-1)...
Setting up libauthen-sasl-perl (2.2000-1)...
Setting up libbrotli1:amd64 (1.2.0-1)...
Setting up binutils-common:amd64 (2.45.90.20260201-1)...
Setting up libsframe3:amd64 (2.45.90.20260201-1)...
Setting up libctf-nobfd0:amd64 (2.45.90.20260201-1)...
Setting up libpackagekit-glib2-18:amd64 (1.3.4-3)...
Setting up gir1.2-packagekitglib-1.0 (1.3.4-3)...
Setting up busybox (1:1.37.0-9)...
Setting up python3-brotli (1.2.0-1)...
Setting up libavahi-common-data:amd64 (0.8-18)...
Setting up libatspi2.0-0t64:amd64 (2.59.1-1)...
Setting up at-spi2-common (2.59.1-1)...
Setting up guestfs-tools (1.52.3-3.1)...
Setting up libbinutils:amd64 (2.45.90.20260201-1)...
Setting up supermin (5.2.2-7.1)...
Setting up libjs-underscore (1.13.7~dfsg+~1.13.0-6)...
Setting up libctf0:amd64 (2.45.90.20260201-1)...
Setting up libatk1.0-0t64:amd64 (2.59.1-1)...
Setting up gir1.2-atk-1.0:amd64 (2.59.1-1)...
Setting up libavahi-common3:amd64 (0.8-18)...
Setting up libgprofng0:amd64 (2.45.90.20260201-1)...
Setting up at-spi2-core (2.59.1-1)...
Setting up libavahi-glib1:amd64 (0.8-18)...
Setting up libavahi-core7:amd64 (0.8-18)...
Setting up libavahi-client3:amd64 (0.8-18)...
Setting up binutils-x86-64-linux-gnu (2.45.90.20260201-1)...
Setting up libatk-bridge2.0-0t64:amd64 (2.59.1-1)...
Setting up libavahi-gobject0:amd64 (0.8-18)...
Setting up binutils (2.45.90.20260201-1)...
Setting up avahi-daemon (0.8-18)...
avahi-daemon.service is a disabled or a static unit not running, not starting it.
avahi-daemon.socket is a disabled or a static unit not running, not starting it.
Setting up avahi-utils (0.8-18)...
Processing triggers for dbus (1.16.2-3)...
Processing triggers for initramfs-tools (0.150)...
update-initramfs: Generating /boot/initrd.img-6.18.8-1-siduction-amd64
E: busybox or busybox-static is required but not installed
update-initramfs: failed for /boot/initrd.img-6.18.8-1-siduction-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
old initramfs-tools package postinst maintainer script subprocess failed with exit status 1
Processing triggers for libc-bin (2.42-11)...
Processing triggers for man-db (2.13.1-1)...
Errors were encountered while processing:
initramfs-tools
Config is in use.
needrestart is being skipped since dpkg has failed
Error: Sub-process /usr/bin/dpkg returned an error code (1)
The message seams wrong to me, as busybox is installed.
# dpkg -l | grep ii | grep busybox
ii busybox 1:1.37.0-9 amd64 Tiny utilities for small and embedded systems
I tried:
# update-initramfs -u -k all
update-initramfs: Generating /boot/initrd.img-6.18.8-1-siduction-amd64
E: busybox or busybox-static is required but not installed
update-initramfs: failed for /boot/initrd.img-6.18.8-1-siduction-amd64 with 1.
but got the same error.
Any idea how I could get the cow off the ice? I did not try to reboot in this situation yet... Thanks.
Did you try to install busybox-static, followed by sudo dpkg --configure -a and sudo update-initramfs -u -k 6.18.8-1-siduction-amd64?
When I try to replace busybox with busybox-static it failed.
# apt install busybox-static
Installing:
busybox-static
REMOVING:
busybox
Summary:
Upgrading: 0, Installing: 1, Removing: 1, Not Upgrading: 0
1 not fully installed or removed.
Download size: 961 kB
Space needed: 1.239 kB / 607 GB available
Continue? [Y/n] Y
Get:1 https://ftp.debian.org/debian unstable/main amd64 busybox-static amd64 1:1.37.0-9 [961 kB]
Fetched 961 kB in 0s (5.978 kB/s)
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
dpkg: busybox: dependency problems, but removing anyway as you requested:
cryptsetup-initramfs depends on busybox | busybox-static; however:
Package busybox is to be removed.
Package busybox-static is not installed.
(Reading database... 359711 files and directories currently installed.)
Removing busybox (1:1.37.0-9)...
Selecting previously unselected package busybox-static.
(Reading database... 359702 files and directories currently installed.)
Preparing to unpack .../busybox-static_1%3a1.37.0-9_amd64.deb...
Unpacking busybox-static (1:1.37.0-9)...
Setting up initramfs-tools (0.150)...
update-initramfs: deferring update (trigger activated)
Setting up busybox-static (1:1.37.0-9)...
Processing triggers for man-db (2.13.1-1)...
Processing triggers for initramfs-tools (0.150)...
update-initramfs: Generating /boot/initrd.img-6.18.8-1-siduction-amd64
E: busybox or busybox-static is required but not installed
update-initramfs: failed for /boot/initrd.img-6.18.8-1-siduction-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
old initramfs-tools package postinst maintainer script subprocess failed with exit status 1
Errors were encountered while processing:
initramfs-tools
Config is in use.
needrestart is being skipped since dpkg has failed
Error: Sub-process /usr/bin/dpkg returned an error code (1)
Quote from: devil on 2026/02/01, 22:50:43
Did you try to install busybox-static, followed by sudo dpkg --configure -a and sudo update-initramfs -u -k 6.18.8-1-siduction-amd64?
# dpkg --configure -a
Setting up initramfs-tools (0.150)...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.150)...
update-initramfs: Generating /boot/initrd.img-6.18.8-1-siduction-amd64
E: busybox or busybox-static is required but not installed
update-initramfs: failed for /boot/initrd.img-6.18.8-1-siduction-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
old initramfs-tools package postinst maintainer script subprocess failed with exit status 1
Errors were encountered while processing:
initramfs-tools
# update-initramfs -u -k 6.18.8-1-siduction-amd64
update-initramfs: Generating /boot/initrd.img-6.18.8-1-siduction-amd64
E: busybox or busybox-static is required but not installed
update-initramfs: failed for /boot/initrd.img-6.18.8-1-siduction-amd64 with 1.
:'(
The error I just got.
important bugs of busybox (1:1.37.0-7 → 1:1.37.0-9) <Outstanding>
b1 - #1126809 - busybox breaks mkinitramfs
b2 - #1126810 - busybox versions 1:1.37.0-8 and 1:1.37.0-9 removed $BUSYBOXDIR stating that initramfs-tools no longer use it, however initramfs-tools depends on initramfs-tools-core which still checks for and uses it in /usr/sbin/mkinitramfs
Summary:
busybox(2 bugs)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...]
I aborted the D-U
:o
Although I have apt-listbugs installed, I didn't get that message.
# dpkg -l | grep ii | grep apt-listbugs
ii apt-listbugs 0.1.47 all tool which lists critical bugs before each APT installation
# apt-listbugs list busybox
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
# apt-listbugs list busybox-static
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
apt purge initramfs-tools
worked for me
(http://https:/piperfarms.us/images/thumb-remove.png)
(http://https:/piperfarms.us/images/remove.png)
Bug report from today.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126810
Quote from: piper on 2026/02/01, 23:53:50
apt purge initramfs-tools
worked for me
Did it bring in dracut etc?
I was able to work around it by downgrading busybox, by
dpkg -i /var/cache/apt/archives/busybox_1%3a1.37.0-7_amd64.deb
then this command to finish all the failed upgrade
apt -f install
Worked for me.
Dracut is also listing some bugs:
important bugs of dracut-core (→ 109-11) <Outstanding>
b1 - #1095646 - dracut-core: Shipping /usr/lib/kernel/install.d/50-dracut.install causes two initrds to be installed on kernel postinst
b2 - #1108404 - dracut-core: Emergency shell does not work due to locked root user
b3 - #1110250 - Emergency shell is inaccessible: "Cannot open access to console, the root account is locked."
b4 - #1121043 - overlayfs module fails to mount an overlay over a BTRFS filesystem, breaking live boot
important bugs of dracut (→ 109-11) <Outstanding>
b5 - #1073825 - dracut: manual dracut creates initramfs-*.img files, post-install hook does initrd.img-*
b6 - #1074609 - dracut: fails to install cryptsetup (lvm-on-luks)
b7 - #1078545 - multipathd.socket may lack Conflicts= lines
b8 - #1103457 - Unable to boot LUKS-encrypted system
b9 - #997827 - dracut: /usr/lib/dracut/dracut-install ommit dependancies in .so
important bugs of dracut (→ 109-11) <Resolved in some Version>
b10 - #1078792 - unbootable system after installing dracut on a standard Debian installation - #2 (Fixed: dracut/105-1 dracut/105-2~exp1 dracut/105-2~exp2 dracut/105-2~exp3 dracut/105-2~exp4 dracut/105-2~exp5 dracut/105-2~exp6 dracut/105-2~exp7 dracut/105-2~exp8)
Summary:
dracut-core(4 bugs), dracut(6 bugs)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...]
Hi all! I got the same error.
What to do? Shall we wait for the fix (the bug is known and registered)?
Looks like the bug was just filed today so I'm going to wait myself.
Quote from: piper on 2026/02/01, 23:53:50
apt purge initramfs-tools
worked for me
Thanks,- I really thought I worked for me too. :)
# apt purge initramfs-tools
Suggested packages:
dracut-network isomd5sum kpartx systemd-cryptsetup
# apt install dracut-network systemd-cryptsetup
Suggested packages:
iscsiuio
Recommended packages:
nbd-client
# apt autopurge
REMOVING:
initramfs-tools-bin* initramfs-tools-core* klibc-utils* libklibc*
Summary:
Upgrading: 0, Installing: 0, Removing: 4, Not Upgrading: 0
# update-initramfs -u -k all
update-initramfs: Generating /boot/initrd.img-6.18.8-1-siduction-amd64
update-initramfs: Generating /boot/initrd.img-6.18.7-1-siduction-amd64
Sorry - it failed, as after reboot systemd-cryptsetup was not able to decrypt root. :'(
So be warned to follow that path too easily like me.
Using my steps and rebooting my setup decrypted fine, not sure if I am using systemd-cryptsetup.
This is maybe a 2-3 year old install on my laptop.
Follow up, yes I am using systemd-cryptsetup to encrypt my laptop.
Quote from: terroreek on 2026/02/02, 00:06:05
I was able to work around it by downgrading busybox, by
dpkg -i /var/cache/apt/archives/busybox_1%3a1.37.0-7_amd64.deb
then this command to finish all the failed upgrade
apt -f install
Worked for me.
Worked for me too.
Didn't find busybox_1.37.0-7_amd64.deb in /var/cache/apt/archives/ so :
wget http://ftp.debian.org/debian/pool/main/b/busybox/busybox_1.37.0-7_amd64.deb
Thank's
wow what a roll, confirm previous busybox was not in apt cache anymore nor in sid repos but the above post saved my day better than gemini could have, then I did
Quotesudo apt-mark hold busybox
I like this particular community of nerds!
I had the same problem last night, after a
apt purge cryptsetup-initramfs
the problem was solved. Please use it only if dosen't use cryptsetup.
Ich hatte letzte Nacht das selbe Problem, nach einem
apt purge cryptsetup-initramfs
war das Problem gelöst. Bitte nur anwenden wenn du cryptsetup nicht benutzt.
Quote from: micspabo on 2026/02/02, 01:23:45
Sorry - it failed, as after reboot systemd-cryptsetup was not able to decrypt root. ....
So
$ sudo apt depends cryptsetup-initramfs
cryptsetup-initramfs
|Depends: busybox
.........You can simply change your debian repo from unstable to stable, then
apt remove busybox cryptsetup-initramfs
apt update
apt install cryptsetup-initramfs (which should pull in busybox as a depedency)
Confirm it is all OK
dpkg --configure -aDon't forget to change the debian repo back to unstable.
You can pin it like @n4ai9i522 says, or just wait until they fix the bug before doing a full-upgrade.
Looks like busybox has been fixed and there is a new version in the repos. If not it will be soon.
Quote from: eriefisher on 2026/02/02, 16:03:17
Looks like busybox has been fixed and there is a new version in the repos. If not it will be soon.
Thanks for the update! I checked, it was updated, everything went smoothly. This glitch was fixed. :)
Looks like I have to do my first desaster-rollback.
I identified the working snapshot number by booting into it, but I am not able to reboot back to the current default subvolume
because that gets stuck at
[ OK ] reached target remote-fs-pre.target - Preparation for Remote File System.
[ OK ] reached target remote-cryptsetup.target - Remote Encrypted Volumes.
[ OK ] reached target remote-fs.target - Remote File System.
[ ** ] Job dev-mapper-luks\x2d400d59ef\x2d905b\x2d47cd\x2d9d2b\x2daa1ccf74c098.device/start running (Xmin Ys / no limit)
As I am not able to boot into the current default subvolume,
how should I do the rollback in that case?
Is Point 3b from <https://forum.siduction.org/index.php?topic=8832.msg70588#msg70588> already possible three years after that post?
# dpkg -l | grep ii | grep siduction-btrfs
ii siduction-btrfs 0.4.0-1 all Optimizes the boot menu and the description in Snapper
Quote from: micspabo on 2026/02/03, 12:25:32
Is Point 3b from <https://forum.siduction.org/index.php?topic=8832.msg70588#msg70588> already possible three years after that post?
No.
You need an r/w snapshot of the working subvolume.
Please take a look at
https://forum.siduction.org/index.php?topic=9305.msg78552#msg78552
Q: Is the GRUB menu visible, and does the system journal show this line?
Reached target local-fs.targetIf so, press the E key when the GRUB menu appears and add " 1" to the kernel line.
This is how you boot into emergency.targe whithout network connection, so the error shown above cannot occur.
Display the list of snapshots and perform a rollback.
snapper list
snapper -a classic rollback <nr>
Quote from: scholle1 on 2026/02/04, 15:02:10
Quote from: micspabo on 2026/02/03, 12:25:32
Is Point 3b from <https://forum.siduction.org/index.php?topic=8832.msg70588#msg70588> already possible three years after that post?
No.
You need an r/w snapshot of the working subvolume.
Please take a look at
https://forum.siduction.org/index.php?topic=9305.msg78552#msg78552
Q: Is the GRUB menu visible, and does the system journal show this line?
Reached target local-fs.target
If so, press the E key when the GRUB menu appears and add " 1" to the kernel line.
This is how you boot into emergency.targe whithout network connection, so the error shown above cannot occur.
Display the list of snapshots and perform a rollback.
snapper list
snapper -a classic rollback <nr>
a.) OK,- Point 3b is not possible. Thanks!
b.) What I read from your given link is that I expect I have to boot from a Siduction usb stick and prepare a "chroot" environment to proceed. Not sure what I have to do in there yet.
c.) When I do a fresh boot I am able to enter the passphrase for
Enter passphrase for hd1,gpt2 (xxx):
then I see the GRUB menu.
When I select the first entry to boot into "current default subvolume", the system get stuck and I cannot check journalctl,- I can only take a picture with my phone.
But I can successfully boot into submenu "siduction snapshots" and boot and login into snapshot number 1712, which I'd like to make the current default somehow. And I can successfully boot into my second OS, where I now writing from.
d.) Do I have to do
Quote
If so, press the E key when the GRUB menu appears and add " 1" to the kernel line.
on my failing current default? And collecting snapper list from there?
Quote from: micspabo on 2026/02/04, 22:22:04
d.) Do I have to do
Quote
If so, press the E key when the GRUB menu appears and add " 1" to the kernel line.
on my failing current default? And collecting snapper list from there?
No, misunderstanding on my part regarding your terminal output.
If decryption fails with the subvolume in question, the hint is of no use.
I tested a solution on my laptop, but without an encrypted hard drive.
Next post.
ENGLISH (deutsch weiter unten)
A solution if booting into the standard subvolume after a DU is no longer possible, even in emergency.target.
Btrfs file system; in this state, no rollback with snapper is possible.Starting point for this example.
The paths must be adapted to your own circumstances.
- siduction installation with configured snapper and the siduction-btrfs package installed.
- The defective standard snapshot has the number 1716
- The snapshot used for recovery has the number 1712
- Determine the kernels present in snapshot 1712. (e.g., 6.18.6-1-siduction-amd64)
- Reminder: For Btrfs, snapshots are also subvolumes!
The solution.
- Boot the siduction live system from a USB stick,
start the chroot helper on the affected hard drive/partition.
Execute the following commands.
btrfs sub li /
The output is a list of the existing subvolumes for /.
We are interested in the lines with
[...] path @snspshots/1712/snapshot
[...] path @snspshots/1716/snapshot
btrfs sub snapshot /.snapshots/1712/snapshot /.snapshots/rescue
This creates a snapshot with the path /@snapshots/rescue from subvolume no. 1712.
Exit chroot and reboot. - When the GRUB menu appears, press the "E" key. Then change the kernel and initrd lines.
linux /@snapshots/rescue/boot/vmlinuz-6.18.6-1-siduction-amd64 [...] rootflags=subvol=@snapshots/rescue [...]
initrd /@snapshots/rescue/boot/initrd.img-6.18.6-1-siduction-amd64
The changed parts are highlighted in bold and underlined.
Boot with F10. We are now in the rescue subvolume.
Start a terminal and become root.
The command
btrfs sub li /
now also shows us a subvolume with the path @snapshots/rescue, and
the command
snapper list
shows a + instead of the usual * for snapshot 1716.
This means that we are not in this snapshot, but it is still the default subvolume.
Snapper does not recognize the subvolume @snapshots/rescue.
We clean up the situation by performing another rollback with snapper.
snapper -a classic rollback 1712
Now continuity is ensured in snapper and we can leave the rescue subvolume with a reboot. - Now that we have arrived at the new snapshot 1718, we should clean up.
First, check the output in the root terminal:
btrfs sub li /
snapper list
Both outputs show the additional snapshots 1717 and 1718.
In snapper, there is a * next to 1718.
Btrfs contains the subvolume with the path @snapshots/rescue. We dispose of it with
btrfs sub delete /.snapshots/rescue
The system is now clean again and, after extensive testing, any snapshots that are no longer needed should be removed.
I hope there are no typos in the commands. Good luck.
DEUTSCHEin Lösungsweg wenn booten in das Standardsubvolumen nach einem DU auch im emergency.target nicht mehr möglich ist.
Btrfs Dateisystem, in diesem Zustand kein Rollback mit snapper möglich.Ausgangslage für dieses Beispiel.
Die Pfade müssen an die eigenen Gegebenheiten angepasst werden.
- siduction Installation mit konfiguriertem snapper und dem installierten Paket siduction-btrfs.
- Der defekte standard Snapshot hat die Nummer 1716
- Der Snapshot, der für die Wiederherstellung benutzt wird, hat die Nummer 1712
- Die im Snapshot 1712 vorhandenen Kernel ermitteln. (z.B. 6.18.6-1-siduction-amd64)
- Zur Erinnerung: Für Btrfs sind Snapshots genauso Subvolumen!
Der Lösungsweg.
- siduction live System vom USB Stick booten,
den Chroot Helfer in die betroffene Festplatte/Partition starten.
Folgende Kommandos ausführen.
btrfs sub li /
Ausgabe ist eine Lister der vorhandenen Subvolumen für /
Für uns von Interesse sind die Zeilen mit
[...] path @snspshots/1712/snapshot
[...] path @snspshots/1716/snapshot
btrfs sub snapshot /.snapshots/1712/snapshot /.snapshots/rescue
Das erstellt einen snapshot mit dem Pfad /@snapshots/rescue vom Subvolumen Nr. 1712.
Chroot verlassen und reboot. - Wenn das GRUB Menü erscheint, die Taste "E" drücken. Dann die Kernel und initrd Zeilen ändern.
linux /@snapshots/rescue/boot/vmlinuz-6.18.6-1-siduction-amd64 [...] rootflags=subvol=@snapshots/rescue [...]
initrd /@snapshots/rescue/boot/initrd.img-6.18.6-1-siduction-amd64
Die geänderten Teile sind fett und unterstrichen hervorgehoben.
Mit F10 booten. Wir befinden uns im rescue Subvolumen. - Ein Terminal starten und zu root werden.
Der Befehl
btrfs sub li /
zeigt uns jetzt auch ein Subvolumen mit dem Pfad @snapshots/rescue und
der Befehl
snapper list
zeigt beim Snapshot 1716 ein + statt des üblichen *.
Das bedeutet, dass wir uns nicht in diesem Snapshot befinden, er aber nach wie vor das Standardsubvolumen ist.
Snapper kennt das Subvolumen @snapshots/rescue nicht.
Wir bereinigen die Situation, indem wir noch einmal einen Rollback mit snapper ausführen.
snapper -a classic rollback 1712
Jetzt ist die Kontinuität in snapper gegeben und wir können das rescue Subvolumen mit einem reboot velrassen. - Im neuem Snapshot 1718 angekommen, sollten wir noch aufräumen.
Zuerst im root Terminal die Ausgaben zur Kontrolle:
btrfs sub li /
snapper list
Beide Ausgaben zeigen die zusätzlichen Snpshots 1717 und 1718.
Bei snapper steht neben 1718 ein *.
Btrfs enthält das Subvolumen mit dem Pfad @snapshots/rescue. Wir entsorgen es mit
btrfs sub delete /.snapshots/rescue
Jetzt ist das System soweit wieder sauber und nach ausführlichen Tests sollten nicht mehr benötigte Shnapshots entfernt werden.
Ich hoffe mir sind in den Kommandos keine Tippfehler unterlaufen. Gutes gelingen.
Quote from: scholle1 on 2026/02/05, 13:03:18
ENGLISH (deutsch weiter unten)
...
I hope there are no typos in the commands. Good luck.
DEUTSCH
...
Ich hoffe mir sind in den Kommandos keine Tippfehler unterlaufen. Gutes gelingen.
Thank you very much for all the details.
With a bit of more time I will try the emergency.target or the kernel parameter
systemd.unit=rescue.target
to see if I can get my fingers into the standard subvolume to execute a rollback from there.
Next autumn I would probably have a little more time to delve into the depths of btrfs – as my retirement is just around the corner. ;)