Return to BSD News archive
#! rnews 4054 sserve.cc.adfa.oz.au
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!news.mn.interact.net!usenet
From: greg@mn.interact.net (Greg Rowe)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Help: Can not boot 2.0.5R
Date: 12 Jun 1995 13:04:45 GMT
Organization: US West-Interact Services, Minneapolis, Minnesota
Lines: 86
Message-ID: <3rhe1d$m4v@sven.mn.interact.net>
References: <3rgem6$2dc@gryphon.phoenix.net>
Reply-To: greg@mn.interact.net
NNTP-Posting-Host: nevis.oss.interact.net
I had somewhat the same problem, I decided to do a complete reinstall on my first IDE
disk (544meg) (contains only a / partition with /home on my second IDE disk). I selected "Use the whole disk" option in the Partition section and set it for bootable.
I then created a swap and / partition under Label. The install went fine but reboot
failed with "No Operating System". After a number of unsuccessful tries, I finally used the Fixit portion of the last Snap boot disk to write the MBR. I could then bring the system up with no problems.
Am I missing something here ? Is the "Standard MBR" being written correctly on the 2.0.5 R boot disks ? Or am I doing something silly? Also, the Fixit stuff on the Snap
floppies was nice. Is that available on 2.0.5R ? Thanks.
In article <3rgem6$2dc@gryphon.phoenix.net>, pflores@phoenix.net (Paul Flores) writes:
> Chun-Yang Chiu (cchiu@uclink.berkeley.edu) wrote:
> : Hi all:
>
> : I am trying to upgrade from 2.0R to 2.0.5R. However, after I have
> : successfully install 2.0.5R(according to the installation program), I can
> : not boot. :( I partitioned my HD(850mb WD IDE) as followed:
>
> : Offset Size End Name Ptype DESC Subtype flag
> : 0 63 62 - 6 unused 0
> : wd0s1 63 614817 614879 wd0s1 2 fat 6
> : wd0s2a 614880 955584 1570463 wd0s2 3 freebsd 165 C>
> : wd0s3b 1570464 96768 1557231 wd0s3 3 freebsd 165 >
>
> : Labelling is as followed:
>
> : Part Mount Size Newfs
> : wd0s1 <NONE> 300MB *
> : wd0s2a / 466MB Y
> : wd0s3b swap 47MB
>
> : In fact, I was installing 2.0.5R over the old 2.0R partition. I also choosed
> : to use the boot manager that was in the installation program of 2.0.5R.
> : Well, I did not choose to have 2 partition for / and /usr, I opted for one
> : single partition for /. wd0s1 is my DOS partition. My motherboard supports
> : LBA, and is using Award bios. I have tried to install and boot with both LBA
> : on and LBA off(I dont know if that's the problem). Well, right now, I am
> : just stucked. When I boot, I get the following message:
>
> : partition is out of reach from the bios.
>
> : By the way, I did not change the geometry of the HD. I used the geometry
> : that was detected by the installation program. Has anyone else encountered
> : the same problem? It puzzles me because I ran 2.0R fine, and I am just
> : installing 2.0.5R over the old 2.0R partition, and now the partition is
> : out of reach? Anyways, any help/clue very very greatly appreciated. Thank
> : you very much.
>
> : Regards,
>
> : Chun Chiu
> : --------------------------------
> : email: cchiu@uclink.berkeley.edu
>
>
>
> I, too am Using the 850 Meg WD drive, and also installed into the
> exisiting partition of FreeBSD.
>
> I was upgrading from 041295-SNAP....
>
> Tryed keeping the old Boot Manager and the New one, but I'm still no
> closer to getting it working. :<
>
> BTW, I noticed when I booted, that all the installed files from the
> previous install where still there! WHY do I HAVE to re-install
> everything with this version of the install program? (Sombody had to
> gripe!!! ;> )
>
> Perhaps I need to back up my dos drive and re-partition the whole thing?
>
> HELP! I want my FreeBSD machine back!!!
>
> Paul
--
Greg Rowe |
US West - Interact Services | INTERNET greg@mn.interact.net
111 Washington Ave. South | Fax: (612) 672-8537
Minneapolis, MN USA 55401 | Voice: (612) 672-8535
To err is human, to really foul up requires the root password.