Running TW with KDE desktop. After an exciting time away trying and failing to set up a remote desktop on this machine (HP-Z640-1) I have returned to UK to find the machine up and running but when I try and log in I have to enter my pw three times before the login is effective. Once logged in all seems normal but I would like to correct the problem. Where should I look first?
I assume that you’re using SDDM as the login manager? You could examine the system journal for issues/errors?
Just to clarify further. Is this occurring with the display manager login screen following a boot, or does this relate to the machine coming out of standby or similar?
anything encrypted ???
Hi, sorry for delayed reply. I am using SDDM and the problem occurs after a reboot. If I then just log out I can log back in with only the one pw entry. Further investigation has now resulted in no login at all so checked and found my / directory 95% full.
A while back I had this problem when I had 50GB btrfs partition but after much effort increased the size to 100GB and this is now effectively full. After the earlier problem I spent time sorting out my snapshots and removing all but last half dozen and thought I had it all sorted but it seems I have it wrong so…
I now cannot boot at all except to minimal grub screen.
With some trepidation I ask if anybody has time to bail me out again. I am burning a DVD Tumbleweed full installation so it is available for booting to rescue system but will definitely need guidance thereafter.
Budgie2
Hmmmm. Do you know why the partition is filling up?
There can be many reasons, from a user creating many large files in their home dir … to system-related excessive file use, like /tmp filling up, log file sub-directories filling up, a rogue application creating too many temp files.
The first thing I would do is to run a Disk Usage Analyzer, to find where the excessive storage is happening, and clean it up.
However, if you know it’s because many large files are being created in your home sub-dir, then I would suggest adding a larger drive (or a second one) … or archiving files away on an external disk, then remove older personal files.
Well, then better start new topic with clear question. And explain what “minimal grub screen” is and what happens after you reach this screen.
You do not need Tumbleweed rescue text-only mode. This will end up with a lot of screenshots. You need any live image (it can be openSUSE, Tumbleweed is better as it has the latest versions of tools) that allows you to boot into GUI, connect to the Internet and copy-paste information into forum posts.
But you need to start with showing some facts, not describing your interpretation of them.
Understood. Will prepare a new Live DVD. A brief check indicated that I have filled up my root with snapshots but will get back to you when I have new Live DVD. I started the Rescue and saw that systems had failed during this start, ie;
Failed to start User Login Management
Failed to start wicked managed network interfaces
Failed to listen on D-Bus System Message Bus Socket
Will get back to you later.
Many thanks.
OK I have now booted to Live distro and am able to use the browser so am posting this with grateful thanks.
Where should I start?
You should start explaining your problem. As I already said - “minimal grub screen” is rather cryptic.
If you are absolutely sure your problem is lack of btrfs space - mount your filesystem and post
btrfs filesystem usage -T /mount-point-where-you-mounted
This is what I have done to mount. I have shown all the steps so far:-
linux@localhost:~> lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT
NAME FSTYPE SIZE MOUNTPOINT
loop0 squashfs 899.6M /run/overlay/squashfs_container
loop1 ext4 5G /run/overlay/rootfsbase
sda 238.5G
|-sda1 vfat 100M
|-sda2 16M
|-sda3 ntfs 237.9G
-sda4 ntfs 499M sdb 931.5G -sdb1 crypto_LUKS 931.5G
sdc 0B
sdd 0B
sde 0B
sr0 iso9660 4.4G /run/overlay/live
nvme0n1 1.8T
|-nvme0n1p1 vfat 8M
|-nvme0n1p2 vfat 512M
|-nvme0n1p3 swap 2G
`-nvme0n1p4 btrfs 1.8T
linux@localhost:~> mkdir -p /mnt
linux@localhost:~> mount /dev/nvme0n1p4 /mnt
mount: /mnt: must be superuser to use mount.
dmesg(1) may have more information after failed mount system call.
linux@localhost:~> sudo mount /dev/nvme0n1p4 /mnt
linux@localhost:~> cd /mnt
linux@localhost:/mnt> ls
boot dev etc home opt proc root run srv sys tmp usr var
linux@localhost:/mnt> cd …
linux@localhost:/>
linux@localhost:/> btrfs filesystem usage -T /mnt
Absolute path to ‘btrfs’ is ‘/usr/sbin/btrfs’, so running it may require superuser privileges (eg. root).
linux@localhost:/> sudo btrfs filesystem usage -T /mnt
Overall:
Device size: 1.82TiB
Device allocated: 1.72TiB
Device unallocated: 99.45GiB
Device missing: 0.00B
Device slack: 0.00B
Used: 1.71TiB
Free (estimated): 104.26GiB (min: 54.53GiB)
Free (statfs, df): 104.26GiB
Data ratio: 1.00
Metadata ratio: 2.00
Global reserve: 512.00MiB (used: 0.00B)
Multiple profiles: no
Data Metadata System
Id Path single DUP DUP Unallocated Total Slack
1 /dev/nvme0n1p4 1.71TiB 8.00GiB 64.00MiB 99.45GiB 1.82TiB -
Total 1.71TiB 4.00GiB 32.00MiB 99.45GiB 1.82TiB 0.00B
Used 1.71TiB 3.25GiB 224.00KiB
linux@localhost:/>
I have not yet mount --bind the essential directories.
On further investigation I have decided on a fresh install, retaining my /home directory. If I may I shall need help preventing this problem with the snapshots.
Interim report,
I have had considerable difficulty while I have been backing up my ~/ directory to a NAS using the Live TW distro. I have tried to ensure that my screen remains on and does not revert to a login screen; the reason being that after needing to “log in” my screen went dark and I could not recover the login page. I have had t start over and while I have been typing this the screen switched to the green “login” screen. Fortunately touching the mouse brought my browser screen, which I am using, available.
How do I stop this unwanted action. I may ahve missed something but has disabled all the power saving options and screen saver that I can in the settings pages.
I think screen locking has been the problem but on this reboot it seems to be OK so please ignore this post.
You’re referring to the lock screen rather than the display manager login. You can adjust the behaviour via System Settings.