From owner-freebsd-current  Tue Jan 28 09:10:58 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA24233
          for current-outgoing; Tue, 28 Jan 1997 09:10:58 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA24224;
          Tue, 28 Jan 1997 09:10:50 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id EAA30531; Wed, 29 Jan 1997 04:06:16 +1100
Date: Wed, 29 Jan 1997 04:06:16 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199701281706.EAA30531@godzilla.zeta.org.au>
To: current@freebsd.org, nate@mt.sri.com
Subject: Re: Disk errors with 2.2B
Cc: bde@freebsd.org
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>I just upgraded one of the disks in my dual-disk workstation to 2.2B
>(via CVS) from an old version of -current (June).
>
>The box (is running) 2.1.6.1 fine, and was running the older version of
>-current w/out problems until yesterday.
>
>Now, at bootup I get the following errrors:
>wd0s5c: hard error reading fsbn 1wd0: status 59<rdy,seekdone,drq,err> \
>	error 10<no_id>
>wd0s6c: hard error reading fsbn 1wd0: status 59<rdy,seekdone,drq,err> \
>	error 10<no_id>
>wd0s7c: hard error reading fsbn 1wd0: status 59<rdy,seekdone,drq,err> \
>	error 10<no_id>
>wd0s8c: hard error reading fsbn 1wd0: status 59<rdy,seekdone,drq,err> \
>	error 10<no_id>
>
>These devices don't exist in /dev, nor do I have anything in my
>partition table for these.  The disk has 3 'slices', DOS, Win95, and
>FreeBSD and no extended anything.

It probably does have an extended slice with garbage entries to get
those errors.  I don't think you can have 2 DOS/Win95 slices without
an extended slice.

Bruce