Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 29 Apr 2010 00:34:05 -0500
From:      "Paul A. Procacci" <pprocacci@datapipe.com>
To:        Jeremy Chadwick <freebsd@jdc.parodius.com>
Cc:        "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>
Subject:   Re: loader.conf problem
Message-ID:  <20100429053405.GB18122@work_machine.myhome.net>
In-Reply-To: <20100429020727.GA39577@icarus.home.lan>
References:  <20100428212613.GA21128@datapipe.net> <20100428220524.GA34041@icarus.home.lan> <20100429000010.GD21128@datapipe.net> <20100429020727.GA39577@icarus.home.lan>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 28, 2010 at 10:07:27PM -0400, Jeremy Chadwick wrote:
> On Wed, Apr 28, 2010 at 07:00:10PM -0500, Paul A. Procacci wrote:
> > On Wed, Apr 28, 2010 at 06:05:24PM -0400, Jeremy Chadwick wrote:
> > > On Wed, Apr 28, 2010 at 04:26:13PM -0500, Paul A. Procacci wrote:
> > > > Gents,
> > > >
> > > > I recent build of FreeBSD8-STABLE (amd64)is not parsing /boot/loade=
r.conf
> > > > properly.  While the machine boots I am getting the following error=
:
> > > >
> > > > > \
> > > > \: unknown command
> > > > \
> > > > --
> > >
> > > Please provide:
> > >
> > > - Contents of /boot/loader.conf
> > > - ls -l /boot
> > >
> > > Thanks.
> > >
> > > --
> > > | Jeremy Chadwick                                   jdc@parodius.com =
|
> > > | Parodius Networking                       http://www.parodius.com/ =
|
> > > | UNIX Systems Administrator                  Mountain View, CA, USA =
|
> > > | Making life hard for others since 1977.              PGP: 4BD6C0CB =
|
> > >
> >
> > Something I should have provided.  Sorry.
> >
> > %cat /boot/loader.conf
> > geom_mirror_load=3D"YES"
> >
> > %ls -l /boot/
> > total 748
> > -r--r--r--  1 root  wheel    7643 Apr 28 15:54 beastie.4th
> > -r--r--r--  1 root  wheel    8192 Apr 28 15:54 boot
> > -r--r--r--  1 root  wheel     512 Apr 28 15:54 boot0
> > -r--r--r--  1 root  wheel     512 Apr 28 15:54 boot0sio
> > -r--r--r--  1 root  wheel     512 Apr 28 15:54 boot1
> > -r--r--r--  1 root  wheel    7680 Apr 28 15:54 boot2
> > -r--r--r--  1 root  wheel    1201 Apr 28 15:54 cdboot
> > drwxr-xr-x  2 root  wheel     512 Apr 28 15:54 defaults
> > -r--r--r--  1 root  wheel     699 Apr 27 22:40 device.hints
> > drwxr-xr-x  2 root  wheel     512 Nov 21 08:29 firmware
> > -r--r--r--  1 root  wheel    2258 Apr 28 15:54 frames.4th
> > -r--r--r--  1 root  wheel    7535 Apr 28 15:54 gptboot
> > -r--r--r--  1 root  wheel   25219 Nov 21 08:30 gptzfsboot
> > drwxr-xr-x  2 root  wheel   11776 Apr 28 15:53 kernel
> > drwxr-xr-x  2 root  wheel   11776 Apr 27 22:36 kernel.old
> > -r-xr-xr-x  1 root  wheel  184320 Apr 28 15:54 loader
> > -r--r--r--  1 root  wheel    5861 Apr 28 15:54 loader.4th
> > -rw-r--r--  1 root  wheel      41 Apr 27 23:52 loader.conf
> > -r--r--r--  1 root  wheel   15219 Apr 28 15:54 loader.help
> > -r-xr-xr-x  1 root  wheel  184320 Apr 27 22:38 loader.old
> > -r--r--r--  1 root  wheel     396 Nov 21 08:30 loader.rc
> > -r--r--r--  1 root  wheel     512 Apr 28 15:54 mbr
> > drwxr-xr-x  2 root  wheel     512 Apr 28 15:56 modules
> > -r--r--r--  1 root  wheel     512 Apr 28 15:54 pmbr
> > -r--r--r--  1 root  wheel  186368 Apr 28 15:54 pxeboot
> > -r--r--r--  1 root  wheel     699 Apr 28 15:54 screen.4th
> > -r--r--r--  1 root  wheel   35132 Apr 28 15:54 support.4th
> > drwxr-xr-x  2 root  wheel     512 Nov 21 08:29 zfs
> > -r--r--r--  1 root  wheel   33280 Nov 21 08:30 zfsboot
> >
> > %md5 /boot/*
> > MD5 (/boot/beastie.4th) =3D d7d88e7385f2eb456e2628ffb81dce5c
> > MD5 (/boot/boot) =3D 91296cd94bc075de685318df2a4afc9f
> > MD5 (/boot/boot0) =3D d5019f554b1a6649dd64e479b36ae90d
> > MD5 (/boot/boot0sio) =3D 4f2616f956de41c0949f07ba234edfdb
> > MD5 (/boot/boot1) =3D fe3c577c089ac9db8f31abaa081ea945
> > MD5 (/boot/boot2) =3D bc4e2df8bf72a7e3b70e34a800638097
> > MD5 (/boot/cdboot) =3D f2fe4225957001913769f3d1b247d5e4
> > MD5 (/boot/defaults) =3D 4553259374ff97e232e86f813c16a8b8
> > MD5 (/boot/device.hints) =3D 992bdbbdb069a4300384e3fe1eb92fd0
> > MD5 (/boot/firmware) =3D 09f25114d80dbd121f92ffc126f33e85
> > MD5 (/boot/frames.4th) =3D 7e9e14adeb0179c96dfc2e4de31687ce
> > MD5 (/boot/gptboot) =3D 72e2bb50b09650320b25ec7a09f5b68e
> > MD5 (/boot/gptzfsboot) =3D e5a49dd7837df4093d4c1051566fe7bf
> > MD5 (/boot/kernel) =3D 13c4c3d256c2993ba9525fc34b98907e
> > MD5 (/boot/kernel.old) =3D 0e73c4caf72fd22594339a6d814516a7
> > MD5 (/boot/loader) =3D e459148bffaca8e0fc2633759499d62d
> > MD5 (/boot/loader.4th) =3D ef3d7bcf3a6f8fdeed3dee4eca86473e
> > MD5 (/boot/loader.conf) =3D 098bd0fbe26459911454967ded77af16
> > MD5 (/boot/loader.help) =3D b553af5cf09e399b1ce850991ef386c4
> > MD5 (/boot/loader.old) =3D 845f8d0e5c9eec3b45ac76ce2c553620
> > MD5 (/boot/loader.rc) =3D 73e4ee17ce1f287f529211cd2cb6c170
> > MD5 (/boot/mbr) =3D db3f526667d01f5851ef3d0ddafb86db
> > MD5 (/boot/modules) =3D fcf04f3c1546b550b3e12ba6d84750c5
> > MD5 (/boot/pmbr) =3D 6daee450f256507904e0aebe78187cf6
> > MD5 (/boot/pxeboot) =3D 4d75944d497e98a4a1f5bfe1719ee944
> > MD5 (/boot/screen.4th) =3D 47d16a951e9f88f52ff0811cdebeeb26
> > MD5 (/boot/support.4th) =3D 04feeb00e7f52a81744713365524e5cf
> > MD5 (/boot/zfs) =3D 91bb533338c037aae3afcadec85b553d
> > MD5 (/boot/zfsboot) =3D 9232895a063604025059b5b42fddf0fc
>
> Can you provide the following output please (not a typo):
>
> hd /boot/loader.conf
>

I just solved my problem.  Apparently someone *points to self* included
an option in src.conf by mistake:

%fgrep FORTH /etc/src.conf
WITHOUT_FORTH=3Dtrue

I assume this was the root of the problem as I now have no problems with th=
e
initially reported error message.

This has been a waste of bits, and I apologize for the noise.

Thanks,
--
Paul Procacci
Manager, UNIX Support Services
Datapipe Managed Global IT Services
1.201.792.4847 (international)
1.888.749.5821 (toll free)

This message may contain confidential or privileged information.  If you ar=
e not the intended recipient, please advise us immediately and delete this =
message.  See http://www.datapipe.com/about-us-legal-email-disclaimer.htm f=
or further information on confidentiality and the risks of non-secure elect=
ronic communication. If you cannot access these links, please notify us by =
reply message and we will send the contents to you.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100429053405.GB18122>