Date: Tue, 29 Aug 2000 07:43:18 -1000 From: "Peter Kurpis" <kurpis@gte.net> To: <freebsd-questions@freebsd.org> Subject: installed 3.2 and can't boot Message-ID: <000f01c011e0$9f959220$cec90a3f@dale2>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
------=_NextPart_000_000C_01C0118C.CC5FD4E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi! I am a FreeBSD newbie, though I've been around UNIX-likes for a few
years, and have successfully installed FreeBSD several times in the =
past.
(BTW, please CC my email address, as I am not (yet) subscribed to the
reflector.)
=20
I just installed 3.2 on a recent vintage (i.e. months old) emachine with =
one 10GB drive. When I tried to boot, right after telling the =
bootmanager
F2 (for FreeBSD) -- F1 for MS Windows works, btw -- it immediately says:
=20
Invalid partition
Invalid partition
No /boot/loader
=20
>> FreeBSD/i386 BOOT
Default: 0:wd(0,a)/kernel
boot:
Invalid partition
No /kernel
=20
Yikes! [That's me, not FreeBSD.] I looked through the FreeBSD =
archives,
and I found a couple of references to similar problems, and the =
suggested
fix was a smaller initial MS Windows slice, followed by a FreeBSD slice,
to get it within "1024 cylinders, 255 heads". My geometry is:
=20
19772 cylinders, 16 heads, 63 sectors
=20
The BIOS has got to be recent, so it's not an LBA problem (or whatever =
is
the latest BIOS kludge to access large disks), or is it? My allocation =
was:
=20
12289662 blocks wd0s1 to FAT (type 11)
7630875 blocks wd0s2 to FreeBSD (type 165), set to bootable
=20
BTW, when I first went to set partitions (in the novice installation), =
it would
not let me allocate a root partition -- I forgot the exact error =
message, but it
said something like partition too large, and something like the =
placement was
wrong (sorry to be so vague). I got around this by asking for automatic =
allocation, and changing the values for each partition, to get:
=20
100 MB for / (UFS Y)
200 MB for swap
3426 MB for /usr (UFS Y) (i.e. the rest of the disk)
=20
and from there, the installation went smoothly.
=20
As for trying to debug this, I tried various options at the boot: =
prompt, like
-s , which didn't work (returning me to the boot: prompt with similar =
messages).
=20
So I booted from scratch with the 2nd CDROM (i.e. live filesystem), and =
it put
me into the /stand/sysinstall Main Menu after a regular looking boot. =
(Is this=20
what is supposed to happen? I remember previous releases just going to =
a
shell prompt.)
=20
From there, I wanted to get to the live filesystem, so I chose the =
Fixit option,
which was the only option that seemed it would get me there. When I =
chose
to run from the CDROM, it told me that this CDROM was for an Alpha =
installation,
and prompted me to put in a CDROM for my machine, so I tried the first =
CDROM.
I got to a shell prompt, after a disconcerting message about not finding =
ld.so ,
but, although my PATH looked reasonable (per set ), it couldn't find =
ls or a=20
number of other things. I did cd / , and used find to look around a =
little, but
there wasn't much helpful there (like, only sh in /bin ). At this =
point, I'm
a little lost. (BTW, I've done a successful installation, albeit on a =
smaller disk,
with this distribution.)
=20
I appreciate your help!
=20
A couple of questions:
=20
(1) If the only solution is to shrink the MS Windows slice, will fips =
work on a
MS Windows 98 slice (i.e. FAT32 (I think))? How small to shrink it?
=20
(2) Once I get FreeBSD successfully installed, will I be able to mount =
the=20
MS Windows slice and access files? I read somewhere that FAT32 wasn't=20
generally supported.
=20
Thanks!
=20
------=_NextPart_000_000C_01C0118C.CC5FD4E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN">
<META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><BR> </DIV></FONT>
<DIV><FONT color=3D#000000 size=3D2>Hi! I am a FreeBSD newbie, =
though I've=20
been around UNIX-likes for a few</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>years, and have successfully =
installed FreeBSD=20
several times in the past.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT><FONT size=3D2>(BTW, please =
CC my email=20
address, as I am not (yet) subscribed to the</FONT></DIV>
<DIV><FONT size=3D2>reflector.)</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>I just installed 3.2 on a recent =
vintage (i.e.=20
months old) emachine with </FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>one 10GB drive. When I tried =
to boot,=20
right after telling the bootmanager</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>F2 (for FreeBSD) -- F1 for MS =
Windows works, btw=20
-- it immediately says:</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2> Invalid=20
partition</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2> Invalid=20
partition</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2> No=20
/boot/loader</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2> >> =
FreeBSD/i386=20
BOOT</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2> Default:=20
0:wd(0,a)/kernel</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2> =
boot:</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2> Invalid=20
partition</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2> No =
/kernel</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>Yikes! [That's me, not =
FreeBSD.] I=20
looked through the FreeBSD archives,</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>and I found a couple of references =
to similar=20
problems, and the suggested</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>fix was a smaller initial MS Windows =
slice,=20
followed by a FreeBSD slice,</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>to get it within "1024 =
cylinders, 255=20
heads". My geometry is:</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2> 19772 =
cylinders, 16=20
heads, 63 sectors</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>The BIOS has got to be recent, so =
it's not an=20
LBA problem (or whatever is</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>the latest BIOS kludge to access =
large disks),=20
or is it? My allocation was:</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2> 12289662 =
blocks wd0s1=20
to FAT (type 11)</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2> =
7630875 blocks=20
wd0s2 to FreeBSD (type 165), set to bootable</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>BTW, when I first went to set =
partitions (in the=20
novice installation), it would</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>not let me allocate a root partition =
-- I forgot=20
the exact error message, but it</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>said something like partition too =
large, and=20
something like the placement was</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>wrong (sorry to be so vague). =
I got around=20
this by asking for automatic </FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>allocation, and changing the values =
for each=20
partition, to get:</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2> 100 MB for =
/ (UFS=20
Y)</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2> 200 MB for=20
swap</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2> 3426 MB for /usr =
(UFS Y)=20
(i.e. the rest of the disk)</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>and from there, the installation =
went=20
smoothly.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>As for trying to debug this, I tried =
various=20
options at the boot: prompt, like</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2> -s , which didn't work =
(returning me to=20
the boot: prompt with similar messages).</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>So I booted from scratch with the =
2nd CDROM=20
(i.e. live filesystem), and it put</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>me into the /stand/sysinstall =
Main=20
Menu after a regular looking boot</FONT><FONT color=3D#000000 =
size=3D2>. =20
(Is this </FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>what is supposed to happen? I =
remember=20
previous releases just going to a</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>shell prompt.)</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>From there, I wanted to get to the =
live=20
filesystem, so I chose the Fixit option,</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>which was the only option that =
seemed it would=20
get me there. When I chose</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>to run from the CDROM, it told me =
that this=20
CDROM was for an Alpha installation,</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>and prompted me to put in a CDROM =
for my=20
machine, so I tried the first CDROM.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>I got to a shell prompt, after a =
disconcerting=20
message about not finding ld.so ,</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>but, although my PATH =
looked=20
reasonable (per set ), it couldn't find ls or a =
</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>number of other things. I =
did cd / ,=20
and used find to look around a little, but</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>there wasn't much helpful there =
(like,=20
only sh in /bin ). At this point, =
I'm</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>a little lost. (BTW, I've done =
a=20
successful installation, albeit on a smaller disk,</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>with this =
distribution.)</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>I appreciate your help!</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>A couple of questions:</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>(1) If the only solution is to =
shrink the MS=20
Windows slice, will fips work on a</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>MS Windows 98 slice (i.e. FAT32 (I=20
think))? How small to shrink it?</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>(2) Once I get FreeBSD successfully =
installed,=20
will I be able to mount the </FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>MS Windows slice and access =
files? I read=20
somewhere that FAT32 wasn't </FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>generally supported.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT color=3D#000000 size=3D2>Thanks!</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV></BODY></HTML>
------=_NextPart_000_000C_01C0118C.CC5FD4E0--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000f01c011e0$9f959220$cec90a3f>