linux mint boot gives this

[jon-will]

Every time I boot linux I get this

I'm not a Linux expert but I guess I have a issue with
1. /etc/defult/grub
here is it:
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=lsb_release -i -s 2> /dev/null || echo Debian
#GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash cryptdevice=/dev/vda2:cryptdisc root=/dev/mapper/cryptdisc"
GRUB_CMDLINE_LINUX=""
GRUB_DISABLE_OS_PROBER=false

#GRUB_DEFAULT=0
#GRUB_TIMEOUT_STYLE=hidden
#GRUB_TIMEOUT=0
#GRUB_DISTRIBUTOR=( . /etc/os-release; echo ${NAME:-Ubuntu} ) 2>/dev/null || echo Ubuntu
#GRUB_CMDLINE_LINUX_DEFAULT="resume=UUID="
#GRUB_CMDLINE_LINUX="cryptdevice=UUID=b1e94589-1dd5-43c3-8f49-03ef088b225c:cryptroot root=/dev/mapper/cryptroot"
GRUB_ENABLE_CRYPTODISK=y
GRUB_DISABLE_OS_PROBER=false

# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
GRUB_DISABLE_OS_PROBER=false

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

---------------------------------------------------------------------------------------------------------
2. My initramfs or vmlinuz file
I have updated both no problem so I don't know.

---------------------------------------------------------------------------------------------------------
3.my fstab or crypttab
fstab:
# /dev/mapper/root_crypted / ext4 defaults,relatime 0 1
#UUID=b1e94589-1dd5-43c3-8f49-03ef088b225c / ext4 defaults,relatime 0 1
#/dev/vda1 /boot ext4 defaults,relatime 0 1
#UUID=f0d57e5c-8c00-4e91-9a3e-4971907e24f4 /boot ext4 defaults,relatime 0 1
/dev/mapper/luks-d1e3de22-69aa-4e39-b8c4-370f3b0ac87a / ext4 defaults 0 1
#/dev/vda1 /boot ext4 defaults,relatime 0 1
UUID=f0d57e5c-8c00-4e91-9a3e-4971907e24f4 /boot ext4 defaults 0

crypttab:
# /etc/crypttab: mappings for encrypted partitions.
#
# Each mapped device will be created in /dev/mapper, so your /etc/fstab
# should use the /dev/mapper/<name> paths for encrypted devices.
#
# See crypttab(5) for the supported syntax.
#
# NOTE: You need not list your root (/) partition here, but it must be set up
# beforehand by the initramfs (/etc/mkinitcpio.conf). The same applies
# to encrypted swap, which should be set up with mkinitcpio-openswap
# for resume support.
#
# <name> <device> <password> <options>
#root_crypted was /dev/vda2
#root_crypted UUID=d1e3de22-69aa-4e39-b8c4-370f3b0ac87a none luks,discard
luks-d1e3de22-69aa-4e39-b8c4-370f3b0ac87a UUID=d1e3de22-69aa-4e39-b8c4-370f3b0ac87a none luks

---------------------------------------------------------------------------------------------------------
or 4. My disks
vda
├─vda1 f0d57e5c-8c00-4e91-9a3e-4971907e24f4
└─vda2 d1e3de22-69aa-4e39-b8c4-370f3b0ac87a
└─luks-d1e3de22-69aa-4e39-b8c4-370f3b0ac87a b1e94589-1dd5-43c3-8f49-03ef088b225c

If it helps I am on bios boot on a qemu vm for mint booth desktop and vm. I have my root partition encrypted with luks

 

[Brickwizard]

