Skip site navigation (1)Skip section navigation (2)
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

[-- Attachment #1 --]


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.)
 
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:
 
     Invalid partition
     Invalid partition
     No /boot/loader
 
     >> FreeBSD/i386 BOOT
     Default: 0:wd(0,a)/kernel
     boot:
     Invalid partition
     No /kernel
 
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:
 
     19772 cylinders, 16 heads, 63 sectors
 
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:
 
     12289662 blocks wd0s1 to FAT (type 11)
      7630875 blocks wd0s2 to FreeBSD (type 165), set to bootable
 
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:
 
     100 MB for / (UFS Y)
     200 MB for swap
    3426 MB for /usr (UFS Y) (i.e. the rest of the disk)
 
and from there, the installation went smoothly.
 
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).
 
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 
what is supposed to happen?  I remember previous releases just going to a
shell prompt.)
 
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 
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.)
 
I appreciate your help!
 
A couple of questions:
 
(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?
 
(2) Once I get FreeBSD successfully installed, will I be able to mount the 
MS Windows slice and access files?  I read somewhere that FAT32 wasn't 
generally supported.
 
Thanks!
 

[-- Attachment #2 --]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

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

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000f01c011e0$9f959220$cec90a3f>