Date: Mon, 4 Jan 1999 15:54:31 +0200 (SAT) From: Robert Nordier <rnordier@nordier.com> To: zapper@idsmail.com (Zapper) Cc: freebsd-current@FreeBSD.ORG Subject: Re: Multiple Partions Message-ID: <199901041354.PAA02020@ceia.nordier.com> In-Reply-To: <368FD169.4BC88D65@idsmail.com> from Zapper at "Jan 3, 99 02:22:02 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Zapper wrote:
> I have Win 95 and FreeBSD 3.0-Current installed on my computer. I have
> 2 hard drives installed with the Win95 OS on the "master" a 1.5G
> Western Digital and FreeBSD on the "slave" a 4.3G Quantum Bigfoot. The
> 4.3 is partitioned with about 2.5G of space for FreeBSD with the
> remaining space allocated to Win 95 programs. When I installed FreeBSD
> from the cd I created a "slice" so I could boot to either Win95 or
> FreeBSD i.e.:
>
> F1 DOS
> F5 FreeBSD
>
> Win95 crashed and I was forced to reinstall it, which I did without
> formatting so as not to mess up my boot partition or so I had hoped.
> To make a long story short, while I am still able to boot to FreeBSD
> and run it, I keep having problems that have just started since I
> reinstalled Win95.
> Problems are, when I do "make buildworld" in /usr/src , it crashes,
> but the errors are different everytime with the most popular error being
>
> cc: Internal compiler error: program cc1 got fatal signal 11
> *** Error code 1
>
> Stop.
>
> I've tried "make buildword" , "make -DNOCLEAN buildword" and just
> plain ole "make world" with no success.
>
> 2nd problem is, when I try to compile a new kernel it crashes also
> with pretty much different errors everytime.
I'd suspect that these errors (and perhaps even the original Win 95
crash) may be due to hardware problems, quite likely memory-related.
It is fairly common to find that FreeBSD (and other UNIX-like OSes)
will crash in these circumstances, even though other OSes seem to
run OK, as UNIX is just more of a "workout" for the hardware.
> Keep in mind that I have had relatively "no" real problems until I
> reinstalled Win 95 so having said all that, my question is, is there a
> way to reinstall the slice or redefine the partition?
By using the FreeBSD dmesg, fdisk, and disklabel commands, you should
be able to display enough information about the disk, slices, and
partitions to decide whether the parameters are reasonable. And you
can use fdisk and disklabel to correct any problems, if necessary.
I'd be fairly surprised if slice/partition problems caused the errors
you are seeing, though.
> Also, since it
> now looks like I'm going to have to "fully" reinstall Win 95 with format
> I know I will totally obliterate my slice. Is there a way to save my
> slice and partition info?
Windows will probably overwrite your boot manager, but is unlikely
otherwise to cause problems, as long as you don't allow it to "delete
partitions" or "use whole disk" or something.
Even after a format, the FreeBSD slice should remain intact. You can
use the Windows fdisk utility to activate the FreeBSD partition, boot
FreeBSD, and then use sysinstall to reinstall the boot manager.
You could save your raw slice and partition info using dd(1), for
example, something like
dd if=/dev/rwd1 of=slice.keep count=1
dd if=/dev/rwd1a of=part.keep skip=1 count=1
should do it.
--
Robert Nordier
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901041354.PAA02020>