From owner-freebsd-current  Wed Sep  4 01:24:18 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id BAA01412
          for current-outgoing; Wed, 4 Sep 1996 01:24:18 -0700 (PDT)
Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA01407
          for <freebsd-current@freebsd.org>; Wed, 4 Sep 1996 01:24:14 -0700 (PDT)
Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id JAA01003; Wed, 4 Sep 1996 09:24:10 +0100 (BST)
Date: Wed, 4 Sep 1996 09:24:10 +0100 (BST)
From: Developer <dev@fgate.flevel.co.uk>
To: Julian Elischer <julian@whistle.com>
cc: freebsd-current@freebsd.org
Subject: Re: HELP URGENT!!!
In-Reply-To: <322C818E.167EB0E7@whistle.com>
Message-ID: <Pine.BSI.3.93.960904092325.970A-100000@fgate.flevel.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



On Tue, 3 Sep 1996, Julian Elischer wrote:

> > 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 :)

Thanks for all your help:) The strange thing is when we rebooted the
machine again this morning it booted up just fine!! I wonder if it could
be a hardware error?

Regards,

Trefor S.