[Error] - var file system is not accessible

SUSE Linux Enterprise Server SLES Configure-Administer
1

Hi guys, after I reboot our SuSE server. I received the error

blogd: no message logging because /var file system is not accessible.

Below is the screenshot for details:

2

I’ve also tried to run the

fsck.ext3 -p -f /dev/sde1

Below is the result:

3

Hi
So I’m guessing /var is on it’s own partition and wasn’t checked
automatically, you need to run fsck on it, if that passes then a reboot
should bring things back up. Or have you changed the disk/partition /var
is on?

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.70-18.9-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

4

Thanks malcolmlewis. However, how can I do that? Also, please check this post #2 https://forums.suse.com/showthread.php?9607-Error-var-file-system-is-not-accessible&p=38414#post38414

You think that’s the problem? I’m so sorry, I too new for Linux.

5

Hi
Just run fsck no extension (sure it’s ext3?) What about the output from;

cat /etc/fstab

What preceded the need to reboot the server?

6

Hi malcolmlewis, here’s the result of the

cat /etc/fstab

Prior to the reboot. Our SuSE is getting slower/hang, also you may read my previous thread. https://forums.suse.com/showthread.php?9590-rootfs-used-100

7

Hi
So are you sure one of the scsi disks isn’t failing then… /dev/sde

The sdparm tool might provide info.

sdparm /dev/sde
8

[QUOTE=malcolmlewis;38416]Hi
So I’m guessing /var is on it’s own partition and wasn’t checked
automatically, you need to run fsck on it, if that passes then a reboot
should bring things back up. Or have you changed the disk/partition /var
is on?

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.70-18.9-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks![/QUOTE]

Thanks for the help malcolmlewis. It seems running the

fsck

fixed the issue. There’s a lot of error block that fixed.