Problem with 11.2 after booting

Firstly Happy New Year everyone.

On New Years day while browsing through my system in Dolphin I suddenly got an error pop saying “The process for the file protocol died unexpectedly.” I couldn’t anything there after. Everything I did would get this error. I tried running dolphin from the cli to see if there were any other errors and saw that there was some problem with the device running out of space. rebooting would not help and as soon as the desktop came up I’d get the “The process for the file protocol died unexpectedly.” message again. See image below (showing desktop immediately after boot up (with desktop icons missing) and konsole open to start dolphin (which did nothing) and starting yast2 showing out of space error message.

http://i198.photobucket.com/albums/aa111/sklipikish/openSUSE/th_636e2bfd.png](http://i198.photobucket.com/albums/aa111/sklipikish/openSUSE/636e2bfd.png)

I logged in at runlevel 3 and deleted the contents of the /tmp and /var/tmp folders hoping that would fix it and it did for five minutes and then the message popped up again.

Can anyone give any pointers what may be causing this? No error show up in the dmesg logs.

First port of call:

Try a new user login
Tell us what it’s like

suse tpx60s wrote:

> Can anyone give any pointers what may be causing this?

my guess is you have some tremendously HUGE log files in /var/log…

try another loging to runlevel 3 and look in /var/log there may be
(depending on how you have logrotate setup) a bunch of .bz2 files
month old you can dump…

and, if /var/log/messages or /var/log/firewall are huge (say, 1GB or
so) look inside and see what is going crazy, because you will probably
need to fix it eventually (as well as tune your logrotate to dump more
often)…


DenverD
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]
Programming: a race between software engineers building bigger/better
idiot-proof programs, and the universe building bigger/better idiots.
So far, the universe is winning. Rick Cook

@caf Nope, logging in as a different user does not help unfortunately. Get the same thing.

@Denver. I looked at the logs and there doesn’t seem to be anything overly large. The largest log file is 3.8MB (mail.info). Is that large for a log file? I had a year’s worth of bz2 files which I deleted but that didn’t help. I found I had a lot of mysql logs which I deleted and that seemed to help for about 20 minutes.

I also get an authentication error when my screen locks and I try unlocking it. The error is “Cannot unlock the session because the authentication system failed to work, you must kill the kscreenlocker (pid 11.363) manually.” The only way out is to ctrl-alt-backspace, after which I can no longer log in to the desktop. The screen just goes blank and returns to the KDE login screen. I am forced to delete the contents of /tmp and /var/tmp folders again before I am able to boot and log into the desktop but still get the “The process for the file protocol died unexpectedly.”

Below is a sample of the errors in the /var/log/messages log file. there seems to be a lot of strange things happening.


