LinuxQuestions.org - Filesystem check failed after full system update

- Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)

- - Filesystem check failed after full system update (https://www.linuxquestions.org/questions/linux-software-2/filesystem-check-failed-after-full-system-update-757083/)

Filesystem check failed after full system update

Hi,

Yesterday I did pacman -Syu (full system update, which involved updates of kernel, udev, e2fsprogs and hdparm) on my Arch linux box and after rebooting, had filesystem errors, like this:

Code:

The superblock could not be read or does not describe a correct ext4

filesystem. If the device is valid and it really contains an ext4

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

    e2fsck -b 8193 <device>



******************* FILESYSTEM CHECK FAILED *************

* Please repair manually and reboot. Note that the root *

* filesystem is currently mounted read-only. To remount *

* it read-write type: mount -n -o remount,rw /          *

* When you exit the mantenance shel the system will    *

* reboot automatically.                                *

*********************************************************



Give root password for mantenance

after pressing CTRL-D (automatic reboot) the fs was checked and the machine booted successfully...

Does this sound familiar to anyone? What is the reason for this?

Thanks a lot,
L.

Hi.

May be in reality file system is ext3, but not ext4?

Quote:

Originally Posted by nimnull22 (Post 3693620)

Hi.

May be in reality file system is ext3, but not ext4?

Well, all my FS are ext4 (which may not be a good idea for /var, but...)
It's just strange: the system boots fine, but from time to time these issues emerge. And, they are fixed automatically by fsck... So, I guess, it has to be a problem with timestamps, or such...

L.

Hi

"The superblock could not be read or does not describe a correct ext4 filesystem."

I wouldn't let it go like that. I suggest to read more about it, may be you can find some logs.
What "boot.msg" says about boot?
In linux nothing happens "from time to time".

I think I read somewhere that when when ext4 came out (and its still pretty new ie its not in RHEL/Centos), you couldn't use it for the boot partition, only other partitions. Don't know if that's still true.

Quote:

Originally Posted by chrism01 (Post 3694927)

I am currently using Ext4 for my /root and /boot partition(s) (which actually are the same on this particular installation) without troubles.

NOTE: This is Slack64 though, if it matters.

Hope this helps up there :)

Sasha

Quote:

Originally Posted by nimnull22 (Post 3694749)

I'm sorry for the stupid question, but where is it located? I don't have it in /var/log...

"I don't have it in /var/log..."

klogd 1.4.1, log source = ksyslog started. It says in first lines of my "boot.msg". I use Opensuse.
Look something started with "boot"

I don't know about Arch linux, but should be something logging boot process.
Look into documentation for Arch linux.

@Grapefruitgirl; ok, good. iirc, that was Fedora, when ext4 first came out.
Maybe its fine now.