#Change Forgotten Login Password for Mint Linux

128 messages · Page 1 of 1 (latest)

dapper tulip
#

Could anyone help me with changing/recovering a lost Mint login password - Thanks

dapper tulip
oak zephyr
#

try pressing esc or holding shift at boot

dapper tulip
#

alright I will try this here shortly

valid hedge
#

u can do it from a live boot

#

and chroot

dapper tulip
#

I should still have the mint live usb around, I'll try to find that

valid hedge
#

once chrooted properly, use commandline commands to adjust the user password

#

do ls /home after chrooted to see old userhome folders if forgot exact username

dapper tulip
#

got busy with work but I found my Mint live usb, so I'm attempting to work on this now, with the "chroot"

#

but also before the live usb... I tried hitting Esc during boot and got the grub command line to show

valid hedge
dapper tulip
#

was just sitting here changing the boot order for the usb yep

#

alright I am now on the live usb desktop, how do I get/run the chroot thing? I don't know what it is

valid hedge
#

you gotta read over the guide, and my condensed notes below it. i linked you.

dapper tulip
#

oh duh... dont mind my brain.. 1sec

valid hedge
#

the article goes into more fluff using parted and grep but u dont gotta. just lsblk -f to ID stuff.

dapper tulip
#

gparted shows /dev/sda ext4 ... which is fine

#

mount /dev/xxxY /rescue - is it supposed to be mount /dev/ext4 /rescue ?

#

mount /dev/sda/ext4 r/escue

valid hedge
#

just do lsblk -f like i said

#

get it @dapper tulip ?

dapper tulip
#

sorry I was fixing discord to put this... I am terrible at linux, it's either just ext4 unless you meant the UUID also

valid hedge
#

damn

#

u have a partitionless sda

#

rarely see that

#

show sdb in gparted

#

this is why u should absolutely label partitions

dapper tulip
valid hedge
#

i think that's the install

#

close gparted

#

open DISKS instead.

#

by name, from the start menu

#

then click partition 2 of sdb. then the play icon, then the blue link

#

press alt+prtscr keys to show a snap of the DISKS window on that exact partition selected and mounted

#

and again on the resulting file manager that opens

dapper tulip
valid hedge
#

close the file manager.

#

click the stop button in DISKS for BOTH p1 and p2 of sdb

dapper tulip
#

done

valid hedge
#

then select sdb2

#

and the gear.

#

do 'edit filesystem'

#

label it LINUX

dapper tulip
#

changed and labeled

valid hedge
#

do same for p1, but label it ESP

#

Then select sda in the disks app. hit play and the blue link, and show

#

(the resulting file manager)

dapper tulip
valid hedge
#

close that file manager for a sec

#

in terminal , do sudo nemo

#

then in the resulting rootmode file manager, press ctrl-L for the address / location bar

#

and wipe it empty, and put /media/mint/1TB

#

and press enter and show

#

is it showing now stuff?

#

any folder named home or your real username within it?

dapper tulip
#

it's completely empty - which as I recall is correct, that was merely storage drive that was never used

valid hedge
#

ok. click stop for it in Disks app after closing root nemo

valid hedge
#

/dev/sdb2

dapper tulip
#

mount /dev/sdb2 /rescue

valid hedge
#

yup . the prompt should show the root in the name

#

and end wiht #

dapper tulip
#

okay I believe it worked... terminal is now... root@mint:/#

valid hedge
#

work thru all the chroot steps.. my condensed notes

#

you'll know you succeeded when u do ls /home and it shows ur real users folder not one called mint

#

at that point, u can do whatever commands to edit the password for the user

dapper tulip
#

believe it's fixed now, rebooting out of live usb to test, seems like all was good using passwd

valid hedge
#

if u get in, then see if that 1 TB drive has permissions to create files on it from a regular file manager.

#

if not, use the gear menu in Disks app to 'take ownership'

dapper tulip
#

no... the normal login didn't work and realized my dumbass did something dumb, I forgot to unmount things after...

#

I went back to the live usb and was going back through everything again... got back to... root@mint:/home/mint#... but ls /home shows "mint" instead of the correct username like before

valid hedge
#

thus ur new root isnt embodied yet

#

it should still have worked if u didnt unmount last time i think.

dapper tulip
#

okay... yea that was it

valid hedge
#

u can do exit to leave the embodied root

dapper tulip
#

now it's back to the correct user.... passwd again

valid hedge
#

ensure u use same region keyboard!!

#

or just use numeric digits

#

from the numeric row on keyboard

dapper tulip
#

yea full english but using basic 1234 to be safe

#

so I do not need to unmount? just "exit" in the terminal?

valid hedge
#

i guess exit the chroot environment

#

and do unmount as per the guide

dapper tulip
#

okay

#

there... this time all appears good, followed every step, nothing missed

valid hedge
#

you could have also su - to new user

#

the new old user, which u just reset the password for. if works, then ur password works

#

eg. if old userid was goblin su - goblin

#

it will prompt for goblin's login password

dapper tulip
#

still didn't work after all that somehow... I should have tried that "su - username"... maybe I still will

valid hedge
#

make sure u only use totally lowercase for username , and it is the proper username from months ago

dapper tulip
#

it was part of a group of test PCs and it's username was simply hpz440new3 and the changed pw in the chroot was changed to just 1234

valid hedge
#

well, as long as u used lowercase during the password command

#

show the command u used here.

dapper tulip
#

it was in that screenshot I put

valid hedge
#

u probably did it wrong then

#

didn't see a single mention of the actual username

#

brush up on that

dapper tulip
#

it's there in the blue isn't it?

valid hedge
#

that's just the userhome's folder name (also the username) but u have to DICTATE IT in the password change command!

valid hedge
dapper tulip
#

fair enough - I am no linux expert, nor a programmer

valid hedge
#

what u did just likely changed the live root (admin's) password for the duration of that live session prob.

dapper tulip
#

went back to live usb... did it all again... used "passwd" correctly this time after googling what the correct way to to do it was... tested it with the "su - hpz440new3" as suggested... rebooted and finally successfully login to the machine with the new password

#

"if u get in, then see if that 1 TB drive has permissions to create files on it from a regular file manager.
if not, use the gear menu in Disks app to 'take ownership' " -- it does not have permission, and my only final question is... when Confirming Take Ownership, should "Enable recursive mode" be checked or no

valid hedge
#

it may but no matter since it's empty u said

#

ONLY do that for data drives.

dapper tulip
#

okay only enable recursive for data drives

valid hedge
#

no, only take ownership of data drives

dapper tulip
#

oh

#

anyways - thank you for the assistance, it is appreciated

#

considering this solved and done for now

valid hedge
#

u may want to tune the data drive AND label it

#

do lsblk -o name,model,label,size,fstype,fssize,fsavail

#

tuning the data partition in this case, partitionless

#

to gain more space

oak zephyr
#

I dunno, I think going to grub menu - advanced options - kernel (whatever is the latest) recovery mode - root shell, then typing

mount -o remount,rw /
passwd yourusername (your username is often the same as your home folder name, which you can see be typing ls /home)
reboot

is easier than this

river minnow
#

Why is this happening? Even though the password I entered was correct.