cant login after editing partitions

Person_1873 · 07-19-2008, 12:25 AM

i wanted to add a couple more partitions to my HDD but i already filled up my partition table, so i coppied my /home partition to an extended partition and added the rest of my partitions but now i cant login,
this is my partition table, mtab output and error message

Code:

root@person1873-laptop:~# fdisk -l

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xba9d1b9e

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        1311    10530576   83  Linux
/dev/sda2            1312        8570    58307917+   5  Extended
/dev/sda3            8571        9207     5116702+  83  Linux
/dev/sda4            9208        9729     4192965   82  Linux swap / Solaris
/dev/sda5            1312        8570    58307886   83  Linux

Code:

/dev/sda1 / ext3 rw,relatime,errors=remount-ro 0 0
proc /proc proc rw,noexec,nosuid,nodev 0 0
/sys /sys sysfs rw,noexec,nosuid,nodev 0 0
varrun /var/run tmpfs rw,noexec,nosuid,nodev,mode=0755 0 0
varlock /var/lock tmpfs rw,noexec,nosuid,nodev,mode=1777 0 0
udev /dev tmpfs rw,mode=0755 0 0
devshm /dev/shm tmpfs rw 0 0
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
/dev/sda5 /home ext3 rw,noexec,nosuid,nodev,relatime 0 0
/dev/sda3 /tmp ext3 rw 0 0
securityfs /sys/kernel/security securityfs rw 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,noexec,nosuid,nodev 0 0
gvfs-fuse-daemon /root/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev 0 0

Code:

/etc/gdm/Xsession: Beginning session setup...
Setting IM through im-switch for locale=en_AU.
Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default.
mkdtemp: private socket dir: Permission denied

could someone please tell me whats goin on?

stress_junkie · 07-19-2008, 05:26 AM

Is root able to log in? I am guessing that you obtained the information in your post by logging in to the root account. If that's the case then we know that the login process is fundamentally okay but normal users cannot log in.

There is a setting which enables/disables normal user login if the user account cannot access its $HOME directory. It is possible that the permissions on the /home directory prevent normal users to see through it to their $HOME directory. Check the ownership and permission settings at the top level of /home. They are typically root:root 755.

Person_1873 · 07-19-2008, 10:36 AM

yea, those permissions are fine, it doesn't auto-create a .Xauthority file if i delete the account and remake it

stress_junkie · 07-19-2008, 02:06 PM

This failure to create an .Xauthority file may be due to file permissions on the $HOME directory. If the account name is "normal" then see if the ownership and permissions are okay for its home directory at /home/normal. They should be normal:users 750. The important number there is the 7 at the beginning of the permission string. The other two numbers can be different.

Person_1873 · 07-19-2008, 09:01 PM

how do i get that printout?

Person_1873 · 07-21-2008, 06:52 PM

all the permissions are correct, everything is owned by the right users, could it be because it's on an extended partition rather than a primary partition? it's easy enough to fix if that is the case!

zer0python · 07-21-2008, 09:12 PM

Not sure, but a quick google search responded that it was because /tmp was not world writable, try:

Code:

chmod 5777 /tmp

see if that fixes your problem.