2 pc impossible to log in

Hi there,
I am scared! In both 2 pc are impossible to log in. All have Xfce4 and in all, if I try to log, I get after the system boot the console and not the windows of Xfce.
I don't know what happened.
In both pc I have made an update and upgrade (apt-get upgrade).
but the fact much more important is that in one the log in password doesn't work at all.

Originally Posted by Paolopd Hi there, I am scared! In both 2 pc are impossible to log in. All have Xfce4 and in all, if I try to log, I get after the system boot the console and not the windows of Xfce. I don't know what happened. In both pc I have made an update and upgrade (apt-get upgrade). but the fact much more important is that in one the log in password doesn't work at all.

No panic, worst case you might have to reinstall.

First, what version of Debian is installed? That might help.

Second, Do you have a live-cd or rescue image you can use to boot to live mode? Live mode can be used to fix many things.

Third. I take it that you CAN log into one of them, but xwindows is not starting. Can you try the command "startx" and report what happens? If it fails, the message may be very important so please prepare to copy that information.

Thanks for your rapid answer.
Well, in both I have Debian 9 and, that's is mysterious, in one of them (desktop) after I restart it for the umpteenth time it works, but the system gave me back this message:

ehci-pci 0000:00:0b.1: EHCI Host Controller
Jul 14 21:21:54 debian kernel: [    1.301480] ehci-pci 0000:00:0b.1: new USB bus registered, assigned bus number 1
Jul 14 21:21:54 debian kernel: [    1.301495] ehci-pci 0000:00:0b.1: debug port 1
Jul 14 21:21:54 debian kernel: [    1.301513] ehci-pci 0000:00:0b.1: can't setup: -12
Jul 14 21:21:54 debian kernel: [    1.301554] ehci-pci 0000:00:0b.1: USB bus 1 deregistered
Jul 14 21:21:54 debian kernel: [    1.301571] ehci-pci 0000:00:0b.1: init 0000:00:0b.1 fail, -12
Jul 14 21:21:54 debian kernel: [    1.301695] ehci-pci: probe of 0000:00:0b.1 failed with error -12

Right now is working.

For the other pc I have found the problem, I think. The partition, where is stored the system, appears to be full (9Gb.) and the problem right now is that I have to reinstall or copy my home directory somewhere and then resize with Gparted.

I hope wpeckham does not mind me offering a warning here

when you change partition tables.....your /etc/fstab file may need to be amended.

for those stuck with UUID fstabs the risk is high it won't boot properly
for those who label their partitions with a label....for ext4 I use e2label command....gparted also works
---there is less chance of system not booting.

Originally Posted by Paolopd Thanks for your rapid answer. Well, in both I have Debian 9 and, that's is mysterious, in one of them (desktop) after I restart it for the umpteenth time it works, but the system gave me back this message: ehci-pci 0000:00:0b.1: EHCI Host Controller Jul 14 21:21:54 debian kernel: [ 1.301480] ehci-pci 0000:00:0b.1: new USB bus registered, assigned bus number 1 Jul 14 21:21:54 debian kernel: [ 1.301495] ehci-pci 0000:00:0b.1: debug port 1 Jul 14 21:21:54 debian kernel: [ 1.301513] ehci-pci 0000:00:0b.1: can't setup: -12 Jul 14 21:21:54 debian kernel: [ 1.301554] ehci-pci 0000:00:0b.1: USB bus 1 deregistered Jul 14 21:21:54 debian kernel: [ 1.301571] ehci-pci 0000:00:0b.1: init 0000:00:0b.1 fail, -12 Jul 14 21:21:54 debian kernel: [ 1.301695] ehci-pci: probe of 0000:00:0b.1 failed with error -12 Right now is working.

I have seen this sort of error on a Fujitsu machine (running Debian 9) with a flaky USB interface (motherboard problem). Sometimes it really struggles to boot, with the constant USB problems. I usually have no problem after hard power cycling it, though. Even so, there's a USB touchscreen which never shows up until maybe a minute or two after boot. It's definitely a hardware problem, because the same model of Fujitsu works 100% every boot. It's PXE boot, so it's literally the same OS booting when I swap the other one in.

For the other pc I have found the problem, I think. The partition, where is stored the system, appears to be full (9Gb.) and the problem right now is that I have to reinstall or copy my home directory somewhere and then resize with Gparted.

If you can resize this partition without resizing or moving swap, then you will be fine. The UUIDs will remain the same. But if you have to move or resize a swap partition, then you might as well just delete the swap partition. The UUID will change, which means messing around with etc/fstab (by default, Debian 9 uses UUIDs rather than device numbers/letters in /etc/fstab and RESUME setting). If you're going to edit etc/fstab anyway, you might as well do things right and not use a swap partition at all. You can later set up a swap file if you really want.

https://wiki.debian.org/Swap

There are numerous advantages with a swap file, not the least of which is that it's really easy to shrink or eliminate the swap file in order to give the OS some breathing space. The only disadvantage is that you no longer have the hibernation feature (suspend functionality is unaffected).

Originally Posted by aus9 I hope wpeckham does not mind me offering a warning here

I never mind. If your comment is valid, it is valuable. If it is not, it is an opportunity to learn or teach. I come here to learn, and if you have something of value that I have not seen before I WANT to see what you have to say.

I have used labels since the great disaster when udev rolled out. (Ubuntu 8 was rolling out at the time I believe) and people were experiencing boot problems all OVER the place. I have never had issues with a resize, but I always use labels so I may have avoided the issue. That was a good thought to mention! Thank you.

Originally Posted by IsaacKuo There are numerous advantages with a swap file, not the least of which is that it's really easy to shrink or eliminate the swap file in order to give the OS some breathing space. The only disadvantage is that you no longer have the hibernation feature (suspend functionality is unaffected).

I still prefer a swap partition, not only for hibernation but for a performance advantage in certain situations.

Also: I have seen a newby try to delete an active swap file, I have never seen one try to remove a working and active swap partition. (Not that it has never happened, just that I have not seen it)

Post has been editted

I have to reinstall or copy my home directory somewhere

I was trying to warn that the OP may be attempting to move his home.
If he moves his home it is more likely he means move to a different partition
so he will need an entry in /etc/fstab for that mount point

I agree that if re-installs over an existing partition he may be ok but I am now tempted to show my fstab

LABEL=t1 / ext4 errors=remount-ro 0 1
LABEL=t4 /t4 ext4 users,rw 0 2

yes /t1 and /t4 and non-compliant FHS directories but its simple and it works
yes home is a sub-dir to /

unfortunately I can't use label for swap partition

Originally Posted by wpeckham I still prefer a swap partition, not only for hibernation but for a performance advantage in certain situations. Also: I have seen a newby try to delete an active swap file, I have never seen one try to remove a working and active swap partition. (Not that it has never happened, just that I have not seen it)

Who cares if a newbie tries to delete an active swap file? It will just fail because the operation is not permitted (even if running as root, the only user with permissions on a swapfile). The only real disadvantage is the lack of hibernation feature. I can't imagine any real life situation where there's a noticeable difference in performance between a swap partition and swapfiles.

In contrast, I find accidentally running out of space on / to be relatively common. Having a big chunk of space that you can immediately acquire on / is convenient. If you still need swapspace, you can create a new swapfile in a different partition (in a multi-partition setup).