[xubuntu-users] tmp-filesystem unusabel

[Hans Schneidhofer]

hi,

I have to mention that the computer has been running without problems
for about 10 years. Haven't had any problems like this before. And now
3 days ago I made another Ubuntu update and should restart the
computer.
That's it with the /tmp directory - it could no longer be read.

Suddenly it was only possible to start in single mode. Therefore
neither users nor network are available. And in this single-user mode
there is, among other things, the command to choose from: journalctl-
xb.

I did that first.

After that I took the installation stick with Ubuntu and booted up with
this stick to get more out of it.

And here I then also carried out these two attempts with e2fsck ... .
Unfortunately so far without success.

I think, the hard drives are all mounted with UUID.
My guess is that the hard disk in question with the /tmp directory is
defective.

So now looked into the /etc/fstab:
#/tmp was on /dev/sdb5 during installation
UUID=10e7e940-3e80-4b09-8192-8d66bbabc2f3 /tmp   ext4  defaults  0  2

My System-RAM is 16 GByte, so I think, this should be enough to prevent
systemctl or fstab from causing random switching on mount.

But can this disc simply be exchanged?
I have already successfully replaced defective hard disks in other
directories such as /usr etc, but what about /tmp and /var directories
????

That was already my idea during the installation (ago this 10 years or
so), to put as many directories as possible on their own hard disks so
that it would be easier to replace individual directories later in the
event of defects.

Hope this makes it easier to help

bye hans

Am Samstag, den 06.08.2022, 08:20 +0200 schrieb Ralf Mardorf:
> On Fri, 05 Aug 2022 12:44:35 +0000, Hans Schneidhofer wrote:
> > journalctl -xb
> 
> Hi,
> 
> you can run this command without being able to start your install?
> How
> are you doing this? I would expect you need to read the journal by
> e.g.
> running a live Linux using the "strings"-command. What does the
> journal
> tell word-for-word?
> 
> > In my case I have it mounted on /dev/sdb5.
> 
> How is it mounted? By fstab? By UUID? Have you checked that the
> partition is still sdb5? It did not become e.g. sdc5?
> 
> > so far I've tried the following:
> > e2fsck -b 8193 /dev/sdb
> 
> From where did you try it? A live Linux? What is the reason for the
> alternative superblock option? What output do you get?
> 
> > Hope anybody can help here ?
> 
> One guess is, that your install expects that sdb5 is tmp and while
> sdb5
> does exist, it's perhaps a file system that can't be accessed for tmp
> usage. It might be that tmp is mounted by fstab using sdb5 for it's
> entry, instead of using an UUID. However, it's not granted that tmp
> is always sdb5, it might become sdc5, just because an USB stick is
> connected. IOW you might need to mount tmp by UUID or even better,
> unless you are low on memory mount tmp as tmpfs either by fstab or by
> systemctl.
> 
> Regards,
> Ralf
>