Strange login issues and mounting problem

Support
1

Hello everyone. So I’m having issues logging into any account that isn’t root. On the login screen, I input my username and password, and it just kicks me back to the login page unless I sign in as root. I checked my etc/passwd file and my user account is still there, this is the output, so I know the account still exists and the home directory is fine:

sinkou:x:1000:1000:patrick:/home/sinkou:/bin/bash

I also looked at other entries to see what is happening:

journalctl -b Nov 06 08:41:56 lotus audit[839]: USER_AUTH pid=839 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication

grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct=“sinkou”

exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success’

Nov 06 08:41:56 lotus audit[839]: USER_ACCT pid=839 uid=0 auid=4294967295 ses=4294967295 msg=‘op=PAM:accounting grantors=pam_access,pam_permit,pam_time acct=“sinkou” exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success’

Nov 06 08:41:56 lotus kernel: audit: type=1100 audit(1604670116.178:48): pid=839 uid=0 auid=4294967295 ses=4294967295 msg=‘op=PAM:authentication grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct=“sinkou” exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success’

Nov 06 08:41:56 lotus kernel: audit: type=1101 audit(1604670116.178:49): pid=839 uid=0 auid=4294967295 ses=4294967295 msg=‘op=PAM:accounting grantors=pam_access,pam_permit,pam_time acct=“sinkou” exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success’

Nov 06 08:41:56 lotus audit[839]: CRED_ACQ pid=839 uid=0 auid=4294967295 ses=4294967295 msg=‘op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct=“sinkou” exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success’

Nov 06 08:41:56 lotus lightdm[839]: pam_unix(lightdm:session): session opened for user sinkou(uid=1000) by (uid=0)

Nov 06 08:41:56 lotus kernel: audit: type=1103 audit(1604670116.218:52): pid=839 uid=0 auid=4294967295 ses=4294967295 msg=‘op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock,pam_gnome_keyring acct=“sinkou” exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success’

Nov 06 08:41:56 lotus systemd-logind[448]: New session 2 of user sinkou.

Nov 06 08:41:56 lotus audit[845]: USER_ACCT pid=845 uid=0 auid=4294967295 ses=4294967295 msg=‘op=PAM:accounting grantors=pam_access,pam_permit,pam_time acct=“sinkou” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’

Nov 06 08:41:56 lotus audit[845]: CRED_ACQ pid=845 uid=0 auid=4294967295 ses=4294967295 msg=‘op=PAM:setcred grantors=? acct=“sinkou” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed’

Nov 06 08:41:56 lotus systemd[845]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[sinkou] ruser=[] rhost=[]

Nov 06 08:41:56 lotus systemd[845]: pam_unix(systemd-user:session): session opened for user sinkou(uid=1000) by (uid=0)

Nov 06 08:41:56 lotus kernel: audit: type=1101 audit(1604670116.234:55): pid=845 uid=0 auid=4294967295 ses=4294967295 msg=‘op=PAM:accounting grantors=pam_access,pam_permit,pam_time acct=“sinkou” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’

Nov 06 08:41:56 lotus kernel: audit: type=1103 audit(1604670116.234:56): pid=845 uid=0 auid=4294967295 ses=4294967295 msg=‘op=PAM:setcred grantors=? acct=“sinkou” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed’

Nov 06 08:41:56 lotus audit[845]: USER_START pid=845 uid=0 auid=1000 ses=3 msg=‘op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct=“sinkou” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’

