Date: Thu, 27 Jul 2000 11:45:11 -0700 (MST) From: John Reynolds <jjreynold@home.com> To: hackers@freebsd.org Subject: Re: unable to use disklabel -B from fixit floppy? Message-ID: <14720.33591.77038.377961@whale.home-net> In-Reply-To: <200007271636.JAA76849@pike.osd.bsdi.com> References: <14719.60144.794393.763015@gargle.gargle.HOWL> <200007271636.JAA76849@pike.osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[ copying -doc because I've got a doc patch for the FAQ ... perhaps :) ]
[ On Thursday, July 27, John Baldwin wrote: ]
>
> Umm, well. First off, disklabel -B doesn't fix your MBR. fdisk does that,
> or boot0cfg if you are using boot0 to dual-boot. However, can you type
Hmmm. Must have just been bit-rot in my brain from WAY back. Maybe it was the
3.x to 4.x transition where I remember seeing ``do disklabel -B'' ... can't
remember. OK, now I know boot0cfg so I'll remember that. Thanks very much!
> disklabel ad0 now and get useful information? Or disklabel ad0sX (where X
> is the slice number for your FreeBSD slice)?
oh yes, no problems.
> Yes, this touches the MBR. The disklabel command serves the same purpose as
> the label editor in sysinstall. IOW, you use disklabel to lay out partitions
> (a-h) within a FreeBSD slice.
>
> See if disklabel ad0 works now.
Absolutely. Since this is a way to recover the MBR in addition to what was
already in the FAQ, I hacked up some changes to that FAQ entry. Attached is a
diff--be gentle, this is my very first time attempting to hack SGML :) ...
(I will go ahead and just send-pr this as well ....)
--- book.sgml.orig Thu Jul 27 11:08:53 2000
+++ book.sgml Thu Jul 27 11:38:03 2000
@@ -1306,22 +1306,22 @@
</answer></qandaentry>
<qandaentry><question>
-<para>Can Windows 95 co-exist with FreeBSD?</para></question><answer>
+<para>Can Windows 95/98 co-exist with FreeBSD?</para></question><answer>
-<para>Install Windows 95 first, after that FreeBSD. FreeBSD's boot
-manager will then manage to boot Win95 and FreeBSD. If you
-install Windows 95 second, it will boorishly overwrite your
+<para>Install Windows 95/98 first, after that FreeBSD. FreeBSD's boot
+manager will then manage to boot Win95/98 and FreeBSD. If you
+install Windows 95/98 second, it will boorishly overwrite your
boot manager without even asking. If that happens, see
the next section.</para>
</answer></qandaentry>
<qandaentry><question>
-<para> Windows 95 killed my boot manager! How do I get it back?
+<para> Windows 95/98 killed my boot manager! How do I get it back?
</para></question><answer>
<para>You can reinstall the boot manager FreeBSD comes with in one of
-two ways:</para>
+three ways:</para>
<itemizedlist>
@@ -1351,6 +1351,24 @@
prompt, be sure to select "Boot Manager."
This will re-write the boot manager to disk. Now quit out of the
installation menu and reboot off the hard disk as normal.</para>
+</listitem>
+
+<listitem>
+<para>Boot the FreeBSD boot floppy (or CD-ROM) and choose the
+<quote>Fixit</quote> menu item. Select either the Fixit floppy or
+CD-ROM #2 (the <quote>live</quote> file system option) as appropriate
+and enter the fixit shell. Then execute the following command:
+</para>
+
+<screen><prompt>Fixit# </prompt> <userinput>boot0cfg -B bootdevice </userinput></screen>
+<para></para>
+
+<para>substituting <quote>bootdevice</quote> for your real boot device such
+as ad0 (first IDE disk), ad4 (first IDE disk on auxiliary controller), da0
+(first SCSI disk), etc.
+
+</para>
+
</listitem>
</itemizedlist>
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation
jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running
jjreynold@home.com FreeBSD 4.0-STABLE. FreeBSD: The Power to Serve.
http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14720.33591.77038.377961>