Comments on: How to Reset Forgotten Root Password in Ubuntu

By: Ravi Saive

Ravi Saive — Tue, 22 Jul 2025 04:39:16 +0000

In reply to Montey. @Montey, You can update your initramfs to include the necessary keyboard and input modules:

sudo update-initramfs -u

Make sure modules like usbhid, hid_generic, or your specific keyboard driver are included in /etc/initramfs-tools/modules. Try editing the GRUB entry again, before pressing F10, add this to your kernel parameters:

rd.break

init=/bin/bash

This can help determine whether keyboard input works at earlier boot stages. If you're locked out entirely, boot from a live Linux USB, mount the encrypted disk, and try unlocking it from there to troubleshoot further.

By: Montey

Montey — Mon, 21 Jul 2025 18:21:47 +0000

I'm running Linux 6.11.0 on iOS, and when I edit the boot parameters (e.g., changing ro quiet...) and press F10 to proceed, I get a screen that says:

"Please unlock disk dm_crypt-0:"

However, at this point, the keyboard stops responding, and I can't type anything to unlock the disk. How can I proceed from here? Any help would be greatly appreciated. Thank you!

By: Ala

Ala — Sun, 10 Sep 2023 17:42:27 +0000

In reply to Oldbaritone. Just get onto "Advanced Options for Ubuntu" and from there, we can get onto the root shell.

By: Joe

Joe — Wed, 15 Mar 2023 22:37:26 +0000

After the reboot step, the Acer laptop continues to slowly scroll : { 3765. etc nonstop with the first numbers increasing in value? Let it run all night and still the laptop is scrolling. Redid it all after shutting down and restarting, Followed the directions again, and once more it is doing the same thing.

Any ideas? I thought it would finally come to an end – but it sure doesn’t look like it. How long should this part of the process continue? Days?

By: Oldbaritone

Oldbaritone — Sun, 26 Feb 2023 02:56:21 +0000

Thanks much for this article, I made the mistake of changing the username when installing the virtual machine, so that name was not included in sudoers and I didn't have the root password. Reboot, reset root PW, visudo, and add the correct user (I use NOPASSWD:ALL since it's a VM on a laptop just for utility) reboot again, and "all better now." :-)