Multiple boot errors upon login

linuxlinux00 · July 20, 2015, 10:43pm

Hello all!

After trying to login to my system I get the following prompt:
*Cannot login to home directory. Using /.
*
after I hit ok another pop up box appears and says:
*CAll to inusertem failed (temporary directories full?) Check your installation.

*I bit more info here on how my setup is…

“Data” is where I’ll usually keep some different software in
“Z” is my business data file drive

I also do have a triple monitor setup and I successfully installed the NVIDIA driver and everything was working just fine after reboot. It seems before I shut off I ran bleachbit turned on the computer today and bam this all happened.

fstab:


UUID=6d85804e-ecba-48b5-8351-16c00e68b72b   /                        ext4     acl,user_xattr           11
/dev/mapper/cr_mnt_Data                                    /mnt/Data          ext4     acl,user_xattr,nofail  02
/dev/mapper/cr_mnt_Z                                        /mnt/Z                ext4     acl,user_xattr,nofail  02
/dev/mapper/cr_home                                         /home                 ext4     acl,user_xattr,nofail   02
UUID=f7268097-baa6-44a2-bb9c-araa2d573f45    /boot                   ext4    acl,user_xattr            12

I’ve been reading about ownership stuff but I think everything looks fine as far as ownership goes. IDK. Kinda stuck here.

Appreciate any help.

gogalthorp · July 20, 2015, 11:22pm

Check space on root. Do you ever log into a GUI as root?

You have a LVM I assume is encrypted maybe???

Is this all one drive??

linuxlinux00 · July 20, 2015, 11:39pm

I have 4 drives in my desktop.

The " /boot " & " / " are on a 120gb SSD. I’ve assigned 100mb to " /boot " and the remaining space on " / "
/home is 2TB - encrypted
/Z is 150 GB - encrypted
/Data is 1TB - encrypted

and no I have not tried logging into GUI as root. I’ll try now…

Hmmm. Odd. I was able to login to GUI as “root” but not my “admin” account

gogalthorp · July 20, 2015, 11:53pm

Looks like home is not being mounted then since /root is not is not in /home so there is access to the root home /root. As a rule you should never run in a GUI logged as root you can cause inadvertent damage

Free space on root? With your set up should be plenty but error logs can grew to very huge sizes and stop running a user GUI

Check your /home and see if any of the files are owned by root

Is it prompting for the passwords??

linuxlinux00 · July 21, 2015, 12:52am

dv:

use%  Mounted on
6%     /
0%     /dev
0%    /dev/shm
1%    /run
0%    /sys/fs/cgroup
41%  /boot

Have plenty of space on all drives. Although I did notice that yeah /home is not being mounted for some reason? And when I go into /home when in cli its blank. Nothing is inside when I go to it. Not even hidden files using “la”

gogalthorp · July 21, 2015, 1:36am

Run smartctl against it you may have a failed drive

nrickert · July 21, 2015, 1:42am

It looks as “/home” is encrypted.

My suggestion would be to boot from live media (such as the opensuse live CD). Then see if you are able to access that encrypted partition.

From what you showed, it is hard to see what is the problem. One messages suggests that “/tmp” might be full, and perhaps the crypto software needs space there. So mount your root partition and see if there is space. I’m assuming “/tmp” is just a directory there.

linuxlinux00 · July 21, 2015, 1:46am

All drives are good.

gogalthorp · July 21, 2015, 1:51am

You can not know that without running smartctl there are many modes of failure. Since we can not see over your shoulder you have to verify you ran the tests

Also had you run bleachbit before with out problem or is this the first run???

linuxlinux00 · July 21, 2015, 3:50am

I’ll have to run it when I get back. I just tested the drives before formatting them and all passed the SMART tests windows. And yeah I’ve used bleachbit for a while now. Just seemed weird…

robin_listas · July 21, 2015, 3:54am

On 2015-07-20 22:46, linuxlinux00 wrote:
>
> Hello all!
>
> After trying to login to my system I get the following prompt:
> -Cannot login to home directory. Using /.
> -
> after I hit ok another pop up box appears and says:

The next error is irrelevant, because “/home” can’t be accessed, it is
defaulting to “/”, and your user has no permissions there, so everything
fails.

In this state, you can only login as root, because it uses “/root”, not
“/home”. However, many people here cringe at login as root in graphics
mode. Better use text mode, safer.

> It
> seems before I shut off I ran bleachbit turned on the computer today and
> bam this all happened.

I wonder if “bleachbit” deleted something it should not. :-?

