From owner-freebsd-hackers Wed Aug 30 04:00:37 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id EAA25802 for hackers-outgoing; Wed, 30 Aug 1995 04:00:37 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id EAA25789 for ; Wed, 30 Aug 1995 04:00:25 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id DAA07870; Wed, 30 Aug 1995 03:59:34 -0700 From: "Rodney W. Grimes" Message-Id: <199508301059.DAA07870@gndrsh.aac.dev.com> Subject: Re: Does fdisk work? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 30 Aug 1995 03:59:33 -0700 (PDT) Cc: jehamby@lightside.com, freebsd-hackers@freefall.FreeBSD.org In-Reply-To: <2416.809771491@time.cdrom.com> from "Jordan K. Hubbard" at Aug 30, 95 01:31:31 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1502 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > > reinstall the EasyBoot MBR from within FreeBSD! Considering my > > configuration, what would be the EXACT command to install a master boot > > record on my first and second IDE hard drive from within FreeBSD? > > There isn't one.. :-( CATION: What I am about to tell you how to do can have catastrofic effects on your disk. You _MUST_ have BACKUPS and a way to recover your system in case of total failure. dd if=/dev/rwd0 of=/dev/rfd0 bs=512 count=1 #Save current MBR record fdisk /dev/rwd0 | lpr #Hard copy is hard to destroy! dd if=mbrimage of=/dev/rwd0 bs=512 count=1 #SPLAT fdisk -u /dev/rwd0 #Tweak the partition table back :1,$s/rwd0/rwd1/g and do it again... You can get the mgrimage from the booteasy distribution, it will call your *BSD partitions 386BSD :-(. > Unfortunately, the only command that whaps MBRs out is sysinstall, and > that's not a standard part of the system, it's only run at > installation time. > > I'm working on this problem (really really!) for 2.1 and hope to > have this problem behind us. For now, I suggest booting DOS and > installing BOOTEASY that way. Really strange, BTW, that it doesn't > see your second drive! It does mine, and I can boot DOS from > either drive using BOOTEASY.. > > Of course, I'm also using SCSI drives but that shouldn't change anything? wd -> sd :-). -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD