Comments on: Can I run fsck or e2fsck when Linux file system is mounted?

By: jim

jim — Mon, 07 Nov 2011 16:47:28 +0000

@ lekensteyn
umount is the original command. some systems have an alias called unmount, but it calls umount

By: aaron

aaron — Tue, 06 Sep 2011 12:55:10 +0000

That actually sounds insane and Linux fsck is much more consistent and accurate and advanced than windows scandisk. As well is the linux file system (choose one but default to ext3/4 to be normal) itself which is light years ahead of the trash called ntfs.

By: Keilaron

Keilaron — Wed, 29 Jun 2011 01:51:02 +0000

Those keyboard lights going on/off indicate what’s referred to as a “Kernel oops” – equivalent to a Windows bluescreen. Try to get a log somehow – maybe (maybe) another VT is enabled at that time, and you could e.g. hit alt-f8 to switch to it and get more verbose information. Or maybe use interactive mode. I don’t remember if CentOS has that.
Like the others have suggested, try booting another system; A liveCD of CentOS if you can.. you might get more information. Maybe the drive is corrupt or your /etc/fstab is incorrect.

By: H5n1

H5n1 — Sat, 12 Mar 2011 09:59:21 +0000

Try to start you PC with a live distro: if it works it’s a system issue, if it doesn’t it’s an hardware issue.

By: jewy

jewy — Fri, 11 Mar 2011 20:50:58 +0000

that bug only in centos? maybe any stick key on you keybord?

By: Khalid Zaidi

Khalid Zaidi — Fri, 04 Mar 2011 10:59:16 +0000

when i start the computer Centos (2.6.18-53.1.19.e15) boot normally and hang up after
Mounting local filesystems: [ OK ]
Enabling local filesystems: [ OK ]
and cursor jam and keyboard lights on/off contineously

please resolve my problem

Khalid Zaidi

By: LordAzuzu

LordAzuzu — Mon, 31 Jan 2011 13:12:03 +0000

You are ridiculous, MORON!

By: Lekensteyn

Lekensteyn — Sat, 27 Nov 2010 21:27:59 +0000

Unmout (2x)? I’t really should be unmount!

By: H5N1

H5N1 — Sat, 02 Oct 2010 08:48:08 +0000

@akrum:
1 – The real difference beween Linux and Windows is in troubleshooting: Windows = reboot | Linux = be root
2 – Even in Windows you can have a Damaged System Disk after checking the disk for errors but Microsoft had never told you
3 – Why THE F**K you think that if you want to correct sectors and FS errors you have to reboot in Windows and run chckdsk at boot-time? Obviously: you can’t do that on a mounted filesystem – just like in Linux!
4 – Take the HD off the machine and mount it on a Windows System will notice that Windows cannot recognize the ext2/3/4 or any other Linux FileSystem. Strange, because almost any Linux System can recognize any Windows FS…
5 – Make sure you have your brain set to “ON” before posting on any Web place…

By: Paulo

Paulo — Mon, 24 May 2010 16:17:42 +0000

@Akrum
what the fsck… are you on drugs?

By: Dave

Dave — Thu, 24 Sep 2009 17:28:13 +0000

@akrum This will actually not work at all. Windows scandisk will not recognize a Linux filesystem. What you are describing is actually the least safe option. Good luck with that.

By: akrum

akrum — Tue, 22 Sep 2009 06:47:24 +0000

this is the difference between windows and linux! too many steps to do a very simple task like scandisk, and also i bear the risk of having my data corrupted because of a scanddisk under linux OMG!
the best thing i’ll do is to take the HD off the machine, scand disk it under windows and back again into the linux machine!

medieval but sounds much safer!

By: source

source — Tue, 16 Jun 2009 14:47:17 +0000

This worked great. I was able to rescue a downed system.

By: Victor Vitayaudom

Victor Vitayaudom — Wed, 25 Mar 2009 21:22:20 +0000

No …

read http://linux.die.net/man/8/fsck and suggest flag -n if mounted

For some filesystem-specific checkers, the -n option will cause the fs-specific fsck to avoid attempting to repair any problems, but simply report such problems to stdout. This is however not true for all filesystem-specific checkers. In particular, fsck.reiserfs(8) will not report any corruption if given this option. fsck.minix(8) does not support the -n option at all.

By: thewordsmith

thewordsmith — Wed, 13 Aug 2008 17:24:42 +0000

That advise above worked great. But I used to be able to rub “shutdown -rF 0″ to force fsck to run on reboot. But as of Fedora 9 on my i686 32 bit system the -F option is missing. Is there any way to get that option back in the shutdown menue?

By: Yaw

Yaw — Tue, 02 Oct 2007 14:38:30 +0000

l will like to know the big difference between fsck and e2fsck commands.