From owner-freebsd-questions  Thu Jan 30 11:22:44 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA25988
          for questions-outgoing; Thu, 30 Jan 1997 11:22:44 -0800 (PST)
Received: from vegemite.Stanford.EDU (vegemite.Stanford.EDU [171.65.76.158])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA25983
          for <freebsd-questions@freebsd.org>; Thu, 30 Jan 1997 11:22:42 -0800 (PST)
Received: (hlew@localhost) by vegemite.Stanford.EDU (8.7.1/8.6.4) id LAA11449; Thu, 30 Jan 1997 11:22:26 -0800 (PST)
Date: Thu, 30 Jan 1997 11:22:25 -0800 (PST)
From: Howard Lew <hlew@sequence.Stanford.EDU>
To: James Fox <jlfox+@pitt.edu>
cc: freebsd-questions@freebsd.org
Subject: Re: MAKEDEV and boot problems
In-Reply-To: <UmwBmfa8XfYH0=lV00@pitt.edu>
Message-ID: <Pine.SUN.3.91.970130112113.11423A-100000@vegemite.Stanford.EDU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 30 Jan 1997, James Fox wrote:

> 
> Should have left "well enough alone", but I didn't.
> I have been running 2.1.0 troublefree for months and
> wanted to get it to recognize my soundblaster card.
> Apparently, I should have merely done "MAKEDEV snd0",
> but I decided to build a new kernel in the process
> to tidy things up. Following chapter 10 in Inst &
> Running FreeBSD I got confused at the MAKEDEV section
> and did a "MAKEDEV all", which I think I will regret.
> I wasn't worried when I rebooted to try the new
> kernel since the book says "don't panic" if your
> new kernel doesn't work, just reboot with kernel.old.
> Well, here's what I'm getting... (I'm booting from
> drive 1 of an Ultrastor SCCSI controller)
> 
> /dev/sd1s1b  no such file or directory
> ..
> /dev/sd1s1f  no such file or directory
> 

I think the fix here is to just use the MAKEDEV to make those files in
/dev when it drops you to a shell.  Then halt and reboot and all should be
fine. 


> Can't stat /dev/sd1s1f
> Automatic file system check failed!
> 
> Unfortunately, this state puts me into a  read-only
> file system, from which I can't even see
> /usr/src/sys/i386/conf/MYKERNEL and wouldn't be able to
> fix it anyway. kernel.old produces the same results.
> 
> Why is the system looking for sd1s1b and sd1s1f ?
> What did I do wrong and most importantly, what do
> I do now?  :-(
> 
> Thanks,
> --Jim Fox
> 
> 
> 


----

|| Shoppers Network              BEST PRICES, FULLY x86 COMPATIBLE & FAST!!!
|| PO BOX 16627                  Cyrix 686s now available!
|| San Francisco, CA  94116      Email - info@shoppersnet.com
| ------------------------------> WWW - http://www2.shoppersnet.com
 -------------------------------> WWW - http://www.shoppersnet.com/shopping