Nov 06 08:41:56 lotus systemd[1]: Started Session 2 of user sinkou.
Nov 06 08:41:56 lotus xdg-user-dirs-update[852]: Can’t create dir /home/sinkou/Desktop
Nov 06 08:41:56 lotus xdg-user-dirs-update[852]: Can’t create dir /home/sinkou/Downloads
Nov 06 08:41:56 lotus xdg-user-dirs-update[852]: Can’t create dir /home/sinkou/Templates
Nov 06 08:41:56 lotus xdg-user-dirs-update[852]: Can’t create dir /home/sinkou/Public
Nov 06 08:41:56 lotus xdg-user-dirs-update[852]: Can’t create dir /home/sinkou/Documents
Nov 06 08:41:56 lotus xdg-user-dirs-update[852]: Can’t create dir /home/sinkou/Music
Nov 06 08:41:56 lotus xdg-user-dirs-update[852]: Can’t create dir /home/sinkou/Pictures
Nov 06 08:41:56 lotus xdg-user-dirs-update[852]: Can’t create dir /home/sinkou/Videos
Nov 06 08:41:56 lotus audit[839]: USER_START pid=839 uid=0 auid=1000 ses=2 msg=‘op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring acct=“sinkou” exe="/usr/bin/lightdm" hostname=? addr=? terminal=:0 res=success’

Nov 06 08:41:56 lotus lightdm[839]: Error writing X authority: Failed to open X authority /home/sinkou/.Xauthority: Permission denied

Nov 06 08:42:08 lotus systemd[846]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[sinkou] ruser=[] rhost=[]

I’m not sure what’s going on, because yesterday everything was okay. I see the “Can’t create dir /*” stuff but I’m not sure how to interpret that so I can fix it.

As for the mounting issue, I have mounted my /dev/sda1 partition to a directory /data - today, Manjaro has decided to unmount this permanently. Furthermore, it has mounted one of my M.2 drive partitions to /data instead. I am able to remount /dev/sda1 to a different directory, say /data2 for example, but on reboot, it just unmounts itself again. My drive is an ext4 file system if that matters. I’d rather not create a new file system over it in the hopes that I can still have access to the ~50GB of actual important data I have on that drive. I had moved my user /home directory in /data so perhaps fixing the mounting issue will fix the user issue as well, but I also ran a usermod -m -d /home/sinkou sinkou to move it back, just in case, and that didn’t seem to work either. One last piece of info is that df does not seem to recognize dev/sda1 though I’m assuming that’s because it’s not currently mounted. Here’s the lsblk if that helps too:

lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT

sda 8:0 0 931.5G 0 disk
└─sda1 8:1 0 931.5G 0 part
nvme0n1 259:0 0 232.9G 0 disk
├─nvme0n1p1 259:1 0 300M 0 part /boot/efi
└─nvme0n1p2 259:2 0 232.6G 0 part /data

2

Your home folder should be in /home, which should preferably (in my opinion) be on a separate partition mounted to /home, it should not be in /data. :slight_smile:

Is nvme0n1p2 your root? It sounds like you may have used the wrong UUID.

Please post the output of lsblk -f and cat /etc/fstab.

I believe that would move the folder /home/sinkou to /home/sinkou, but I may be wrong.

Use cp or rsync.

rsync -aAXh /data2/sinkou /home/

Do you want a separate /home partition, a /data partition, or both?

3

Right, so I just ended up going with a fresh install. I lost all the data I had but as long as stuff works now I really don’t care.

The goal I want (ideally) is my /dev/sda drive to be for other programs, games, and stuff. I learned my lesson and I will no longer attempt to touch anything on my M.2 drive lmao. My problem now comes in the form of mounting a partition, /dev/sda1. It seems that no matter where I mount this drive to, it will cause a complete system failure, so I decided to remove the partition entirely for now until I can figure out what I’m doing wrong. I’ve made /sda1 a primary partition in the past which might be the issue since I don’t plan on booting from it, does this really matter though? I’m pretty sure nvme0n1p2 is my root, yes. Here’s the outputs of what you were talking about:

lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT

sda

nvme0n1

├─nvme0n1p1 vfat FAT32 236D-5392 299.1M 0% /boot/efi
└─nvme0n1p2 ext4 1.0 0ae77f05-f657-47d8-be93-fd9e6d4943ca 206.3G 4% /

cat /etc/fstab # /etc/fstab: static file system information.

Use ‘blkid’ to print the universally unique identifier for a device; this may

be used with UUID= as a more robust way to name devices that works even if

disks are added and removed. See fstab(5).

UUID=236D-5392 /boot/efi vfat umask=0077 0 2

UUID=0ae77f05-f657-47d8-be93-fd9e6d4943ca / ext4 defaults,noatime 0 1