Jan  4 11:17:50 suntp001 kdm_config[11634]: Multiple occurrences of section [General] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
Jan  4 11:17:50 suntp001 kdm_config[11634]: Multiple occurrences of section [Xdmcp] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
Jan  4 11:17:50 suntp001 kdm_config[11634]: Multiple occurrences of section [X-*-Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
Jan  4 11:17:50 suntp001 kdm_config[11634]: Multiple occurrences of section [X-*-Greeter] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
Jan  4 11:17:50 suntp001 kdm_config[11634]: Multiple occurrences of key 'Language' in section [X-*-Greeter] of /usr/share/kde4/config/kdm/kdmrc
Jan  4 11:17:50 suntp001 kdm_config[11634]: Multiple occurrences of key 'ShowUsers' in section [X-*-Greeter] of /usr/share/kde4/config/kdm/kdmrc
Jan  4 11:17:50 suntp001 kdm_config[11634]: Multiple occurrences of key 'UseBackground' in section [X-*-Greeter] of /usr/share/kde4/config/kdm/kdmrc
Jan  4 11:17:50 suntp001 kdm_config[11634]: Multiple occurrences of key 'UseTheme' in section [X-*-Greeter] of /usr/share/kde4/config/kdm/kdmrc
Jan  4 11:17:50 suntp001 kdm_config[11634]: Multiple occurrences of section [X-:*-Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
Jan  4 11:17:50 suntp001 kdm_config[11634]: Multiple occurrences of section [X-:0-Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them.
Jan  4 11:17:50 suntp001 kdm[2367]: Cannot create X server authorization file

Jan  4 11:17:59 suntp001 kernel:  3201.949213] --- end trace 54d463205e130713 ]---
Jan  4 11:18:00 suntp001 console-kit-daemon[2443]: WARNING: Cannot create file /var/run/ConsoleKit/database~: No space left on device
Jan  4 11:18:04 suntp001 kdm[2367]: X server died during startup
Jan  4 11:18:04 suntp001 kdm[2367]: X server for display :1 cannot be started, session disabled
Jan  4 11:18:34 suntp001 console-kit-daemon[2443]: WARNING: Cannot create file /var/run/ConsoleKit/database~: No space left on device
Jan  4 11:18:34 suntp001 console-kit-daemon[2443]: WARNING: Cannot unlink /var/run/ConsoleKit/database: No such file or directory
Jan  4 11:19:00 suntp001 console-kit-daemon[2443]: WARNING: Cannot create file /var/run/ConsoleKit/database~: No space left on device
Jan  4 11:19:00 suntp001 console-kit-daemon[2443]: WARNING: Cannot unlink /var/run/ConsoleKit/database: No such file or directory
Jan  4 11:19:26 suntp001 console-kit-daemon[2443]: WARNING: Cannot create file /var/run/ConsoleKit/database~: No space left on device
Jan  4 11:19:26 suntp001 console-kit-daemon[2443]: WARNING: Cannot unlink /var/run/ConsoleKit/database: No such file or directory
Jan  4 11:19:26 suntp001 console-kit-daemon[2443]: WARNING: Cannot create file /var/run/ConsoleKit/database~: No space left on device
Jan  4 11:19:26 suntp001 console-kit-daemon[2443]: WARNING: Cannot unlink /var/run/ConsoleKit/database: No such file or directory
Jan  4 11:20:13 suntp001 crontab[11905]: (root) LIST (root)
Jan  4 11:20:13 suntp001 crontab[11913]: (root) LIST (root)
Jan  4 11:24:46 suntp001 console-kit-daemon[2443]: WARNING: Cannot create file /var/run/ConsoleKit/database~: No space left on device
Jan  4 11:24:46 suntp001 console-kit-daemon[2443]: WARNING: Cannot unlink /var/run/ConsoleKit/database: No such file or directory
Jan  4 11:25:06 suntp001 kdm[2367]: X server for display :0 terminated unexpectedly
Jan  4 11:25:14 suntp001 checkproc: checkproc: can not get session id for process 7561!
Jan  4 11:25:15 suntp001 smartd[5037]: Device: /dev/sda [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 116 to 117
Jan  4 11:25:15 suntp001 smartd[5037]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 61 to 58
Jan  4 11:25:15 suntp001 smartd[5037]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 39 to 42
Jan  4 11:25:15 suntp001 smartd[5037]: Device: /dev/sda [SAT], SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 53 to 54
Jan  4 11:26:20 suntp001 console-kit-daemon[2443]: WARNING: Cannot create file /var/run/ConsoleKit/database~: No space left on device
Jan  4 11:26:56 suntp001 console-kit-daemon[2443]: WARNING: Cannot create file /var/run/ConsoleKit/database~: No space left on device
Jan  4 11:26:56 suntp001 console-kit-daemon[2443]: WARNING: Cannot unlink /var/run/ConsoleKit/database: No such file or directory
Jan  4 11:28:49 suntp001 kdm[2367]: X server for display :0 terminated unexpectedly
Jan  4 11:28:57 suntp001 console-kit-daemon[2443]: WARNING: Cannot create file /var/run/ConsoleKit/database~: No space left on device
Jan  4 11:28:58 suntp001 checkproc: checkproc: can not get session id for process 12302!
Jan  4 11:29:11 suntp001 console-kit-daemon[2443]: WARNING: Cannot create file /var/run/ConsoleKit/database~: No space left on device
Jan  4 11:30:01 suntp001 /usr/sbin/cron[13360]: (root) CMD (test -x /usr/lib/cron/run-crons && /usr/lib/cron/run-crons >/dev/null 2>&1)
Jan  4 11:30:13 suntp001 shutdown[13383]: shutting down for system reboot
Jan  4 11:30:13 suntp001 init: Switching to runlevel: 6

Jan  4 11:30:17 suntp001 console-kit-daemon[2443]: WARNING: Cannot create file /var/run/ConsoleKit/database~: No space left on device
Jan  4 11:30:17 suntp001 console-kit-daemon[2443]: WARNING: Cannot unlink /var/run/ConsoleKit/database: No such file or directory
Jan  4 11:30:18 suntp001 console-kit-daemon[2443]: WARNING: Cannot create file /var/run/ConsoleKit/database~: No space left on device
Jan  4 11:30:18 suntp001 console-kit-daemon[2443]: WARNING: Cannot unlink /var/run/ConsoleKit/database: No such file or directory
Jan  4 11:30:18 suntp001 console-kit-daemon[2443]: WARNING: Cannot create file /var/run/ConsoleKit/database~: No space left on device
Jan  4 11:30:18 suntp001 console-kit-daemon[2443]: WARNING: Cannot unlink /var/run/ConsoleKit/database: No such file or directory

Edit: Forgot to add that my / folder has 2.5GB free disk space so I don’t think it’s physical disk space that is the problem.

There are so many messages with “No space left on device” … it does appear to be that we are being told something.

Still, can you humour us, and provide/post the output of:

df -Th

And
Can you please explain your initial screen shot which I assume is showing your attempts to start dolphin in the terminal??

But why is it @# (that is root)

On 2011-01-04 13:06, suse tpx60s wrote:
>

> @Denver. I looked at the logs and there doesn’t seem to be anything
> overly large. The largest log file is 3.8MB (mail.info). Is that large
> for a log file?

Not really.

> I had a year’s worth of bz2 files which I deleted but
> that didn’t help. I found I had a lot of mysql logs which I deleted and
> that seemed to help for about 20 minutes.

You are doing something wrong, which try to solve a problem using the
software that is causing the problem. You can not try to solve this while
logged in graphical mode!

Denver told you to log in runlevel 3 → means text mode only.

Log out, press ctrl-alt-f1, log there (text) as root (yes, root), and work.
First command: “init 3”. Or, if booting, type “3” on the grub prompt, wait,
and login.

> I also get an authentication error when my screen locks and I try
> unlocking it. The error is “Cannot unlock the session because the
> authentication system failed to work, you must kill the kscreenlocker
> (pid 11.363) manually.” The only way out is to ctrl-alt-backspace, after
> which I can no longer log in to the desktop. The screen just goes blank

All those errors are irrelevant. Your main problem is a full or almost full
disk: solve that first. In text mode.

In text mode, type “mc”, which is a file text browser called Midnight
Commander", imitating the old MsDos Norton Commander, a wonderful for the
linux administrator.

Code:

Left File Command Options Right
┌<─ ~ ──────────────────────────v>┐┌<─ ~ ──────────────────────────v>┐
│ Name │ Size │ MTime ││ Name │ Size │ MTime │
│/… │P–DIR│ ▴│/… │P–DIR│ ▴
│/.AbiSuite │ 72│Jul 9 2009 ◈│/.AbiSuite │ 72│Jul 9 2009 ◈
│/.Sear~escue│ 67│Oct 18 2006 ▒│/.Sear~escue│ 67│Oct 18 2006 ▒
│/.Skype │ 89│Nov 6 2007 ▒│/.Skype │ 89│Nov 6 2007 ▒
│/.acrobat │ 18│Oct 18 2006 ▒│/.acrobat │ 18│Oct 18 2006 ▒
│/.adobe │ 87│Jan 31 2010 ▒│/.adobe │ 87│Jan 31 2010 ▒
│/.alsaplayer│ 40│Oct 18 2006 ▒│/.alsaplayer│ 40│Oct 18 2006 ▒
│/.animail │ 61│Oct 18 2006 ▒│/.animail │ 61│Oct 18 2006 ▒
├─────────────────────────────────▾├─────────────────────────────────▾
│/… ││/… │
└─────────────────────────────────┘└─────────────────────────────────┘
Hint: Tab changes your current panel.
cer@Telcontar:~> ^]
1Help 2Menu 3View 4Edit 5Copy 6RenMov 7Mkdir 8Delete

One of the functions it has is in the command menu the entry “show
directory sIzes”. Navigate first to the root directory (/) and do it.

Code:

Left File Command Options Right
┌<─ ~ ────────────┌───────────────────────────────┐────────────────v>┐
│ Name │ Siz│ Directory tree │ize │ MTime │
│/… │P–D│ Find file M-? │-DIR│ ▴
│/.AbiSuite │ │ sWap panels C-u │ 72│Jul 9 2009 ◈
│/.Sear~escue│ │ switch Panels on/off C-o │ 67│Oct 18 2006 ▒
│/.Skype │ │ Compare directories C-x d │ 89│Nov 6 2007 ▒
│/.acrobat │ │ eXternal panelize C-x ! │ 18│Oct 18 2006 ▒
│/.adobe │ │ show directory sIzes │ 87│Jan 31 2010 ▒
│/.alsaplayer│ │ ───────────────────────────── │ 40│Oct 18 2006 ▒
│/.animail │ │ command History │ 61│Oct 18 2006 ▒
├─────────────────│ diRectory hotlist C-\ │──────────────────▾
│/… │ Active VFS list C-x a │ │
└─────────────────│ Background jobs C-x j │──────────────────┘
Hint: Tab changes │ ───────────────────────────── │
cer@Telcontar:~> │ Undelete files (ext2fs only) │ ^]
1Help 2Menu 3V│ ───────────────────────────── │dir 8Delete

