Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #76932 > unrolled thread
| Started by | Hideki Yamane <henrich@iijmio-mail.jp> |
|---|---|
| First post | 2022-11-05 11:50 +0100 |
| Last post | 2022-11-14 18:40 +0100 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.kernel
Bug#1023492: linux-signed-amd64: Cannot boot with message "cryptsetup: Waiting for encrypted source device UUID=xxxx..." Hideki Yamane <henrich@iijmio-mail.jp> - 2022-11-05 11:50 +0100
Bug#1023492: marked as done (linux-signed-amd64: Cannot boot with message "cryptsetup: Waiting for encrypted source device UUID=xxxx...") "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-11-14 18:40 +0100
| From | Hideki Yamane <henrich@iijmio-mail.jp> |
|---|---|
| Date | 2022-11-05 11:50 +0100 |
| Subject | Bug#1023492: linux-signed-amd64: Cannot boot with message "cryptsetup: Waiting for encrypted source device UUID=xxxx..." |
| Message-ID | <FooUp-1ynW-1@gated-at.bofh.it> |
Source: linux-signed-amd64 Version: 6.0.6+2 Severity: important Dear Maintainer, I cannot boot my amd64 PC with linux-image-6.0.0-2-amd64, it just shows "cryptsetup: Waiting for encrypted source device UUID=xxxx" again and again, then falled down to busybox shell. With 6.0.0-1 works, 6.1~rc3+1~exp1 in experimental also does not work. $ LANG=C df -h -x tmpfs Filesystem Size Used Avail Use% Mounted on udev 15G 0 15G 0% /dev /dev/mapper/tiny--vg-system 328G 224G 104G 69% / /dev/sda2 235M 221M 1.8M 100% /boot /dev/mapper/tiny--vg-home 559G 391G 168G 70% /home /dev/nvme0n1p1 256M 34M 223M 14% /boot/efi $ mount|grep mapper /dev/mapper/tiny--vg-system on / type btrfs (rw,relatime,ssd,space_cache,subvolid=5,subvol=/) /dev/mapper/tiny--vg-home on /home type btrfs (rw,relatime,compress=zstd:3,ssd,space_cache,subvolid=5,subvol=/) -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.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
[toc] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2022-11-14 18:40 +0100 |
| Subject | Bug#1023492: marked as done (linux-signed-amd64: Cannot boot with message "cryptsetup: Waiting for encrypted source device UUID=xxxx...") |
| Message-ID | <FrLB7-3HJB-3@gated-at.bofh.it> |
| In reply to | #76932 |
[Multipart message — attachments visible in raw view] — view raw
Your message dated Mon, 14 Nov 2022 22:37:22 +0900 with message-id <20221114223722.766c6f865f52fa4426a2b9a0@iijmio-mail.jp> and subject line has caused the Debian Bug report #1023492, regarding linux-signed-amd64: Cannot boot with message "cryptsetup: Waiting for encrypted source device UUID=xxxx..." 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.) -- 1023492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023492 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web