Login Incorrect Error

saleem · 2024-04-04 20:20:47

Just updated system and now can not login to system either at tty or with a login manager

on tty when I enter username ans then password I get out put Login Incorrect

On reading old posts and digging I traced these findings , posting it here , need help to fix it

# pacman -Qs pam
local/pam 1.6.0-4
    PAM (Pluggable Authentication Modules) library
local/pambase 20230918-1
    Base PAM configuration for services
local/shadow 4.15.1-2
    Password and account management tool suite with support for shadow files and
    PAM
[root@home-pc /]# pacman -Qikk pam pambase shadow
Name            : pam
Version         : 1.6.0-4
Description     : PAM (Pluggable Authentication Modules) library
Architecture    : x86_64
URL             : http://linux-pam.org
Licenses        : GPL-2.0-only
Groups          : None
Provides        : libpam.so=0-64  libpamc.so=0-64  libpam_misc.so=0-64
Depends On      : glibc  libtirpc  pambase  audit  libaudit.so=1-64  libxcrypt
                  libcrypt.so=2-64
Optional Deps   : None
Required By     : kbd  libcap  openssh  polkit  sddm  shadow  sudo  systemd
                  util-linux
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 3.24 MiB
Packager        : Tobias Powalowski <tpowa@archlinux.org>
Build Date      : Thu 15 Feb 2024 01:15:27 AM PKT
Install Date    : Wed 03 Apr 2024 03:32:39 AM PKT
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : SHA-256 Sum

pam: 566 total files, 0 altered files
Name            : pambase
Version         : 20230918-1
Description     : Base PAM configuration for services
Architecture    : any
URL             : https://www.archlinux.org
Licenses        : GPL-3.0-or-later
Groups          : None
Provides        : None
Depends On      : None
Optional Deps   : None
Required By     : pam
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 2.68 KiB
Packager        : David Runge <dvzrv@archlinux.org>
Build Date      : Mon 18 Sep 2023 06:14:56 PM PKT
Install Date    : Wed 03 Apr 2024 03:32:39 AM PKT
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : SHA-256 Sum

pambase: 8 total files, 0 altered files
Name            : shadow
Version         : 4.15.1-2
Description     : Password and account management tool suite with support for
                  shadow files and PAM
Architecture    : x86_64
URL             : https://github.com/shadow-maint/shadow
Licenses        : BSD-3-Clause
Groups          : None
Provides        : None
Depends On      : glibc  acl  libacl.so=1-64  attr  libattr.so=1-64  audit
                  libaudit.so=1-64  libxcrypt  libcrypt.so=2-64  pam
                  libpam.so=0-64  libpam_misc.so=0-64
Optional Deps   : None
Required By     : base  util-linux
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 3.75 MiB
Packager        : David Runge <dvzrv@archlinux.org>
Build Date      : Mon 01 Apr 2024 03:19:58 PM PKT
Install Date    : Wed 03 Apr 2024 03:32:48 AM PKT
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : SHA-256 Sum