Once it shows you the directory sizes (it takes a lonoooong time) you
should see one that is TOO big. Enter it, and repeat the procedure, till
you find which directory is filling with files so big that leave you
without breathing space.

Before deleting the file, investigate a bit. The key “F3” displays the
file, if it is a log it will have thousand of similar entries. Copy them
and tell us.

There is a text editor in mc (F4). You can also copy-paste from one
terminal to another terminal, using the mouse (in text mode, yes). For this
you need first to start the service “gpm”, and for this you need to tell it
which mouse to use in the file “/etc/sysconfig/mouse” - I have:

MOUSEDEVICE="/dev/mouse"
MOUSETYPE=“exps2”

You can learn the mouse type from X config.

XMOUSETYPE=“imps/2”


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

Here is the output.

Filesystem    Type    Size  Used Avail Use% Mounted on
/dev/sda5     ext4     20G   17G  2.5G  87% /
udev         tmpfs    1.5G  296K  1.5G   1% /dev
/dev/sda7     ext4     45G  9.2G   33G  22% /VAULT
/dev/sda1  fuseblk     40G   13G   27G  33% /windows/C
/dev/sda6     ext4     34G   14G   19G  43% /home
/dev/sda9     ext4     99G   32G   63G  34% /Repos
/dev/sda10    ext4     50G   42G  5.3G  89% /VirtualBoxVM
192.168.1.11:/DATA_I
               nfs     55G   26G   26G  51% /mnt/Data_I
