Arch Linux

Nixxx

Member

From: Poland

Registered: 2009-08-01

Posts: 85

Failsystem check failed

Hi all. I have a little question

My HDD looks like this:

sda1 windows
sda2 arch (ext4)
sda3 swap
sda4 Music,Movies etc. (ext4 )

To have this all mounted i'm adding to lines two my fstab

/dev/sda1 /mnt/windows ntfs-3g rw,user,auto 0 0
/dev/sda4 /mnt/media ext4 rw,user,auto 0 0

everything works perfectly until i want to force check of sda4 during the system startup. I'm adding

/dev/sda4 /mnt/media ext4 rw,user,auto 0 2

For a some time it works fine but after a few startups i have something like that:

Failsystem check faild, then an information with the command concerning remounting and read only mode. Of course system is booting to console but I'm unable to start any of the programs.

Replaceing 2 with 0 brings everything to normal and my KDE starts well.

Can someone know what's the reason of such a behavior? Should I skip the filechecking?

Last edited by Nixxx (2009-11-21 15:20:02)

.:B:.

Forum Fellow

Registered: 2006-11-26

Posts: 5,819

Website

Re: Failsystem check failed

You shouldn't skip filesystem checks, try using 1 instead of 2. Does the system report on which partition it chokes?

BTW - If you're comfortable with having stuff in /mnt that's fine, but the FHS directory is /media. /mnt is only meant for temporary stuff, but Slackware used/uses it to mount partitions (old habits die hard you know).

---

Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Nixxx

Member

From: Poland

Registered: 2009-08-01

Posts: 85

Re: Failsystem check failed

1. I've found something like that:
"pass-num Controls the order in which fsck checks the device/partition for errors at boot time. The root device should be 1. Other partitions should be 2, or 0 to disable checking." so it seems that setting 1 insted of 2 is not recommended.

2. Does it really metter whether i mount the file system to /mnt or /media? I'll try to change it as You suggested.

Nixxx

Member

From: Poland

Registered: 2009-08-01

Posts: 85

Re: Failsystem check failed

I've changed /mnt to /media and the problem seems to gone. It's to erly to say that the issue was fixed but since then I haven't got any problem with mounting on startup. fstab entry looks like this:

/dev/sda4 /media/media ext4 rw,user,auto 0 2

Last edited by Nixxx (2009-11-23 18:39:23)

Nixxx

Member

From: Poland

Registered: 2009-08-01

Posts: 85

Re: Failsystem check failed

Today the probem got back. "Filesystem check faild" appeared.  To fix the main partition i used "mount -n -o remount,rw /". But it doest't work with sda4. So I had to launched one of the live CD distros and edit fstab by replaceing 2 with 0 for skipping filechecking of sda4. After reebot again "Filesystem check faild" so I typed "mount -n -o remount,rw /" once more and after reoot the system finally start working. Any other suggestions why I'm experiencing such problems? Maybe i shoud skip filechecking also for "/" partition?. I'll be glad if someone could help. THNX

fphillips

Member

From: Austin, TX

Registered: 2009-01-24

Posts: 202

Re: Failsystem check failed

I thought maybe you needed to use 0,0 or 1,2 but I just tried 0,2 here and it worked too.

Can I see the output of these:

cat /proc/mounts

(as root) tune2fs -l /dev/sda[24] |grep -C2 check

Nixxx

Member

From: Poland

Registered: 2009-08-01

Posts: 85

Re: Failsystem check failed

I've totally skipped filesystem check now, so my fstab looks like this:

/dev/sda2 / ext4 defaults 0 0
/dev/sda3 swap swap defaults 0 0

/dev/sda1 /media/windows ntfs-3g rw,user,auto 0 0
/dev/sda4 /media/media ext4 rw,user,auto 0 0

cat /proc/mounts

rootfs / rootfs rw 0 0
/dev/root / ext4 rw,relatime,barrier=1,data=ordered 0 0
none /dev tmpfs rw,relatime,mode=755 0 0
none /proc proc rw,relatime 0 0
none /sys sysfs rw,relatime 0 0
none /dev/pts devpts rw,relatime,mode=600 0 0
none /dev/shm tmpfs rw,relatime 0 0
/dev/sda1 /media/windows fuseblk rw,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/sda4 /media/media ext4 rw,nosuid,nodev,noexec,relatime,barrier=1,data=ordered 0 0

tune2fs -l /dev/sda2 |grep -C2 check

Mount count:              3
Maximum mount count:      39
Last checked:             Sat Nov 28 23:59:07 2009
Check interval:           15552000 (6 months)
Next check after:         Fri May 28 00:59:07 2010
Lifetime writes:          13 GB
Reserved blocks uid:      0 (user root)

tune2fs -l /dev/sda4 |grep -C2 check

Mount count:              27
Maximum mount count:      39
Last checked:             Sat Nov 21 15:36:27 2009
Check interval:           15552000 (6 months)
Next check after:         Thu May 20 16:36:27 2010
Lifetime writes:          71 GB
Reserved blocks uid:      0 (user root)

Last edited by Nixxx (2009-11-29 09:33:39)

fphillips

Member

From: Austin, TX

Registered: 2009-01-24

Posts: 202

Re: Failsystem check failed

Thanks. So they are both mounting ext4,rw and sda4 has had a successful completion 8 days ago. The next step would be to try e2fsck on sda4 to try to repair or see what errors it gives.

You'll need to remount,ro sda4 first then probably e2fsck -p /dev/sda4, but see --help to be as cautious as you like first.

Nixxx

Member

From: Poland

Registered: 2009-08-01

Posts: 85

Re: Failsystem check failed

Thanks for help, all You've mentioned works fine. After e2fsck -p /dev/sda4 I can run the system with filechecking again BUT I'm rather looking for a contant solution of this problem and the origin of such inconvenience. I'm reinstalling the system approximately every 3 - 4 months so I barely doubt that the filesystem is corrupted. I'm also formatting the disk and creating partitions pretty often so I'm rejecting fragmentation issue. I don't also know anything about any bad sectors. Just wondering whether this is the Arch or my HDD issue? Is it connected maybe with the 2 operating systems on one HDD? It is so easy to edit fstab and set the skipping of filesystem check but why it's so difficult to skip it automaticly during the booting when something goes wrong instead of crashing the system? I'm sorry for my tone but it really drives me nuts and many times I had to spent a lot of time fixing same problem when he suddenly jumped out from nowhere....

Last edited by Nixxx (2009-11-30 14:34:41)

.:B:.

Forum Fellow

Registered: 2006-11-26

Posts: 5,819

Website

Re: Failsystem check failed

I assume this must be some quirk (maybe in the initscripts) that triggers the prompt. I installed a new kernel on my server yesterday evening and I got the same problem. Partitions were fine, forced file system checks would not find anything - at all.

I ended up gradually setting 0/1/2 for the filesystem check in fstab, and somehow it works without problems again. I'm puzzled though...

---

Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Nixxx

Member

From: Poland

Registered: 2009-08-01

Posts: 85

Re: Failsystem check failed

The problem does not exist when the boot process skips the filechecking at all ("0" is set in fstab in every bootable partition).  I have the same situation that suddenly system boots properly one time, the other it fails...