Not Cleanly Unmounted


Forum: HD Install
Topic: Not Cleanly Unmounted
started by: Lobes06

Posted by Lobes06 on Aug. 31 2006,23:11
It seems like every other reboot of my system, I get the following:

/dev/hda1 was not cleanly unmounted, check forced.
Deleted inode 327743 has zero dtime. FIXED

And it tells me to run the following command:

mount -n -o remount,rw /

So I do, and reboot, and it boots up fine. It seems to happen almost every other boot/reboot. Any idea what this is, and better yet, any way to fix it?

I did a HD install (not frugal) on a Dell Dimension 450MHz.

Thank in advance!

Posted by ^thehatsrule^ on Sep. 01 2006,14:35
Basically the system had shutdown/rebooted without unmounting the hard drive - do you use the shutdown options in DSL?

Could also be a hardware/formatting/geometry problem.

Posted by Lobes06 on Sep. 01 2006,14:42
Quote (^thehatsrule^ @ Sep. 01 2006,10:35)
Basically the system had shutdown/rebooted without unmounting the hard drive - do you use the shutdown options in DSL?

Could also be a hardware/formatting/geometry problem.

I just right-click on the desktop, and choose "Reboot". So, whatever the default shutdown options are is what I use. Can you point me where to look for those?

I'm fairly confident the hardware is ok, but heck with a machine that old you never know.

Posted by ^thehatsrule^ on Sep. 01 2006,19:37
Yea, those are the options.

If you want to really have time and want to try it, you might want to (i.e. with cfdisk)0 delete all the partitions off your hard drive, recreate them, format to ext2, and then reinstall DSL.  It'll might be a pain, though, just to see if this your condition is permanent or not.

Posted by brianw on Sep. 03 2006,22:11
What version of DSL?
When you shutdown/reboot are there any messages on the screen saying something like:

can't umount ? trying ? instead

Instead of using the shutdown from the menu exit to the prompt and type

sudo shutdown -r now

and follow what is happening, expecially look for the errors above or any other errors reported.

Posted by Lobes06 on Sep. 03 2006,22:19
Quote (brianw @ Sep. 03 2006,18:11)
What version of DSL?
When you shutdown/reboot are there any messages on the screen saying something like:

can't umount ? trying ? instead

Instead of using the shutdown from the menu exit to the prompt and type

sudo shutdown -r now

and follow what is happening, expecially look for the errors above or any other errors reported.

Using DSL 3.0.1.

Yes! When shutting down, there IS a message stating something like:

can't umount / trying /dev/hda1 instead

What does that mean?

Posted by brianw on Sep. 04 2006,22:41
couple more questions:

When booting you see the "Running from HD ..." correct?

Did you get the same results manually calling shutdown?

What is the output of : sudo fdisk -l

Did you remove the frugal boot command from the boot line (not sure if this affects anything or not but I always remove it)?

I get this problem if I run the reboot or halt commands directly (what happens is the rmount -ro / command does not get run so it does not unmount properly).

Posted by Lobes06 on Sep. 05 2006,01:51
Here is everything I see on my boot:

Quote

INIT: version 2.78-knoppix booting
Running Linux Kernel 2.4.26
Running fom HD, checking filesystems...
Activating swap...
Checking root file system...
fsck 1.34-WIP (21-May-2003)
/dev/hda was not cleanly unmounted, check forced.
Deleted inode 327743 has zero dtime. FIXED.
/dev/hda1: ***** REBOOT LINUX *****
/dev/hda1: 11836/1753088 files (0.1% non-contiguous), 91685/3504170 blocks

fsck failed. Please repair manually and reboot. Please note
that the root file system is currently mounted read-only. To
remount it read-write:

  # mount -n -o remount,rw /

CONTROL-D will exit from this shell and REBOOT the system.


I get the same results when doing a reboot from the GUI or a shutdown as you advised from the command line. After typing in the command above, and reboot, it loads fine.

The output of sudo fdisk -l is as follows:

Quote

Desk /dev/hda: 14.4 GB, 14453268480 bytes
255 heads, 63 sectors/track, 1757 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

/dev/hda1   *    1    1745    14016681    83    Linux
/dev/hda2        1746 1757   96390          5     Extended
/dev/hda5        1746 1757   96358+       82    Linux Swap


Here is my boot line:

Quote

kernel /boot/linux24 root=/dev/hda1 quiet vga=791 noacpi noapm nodma noscsi frugal


I'll remove the frugal from there to see if it helps.

Posted by ^thehatsrule^ on Sep. 06 2006,20:50
The frugal line will just mount the partition that contains the dsl image as read-write, rather than read-only.

If you are only using that for the base image, it should be no problem for you to remove it!

Posted by brianw on Sep. 10 2006,01:04
Sorry for the delay in responding.  When you say that you run the command I am assuming you run the mount command is that correct?

Have you manually run the fsck command at the prompt before a reboot?

If you type fsck --help (use sudo in front if you are not currently root) you get a list of the options.  If you use -p or -y the process will be automatic (-p repairs automatically -y answers yes automatically each time a fix is required).

Posted by Lobes06 on Sep. 10 2006,01:37
Quote (brianw @ Sep. 09 2006,21:04)
Sorry for the delay in responding.  When you say that you run the command I am assuming you run the mount command is that correct?

Have you manually run the fsck command at the prompt before a reboot?

If you type fsck --help (use sudo in front if you are not currently root) you get a list of the options.  If you use -p or -y the process will be automatic (-p repairs automatically -y answers yes automatically each time a fix is required).

Here are the results from running fsck -v


fsck 1.34-WIP (21-May-2003)
e2fsck 1.34-WIP (21-May-2003)
/dev/hda1 is mounted.

WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)? yes

/dev/hda1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

11804 inodes used (0%)
    14 non-contiguous inodes (0.1%)
        #of inodes with ind/dind/tind blocks: 412/0/0
91514 blocks used (2%)
      0 bad blocks
      0 large files

5360 regular files
1018 directories
1489 character device files
3390 block device files
3 fifos
0 links
527 symbolic links (527 fast symbolic links)
8 sockets
--------
11795 files



I guess that means there were no errors? I guess I can just live with having to boot twice whenever I want to use it (or just not turn it off)! But it would be nice to at least know whats causing it...

Thanks again for your help, I sure do appreciate it.

Posted by mantorp on Sep. 25 2006,23:07
For what it's worth I also have the same problem, with the added bonus that if I use an id other than dsl that was setup at the install it won't shut down either.
Posted by mantorp on Sep. 25 2006,23:10
For what it's worth I also have the same problem, with the added bonus that if I use an id other than dsl that was setup at the install it won't shut down either.
Powered by Ikonboard 3.1.2a
Ikonboard © 2001 Jarvis Entertainment Group, Inc.