Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 14 Jun 2003 00:45:33 +0900
From:      "Luke Kearney" <lukek@meibin.net>
To:        "Bill Moran" <wmoran@potentialtech.com>, "Rohit" <rohitvis@rogers.com>
Cc:        questions@freebsd.org
Subject:   Re: Booting takes too long. Why? (/ was not properly dismounted)
Message-ID:  <002001c331c2$d35511d0$230aa8c0@MAGOME>
References:  <200306131011.47302.rohitvis@rogers.com><3EE9DCDB.20607@potentialtech.com> <200306131035.51185.rohitvis@rogers.com> <3EE9F138.4030200@potentialtech.com>

next in thread | previous in thread | raw e-mail | index | archive | help
could the shutdown binary be broken on your installations ? are you running
the same release on all machines installed from the same media ?

LukeK

----- Original Message -----
From: "Bill Moran" <wmoran@potentialtech.com>
To: "Rohit" <rohitvis@rogers.com>
Cc: <questions@freebsd.org>
Sent: Saturday, June 14, 2003 12:43 AM
Subject: Re: Booting takes too long. Why? (/ was not properly dismounted)


> Rohit wrote:
> > Here is the dmesg. However, I should tell you that this has been the
case with
> > all my FreeBSD boxes. I have two PC's running FreeBSD and a Compaq
laptop
> > running FreeBSd all have different types of harddrives.
> >
> > The main problem is that everytime I boot I get the message saying / was
not
> > dismounted properly and then it goes through and fixes all the drive
block
> > errors. (This is the case on all my computers)
>
> My mistake ... I misread your original post.
>
> > I shutdown using the shutdown -h now command
> > or reboot using reboot now
>
> How big is your / partition?  During the halt/reboot sequence, does it
give any
> errors?  Are all the buffers flushed?
>
> I'm grasping at straws here ... Is there some daemon running that takes
too long
> to shutdown or doesn't shutdown cleanly, thus preventing the system from
flushing
> all its buffers and marking the fs clean?
>
> One thing to try: manually stop all processes that you can, then issue
"sync" a
> few times, then (when disk activity has stopped) issue reboot.  See if /
is still
> dirty on reboot.
>
> Does fsck succeed during boot?  Possibly boot into single-usr mode and
issue
> "fsck -y" until the filesystems are all marked clean, then try your
standard
> method of rebooting and see if the / partition is now clean.
>
> Many guesses here.  Hopefully one of them will be helpful.
>
> --
> Bill Moran
> Potential Technologies
> http://www.potentialtech.com
>
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
"freebsd-questions-unsubscribe@freebsd.org"
>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002001c331c2$d35511d0$230aa8c0>