warning: shadow: /usr/bin/groupmems (GID mismatch)
warning: shadow: /usr/bin/groupmems (Permissions mismatch)
shadow: 588 total files, 1 altered file
[root@home-pc /]# pacman -Qkk $(pacman -Qqo /etc/pam.d/)
kbd: 815 total files, 0 altered files
openssh: 81 total files, 0 altered files
pambase: 8 total files, 0 altered files
sddm: 251 total files, 0 altered files
warning: shadow: /usr/bin/groupmems (GID mismatch)
warning: shadow: /usr/bin/groupmems (Permissions mismatch)
shadow: 588 total files, 1 altered file
warning: sudo: /etc/sudoers.d (Permissions mismatch)
sudo: 239 total files, 1 altered file
warning: systemd: /etc/systemd/journal-remote.conf (UID mismatch)
warning: systemd: /etc/systemd/journal-remote.conf (GID mismatch)
warning: systemd: /etc/systemd/journal-remote.conf (Permissions mismatch)
backup file: systemd: /etc/systemd/journal-remote.conf (Modification time mismatch)
backup file: systemd: /etc/systemd/journal-remote.conf (Size mismatch)
backup file: systemd: /etc/systemd/journal-remote.conf (SHA256 checksum mismatch)
warning: systemd: /etc/systemd/journal-upload.conf (UID mismatch)
warning: systemd: /etc/systemd/journal-upload.conf (GID mismatch)
warning: systemd: /etc/systemd/journal-upload.conf (Permissions mismatch)
backup file: systemd: /etc/systemd/journal-upload.conf (Modification time mismatch)
backup file: systemd: /etc/systemd/journal-upload.conf (Size mismatch)
backup file: systemd: /etc/systemd/journal-upload.conf (SHA256 checksum mismatch)
warning: systemd: /etc/systemd/journald.conf (UID mismatch)
warning: systemd: /etc/systemd/journald.conf (GID mismatch)
warning: systemd: /etc/systemd/journald.conf (Permissions mismatch)
backup file: systemd: /etc/systemd/journald.conf (Modification time mismatch)
backup file: systemd: /etc/systemd/journald.conf (Size mismatch)
backup file: systemd: /etc/systemd/journald.conf (SHA256 checksum mismatch)
warning: systemd: /etc/xdg/systemd/user (File type mismatch)
warning: systemd: /var/log/journal (GID mismatch)
systemd: 1449 total files, 5 altered files
warning: util-linux: /etc/pam.d/su (UID mismatch)
warning: util-linux: /etc/pam.d/su (GID mismatch)
warning: util-linux: /etc/pam.d/su (Permissions mismatch)
backup file: util-linux: /etc/pam.d/su (Modification time mismatch)
util-linux: 526 total files, 1 altered file

seth · 2024-04-04 21:45:23

How did you enter the root account? chroot?
Do you use a standard US QWERTY keyboard?
If not, what if you change the password of the user to sth. qwerty-safe like "12345"?

When the login fails and assuming the root login is from a chroot, do not reboot by holding the power button.
Try frenetically pressing ctrl+alt+del or a short powerbutton push.
Then check the journal of that system for the failed login, notably pam errors: https://wiki.archlinux.org/title/System … al_to_view

saleem · 2024-04-04 22:15:19

seth wrote:

How did you enter the root account? chroot?
Do you use a standard US QWERTY keyboard?
If not, what if you change the password of the user to sth. qwerty-safe like "12345"?
When the login fails and assuming the root login is from a chroot, do not reboot by holding the power button.
Try frenetically pressing ctrl+alt+del or a short powerbutton push.
Then check the journal of that system for the failed login, notably pam errors: https://wiki.archlinux.org/title/System … al_to_view

Root account approach , Chroot , yes because system wont let me login in any other way
Do you use a standard US QWERTY keyboard? Yes on my laptop
If not, what if you change the password of the user to sth. qwerty-safe like "12345"? I can give this a try as well

for the last part from chroot I checked

No journal files were found.
No journal boot entry found from the specified boot offset (+0).

Last edited by saleem (2024-04-04 22:20:08)

seth · 2024-04-04 22:50:37

Did you disable the Storage in https://man.archlinux.org/man/core/syst … .conf.5.en ?

saleem · 2024-04-05 09:33:39

seth wrote:

Did you disable the Storage in https://man.archlinux.org/man/core/syst … .conf.5.en ?

I am afraid I'm not aware how to do that .

What command/commands will need to be run to do that ??

seth · 2024-04-05 11:33:27

It's a config file, you'd have had to disabled the Storage there.
Alternatively you didn't look at the journal of the installed system but just ran journalctl on the installation iso?
That won't work and would not help anyway.

saleem · 2024-04-05 13:31:58

seth wrote:

It's a config file, you'd have had to disabled the Storage there.
Alternatively you didn't look at the journal of the installed system but just ran journalctl on the installation iso?
That won't work and would not help anyway.

Got it and re ran the command and got this output command

# journalctl -D /mnt/var/log/journal -e
No journal files were found.
No journal boot entry found from the specified boot offset (+0).

Last edited by saleem (2024-04-05 13:32:45)

seth · 2024-04-05 14:02:29

