From owner-freebsd-questions Tue Aug 29 10:44:11 2000 Delivered-To: freebsd-questions@freebsd.org Received: from smtppop3.gte.net (smtppop3pub.gte.net [206.46.170.22]) by hub.freebsd.org (Postfix) with ESMTP id 47E2737B422 for ; Tue, 29 Aug 2000 10:44:03 -0700 (PDT) Received: from dale2 (1Cust206.tnt3.hilo.hi.da.uu.net [63.10.201.206]) by smtppop3.gte.net with SMTP for ; id MAA16357956 Tue, 29 Aug 2000 12:40:09 -0500 (CDT) Message-ID: <000f01c011e0$9f959220$cec90a3f@dale2> From: "Peter Kurpis" To: Subject: installed 3.2 and can't boot Date: Tue, 29 Aug 2000 07:43:18 -1000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000C_01C0118C.CC5FD4E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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

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