From memory, I think it's an HDD fault, either Ubuntu is not seeing it or it may be at the end of its life. But as you're using a VM may be a problem with the VM settings [sorry I am not into VM's but plenty of other members are] edit your title to include your using a VM, to avoid replies on direct installation

 

[Condobloke]

If it helps I am on bios boot on a qemu vm for mint booth desktop and vm. I have my root partition encrypted with luks

Why not delete and reinstall the vm ?

Welcome to linux.org !

 

[jon-will]

Why not delete and reinstall the vm ?

Welcome to linux.org !

I did. Still does not work.

 

[jon-will]

I did. Still does not work.

But I think it is worth saying I used this

GitHub - pieroproietti/penguins-eggs: On the road of Remastersys, Refracta, Systemback and father Knoppix!

On the road of Remastersys, Refracta, Systemback and father Knoppix! - pieroproietti/penguins-eggs

github.com

Krill should do it but it does not.

 

[dos2unix]

This could be a number of things. mdadm is a RAID manager.
Since you're using busybox, I would try this first. There are no guarantees this always works.
It works for me "sometimes".

fsck /dev/sda1

See if you can reassemble the array.

cat /proc/mdstat

mdadm --assemble --scan

You should then be able to exit

exit

Hopefully your computer will boot up at this point. Once you can login, do this.

update-initramfs -u

 

[jon-will]

This could be a number of things. mdadm is a RAID manager.
Since you're using busybox, I would try this first. There are no guarantees this always works.
It works for me "sometimes".

fsck /dev/sda1

See if you can reassemble the array.

cat /proc/mdstat

mdadm --assemble --scan

You should then be able to exit

exit

Hopefully your computer will boot up at this point. Once you can login, do this.

update-initramfs -u

I'll give it a try. I have a snap shot anyway.

 

[jon-will]

This could be a number of things. mdadm is a RAID manager.
Since you're using busybox, I would try this first. There are no guarantees this always works.
It works for me "sometimes".

fsck /dev/sda1

See if you can reassemble the array.

cat /proc/mdstat

mdadm --assemble --scan

You should then be able to exit

exit

Hopefully your computer will boot up at this point. Once you can login, do this.

update-initramfs -u

When I do cat /proc/mdstat I get this:

Any clue? Or should I do this in chroot?

Also is sda1 boot or root?

 

[jon-will]

This could be a number of things. mdadm is a RAID manager.
Since you're using busybox, I would try this first. There are no guarantees this always works.
It works for me "sometimes".

fsck /dev/sda1

See if you can reassemble the array.

cat /proc/mdstat

mdadm --assemble --scan

You should then be able to exit

exit

Hopefully your computer will boot up at this point. Once you can login, do this.

update-initramfs -u

WAIT! I am not using raid. I don't know if this will still work. Are you sure?

 

[dos2unix]

WAIT! I am not using raid. I don't know if this will still work. Are you sure?

You might not be using it, but the mdadm is definutely for software RAID administration.
If you are positive you aren't using software RAID then there is another problem.

How did you install this? What did you install it to?

What is the output of...

cat /proc/mdstat

...and...

sudo mdadm --detail --scan

It's possible you have a hardware RAID controller.

lspci | grep -i raid

If all of this returns nothing, then the question is... why are you getting mdadm errors? Where are you getting them from?

 

[jon-will]

I'm sure raid is not here. I have one disk

But regardless, here the out you wanted:

I have years of knowledge, but no clue what is going on.
EDIT: Also I used this to make a iso

GitHub - pieroproietti/penguins-eggs: On the road of Remastersys, Refracta, Systemback and father Knoppix!

On the road of Remastersys, Refracta, Systemback and father Knoppix! - pieroproietti/penguins-eggs

github.com

Krill should do encryption (even if the GUI should not) but this is what I get.

 

[osprey]

I'm sure raid is not here. I have one disk
View attachment 24038
But regardless, here the out you wanted:
View attachment 24039
I have years of knowledge, but no clue what is going on.
EDIT: Also I used this to make a iso

GitHub - pieroproietti/penguins-eggs: On the road of Remastersys, Refracta, Systemback and father Knoppix!

On the road of Remastersys, Refracta, Systemback and father Knoppix! - pieroproietti/penguins-eggs

github.com

Krill should do encryption (even if the GUI should not) but this is what I get.

Perhaps check the BIOS/UEFI and see if there is a setting for RAID. If there is, you can turn it off, and replace it with AHCI, which is the common alternative. Then you won't have any use for the mdadm command or package.

 

[Fanboi]

Is cryptsetup (or similar) in your initramfs?
Was this output:

vda
├─vda1 f0d57e5c-8c00-4e91-9a3e-4971907e24f4
└─vda2 d1e3de22-69aa-4e39-b8c4-370f3b0ac87a
└─luks-d1e3de22-69aa-4e39-b8c4-370f3b0ac87a b1e94589-1dd5-43c3-8f49-03ef088b225c

from the recovery console?
Can you post the output of ls /dev/mapper/ ?

...

So long, as I'm off to bed and sobriety tomorrow (tsk tsk), if there's no devices mapped there, you can manually do:

cryptsetup luksOpen /dev/vda2 rootvol
mount -o rw /dev/mapper/rootvol /
exit

BTW, "luksOpen" is not a typo
Otherwise, if your disk is mapped:

mount -o rw /dev/mapper/<whatever UUID or label was in mapper/> /
exit

IIRC, this should now start booting again where it left off. Once you're into your system we can poke around with what's wrong (the main purpose of this post is for the sake of some poor sod whose bare metal system is giving these issues as with a VM, you can mount the vhd from your host if you have anything important to salvage).
Word to the wise: Full encryption is more trouble than it's worth because minor damage can render your files inaccessible. If you feel the need, encrypt just your home directory (either a separate partition or file -- no re-partitioning in the latter case and much safer as you can back it up in a click). Personally I use a couple of encrypted images for what I don't want people poking around at, but mostly my private stuff isn't that private and with the mess my file structure is, good luck to anyone finding anything anyway.