ls /mnt/var/log /etc/systemd/journald.conf.d # is the actually the installed /var/log and what custom journald.conf drop-ins do you have
cat /etc/systemd/journald.conf
cat /etc/systemd/journald.conf.d/local.conf

You can pipe that into 0x0.st

cat /etc/systemd/journald.conf | curl -F 'file=@-' 0x0.st

saleem · 2024-04-05 17:32:34

seth wrote:

ls /mnt/var/log /etc/systemd/journald.conf.d # is the actually the installed /var/log and what custom journald.conf drop-ins do you have
cat /etc/systemd/journald.conf
cat /etc/systemd/journald.conf.d/local.conf

You can pipe that into 0x0.st

cat /etc/systemd/journald.conf | curl -F 'file=@-' 0x0.st

Something seems quite messed up on this installation , perhaps , I need to do a fresh install

# ls /mnt/var/log /etc/systemd/journald.conf.d
ls: cannot access '/mnt/var/log': No such file or directory
ls: cannot access '/etc/systemd/journald.conf.d': No such file or directory
[root@home-pc /]# cat /etc/systemd/journald.conf
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it under the
#  terms of the GNU Lesser General Public License as published by the Free
#  Software Foundation; either version 2.1 of the License, or (at your option)
#  any later version.
#
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file (or a copy of it placed in
# /etc/ if the original file is shipped in /usr/), or by creating "drop-ins" in
# the /etc/systemd/journald.conf.d/ directory. The latter is generally
# recommended. Defaults can be restored by simply deleting the main
# configuration file and all drop-ins located in /etc/.
#
# Use 'systemd-analyze cat-config systemd/journald.conf' to display the full config.
#
# See journald.conf(5) for details.

[Journal]
#Storage=auto
#Compress=yes
#Seal=yes
#SplitMode=uid
#SyncIntervalSec=5m
#RateLimitIntervalSec=30s
#RateLimitBurst=10000
#SystemMaxUse=
#SystemKeepFree=
#SystemMaxFileSize=
#SystemMaxFiles=100
#RuntimeMaxUse=
#RuntimeKeepFree=
#RuntimeMaxFileSize=
#RuntimeMaxFiles=100
#MaxRetentionSec=
#MaxFileSec=1month
#ForwardToSyslog=no
#ForwardToKMsg=no
#ForwardToConsole=no
#ForwardToWall=yes
#TTYPath=/dev/console
#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
#MaxLevelWall=emerg
#LineMax=48K
#ReadKMsg=yes
#Audit=yes
[root@home-pc /]# cat /etc/systemd/journald.conf.d/local.conf
cat: /etc/systemd/journald.conf.d/local.conf: No such file or directory

seth · 2024-04-05 20:10:41

I forgot the "/mnt" ahead of the /etc/… paths, sorry about that.

However w/

ls: cannot access '/mnt/var/log': No such file or directory

Do you actually have the root partition of the installed system mounted at /mnt?
Do you maybe use a dedicated /var partition that you forgot to mount?
Or are you trying this from with a chroot to the installed system (if so, don't query anything in /mnt, the default journalctl will just work)

lsblk -f

saleem · 2024-04-05 20:41:17

seth wrote:

I forgot the "/mnt" ahead of the /etc/… paths, sorry about that.
However w/
ls: cannot access '/mnt/var/log': No such file or directory
Do you actually have the root partition of the installed system mounted at /mnt?
Do you maybe use a dedicated /var partition that you forgot to mount?
Or are you trying this from with a chroot to the installed system (if so, don't query anything in /mnt, the default journalctl will just work)
lsblk -f

Do you actually have the root partition of the installed system mounted at /mnt? Yes . I am chrooting from another arch linux installation and I can browse and see contents of /mnt in a file manager as can be seen below

[root@home-pc mnt]# ls
bin   dev  home  lib64	     mnt  proc	run   srv  tmp	var
boot  etc  lib	 lost+found  opt  root	sbin  sys  usr

Do you maybe use a dedicated /var partition that you forgot to mount? /var is mounted too as can be seen above

Or are you trying this from with a chroot to the installed system (if so, don't query anything in /mnt, the default journalctl will just work) Yes I am chrooting from another installed arch linux

Now last part , this target partition is /dev/sda8 so

# lsblk -f
NAME    FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda                                            
├─sda1                                         
├─sda2                                         
├─sda5                                         [SWAP]
├─sda6                             3.2G    78% /etc/resolv.conf
├─sda7                                         
├─sda8                            13.5G    24% /
├─sda9                                         
├─sda10                                        
├─sda11                                        
├─sda12                                        
└─sda13                                        
sr0

About previous commands the contents of /mnt/etc/systemd/journald.conf on this messed up installation is same as I pasted above i.e

[Journal]
#Storage=auto
#Compress=yes
#Seal=yes
#SplitMode=uid
#SyncIntervalSec=5m
#RateLimitIntervalSec=30s
#RateLimitBurst=10000
#SystemMaxUse=
#SystemKeepFree=
#SystemMaxFileSize=
#SystemMaxFiles=100
#RuntimeMaxUse=
#RuntimeKeepFree=
#RuntimeMaxFileSize=
#RuntimeMaxFiles=100
#MaxRetentionSec=
#MaxFileSec=1month
#ForwardToSyslog=no
#ForwardToKMsg=no
#ForwardToConsole=no
#ForwardToWall=yes
#TTYPath=/dev/console
#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
#MaxLevelWall=emerg
#LineMax=48K
#ReadKMsg=yes
#Audit=yes

seth · 2024-04-05 20:46:51

While you're chrooted in, /mnt should™ be empty and "journalctl -D /mnt/var/log/journal" is wrong, just run "journalctl -b -1" (-b won't work because the *current* boot is on the install iso)

To be sure: you also cannot just login via ssh?
Did you try to reset the password from the chroot?

saleem · 2024-04-05 20:57:12

seth wrote:

While you're chrooted in, /mnt should™ be empty and "journalctl -D /mnt/var/log/journal" is wrong, just run "journalctl -b -1" (-b won't work because the *current* boot is on the install iso)
To be sure: you also cannot just login via ssh?
Did you try to reset the password from the chroot?

I did change user password from chroot to 12345 , and did one aggressive step ahead by removing everything except base and did all the installation again through chroot from zero , removed user and its home and added it again with password 12345

looks like .... a total fresh install would be better , polybar will give issues but sorry I could not thank you for helping me with the dropping icons in other thread I posted , that tip helps with setting up easily now .

Havent tried login in with ssh as I do not have knowledge how to do that.

seth · 2024-04-05 21:03:31

Make sure to "systemctl enable sshd" in the chroot, then "ssh <IP of broken host>" from a second host.

a total fresh install would be better

removing everything except base and did all the installation again through chroot from zero , removed user and its home and added it again with password 12345

That basically is a complete re-install, didn't you lose any data when removing the $HOME???
We might have lost the journal through that, though.

Since you're in a chroot anyway, you could maybe https://wiki.archlinux.org/title/Getty#Virtual_console which should™ immediately log you into the system.
If that works, you can attempt a 2nd login on a 2nd TTY and check the journal on the failing from the active login in TTY1

Arch Linux

#1 2024-04-04 20:20:47

Login Incorrect Error

#2 2024-04-04 21:45:23

Re: Login Incorrect Error

#3 2024-04-04 22:15:19

Re: Login Incorrect Error

#4 2024-04-04 22:50:37

Re: Login Incorrect Error

#5 2024-04-05 09:33:39

Re: Login Incorrect Error

#6 2024-04-05 11:33:27

Re: Login Incorrect Error

#7 2024-04-05 13:31:58

Re: Login Incorrect Error

#8 2024-04-05 14:02:29

Re: Login Incorrect Error

#9 2024-04-05 17:32:34

Re: Login Incorrect Error

#10 2024-04-05 20:10:41

Re: Login Incorrect Error

#11 2024-04-05 20:41:17

Re: Login Incorrect Error

#12 2024-04-05 20:46:51

Re: Login Incorrect Error

#13 2024-04-05 20:57:12

Re: Login Incorrect Error

#14 2024-04-05 21:03:31

Re: Login Incorrect Error

Board footer