192.168.1.11:/DATA_II
               nfs     47G   21G   24G  48% /mnt/Data_II
192.168.1.11:/media/LacieMedia
               nfs     20G   12G  7.3G  62% /mnt/LacieMedia
192.168.1.11:/media/LacieBackup
               nfs    230G  121G   98G  56% /mnt/LacieBackup

@caf: The reason I tried to start dolphin as root was because it only showed an empty window with the "“The process for the file protocol died unexpectedly.” message when starting as the normal user so I wanted to see if the same happened when I tried as su.

@robin_listas: Thanks for the suggestions. I’ll try work through them and report back. Incidentally, I was logged in on runlevel 3 when I deleted the log files. My main problem is lack of command line knowledge and I don’t have another PC to refer to in parrallel when working in runlevel 3. So it’s very slow trying to do things at the cli with very limited knowledge of the commands. I keep having to boot back into the DE to look up commands.

Any way I’ll try MC and what you suggest and hopefully I’ll find the culprit.

I build with 20GB for /
But I never fill more than half. I’m not sure of your situation as it stands, but I assume it should be OK. Unless others think differently.

Have you been filling your trash can, either in /home or (less likely but in / )?

One thing you could do (if system stable long enough) is install irssi chat program. Then if in run level 3 and you need help, go to IRC channel #suse and ask for help. I think the command to launch irrsi once in run level 3 (with software installed) is:

