[SOLVED]Password Not Working after Update. Reset @ Grub Menu not working

[HilltopsGM]

Hi Folks,
I have a VM running 19.3 that just completed a Kernel update.
I rebooted and the password is not working.
The disk was getting full (~500MB's space left. Not sure if this was a factor).

I found this reset process: https://community.linuxmint.com/tutorial/view/339

When I follow that I get:

Code: Select all

[     1.708613]  [drm:vmw_host-log  [vmwgfx]]  *ERROR*  Failed to send log
[     1.709199]  [drm:vmw_host-log  [vmwgfx]]  *ERROR*  Failed to send log
bash:  cannot set terminal process group (-1):  Inappropriate ioctl for device
bash:  no job control in this shell
root@(non):/#

When I type: passwd username
. . . I get:

Code: Select all

passwd:  user 'username' does not exist
root@(non):/#

Thoughts?

[Cosmo.]

What does ls /home give?

[HilltopsGM]

What does ls /home give?

Ok, like a dummy I was not putting everything in Lower Case when I entered the UserName . . . however, after continuing to follow the instructions and getting a "Successful Password Update" message, rebooting and entering the password simply returns me to the login page again where is asks me for my password.

Next Suggestion(s)?

Thanks.

[HilltopsGM]

Interestingly enough, when I enter an incorrect password I get the Message, "Invalid Password, please try again" message - as one would expect.
When I enter the correct one, I don't.
The screen goes black for a second and then brings me back to the login page.

Running VirtualBox 7.04 - just updated it and brought this extension pack up to the same from . . . 6.13??? (I think it was).
I don't think that has anything to do with it, but I thought I'd mention it.

====================

I also tried booting with the last known working Kernel and I get the same behaviour.

[Cosmo.]

It seems, that your (virtual) drive is full and the system refuses because of this to log in.
You have 2 options:
Either increase the size of the drive
or boot the VM with the live system and make room free.

[HilltopsGM]

It seems, that your (virtual) drive is full and the system refuses because of this to log in.
You have 2 options:
Either increase the size of the drive
or boot the VM with the live system and make room free.

Yep. That was the problem.
Removed some files to create room and we were good to go again.
Thanks for the help Cosmo!