Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!MathWorks.Com!solaris.cc.vt.edu!csugrad.cs.vt.edu!not-for-mail
From: jaitken@csugrad.cs.vt.edu (Jeff Aitken)
Newsgroups: comp.os.386bsd.questions
Subject: FreeBSD 1.1 installation problem
Date: 12 Jul 1994 01:35:14 -0400
Organization: Virginia Tech Computer Science Dept, Blacksburg, VA
Lines: 30
Message-ID: <2vta2i$2d0@csugrad.cs.vt.edu>
Reply-To: jaitken@vt.edu
NNTP-Posting-Host: csugrad.cs.vt.edu
X-Newsreader: TIN [version 1.2 PL2]
I have a 486/dx2 66, PCI/ISA. Western Digital "Paradise" video card,
Western Digital wd8003e ethernet (0x280, irq5, 0xd800), a PCI IDE
controller handling 2 conner drives. One drive (C:) is 170MB and
contains dos/windows. Drive d: is 420MB (brand new today - yeah!) and
to be used entirely for freebsd. I boot the kcopy_ah.flp, which appears
to go OK. However, when I insert the filesyst.flp diskette, it goes
through it's sequence of searchine for hardware, then spits out
something about wd0 not being labeled, then about a problem with fd0.
It then says something to the effect of "can't mount root", declares
that it's in a "panic", and tells me I must reboot. Something tells me
this isn't normal. I realize the errors I've given are not too
descriptive, but I don't have them right in front of me. But I was
hoping someone will say "oh yeah, that's easy to fix" and then proceed
to enlighten me.
Off the top of my head, it looks like something with fd0 is hosed. It
says something about "operation timeout" once or twice, then a different
error regarding fd0d, then the panic stuff and reboot.
Thanks for any assistance - please email any siggestions. if I solve
the problem, I will be more than happy to post what went wrong and why,
along with how to fix it.
Oh yeah, the disk is *not* write protected ;)
--
Jeff Aitken jaitken@vt.edu
A witty saying proves nothing, but saying something stupid gets
peoples' attention