[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1023503: marked as done (busybox-static: "ALERT! UUID=xxx does not exist. Dropping to a shell!" since 1:1.35.0-3)

Your message dated Sat, 21 Jan 2023 19:52:12 +0300
with message-id <19e888b1-c7be-78af-1b16-e51acc21d446@msgid.tls.msk.ru>
and subject line Re: busybox-static: "ALERT! UUID=xxx does not exist. Dropping to a shell!" since 1:1.35.0-3
has caused the Debian Bug report #1023503,
regarding busybox-static: "ALERT! UUID=xxx does not exist. Dropping to a shell!" since 1:1.35.0-3
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.)


-- 
1023503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023503
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: busybox-static
Version: 1:1.35.0-3
Severity: normal

Hello everynyan!

Since 1:1.35.0-3, initramfs doesn't find the UUID of the root partition
anymore and drops me to a shell. In the shell however, the uuid is
listed in both /dev/disk/by-uuid and blkid.

At first, I didn't even know how I would boot going forward. First I
tried seting rootdelay in grub, but without any success. Only randomly
would I try to go root=/dev/sda2, setting the root partition by path,
thereby being able to see my login screen again.

Unsure of what to do, I tune2fs -U random every uuid and change the
fstab accordingly, followed by update-initramfs -u and update-grub.
When rebooting, initramfs just complains that it can't locate the new
uuid. Next I randomly downgrade packages that apt updated recently.
Ultimately I discover that when using busybox-static 1:1.35.0-2, the
problem is gone. When upgrading back to 1:1.35.0-3, it's there again.

There you go,

Bye


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 1:1.35.0-4

On Sat, 5 Nov 2022 15:37:32 +0100 Stefan Berzl <stefanberzl@gmail.com> wrote:

Package: busybox-static
Version: 1:1.35.0-3
Severity: normal

Hello everynyan!

Since 1:1.35.0-3, initramfs doesn't find the UUID of the root partition
anymore and drops me to a shell. In the shell however, the uuid is
listed in both /dev/disk/by-uuid and blkid.


This is #1023501, which has been fixed in 1.35.0-4:

busybox (1:1.35.0-4) unstable; urgency=medium

  * static build: disable blkid applet (CONFIG_BLKID, #1023501)

    Since static build has CONFIG_FEATURE_PREFER_APPLETS=y, enabling
    any utility which is also provided by the system in other ways
    can be risky, since busybox shell will choose its applet version
    instead of running the actual utility, even if that utility file
    exists in $PATH. After enabling blkid, we effectively overwrote
    blkid from libblkid as used in initramfs. The result was non-
    working udev rules for block devices (not creating /dev/disk/by-*/),
    and the system's unbootable.

    Disable it for now at least on static build.
    Closes: 1023501

Thanks,

/mjt

--- End Message ---
Reply to: