Your message dated Tue, 22 Apr 2025 22:07:11 +0000 with message-id <E1u7Lln-009udx-LZ@fasolo.debian.org> and subject line Bug#1103476: fixed in rescue 1.100 has caused the Debian Bug report #1103476, regarding "debian-installer: Rescue mode cannot execute a shell for any default btrfs installations" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1103476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103476 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: debian-installer: Rescue mode can not execute shell when root filesystem is btrfs
- From: Tyler Riddle <cardboardaardvark@gmail.com>
- Date: Thu, 10 Apr 2025 14:24:58 -0600
- Message-id: <[🔎] 174431669893.3629.10582648992731094445.reportbug@gornon>
Package: debian-installer Version: Trixie Alpha 1 Severity: normal Tags: d-i X-Debbugs-Cc: cardboardaardvark@gmail.com, debian-boot@lists.debian.org Dear Maintainer, When using rescue mode with a root file system that is btrfs the option to launch a shell inside the root file system does not function. This is because when the Debian installer created the btrfs file system it setup a subvolume named rootfs and performed the install into it. When the file system is mounted in rescue mode it is not mounted using the subvolume so /target has a directory inside it named @rootfs and that directory is where the actual root file system is. In order to get a shell inside the root file system I use the following work around: 1) Launch a shell inside the rescue environment 2) execute chroot /target/@rootfs /bin/bash --login It's annoying but it works. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.12.21-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
- To: 1103476-close@bugs.debian.org
- Subject: Bug#1103476: fixed in rescue 1.100
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Tue, 22 Apr 2025 22:07:11 +0000
- Message-id: <E1u7Lln-009udx-LZ@fasolo.debian.org>
- Reply-to: Nicholas D Steeves <sten@debian.org>
Source: rescue Source-Version: 1.100 Done: Nicholas D Steeves <sten@debian.org> We believe that the bug you reported is fixed in the latest version of rescue, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1103476@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicholas D Steeves <sten@debian.org> (supplier of updated rescue package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Tue, 22 Apr 2025 13:59:04 -0400 Source: rescue Binary: rescue-check rescue-mode Architecture: source all Version: 1.100 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team <debian-boot@lists.debian.org> Changed-By: Nicholas D Steeves <sten@debian.org> Description: rescue-check - enter d-i rescue mode if requested (udeb) rescue-mode - mount requested partition and start a rescue shell (udeb) Closes: 1018894 1103476 Changes: rescue (1.100) unstable; urgency=medium . * Team upload. . [ Pascal Hambourg and Nicholas D Steeves ] * Add preliminary support for rescuing Debian installed to a btrfs subvolume (Closes: #1018894, #1103476). Supported rescue cases are: 1. The default installation to @rootfs (bookworm and later) 2. The default installation to subvolid=5 (buster or earlier). "subvolid=5" was chosen over "subvol=/" for maximum disambiguation. Checksums-Sha1: 430271a0c5aef9aad0ca98a78f0eb6c1a24afc05 1653 rescue_1.100.dsc bc3a0c0673aa0c4966e3f11317a8ab0f93b73568 145672 rescue_1.100.tar.xz 279c7619bee0c655d6b8ff2ec12ef85d94309830 2488 rescue-check_1.100_all.udeb 5f1244cbc621ceab6a48b3a401dbaba0b2d02b30 103656 rescue-mode_1.100_all.udeb af194b29654e962a9050c7ad20cfe7db1cbf0f3c 5895 rescue_1.100_amd64.buildinfo Checksums-Sha256: e453db95d9052dfb25b80a30e91d5a3c8079f9d3434b02cd5bb3e96206e7338e 1653 rescue_1.100.dsc 585625a5e2739b65db25dbc14bf9d036a0e6a082db5a8d07a13c57e7cfe1f04d 145672 rescue_1.100.tar.xz 4a79103bf9abd093c16e7dea3d30a24c4e224b59491c7985bd9e4594b6ef8337 2488 rescue-check_1.100_all.udeb 22bfc01c4211ee571124f16a26e38457fbf8b6f396153c667095372568a147ce 103656 rescue-mode_1.100_all.udeb 7464f90a8cda30bb9cb63a95e0d70ad5ac046f74ba70a61fc825c94aa7c1e5db 5895 rescue_1.100_amd64.buildinfo Files: da5bc22697d0c189781550562155ab12 1653 debian-installer optional rescue_1.100.dsc 6560475e0e3fc77a023cb940ce523442 145672 debian-installer optional rescue_1.100.tar.xz 4aa0d3e5491f280709f48f3108ce9ee6 2488 debian-installer optional rescue-check_1.100_all.udeb ed8babbd28e4afdaee57016e66fb455f 103656 debian-installer optional rescue-mode_1.100_all.udeb 6e0d940dd9b8fcd7aa29bd7e32b7090f 5895 debian-installer optional rescue_1.100_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE4qYmHjkArtfNxmcIWogwR199EGEFAmgIDtQACgkQWogwR199 EGEZ3w/8CAR0TQvFqFhCRhHQ4ph3uA+CdHMWef2iWyfUoaQKgRN/iDHMKhr/+hB2 /5waOnH/YKaHZc3S9MuvmW8vszmSzfZ8mA0yDSyeXYpo7Oud0unsy3IW0cQ4GIxT 8gf+ylvC8SSANGXSM7kqlly8ZskPo5q8TyW2mpV6Al2O3z5JJZwad81ccFWfGm4I x/EvmjqV9Ac2RXVfu+ex3wNZDrKkMxYYW/440tL6px2dQ1JOOf36529lk5Fuk7uB m2904ZUXumbRNCdV0LFS0tzi+mtRLayGoaZwCq9hr/F/FMD6XnQtuz95gWUFG+Dq 1ewMSpgabaZMLr1EQ2pExjU9V4/c39btI3ZJyNt7TLDhtic14+a0o1Y0UdgG6eAA 98krxl3BIX6ig/+arXSPb/rl3HABjv6dNCVoSJv3tQcd+pAYQdIcaSZ6awXlA55N CKbaeaXZzDavNbvGCYRgESKkrdivurAbEpreM704guPZqIJI59GYW3ZYYM8UrcT/ 692tE2G8JMCWKL+79XXHT47bzZRlBI32XkHNFa7ueDDpro1bQpiAaqKDk7pSa/Ji +N8qtJulrQ7ch2qRtZhKQHaH3D6ck4f3b3xl7hEMgH8V+qnTrYbgUCCmbotdBZBn 6qhKihAPo9amP4qbG129hQMIbSmPXai1VkOgLmYOHbQ+kmJLdt0= =8QGn -----END PGP SIGNATURE-----Attachment: pgpmSV8ZZ2UgR.pgp
Description: PGP signature
--- End Message ---