Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!cs.utexas.edu!uunet!Germany.EU.net!netmbx.de!zrz.TU-Berlin.DE!cs.tu-berlin.de!klier
From: klier@cs.tu-berlin.de (Jan Klier)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: FreeBSD hangs o n boot!
Date: 22 Nov 1993 10:57:57 GMT
Organization: Technical University of Berlin, Germany
Lines: 35
Message-ID: <2cq5vl$ro6@news.cs.tu-berlin.de>
References: <matrix.753754654@noc> <2cpnl4$407@itu1.sun.ac.za>
NNTP-Posting-Host: jet.cs.tu-berlin.de
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
abs@cs.sun.ac.za (Andre Skarzynski) writes:
>Also, I found that the entries in the /etc/fstab are important. I have not got
>my machine near me so I can not check, but something like the following:
>/dev/wd0a / ufs rw 1 1
>/dev/wd0e /usr ufs rw 1 2
>/dev/wd1a /home ufs rw 1 2
>/dev/wd1e /u ufs rw 1 2
I just reported this to Jordan.
My system (2 IDE, 1 SCSI disk) hangs during the fsck when it boots,
apparently because of a timing problem when multiple checks are run
simultansously in the second pass. In this case the system just locks
up after entering the second pass of fsck.
Multiple checks are only done for partitions on different disks, so this
problem might only occur if you mount partitions from several disks within
the second pass (as it is the case with wd0e, wd1a or wd1e in the above
example).
A possible way to go around this problem is to edit the file /etc/rc and
change the line
fsck -p to fsck -p -l 1
which tells fsck to run only one check at a time. It takes a bit longer but
doesn't lock up the system. And it's only needed if the system isn't
shutdown with fastboot.
jan
--
*********** Freedom is inversely proportional to security ******************
Jan Klier Berlin, Germany
e-mail: klier@cs.tu-berlin.de cis : 100022,1700
| jklier@ipk.fhg.de | 100022.1700@compuserve.com