irssi -c irc.freenode.net

or

irssi /connect irc.freenode.net

I’m not at a linux pc right now so I can not test that.

Also, once logged on to go to #suse simply type:

 /join #suse 

Do NOT try to join IRC chat with root permissions. ONLY do so as a regular user.

Typically there are knowledgeable people on IRC chat who can provide command line suggestions.

@caf: Yes, my root is also 20GB. I’m not aware of my trash being filledt as I usually do a shift-delete so it doesn’t delete to the trash can.

@oldcpu: Thanks for that. It’ll be useful as my system seems to be coming less stable the more times it gets rebooted. I can no longer log into the DE, even after deleting the tmp folder contents so I’ve bumped someone off their PC (persuaded them to go for a coffee) to type this.

You may also find a liveCD that allows you to easily access your system and the internet useful, one example isPartedMagic

From post #7 I see, for example,

Code:

Left File Command Options Right
┌<─ ~ ──────────────────────────v>┐┌<─ ~ ──────────────────────────v>┐
│ Name │ Size │ MTime ││ Name │ Size │ MTime │
│/… │P–DIR│ ▴│/… │P–DIR│ ▴
│/.AbiSuite │ 72│Jul 9 2009 ◈│/.AbiSuite │ 72│Jul 9 2009 ◈
│/.Sear~escue│ 67│Oct 18 2006 ▒│/.Sear~escue│ 67│Oct 18 2006 ▒
│/.Skype │ 89│Nov 6 2007 ▒│/.Skype │ 89│Nov 6 2007 ▒
│/.acrobat │ 18│Oct 18 2006 ▒│/.acrobat │ 18│Oct 18 2006 ▒
│/.adobe │ 87│Jan 31 2010 ▒│/.adobe │ 87│Jan 31 2010 ▒
│/.alsaplayer│ 40│Oct 18 2006 ▒│/.alsaplayer│ 40│Oct 18 2006 ▒
│/.animail │ 61│Oct 18 2006 ▒│/.animail │ 61│Oct 18 2006 ▒
├─────────────────────────────────▾├─────────────────────────────────▾
│/… ││/… │
└─────────────────────────────────┘└─────────────────────────────────┘
Hint: Tab changes your current panel.
cer@Telcontar:~> ^]
1Help 2Menu 3View 4Edit 5Copy 6RenMov 7Mkdir 8Delete

What?

On 2011-01-05 08:36, dvhenry wrote:
>
> From post #7 I see, for example,

>> What?

What “what”?


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

On 2011-01-04 16:06, suse tpx60s wrote:
>
> oldcpu;2273537 Wrote:
>> There are so many messages with “No space left on device” … it does
>> appear to be that we are being told something.
>>
>> Still, can you humour us, and provide/post the output of:
>>
>>>
> Code:
> --------------------
> > > df -Th
> --------------------
>>>
> Here is the output.
>
> Code:
> --------------------
> Filesystem Type Size Used Avail Use% Mounted on
> /dev/sda5 ext4 20G 17G 2.5G 87% /
> udev tmpfs 1.5G 296K 1.5G 1% /dev
> /dev/sda7 ext4 45G 9.2G 33G 22% /VAULT
> /dev/sda1 fuseblk 40G 13G 27G 33% /windows/C
> /dev/sda6 ext4 34G 14G 19G 43% /home
> /dev/sda9 ext4 99G 32G 63G 34% /Repos
> /dev/sda10 ext4 50G 42G 5.3G 89% /VirtualBoxVM
> 192.168.1.11:/DATA_I
> nfs 55G 26G 26G 51% /mnt/Data_I
> 192.168.1.11:/DATA_II
> nfs 47G 21G 24G 48% /mnt/Data_II
> 192.168.1.11:/media/LacieMedia
> nfs 20G 12G 7.3G 62% /mnt/LacieMedia
> 192.168.1.11:/media/LacieBackup
> nfs 230G 121G 98G 56% /mnt/LacieBackup
>
> --------------------

