Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.mel.connect.com.au!munnari.OZ.AU!spool.mu.edu!newspump.sol.net!www.nntp.primenet.com!nntp.primenet.com!ddsw1!news.mcs.net!usenet
From: Scott Perry <sperry@os-knight.com>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Help, install corrupts partition table
Date: Thu, 05 Sep 1996 12:28:49 -0500
Organization: OS-Knight Corp.
Lines: 38
Message-ID: <322F0DD1.789F@os-knight.com>
NNTP-Posting-Host: sperry-2.pr.mcs.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.0 (X11; I; SunOS 5.5 sun4m)
Please Help!!!!
I am trying to install Freebsd 2.15 on the 3rd or 4th
partition of a 4GB SCSI disk (all partitions are 1GB) and it installs,
but corrupts the starting location of it's partition as well as the
starting location of the next partition (it leaves the first 2
partitions alone).
I am NOT redefining the partition table during the
installation. I define the partition table using linux and make the
(empty) partition freebsd type (0xa5 (or 165, whichever you prefer)),
then I take all defaults for within the slice.
I select no mbr changes, and install all filesets. If I install
on my boot drive, it replaces system commander (my multi-os boot
manager) with freebsd's boot manager. I then reinstall system
commander's boot file, at which point it flags partition 3 & 4 as
starting on head 255 instead of head 0 (or some such).
This illegal head stops system commander from seeing the
partition as bootable.
I could even live with that if there was some way to boot from
dos's autoexec.bat and point to the correct partition as a boot
argument. (System Commander manages your boot files for each OS, thus
keeping each set of boot files pristine).
That's the story. I need to either stop freebsd from redefining
the partition table (and leave it sane for System Commander), or find a
way to boot from dos and point to the correct partition with boot
arguments. (Floppy boot is unacceptable).
If I can't resolve this, I will be forced to give up on freebsd,
and I was really looking forward to working with it.
Any suggestions would be helpful.
Thanks in advance,
Scott A. Perry
Freebsd'er to be (hopefully)
sperry@os-knight.com