Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!uunet!ihz.compuserve.com!sam From: sam@csi.compuserve.com (Sam Neely) Subject: Re: Has anybody installed 386bsd on a >1gb SCSI drive? Message-ID: <C5wpLs.EKx@csi.compuserve.com> Organization: CompuServe Incorporated References: <C5rGGw.BH3@csi.compuserve.com> <JKH.93Apr21220810@whisker.lotus.ie> Date: Thu, 22 Apr 1993 22:39:25 GMT Lines: 35 In article <JKH.93Apr21220810@whisker.lotus.ie> jkh@whisker.lotus.ie (Jordan K. Hubbard) writes: >I've had no trouble, and I also have a MAXSTOR P1-17 (though I boot >off of a 1.01GB DEC drive now, for speed). Did you also format the >drive with Adaptec's format utility? I found that to be necessary >before the silly thing would let me fdisk it. > >Here's the translations I'm using.. > > [[ deleted ]] > >3 partitions: ># size offset fstype [fsize bsize cpg] > a: 2936593 0 4.2BSD 1024 8192 0 # (Cyl. 0 - 1776*) > c: 2936593 0 unused 0 0 # (Cyl. 0 - 1776*) I too can get it to work if I use the entire drive. I run into problems when I want both DOS and 386bsd on my drive, and try to set up "correct" partition table entries. Lars Grupe has suggested that I "fake up" a partition table entry. Basically, build a proper DOS partition, and a 386bsd partition, but let the 386bsd partition end at the 1gb mark. Then write a disklable that points ends at the end of the drive. While the partition table entry will not point to the entire drive, the disklabel will, and 386bsd will be happy. By the way, Jordan, the example above does not end on a cylinder boundry. If the above numbers for for the disk geometry are correct, then the size should be 2939034. - Sam -- Sam Neely, CompuServe Incorporated +1 614 538 3718 (voice) 5000 Arlington Centre Blvd, Columbus, OH 43220 +1 614 457 0348 (FAX) Electronic Mail: InfoPlex: >CSI:SAM Internet: sam@csi.compuserve.com To err is human, to forgive is against company policy