From owner-freebsd-questions Fri Mar 16 2:41:41 2001 Delivered-To: freebsd-questions@freebsd.org Received: from ibis.worldnet.net (ibis.worldnet.net [195.3.3.14]) by hub.freebsd.org (Postfix) with ESMTP id 4004737B718 for ; Fri, 16 Mar 2001 02:41:38 -0800 (PST) (envelope-from briceg@worldnet.net) Received: from m3.worldnet.net (m2.worldnet.net [195.3.3.6]) by ibis.worldnet.net (8.11.2/8.11.1) with ESMTP id f2GCaA735970 for ; Fri, 16 Mar 2001 13:36:10 +0100 (CET) (envelope-from briceg@worldnet.net) Received: from salegoth.worldnet.net (nat-srv1.kaptech.net [195.3.9.4]) by m3.worldnet.net (8.11.2/8.11.1) with ESMTP id f2GAfQM21311 for ; Fri, 16 Mar 2001 11:41:27 +0100 (CET) (envelope-from briceg@worldnet.net) Message-Id: <4.3.1.0.20010316111309.02847d60@mail.worldnet.net> X-Sender: briceg@mail.worldnet.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Fri, 16 Mar 2001 11:44:55 +0100 To: freebsd-questions@FreeBSD.org From: Brice Gensburger Subject: top: nlist failed with FreeBSD 4.2 RELEASE and 4.3 BETA Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We have some strange problem with a FreeBSD install. Here's the trick: with a freshly installed FreeBSD 4.2: bash-2.04$ top top: nlist failed bash-2.04$ pstat pstat: undefined symbol: _numvnodes at first, i thought: ok, let's redo a kernel and make the world.. the box is now 4.3 BETA $ uname -a FreeBSD zinc 4.3-BETA FreeBSD 4.3-BETA #0: Thu Mar 15 11:06:54 CET 2001 root@oxygen.psi1.kapt.net:/mnt/sys/FreeBSD/KAPTECH-1/src/sys/compile/KAPTECH-1 i386 $ top top: nlist failed $ pstat pstat: undefined symbol: _numvnodes after searching the web for help, i've found some hints to a problem with boot: http://ns.xinetd.com/freebsd/msg00518.html and, http://www.geocrawler.com/archives/3/151/2001/1/0/5044722/ the last one says: This is the error you get when you don't boot via /boot/loader. If your boot0 is loading your kernel directly, it doesn't have all of the necessary symbols at runtime. ok, i can buy that, because we're trying to setup an automatic install for freeBSD, and, since it's not standard, it may well be the root of the problem.. ( brief overview: we boot with PXE, get an IP with DHCP, get an MFS.root done with the 4.2 RELEASE stock kernel, an install.cfg for sysinstall.. sysinstall executes, and finally mount a NFS to get at a copy of the 4.2R CD and install files from this one. i must stress all we changed was the install.cfg, to have sysinstall run non-interactive with the defaults that pleased us on our other installs. http://matt.simerson.net/computing/freebsd.netboot.shtml ) For what i see from the boot sequence, once the install is over and the server boot from disk, /boot/loader isn't run. i don't see the Btx loader anywhere... i've looked at the man pages for boot, boot0cfg, the FreeBSD handbook, and the Complete FreeBSD i bought a few months ago, and i didn't find how to correct the boot sequence.. :-| i ran /stand/sysinstall, to reinstall the Boot Manager, to no avail... any idea? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message