not cleanly unmounted check forced

christyc · 01-22-2002, 04:06 PM

I've been searching, all I can find is WHY Iget this, which I know.
(locked up, shut down with power button)
What I cannot find on 9 pages of google or searching here yet is what is the next step to getting OUT of it?

Thanks? Thanks.

karanc · 01-22-2002, 04:28 PM

Quote:

When and how to use the File System Check (fsck) utility.

The fsck command is used to check and repair inconsistencies in the file system. File system checks should be done in the following situations:
Whenever system has experienced a sudden or improper power off.
When booting the system this message is displayed: "Type Ctrl -d to proceed with normal startup, (or give root password for system maintenance)".
When unusual software behavior is observed.
When a df -k command does not display all of the expected partitions.
The following describes how to do a file system check. If the system is already at an OK prompt, proceed to step 3. If the "Ctrl-d" message described above is on the screen, go to step 4.

1. Open Terminal or Command Tool window and log in as the root user. Right-click on background, right-select Programs, right-select Terminal or Command Tool. Type: su <Enter>. Type root password when prompted and hit <Enter>. You will not see the characters on the screen as you type.

2. Type: sync;sync;halt <Enter>. The system will synchronize the file systems and come down to an ok prompt.

3. At ok prompt, type: boot -s <Enter>.
Note: -s boots up in single user mode -- this is advised because multipass processing could possibly delete files as users try to read or write their data.

4. The system will boot and display the following message: Type Ctrl -d to proceed with normal startup, (or give root password for system maintenance):

5. Type the root password and hit <Enter>. You will not see the characters appear as you type.

6. A # prompt displays. Type: fsck -y <Enter>.
Note: -y assumes a yes response to all questions asked by fsck.

7. There are five phases of fsck that will scroll on the screen for each partition. File system check is completed when it is back to the # prompt. Sometimes running it several times is helpful.

8. If "Cleanup Phase" statuses "filename FILE SYSTEM STATE NOT SET TO OKAY": Type: fsck -m <Enter> to determine if you should run fsck again. It will indicate if file(s) need checking.

9.) A # prompt displays. Type: sync;sync;halt <Enter>.

10.) When finished, type: boot <Enter>.

NOTE: When the "shutdown" command is not available in the Xerox software, the proper way to shut down the system is to follow steps 1 and 2 above. If the system is shut down in a more abrupt way (such as flipping the controller power switch), superblock information and data may be in transition, which will cause file system corruption or inconsistencies.

Scotty2435 · 01-22-2002, 04:59 PM

this is similar to Windows running scan disc after a bad shutdown

beep_beep · 08-22-2002, 12:42 AM

I have problem AFTER running fsck,
now every time my SuSE7.3 starts I see the:
"/dev/hda10 was not cleanly unmounted check forced",
evrything works fine after long time checking of /dev/hda10,
and I need a solution to UNMOUNT cleanly, to avoid messages and checking like this.

Note : During shotdown unmounting seems to be clean...

If somebody knows how to fix the problem, please send Your answer.
Thanks.

mrGee · 08-23-2002, 04:40 AM

Hi
check ;
http://www.tldp.org/HOWTO/Tips-HOWTO.html

2.10 How do I stop my system from fscking on each reboot? Dale Lutz,
2.11 How to avoid fscks caused by "device busy" at reboot time. Jon Tombs,
Maybe this leads to an answer, haven't tried it myself, just stumbled over it and recalled your questions on this.

good luck

Bert · 08-23-2002, 04:54 AM

I used to get this problem with Redhat 7.0.

The problem is actually with X Windows. AT the time, this was used as an argument to run X Windows as little as possible - which I still believe as it effectively more than doubles your system overhead in Linux and certainly used to be the weakest link in the distribution.

Another possibility is that a kernel module you are using is creating a resource lock. Check that your hardware drivers are up2date.

X Windows can and will lock up RH7.0 entirely. No Ctrl+Alt+Del, no switching to tty terminal mode, no nothing. Just you and the Big Red Switch. X Windows and the distro have improved. Don't go for 7.2, try 7.3 - it seems to be put together better, with less coupling between kernel modules.

Upgrade to 7.3 or use X Windows less.

Bert

beep_beep · 08-24-2002, 12:19 PM

mrGee, tank You for help! next time I'll chek your solution, but only next time, cause I performed reinstall.