From owner-freebsd-questions  Thu Apr 27 23:33:22 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id XAA00925
          for questions-outgoing; Thu, 27 Apr 1995 23:33:22 -0700
Received: from hda.com (hda.com [199.232.40.182])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA00919
          for <questions@FreeBSD.org>; Thu, 27 Apr 1995 23:33:18 -0700
Received: (dufault@localhost) by hda.com (8.6.9/8.3) id CAA07364; Fri, 28 Apr 1995 02:31:46 -0400
From: Peter Dufault <dufault@hda.com>
Message-Id: <199504280631.CAA07364@hda.com>
Subject: Re: fd0c: hard error reading fsbn 16 0f 16-31
To: terry@cs.weber.edu (Terry Lambert)
Date: Fri, 28 Apr 1995 02:31:45 -0400 (EDT)
Cc: procecorjb@Vir.com, questions@FreeBSD.org
In-Reply-To: <9504280138.AA18160@cs.weber.edu> from "Terry Lambert" at Apr 27, 95 07:38:11 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 1689      
Sender: questions-owner@FreeBSD.org
Precedence: bulk

Terry Lambert writes:
> 
> > ++++++++++++++++
> > fd0c: hard error reading fsbn 16 0f 16-31 (ST0 40<abmrnl> ST1<no_am> ST2 0
> > cyl 0 hd sec 17)
> > panic:cannot mount root
> > 
> > syncing disks... done
> > Automatic reboot in 15 sec etc........
> > +++++++++++++++++
> > 
> > I'm thought my hd and cd were supported.
> > I've got,
> > buslogic bt-946c Fast SCSI PCI controller
> > 1.06 Gb drive SCSI
> > 4x cd SCSI 
> > 3-1/4 1.44Mb Floppy
>         ^^^^^^
> 	**MAKE SURE YOUR BIOS SETUP KNOWS THIS!!!**
> 
> > 
> > What can be the problem????
> 
> Otherwise your floppy has a bad block on it.  You need to reformat it,
> and if that doesn't fix it, use a new floppy.
> 
> fd0c = floppy disk slice 'c'
> fsbn = file system block number.
> 
> I can't decode the status words returned by the floppy controller
> without books or code in front of me.  Maybe someone will elaborate
> on exactly what your floppy controller doesn't like about your
> floppy, since I can't figure out what "abmrnl" is supposed to be an
> abbreviation for.

We did have the "2.0 boot floppy problem".  It would be helpful to
include a little more info.  We need to at least know exactly which
software you're booting (2.0R, snap version, etc.), and info such
as the motherboard manufacturer and BIOS manufacturer if you know
them.  The "boot floppy problem" was present at least in some Micronics
motherboards with Phoenix BIOS.

That problem is fixed in any of the snaps.  Try a different boot floppy,
and if it fixes it install the snap.

-- 
Peter Dufault               Real Time Machine Control and Simulation
HD Associates, Inc.         Voice: 508 433 6936
dufault@hda.com             Fax:   508 433 5267