Bug#974939: closed by Ben Hutchings (Re: Bug#974939: machine does not boot)
Hi Ben,
On Mon, Nov 23, 2020 at 10:45:09AM +, Debian Bug Tracking System wrote:
> I recommend that you always check the list of packages to be removed in
> a dist-upgrade, if you have some packages installed from
> testing/unstable.
yes. :/
> It doesn't exist in stable. Perhaps you installed something from
> testing/unstable that required it? libgcc-s1 breaks the stable version
> of cryptsetup-initramfs.
I checked. My apt and libc6 are both from stable, and should thus only
have stable dependencies, right?
However, removing libgcc-s1 broke apt ("could not load shared
library...").
Thanks for the heads-ups,
Toni
Bug#974939: machine does not boot
Hi Ben, On Mon, Nov 23, 2020 at 10:12:01AM +, Ben Hutchings wrote: > On Mon, 2020-11-23 at 10:04 +, Toni Mueller wrote: > > I agree, but I can only file a bug report against the kernel package. > > Please find the output of this command attached. > cryptsetup support is not included in the newer initramfs images. I saw that, but was not aware of this package: > Did you remove cryptsetup-initramfs by accident? Not that I am aware of, and definitely not intentionally. Until now, I had no idea that it even existed. But I can now see that it was removed in a dist-upgrade run on the 9th of May last year (huh?!?). But there seems to be a problem to re-install it: # apt install cryptsetup-initramfs -y ... The following packages will be REMOVED: libgcc-s1 The following NEW packages will be installed: cryptsetup-initramfs WARNING: The following essential packages will be removed. This should NOT be done unless you know exactly what you are doing! libgcc-s1 0 upgraded, 1 newly installed, 1 to remove and 2 not upgraded. E: Essential packages were removed and -y was used without --allow-remove-essential. Since libgcc-s1 is being provided by libgcc1, I am inclined to run with --allow-remove-essential. But this is still quite scary! (I wasn't aware of libgcc-s1, either. :( ) Thanks, Toni
Bug#974939: machine does not boot
On Mon, 2020-11-23 at 10:04 +, Toni Mueller wrote: > > Hi Ben! > > On Tue, Nov 17, 2020 at 11:26:53AM +, Ben Hutchings wrote: > > On Mon, 2020-11-16 at 19:41 +, Toni wrote: > > > Package: src:linux > > > Version: 4.19.152-1 > > > Severity: critical > > > passphrase, but using these two kernels, I'm not, and the machine just > > > cycles trying to find the root partition. I am now running the -10 > > > kernel again, which I would like to get off of. I've tried recovery mode > > > without any success. > > > > This is probably an issue with the initramfs built for this kernel, and > > not with the kernel itself. Please send the output of the command: > > > > lsinitramfs /boot/initrd.img-4.19.0-12-amd64 > > I agree, but I can only file a bug report against the kernel package. > Please find the output of this command attached. [...] cryptsetup support is not included in the newer initramfs images. Did you remove cryptsetup-initramfs by accident? Ben. -- Ben Hutchings For every complex problem there is a solution that is simple, neat, and wrong. signature.asc Description: This is a digitally signed message part
Bug#974939: machine does not boot
Hi, On Tue, Nov 17, 2020 at 12:50:19PM +0100, Bastian Blank wrote: > On Mon, Nov 16, 2020 at 07:41:05PM +, Toni wrote: > > Severity: critical > > Sorry, no. This problem does not break the package for everyone. > > > On the console, after dmesg, these three lines repeat ad nauseum: > > mdadm: No arrays found in config file or automatically > > Volume group "ev0" not found > > Cannot process volume group ev0 > > mdadm: No arrays found in config file or automatically > > Volume group "ev0" not found > > Cannot process volume group ev0 > > So it actually boots, but the boot process is not able to find your root > filesystem? It loads the kernel, I can see the dmesg, and then I see an endless loop of these messages. So yes, there's something broken with encrypted partitions, that wasn't broken until the -10 kernel. > Yes, that look pretty normal and like something the Debian installer > would create. It did. > What is the content of /etc/crypttab? /etc/fstab? /boot/grub/grub.conf? > What do you have mdadm for? I don't have mdadm devices in this machine (it's a laptop with only one SSD, anyway). I don't know why mdadm is present on this machine, but it has "always" been, with no detrimental effects until possibly recently. Thanks, Toni
Bug#974939: machine does not boot
Control: severity -1 important On Mon, Nov 16, 2020 at 07:41:05PM +, Toni wrote: > Severity: critical Sorry, no. This problem does not break the package for everyone. > On the console, after dmesg, these three lines repeat ad nauseum: > mdadm: No arrays found in config file or automatically > Volume group "ev0" not found > Cannot process volume group ev0 > mdadm: No arrays found in config file or automatically > Volume group "ev0" not found > Cannot process volume group ev0 So it actually boots, but the boot process is not able to find your root filesystem? > The disk configuration is pretty straightforward: > > git:(master*)$ lsblk > NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT > nvme0n1 259:00 953.9G 0 disk > ├─nvme0n1p1 259:10 238.4M 0 part > ├─nvme0n1p2 259:20 3.5G 0 part > ├─nvme0n1p3 259:30 953M 0 part /boot > └─nvme0n1p4 259:40 949.2G 0 part > └─nvme0n1p4_crypt 253:00 949.2G 0 crypt > ├─ev0-swap 253:10 29.8G 0 lvm [SWAP] > ├─ev0-root 253:20 789.4G 0 lvm / Yes, that look pretty normal and like something the Debian installer would create. What is the content of /etc/crypttab? /etc/fstab? /boot/grub/grub.conf? What do you have mdadm for? Regards, Bastian -- You can't evaluate a man by logic alone. -- McCoy, "I, Mudd", stardate 4513.3
Bug#974939: machine does not boot
Control: tag -1 moreinfo Control: severity -1 important On Mon, 2020-11-16 at 19:41 +, Toni wrote: > Package: src:linux > Version: 4.19.152-1 > Severity: critical > > > Hi, > > with the two latest kernels, linux-image-4.19.0-12-amd64 and > linux-image-4.19.0-11-amd64, my machine does not boot, the reason being > that something with cryptsetup is amiss. I used to be asked for a > passphrase, but using these two kernels, I'm not, and the machine just > cycles trying to find the root partition. I am now running the -10 > kernel again, which I would like to get off of. I've tried recovery mode > without any success. This is probably an issue with the initramfs built for this kernel, and not with the kernel itself. Please send the output of the command: lsinitramfs /boot/initrd.img-4.19.0-12-amd64 > On the console, after dmesg, these three lines repeat ad nauseum: > > mdadm: No arrays found in config file or automatically > Volume group "ev0" not found > Cannot process volume group ev0 > mdadm: No arrays found in config file or automatically > Volume group "ev0" not found > Cannot process volume group ev0 [...] If you wait for about 30 seconds you should get a shell with the prompt "(initramfs)". At the shell prompt, run: ls -l /dev/nvme* Are the expected partitions listed? Ben. -- Ben Hutchings Usenet is essentially a HUGE group of people passing notes in class. - Rachel Kadel, `A Quick Guide to Newsgroup Etiquette' signature.asc Description: This is a digitally signed message part
Bug#974939: machine does not boot
Package: src:linux Version: 4.19.152-1 Severity: critical Hi, with the two latest kernels, linux-image-4.19.0-12-amd64 and linux-image-4.19.0-11-amd64, my machine does not boot, the reason being that something with cryptsetup is amiss. I used to be asked for a passphrase, but using these two kernels, I'm not, and the machine just cycles trying to find the root partition. I am now running the -10 kernel again, which I would like to get off of. I've tried recovery mode without any success. On the console, after dmesg, these three lines repeat ad nauseum: mdadm: No arrays found in config file or automatically Volume group "ev0" not found Cannot process volume group ev0 mdadm: No arrays found in config file or automatically Volume group "ev0" not found Cannot process volume group ev0 I think this bug is critical, since I can't get to anything with this state of the machine. The disk configuration is pretty straightforward: git:(master*)$ lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme0n1 259:00 953.9G 0 disk ├─nvme0n1p1 259:10 238.4M 0 part ├─nvme0n1p2 259:20 3.5G 0 part ├─nvme0n1p3 259:30 953M 0 part /boot └─nvme0n1p4 259:40 949.2G 0 part └─nvme0n1p4_crypt 253:00 949.2G 0 crypt ├─ev0-swap 253:10 29.8G 0 lvm [SWAP] ├─ev0-root 253:20 789.4G 0 lvm / There is one other (data) partition, but that's it for what the system has. Cheers, Toni -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Dell Inc. product_name: Precision 5530 product_version: chassis_vendor: Dell Inc. chassis_version: bios_vendor: Dell Inc. bios_version: 1.13.0 board_vendor: Dell Inc. board_name: 0X78C1 board_version: A02 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers [8086:3ec4] (rev 07) Subsystem: Dell 8th Gen Core Processor Host Bridge/DRAM Registers [1028:087d] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 07) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 07) Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [1028:087d] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:08.0 System peripheral [0880]: Intel Corporation Skylake Gaussian Mixture Model [8086:1911] Subsystem: Dell Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [1028:087d] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:12.0 Signal processing controller [1180]: Intel Corporation Cannon Lake PCH Thermal Controller [8086:a379] (rev 10) Subsystem: Dell Cannon Lake PCH Thermal Controller [1028:087d] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: intel_pch_thermal Kernel modules: intel_pch_thermal 00:14.0 USB controller [0c03]: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller [8086:a36d] (rev 10) (prog-if 30 [XHCI]) Subsystem: Dell Cannon Lake PCH USB 3.1 xHCI Host Controller [1028:087d] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
