Luks encrypted root partition won't boot

The best answer that I can give is from a thread on from about 3 yrs. ago, but it still applies.

1 Like

That is the shutdown process. So nothing useful. :man_shrugging:


Thank you tnaser I might try chrooting in and reinstalling the grub. However I have had many successful boots, this is not a newly encrypted drive.

My bad. Not familiar with the output.

When you do that, also do this:
edit /etc/default/grub
and remove the “quiet” parameter from the kernel command line
so that you will see the messages that are normally printed to the screen during boot.

sudo update-grub
after changes to that file

1 Like

I chrooted in, changed the entries in /etc/default/grub, and updated the grub. I can now see messages printed to screen during boot.

There are messages referring to
ACPI BIOS Error (bug), and
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

These are not the only things that are printed there - or are they?
And you are (normally) dropped into an (pretty limited) emergency shell.

No they’re not the only things. I can’t upload an image tho. And no not dropped into a shell. I have to force power off.

At least it is kernel related. Maybe an non-complete update? Search for mkinitcpio, grub-install and update-grub

Yes you can - just not directly to here.
Use a service, share the URL.
If you think it is useful.

1 Like
1 Like

Here is a link to the screen showing the failed boot process

I’ll not sure what you mean by search for mkinitcpio

I found this:



The BIOS seems to be pretty outdated. ASUS Zenbook UX410UQ - Support Latest one is dated at 2020/05/25 .

That could be a problem here… update it.


The problem is the mounting process of the root partition. It could be simply that the storage device (whatever type) is damaged or just the filesystem.


The ACPI errors refer to the BIOS which is outdated since 6 years.

Think. What did you change/install/remove/edit before this happened?

What did you change now? Because…

…kernel can’t find root filesystem now.

So now either you have wrong root= set or wrong mkinitcpio hooks/modules or something. :man_shrugging:

Now secure boot is enabled after updating bios so will have to troubleshoot around windows recovery environment there to disable before getting back into this issue.

After updating the BIOS, administrator password appears to have reset and enabled secure boot. So I can no longer dual boot, or access the BIOS using admin. Anyone know how to get around this on an Asus UX410UQ? Asus support have advised sending into service centre(!). Haven’t been able to find any real solutions searching the web…

How about disabling secure boot?

Secure boot can’t be disabled without administrator password to BIOS (my system allows for User and admin access, I assume this is the same for all systems).

I have found examples to reset admin BIOS access by changing the system date to ‘special’ values, and then using Alt-r when prompted for BIOS password, to provide a recovery password, however when I reset the date I’m unable to access this recovery pathway.