*BSD News Article 1996


Return to BSD News archive

Path: sserve!manuel!munnari.oz.au!mips!mips!darwin.sura.net!haven.umd.edu!mimsy!nocusuhs!nmrdc1!rdc30
From: rdc30@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson)
Newsgroups: comp.unix.bsd
Subject: 386BSD Install problem + solution
Message-ID: <1992Jul17.193043.5249@nmrdc1.nmrdc.nnmc.navy.mil>
Date: 17 Jul 92 19:30:43 GMT
Organization: Naval Medical Research & Development Command
Lines: 32

I encountered a problem when installing the new release of 386BSD over the 
previous version on my hard drive (a CP2064) and after much fiddling, solved
it.  In case others have the same problem, I'll provide the details and 
solution.

The bootup and install all seemed to go fine, my hard drive was properlly
indentified and the other installed devices as well.  Since I had a previous
version installed on the entire hd (the Butler no-fpu kernel), I answered yes
to the questions about re-installing and using the entire hd.  Everything went
well untill the reboot off the newly installed hd.  After identifying the
installed devices, it complained about a missing bad sector table on wd0, 
asserted a vm_fault and went into an automatic reboot.

After much fiddling, I determined that the problem was the new partitioning
of the hd without the bad sector table, but the disklabel still had the "sf"
flag (bad144 style bad sector table) asserted.  This was causing the errors 
and panic and reboot.  To correct the problem, I booted off the old kernel
boot floppy, edited the disktab to create a new entry with the same partions
as the install program had created but left off the "sf" option since this is
an IDE drive.  I then used disklabel to write out the corrected version and 
rebooted from the hd.  No errors!!  Next step is to get bindist onto the hd.

Looks like the new install, needs to more completely write over the old 
disklabel contents if the autodetermined params differ from the old ones.

Mike


LCDR Mike Dobson, Sys Admin for | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil
nmrdc1.nmrdc.nnmc.navy.mil      | UUCP:   ...uunet!mimsy!nmrdc1!rdc30
AT&T 3B2/600G Sys V R 3.2.3     | BITNET:   dobson@usuhsb or nrd0mxd@vmnmdsc
WIN/TCP for 3B2  R3.2           | MCI-Mail: 377-2719 or 0003772719@mcimail.com