*BSD News Article 31780


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!constellation!convex!news.oc.com!news.kei.com!MathWorks.Com!europa.eng.gtefsd.com!howland.reston.ans.net!math.ohio-state.edu!jussieu.fr!univ-lyon1.fr!ensta!bsdtest.ensta.fr!bouyer
From: bouyer@bsdtest.ensta.fr (Manuel Bouyer)
Newsgroups: comp.os.386bsd.misc
Subject: Re: fsck freezing netBSD on boot
Date: 16 Jun 1994 20:19:16 GMT
Organization: Ecole Nationale Superieure de Techniques Avancees, Paris
Lines: 36
Distribution: world
Message-ID: <2tqc44$5bq@ici-paris.ensta.fr>
References: <9406162003.AA15779@dsif.fee.unicamp.br>
NNTP-Posting-Host: bsdtest.ensta.fr

In article <9406162003.AA15779@dsif.fee.unicamp.br>, Renato@dsif.fee.unicamp.br writes:
|> Hi there,
|> 
|>   I've recently installed NetBSD on my computer; everything is OK, except for
|> the fsck -p call in /etc/rc. It just freezes the machine at boot time.
|>   I had to remove this call from /etc/rc, and without it the boot goes on
|> normally.
|>   If I issue fsck after the whole boot stuff, it works fine.
|>   I have two IDE HDs (43Mb and 270Mb), both having NetBSD and DOS partitions.
|>   Any clue???
|> 
|>   Oh, another info that might be helpful; I always receive the message:
|> 	wd0c : extra interrupt       (or something very close to that)
|>   also at boot time.
|>   I guess there's something related between this message and the freezing fsck.
|>   Well, it's just a guess. I can't figure out what's going on.
|>   Thanks in advance for any hint.

I think that the probleme comes from the 2 ide drives. I think that the solution
is to recompile a kernel configured whith swap on both ide drives (in your
config file:
config      netbsd  root on wd0 swap on wd0 and wd1
)
You don't need to have swap installed on both drives, it just have to 
be configured.
This is to have the kernel acces the kernel acces the second ide drive
and load the disklabel before the fsck. This is also done when you do a
'mount -a', that is the reason why fsck works after the boot completes.

I didn't try this myself, i just remember having read this in the news.
Perhaps there is more details on the faqs.

--
Manuel Bouyer, Ecole Nationale Superieure de Techniques Avancees, Paris
email: bouyer@ensta.fr
--