Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!mel.dit.csiro.au!its.csiro.au!dmssyd.syd.dms.CSIRO.AU!metro!news.cs.su.oz.au!harbinger.cc.monash.edu.au!msuinfo!agate!ihnp4.ucsd.edu!usc!sol.ctr.columbia.edu!usenet.ucs.indiana.edu!nickel.ucs.indiana.edu!pi From: pi@nickel.ucs.indiana.edu (Raymond L. Gilbert) Subject: booteasy problem: 2 IDE drives Message-ID: <CMsw6M.DJ0@usenet.ucs.indiana.edu> Sender: news@usenet.ucs.indiana.edu (USENET News System) Nntp-Posting-Host: nickel.ucs.indiana.edu Organization: Indiana University Date: Thu, 17 Mar 1994 08:42:22 GMT Lines: 74 OK like I promised after my last post I'm back.... This is a much more distressing problem than the previous one (which was fixed!). Here's the situation: I originally had 1 IDE drive running MS-DOS. When I started setting up FreeBSD 1.0, I completely disconnected it and connected another IDE drive to install BSD on. Tonight was the night I finally felt comfortable enough with my FreeBSD system to take the bold step of trying to hook my other drive back up. I had previously grabbed a copy of BOOTEASY specifically in anticipation of this step. The situation I wanted to set up was to have my 124 meg IDE MS-DOS drive as the 1st drive, and my 340 meg IDE FreeBSD drive as the 2nd drive. When I tried to boot my computer, it sat there for a long time and finally gave me the insightful message: Error Reading drive D: Press F1 to resume Then after pressing F1, I get my BOOTEASY menu: F1 - dos F5 - ? Well, F5 didn't give me anything except the menu again, but after a lot of coaxing, I finally got to my drive C with F1. It wasn't behaving normally however... things were taking a really long time for simple things like even dir. I thought maybe if I got BOOTEASY loaded up I could solve everything and just be able to choose which hard drive I wanted to boot from. BOOTEASY took a loooong time to load up and finally reported error 128 writing to drive 0. I wasn't exactly sure which drive this was any more since my DOS drive was acting so strangely. When I disconnected my FreeBSD drive, everything seemed to work perfectly normally. I ran BOOTEASY again and of course it only was able to configure the one drive. Finally I gave up and decided I needed to do something fancy with the disklabel on my 2nd drive like it suggessts in the FAQ. So I disconnected my DOS drive and connected my FreeBSD drive alone, and guess what? Now my FreeBSD drive comes up with the BOOTEASY prompt! F1 - dos When I try to hit F1, it just gives me the menu again. Since then, I haven't been able to access my FreeBSD system at all! :-( :-( Now that my longwinded story is out, here are my questions: a) Is my 340 meg IDE drive totally hosed? Do I need to start from the beginning and re-install everything from scratch again? Or is there a way to recover my origianl boot sector? Currently, I have no way of reliably establishing a link between BOOTEASY and my 2nd drive. b) once I get a) settled (one way or the other), what do I need to do be able to choose which drive I boot off of? (I've got no particular attacthment to BOOTEASY; I just thought from discussions I read on here that it would be the easiest). c) if and when I get b) settled, how do I set it up so that my DOS partition is mounted as a filesystem accessable from FreeBSD? The FAQ is very clear on how to do this for a DOS partition on the same disk, but not for 2 seperate disks. Do I have to make a small token partition of FreeBSD on my DOS disk to be able to mount it, as I've seen others here suggest? Thanks a million in advance to anyone that can help me solve any of these perplexing problems! :-) -- /----------------------------------------------------------------------------\ | Raymond L. Gilbert | "...the present rule in computing the circle's | | pi@indiana.edu | area is entirely wrong..." | | IUB Dept. of Physics | - Bill No. 246, Indiana State Legislature, 1897|