From owner-freebsd-current  Tue Sep  3 12:08:44 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id MAA19388
          for current-outgoing; Tue, 3 Sep 1996 12:08:44 -0700 (PDT)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA19379
          for <freebsd-current@freebsd.org>; Tue, 3 Sep 1996 12:08:40 -0700 (PDT)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA22742; Tue, 3 Sep 1996 12:07:10 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22) by whistle.com via smap (V1.3)
	id sma022740; Tue Sep  3 12:07:01 1996
Message-ID: <322C818E.167EB0E7@whistle.com>
Date: Tue, 03 Sep 1996 12:05:50 -0700
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: Developer <dev@fgate.flevel.co.uk>
CC: freebsd-current@freebsd.org
Subject: Re: HELP URGENT!!!
References: <Pine.BSI.3.93.960903183840.288A-100000@fgate.flevel.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Developer wrote:
> 
> Please can someone suggest what to do... our BSD 2.2 server crashed and
> when we re-booted we get this error as soon as fsck kicks in:-
> 
> Debugger("sd")
> Stopped at _Debugger+0x26: movb $0,_in_Debugger.116
> db>
> 
> If I then type cont I get:
> 
> Can't open /dev/rsd2a Device not configured.
> 
> In /var/log/messages there is this error:-
> 
> /kernel: sd2: Can't deal with 767 bytes logical blocks
this message doesn't come from the label, but from the disk driver
when it asks the drive how it is formatted..
        /*
         * Load the physical device parameters
         */
        sd_get_parms(unit, 0);  /* sets SDEV_MEDIA_LOADED */
        if (sd->params.secsiz != SECSIZE) {     /* XXX One day... */
                printf("sd%ld: Can't deal with %d bytes logical
blocks\n",
                    unit, sd->params.secsiz);
                Debugger("sd");

here is the debugger call.. the original intention is to let you
examine the results from the sd_get_params call
                errcode = ENXIO;
                goto bad;
        }

Your disk has been "partially reformetted"
OR
it's gone crazy
OR
sd_get_parms(unit,0)
is returning garbage (probably also due to a mad disk)

> 
> Seems like the disklabel is dodgy :(

nope.. see above..

> 
> Any ideas how to fix it? It's desperate??

compile a kernel with the SCSIDEBUG
then after booting do:
scsi -d 15 -f /dev/rsd2.ctl
this will turn on TONS of debugging
if it's too  much -d 1 might be better

this should give you the results of all operations affecting 
that device...

julian
in the mean-while 
don't write to that device (not that it'll let you :)


get a new disk?

> 
> Regards,
> 
> Trefor S.