I am running OpenSuse Tumbleweed.
Yesterday I started as usual the machine, but only got to tty1. I entered username/password and then tried to start the graphical interface using startx
After typing startx I got:
xauth: error in locking authority file /home/javierhilda/.serverauth.3506
xauth: error in locking authority file /home/javierhilda/.Xauthority
xauth: error in locking authority file /home/javierhilda/.Xauthority
xauth: error in locking authority file /home/javierhilda/.Xauthority
xauth: (stdin):1: bad display name "install:0" in "add" command
Waiting for X server to begin accepting connections
.(EE)
Fatal server error:
(EE) Could not create lock file in /tmp/.tX0-lock
(EE)
Please consult the X.Org Foundation Support at http://wiki.x.org for help
(EE)
xinit: giving up
xinit: unable to connect to X server: connection refused
xinit: server error
--------------------------------------------------------------------------
xinit failed. /usr/bin/Xorg is not setuid, maybe that's the reason?
If so either use a display manager (strongly recommended) or adjust /etc/permissions.local and run "chkstat --system --set" afterwards
xauth: error in locking authority file /home/javierhilda/.Xauthority
I also tried the same (startx command) from root user with no results.
I rebooted and the system informed me it entered in recovery mode, so it asked several (a lot) of times for root password, it was painfully slow to get to the cursor.
Once I did, I tried to move some files from one directory to another, and it would not let me do that because there was no space left on the drive (there were yesterday several GB of free space).
Please help me recover control of my computer, thanks in advance for your cooperation.
Wild guess, but it appears to me that you are booting to a read-only file system. Perhaps a BTRFS problem, maybe someone with that experience will jump in now that I have replied to you.
Meantime, I will see if I can dig something up, but I don’t use BTRFS myself. Good luck.
Can you check which .Xauthority-files are in your home folder with
ls -l .Xauthority*
Removing all of these files and apparently .serverauth.3506 from your home directory (everything without sudo/root privileges) could solve the issue with X not starting.
After removing the files you would have to restart X / reboot.
What size is your / filesystem? Snapshotting configured by a default installation with BTRFS as the / filesystem can easily exhaust freespace on an otherwise adequately sized partition if not administratively maintained.
sudo fdisk -l /dev/sda
Disco /dev/sda: 465,76 GiB, 500107862016 bytes, 976773168 sectores
Modelo de disco: WDC WD500LPVX-2
Unidades: sectores de 1 * 512 = 512 bytes
Tamaño de sector (lógico/físico): 512 bytes / 4096 bytes
Tipo de etiqueta de disco: gpt
Identificador de disco: 84629602-5EC2-4FDB-B2F2-E2CEE566FFB7
Disposit. Comienzo Final Sectores Tamaño Tipo
/dev/sda1 2078 1230847 1228800 600M Entorno de recuperación de Windows
/dev/sda2 1230848 1845247 614400 300M Sistema EFI
/dev/sda3 1845248 2107391 262144 128M Reservado para Microsoft
/dev/sda4 2107392 491880447 489773056 233,5G Datos básicos de Microsoft
/dev/sda5 948938752 976773119 27834368 13,3G Entorno de recuperación de Windows
/dev/sda6 491880448 944744447 452864000 215,9G Sistema de ficheros de Linux
/dev/sda7 944744448 948938751 4194304 2G Linux swap
Las entradas en la tabla de particiones no están en el orden del disco
I also tried
sudo -i
du -ah / | sort -rh | head -n 20
sort: cannot create temporary file in '/tmp': No space left on device
So it’s confirmed that somehow the disk is full (as I said, just a day before it had plenty of space).
I don’t know which files would be safe to delete in order to be able to start the GUI properly and also how to fix this (I guess it had to do with the upgrades of the system).
Thanks in advance to all of you that are helping me.
You were right, it was a typo. I am copying from the notes I took, because I am using the same notebook (but running Windows now, as you may have noticed it’s a dual boot system).
So , I did type
ls -l .Xauthority*
When I finally could access the system, after several “exit” commands, I got this:
exit
Reloading system manager configuration.
Starting default.target
[ 2610.804181 ][ T1227 ] /var/lib/snapd/snaps/core_15925.snap: Can't lookup blockdev
[ 2634.177767 ][ T1286 ] /var/lib/snapd/snaps/snapd_19993.snap: Can't lookup blockdev
[ 2637.879979 ][ T1291 ] /var/lib/snapd/snaps/teams-for-linux_436.snap: Can't lookup blockdev
/bin/mv: cannot overwrite '/var/log/boot.omsg': No queda espacio en el dispositivo
/bin/sh: línea 1: /var/log/boot.msg: No queda espacio en el dispositivo
Welcome to openSUSE Tumbleweed 20240205 - Kernel 6.7.2-1-default (tty1)
The statement “No queda espacio en el dispositivo” means “No space left on device”
Remount /tmp using tmpfs (RAM FS): sudo mount -t tmpfs none /tmp.
If you’re absolutely sure, you can delete some of the snapper snapshots.
That should save up some space.
Next would be large media files.
This should free up just enough space to enable getting the system in a working state again.
If zypper is configured to keep downloaded packages, you can gain space by removing them: sudo zypper clean.
Check the subdirectory in /var/log/journal/. If it has files more than 6 months old or file count is more than a dozen or so, its doing a lot of space wasting. Space it uses is configurable in /etc/systemd/journald.conf.
Snapshots can be humonguous space consumers. Ancient snapshots aren’t needed. Delete excess.
First you need to finish the search for waste. How old is this installation? How often have you been doing upgrades? If old installation and keeping packages in cache your space problem could be almost entirely /var/log/cache/zypp/. Did you try sudo zypper clean? Your 200GB+ TW filesystem shouldn’t have a problem supporting more than 5 snapshots, unless you have been saving many large files such as videos or .isos.
Originally I had installed version 15.2, then (last year) switched to Tumbleweed. The system offers different package upgrades quite often, sometimes there are several hundreds packages to update.
I did try sudo zypper clean, although I don´t know how much space was recovered with that command.
/var/log/cache/zypp
does not exist on my system. However I do have /var/cache/zypp wich has 106,8 MB.
And yes, I do have some large files on my system (not too large, but there are many, that amounts to about 150 GB).
That was error missed at the time, and the forum software doesn’t allow edits after 10 minutes. /var/cache/zypp/packages/ is what I should have typed.
Between the 233.5G / filesystem size, your 150G files on / instead of /home/, and the OS with BTRFS and snapshotting, I can see freespace able to run short if snapshot count gets past a relatively small number.
How much is your current freespace? How many snapshots remain?