I fail to see any full enough partition - unless this is after the remove
operation.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

@Carlos
I’m doing this from a Gparted live CD as I can no longer do anything from openSUSE, even in init 3! I don’t have mc installed and wasn’t able to install with zypper either as it just got out of space errors - this was while in runlevel 3.

So, booting with gparted, I ran mc and looked at the directory sizes but nothing appears overly large or out of the ordinary.

The largest directories (excluding my non system directories) are /lib (112709K), /var (385176K) and /usr (5858M).
/usr has three large directories: /lib (155758K), /bin (90887K) and /share (51945K)
/var has two large directories: /lib (25234K) and /db (18576K)
/lib only has one large directory: /modules (53444K)

In all three cases above, none of those appear excesively large and drilling down doesn’t highlight a single extraordinarily large directory or file.

I don’t know where to go from here as my system is pretty much unusable and even in runlevel 3 many commands won’t execute due to the lack of disk space error.

I’m not sure if disk space is the actual cause of my problems. Can it be a corrupted configuration file or environment setting causing this?

OK, maybe some progress. After some googling I found that I may have run out of inodes on the root filesystem. Running df -i. Note that I’m running this from a live CD so only the two /dev/… filesystems are relevant here.
gives:

root@sysresccd /root % df -i
Filesystem            Inodes   IUsed   IFree IUse% Mounted on
tmpfs                 213896     349  213547    1% /
/dev/sr0                   0       0       0    -  /mnt/cdrom
/dev/loop0             54320   54320       0  100% /mnt/livecd
tmpfs                 213896     349  213547    1% /mnt/memory
udev                  213896    3237  210659    2% /dev
tmpfs                 213896      92  213804    1% /lib/firmware
/dev/sda5            1310720 1310686      34  100% /mnt/myroot-sda5
/dev/sda7            2921280  151174 2770106    6% /mnt/myvault-sda7

As we can see /dev/sda5 has used all it’s inodes. Now the question is what can I do to fix this? I haven’t really been able to find a clear solution that doesn’t confuse me even more. Can anyone help or suggest a way to increase the inode count?

On 2011-01-05 12:06, suse tpx60s wrote:
> I don’t know where to go from here as my system is pretty much unusable
> and even in runlevel 3 many commands won’t execute due to the lack of
> disk space error.

Type “df -h” in your real system (not the live cd). There must be something
that is full.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

I already did that in post#8

Filesystem    Type    Size  Used Avail Use% Mounted on
/dev/sda5     ext4     20G   17G  2.5G  87% /
udev         tmpfs    1.5G  296K  1.5G   1% /dev
/dev/sda7     ext4     45G  9.2G   33G  22% /VAULT
/dev/sda1  fuseblk     40G   13G   27G  33% /windows/C
/dev/sda6     ext4     34G   14G   19G  43% /home
/dev/sda9     ext4     99G   32G   63G  34% /Repos
/dev/sda10    ext4     50G   42G  5.3G  89% /VirtualBoxVM
192.168.1.11:/DATA_I
               nfs     55G   26G   26G  51% /mnt/Data_I
192.168.1.11:/DATA_II
               nfs     47G   21G   24G  48% /mnt/Data_II
192.168.1.11:/media/LacieMedia
               nfs     20G   12G  7.3G  62% /mnt/LacieMedia
192.168.1.11:/media/LacieBackup
               nfs    230G  121G   98G  56% /mnt/LacieBackup

Did you see my post above where I found that it may be a problem with running out of inodes on the / filesystem? I think that is the cause as it shows 100% used for /ddev/sda5 (my / filesystem). I just can’t see how to correct this without having to receate the filesystem.