From owner-freebsd-questions  Thu Jan 30 09:39:13 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA21389
          for questions-outgoing; Thu, 30 Jan 1997 09:39:13 -0800 (PST)
Received: from post-ofc01.srv.cis.pitt.edu (root@post-ofc01.srv.cis.pitt.edu [136.142.185.25])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA21384
          for <freebsd-questions@freebsd.org>; Thu, 30 Jan 1997 09:39:10 -0800 (PST)
Received: from local (root@localhost)
          by post-ofc01.srv.cis.pitt.edu (8.8.5/cispo-2.0.1.7)
          ID <MAA13967@post-ofc01.srv.cis.pitt.edu> for freebsd-questions@freebsd.org;
          Thu, 30 Jan 1997 12:39:06 -0500 (EST)
Received: via switchmail; Thu, 30 Jan 1997 12:39:06 -0500 (EST)
Received: from unixs-eval.cis.pitt.edu via qmail
          ID </afs/pitt.edu/service/mailqs/q1/QF.MmwBmh:8XfYH025kM0>;
          Thu, 30 Jan 1997 12:38:55 -0500 (EST)
Received: from unixs-eval.cis.pitt.edu via qmail
          ID </afs/pitt.edu/usr5/jlfox/.Outgoing/QF.omwBmfu8XfYH0=lVA0>;
          Thu, 30 Jan 1997 12:38:52 -0500 (EST)
Received: from VUI.Andrew.3.70.CUILIB.3.45.SNAP.NOT.LINKED.unixs.eval.cis.pitt.edu.sun4m.54
          via MS.5.6.unixs-eval.cis.pitt.edu.sun4_51;
          Thu, 30 Jan 1997 12:38:51 -0500 (EST)
Message-ID: <UmwBmfa8XfYH0=lV00@pitt.edu>
Date: Thu, 30 Jan 1997 12:38:51 -0500 (EST)
From: James Fox <jlfox+@pitt.edu>
To: freebsd-questions@freebsd.org
Subject: MAKEDEV and boot problems
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


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

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