Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP
id AA5492 ; Fri, 01 Jan 93 01:47:04 EST
Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!spool.mu.edu!uunet!noc.near.net!ceylon!genesis!steve2
From: steve2@genesis.nred.ma.us (Steve Gerakines)
Newsgroups: comp.unix.bsd
Subject: [386bsd] startup fixed
Message-ID: <9212232827@genesis.nred.ma.us>
Date: 22 Dec 92 22:31:16 GMT
Organization: Genesis Public Access Minix +1 508 664 0149
Lines: 38
Thanks to all who sent me messages for getting my system up and booting
on the hard disk. I'm using an UltraStor 24F controller in ISA mode,
and a Maxtor 535SY drive.
After finally getting the system to boot off the hard disk, I found that
the system would only start up in standalone, no matter what I did. For
the benefit of anyone else who runs into this problem, here's what I found.
The boostrap (bootwd) forces standalone mode if one of two conditions
occur: the disklabel's magic number isn't found, or a labeled partition
doesn't match up with the cylinder boundary the bootstrap physically
loaded from.
Turns out I ran into the second case. The initial bootstrap (wdboot)
was retreiving an incorrect "off" value (current cylinder offset - the
cylinder the boostrap ended up at after loading) from the controller.
To quickly remedy this, I whipped out the handy dandy diskeditor for the
zillionth time and made the following patches to the first boot sector:
00DB: EC 31 C9 becomes B0 F4 90
00E1: E4 84 EC becomes B0 00 90
^^
||
In this case, my 386BSD "A" partition starts at cylinder 244, so I plugged
in $F400.
Seems to me it probably would have been a little safer, especially at
do or die boot time, to go after the BIOS for this information instead
of asking the controller directly.
Hope this saves at least one person some needless aggravation. :-)
- Steve
--
Steve Gerakines |
steve2@genesis.nred.ma.us | "I have a three user 386BSD TV license." - me
+1 (508)664-0149 |