From owner-freebsd-hackers  Tue Jun  6 19:41:20 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id TAA26717
          for hackers-outgoing; Tue, 6 Jun 1995 19:41:20 -0700
Received: from servo.ipsilon.com (servo.Ipsilon.COM [204.160.241.205])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA26696
          for <hackers@freebsd.org>; Tue, 6 Jun 1995 19:41:14 -0700
Received: (from hoffman@localhost) by servo.ipsilon.com (8.6.11/8.6.10) id TAA20436; Tue, 6 Jun 1995 19:39:49 -0700
Date: Tue, 6 Jun 1995 19:39:49 -0700
From: Eric Hoffman <hoffman@Ipsilon.COM>
Message-Id: <199506070239.TAA20436@servo.ipsilon.com>
To: hackers@freebsd.org
Subject: 2.0.5 scsi boot configuration whine
Sender: hackers-owner@freebsd.org
Precedence: bulk


I would not ask here, but I have tried several things including fdisk
with a 2.0 boot disk with a 2.0.5 install after that.  the basic
problem I have is "paritition out of reach from the bios" error when
an attempt is made to boot sd(0,a)/kernel.

This drive/controller hasn't had any problems running 2.0 stock or any
of the SNAPs.

I have a single drive on an NCR SCSI with an unfortunate geometry:
2234/7/68. It doesn't seem to matter if the FreeBSD starts at 0, 4
(which is where 2.0.5 puts it), or 68 (which is where 2.0.5 will put
it after being corrected about the geometry using "G" in the new
fdisk). when corrected about the geometry, it will come up next time
as 37978/7/4, the same total number of blocks, but using BIOSs 6 bit
sector count.

an unfortunate victim of geometry translation?