>
> fstab:
>
> Code:
> --------------------
>
> UUID=6d85804e-ecba-48b5-8351-16c00e68b72b / ext4 acl,user_xattr 11
> /dev/mapper/cr_mnt_Data /mnt/Data ext4 acl,user_xattr,nofail 02
> /dev/mapper/cr_mnt_Z /mnt/Z ext4 acl,user_xattr,nofail 02
> /dev/mapper/cr_home /home ext4 acl,user_xattr,nofail 02
> UUID=f7268097-baa6-44a2-bb9c-araa2d573f45 /boot ext4 acl,user_xattr 12
>
> --------------------

From the above it looks like you are using encripted filesystems for
/home, /mnt/Data and /mnt/Z. Please post the contents of “/etc/crypttab”
so that we can see what device contains them.

Also run “sbin/dmsetup ls” to find out if any of them is currently
available.

Of course, at some point during boot you should have got a prompt to
enter the filesystem passphrases. Did you?

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

linuxlinux00 · July 21, 2015, 11:52am

The next error is irrelevant, because “/home” can’t be accessed, it is
defaulting to “/”, and your user has no permissions there, so everything
fails.

In this state, you can only login as root, because it uses “/root”, not
“/home”. However, many people here cringe at login as root in graphics
mode. Better use text mode, safer.

Yeah, I’m able to login as root in graphic and text mode. But as my regular account its a not go in GUI, but i can in text mode.

I wonder if “bleachbit” deleted something it should not. :-?

That’s kinda what I’m thinking. Plus i did run as root… usually i dont.

From the above it looks like you are using encripted filesystems for
/home, /mnt/Data and /mnt/Z. Please post the contents of “/etc/crypttab”
so that we can see what device contains them.

Also run “sbin/dmsetup ls” to find out if any of them is currently
available.

/etc/cryttab: ( the “” is the disk name. just too lazy to type all that lol)

cr_mnt_Data   /dev/disk/by-id/ata-""-part1  none none  
cr_mnt_Z       /dev/disk/by-id/ata-""-part1 none none
cr_mnt_home /dev/disk/by-id/ata-""-part1 none none

I ran “sudo ./dmsetup ls” and it returned No device found

Of course, at some point during boot you should have got a prompt to
enter the filesystem passphrases. Did you?

In gui yes i did. I entered all passwords and lead me to gui login screen. BUT if i try and enter password for drives in cli it won’t accept them. Kinda ■■■■■■■■ bricks because if i loose that encrypted data im SOL. lol.

Thanks mate!

linuxlinux00 · July 21, 2015, 11:57am

I booted to the live cd and entered the password for the drives. Its accepted none of them. I’m freaking on about the data. Can’t lose it…

As far as whats encrypted is my
/home
/Z
/Data
drives.

robin_listas · July 21, 2015, 12:34pm

On 2015-07-21 11:56, linuxlinux00 wrote:

>> I wonder if “bleachbit” deleted something it should not. :-?
>
> That’s kinda what I’m thinking. Plus i did run as root… usually i
> dont.

I’ve never used that application.

>> From the above it looks like you are using encripted filesystems for
>> /home, /mnt/Data and /mnt/Z. Please post the contents of “/etc/crypttab”
>> so that we can see what device contains them.
>>
>> Also run “sbin/dmsetup ls” to find out if any of them is currently
>> available.
>
> /etc/cryttab: ( the “” is the disk name. just too lazy to type all that
> lol)
>
> Code:
> --------------------
> cr_mnt_Data /dev/disk/by-id/ata-“”-part1 none none
> cr_mnt_Z /dev/disk/by-id/ata-“”-part1 none none
> cr_mnt_home /dev/disk/by-id/ata-“”-part1 none none
> --------------------

So, no LVM, but independent partitions.

> I ran “sudo ./dmsetup ls” and it returned No device found

Typed like that it should not work.


minas-tirith:~ # ./dmsetup ls
-bash: ./dmsetup: No such file or directory
minas-tirith:~ # dmsetup ls
cr_home  	(253:0)
minas-tirith:~ #

Of course, at some point during boot you should have got a prompt to
enter the filesystem passphrases. Did you?

In gui yes i did. I entered all passwords and lead me to gui login
screen. BUT if i try and enter password for drives in cli it won’t
accept them. Kinda ■■■■■■■■ bricks because if i loose that encrypted
data im SOL. lol.

The manual commands to mount an encrypted device are:


cryptsetup luksOpen $CR_DEVICE $CR_NAME
mount $FSTAB_MOUNT

Of course, replacing the tokens with the appropriate names.

Like this:


cryptsetup luksOpen /dev/disk/by-id/ata-""-part1 cr_mnt_home

It should prompt for your password.

You could also try:


file -s /dev/disk/by-id/ata-""-part1

You should get a response similar to this:


> minas-tirith:~ # file -s /dev/loop0
> /dev/something: LUKS encrypted file, ver 1 [aes, cbc-essiv:sha256, sha1] UUID: 57d5fbea-....
> minas-tirith:~ #

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

