Control: severity -1 important
On Mon, Nov 16, 2020 at 07:41:05PM +0000, 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
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
> nvme0n1 259:0 0 953.9G 0 disk
> ├─nvme0n1p1 259:1 0 238.4M 0 part
> ├─nvme0n1p2 259:2 0 3.5G 0 part
> ├─nvme0n1p3 259:3 0 953M 0 part /boot
> └─nvme0n1p4 259:4 0 949.2G 0 part
> └─nvme0n1p4_crypt 253:0 0 949.2G 0 crypt
> ├─ev0-swap 253:1 0 29.8G 0 lvm [SWAP]
> ├─ev0-root 253:2 0 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
