From owner-freebsd-current  Thu Jan  2 02:26:08 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id CAA27123
          for current-outgoing; Thu, 2 Jan 1997 02:26:08 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA27118;
          Thu, 2 Jan 1997 02:26:00 -0800 (PST)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id CAA13738; Thu, 2 Jan 1997 02:25:58 -0800 (PST)
To: current@freebsd.org
cc: joerg@freebsd.org
Subject: Did my floppy drive just break or does fdformat no longer work?
Date: Thu, 02 Jan 1997 02:25:58 -0800
Message-ID: <13734.852200758@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Running a kernel built as of this morning from -current, I can no longer
format floppies - I get a cascade of kernel warning messages:

jkh@time-> fd0c: hard error reading fsbn 18 of 16-19 (ST0 44<abnrml,top_head> ST1 4<sec_not_fnd> ST2 0 cyl 0 hd 1 sec 1)
fd0c: hard error reading fsbn 18 of 16-19 (ST0 44<abnrml,top_head> ST1 4<sec_not_fnd> ST2 0 cyl 0 hd 1 sec 1)
...

And so on.  I can take the exact same floppy over to my 2.1.6 box and
format it there, so I'm positive it's not a bad floppy (that's what I
first thought too until the 10th one I tried proved "bad" and I
started doing some comparison testing).

This could the floppy driver, it could be something it depends on,
I dunno!

					Jordan