linuxlinux00 · July 21, 2015, 1:12pm

I’ve never used that application.

It’s pretty good for cleaning always used it in ubuntu and kubuntu.

So, no LVM, but independent partitions.

Yup.

Typed like that it should not work.

minas-tirith:~ # ./dmsetup ls
-bash: ./dmsetup: No such file or directory
minas-tirith:~ # dmsetup ls
cr_home (253:0)
minas-tirith:~ #

Even when typed “dmsetup ls” I still get No Devices found

The manual commands to mount an encrypted device are:

cryptsetup luksOpen $CR_DEVICE $CR_NAME
mount $FSTAB_MOUNT

Of course, replacing the tokens with the appropriate names.

Like this:

cryptsetup luksOpen /dev/disk/by-id/ata-“”-part1 cr_mnt_home

It should prompt for your password.

You could also try:

file -s /dev/disk/by-id/ata-“”-part1

You should get a response similar to this:

minas-tirith:~ # file -s /dev/loop0
/dev/something: LUKS encrypted file, ver 1 [aes, cbc-essiv:sha256, sha1] UUID: 57d5fbea-…
minas-tirith:~ #

I’ve tried the:

cryptsetup luksOpen /dev/disk/by-id/ata-""-part1 cr_mnt_home

but it keeps saying “No key available with this passphrase” I know the password and I’ve double checked everything.

the “file -s /dev/disk/by-id/ata-”“-part1” method returns with "/dev/disk/by-id/ata…-part1: symbolic link to ‘…/…/sdc1’

Thanks

robin_listas · July 21, 2015, 1:28pm

On 2015-07-21 13:16, linuxlinux00 wrote:

> but it keeps saying “No key available with this passphrase” I know the
> password and I’ve double checked everything.

Try the three partitions.

> the “file -s /dev/disk/by-id/ata-”"-part1" method returns with
> "/dev/disk/by-id/ata…-part1: symbolic link to ‘…/…/sdc1’

Well, then just replace the device with “/dev/sdc1” and try again.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

linuxlinux00 · July 22, 2015, 7:34am

Try the three partitions.

Not too sure what you mean there

Well, then just replace the device with “/dev/sdc1” and try again.

Will try that now.

linuxlinux00 · July 22, 2015, 8:30am

Was browsing around and found another person was having an issue too. Not got solved though. This is the cryptsetup luksDump for my home drive.

Version:        1
Cipher name:    aes
Cipher mode:    xts-plain64
Hash spec:      sha1
Payload offset: 4096
MK bits:        256
MK digest:      79 ba de 8f d3 25 3d 08 25 2c c5 a1 8c c2 b4 19 4f bc 5b 8e 
MK salt:        92 b6 7b 57 9b 19 94 d2 db a1 db f4 34 21 af ed 
                13 77 12 35 74 d0 c1 42 d9 f0 50 ed 55 61 19 10 
MK iterations:  156000
UUID:           00c39e52-60bb-4ee4-b7f5-688c3d062d94

Key Slot 0: ENABLED
        Iterations:             627450
        Salt:                   2c d1 84 37 83 2e aa c7 58 62 3f 47 17 45 b9 3d 
                                8e b9 0f 5b dd d3 c5 1f 63 09 8f 94 04 a5 e1 40 
        Key material offset:    8
        AF stripes:             4000
Key Slot 1: DISABLED
Key Slot 2: DISABLED
Key Slot 3: DISABLED
Key Slot 4: DISABLED
Key Slot 5: DISABLED
Key Slot 6: DISABLED
Key Slot 7: DISABLED

robin_listas · July 22, 2015, 12:34pm

On 2015-07-22 07:36, linuxlinux00 wrote:
>
>> Try the three partitions.
>>
> Not too sure what you mean there

Well, you have three encrypted partitions: try if any of them can be
decoded. Data, Z, home.

>> Well, then just replace the device with “/dev/sdc1” and try again.
> Will try that now.
>
>

I see you tried luksDump on your home: the device seems to be there, intact.

You /just/ have a problem with the password. I would suggest typing the
password in the terminal, with " echo somepassword" to see if all
characters can be typed correctly.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

linuxlinux00 · July 23, 2015, 5:51am

Well, you have three encrypted partitions: try if any of them can be
decoded. Data, Z, home.

I’ve tried all of them and nothing. Still saying I have the incorrect password.

I see you tried luksDump on your home: the device seems to be there, intact.

You /just/ have a problem with the password. I would suggest typing the
password in the terminal, with " echo somepassword" to see if all
characters can be typed correctly.

Everything is coming out correctly. This sucks. I just may have to format all my data