Date: Thu, 05 Apr 2007 15:24:33 -0700 From: John Clark <jclark@metricsystems.com> To: Vladimir Botka <vlado@botka.homeunix.org> Cc: freebsd-current@freebsd.org Subject: Re: Strange NFS root booting behavior. Message-ID: <46157721.90707@metricsystems.com> In-Reply-To: <20070405080212.2d7d1c8d@srv> References: <46144FC6.3050801@metricsystems.com> <20070405080212.2d7d1c8d@srv>
next in thread | previous in thread | raw e-mail | index | archive | help
Vladimir Botka schrieb: > > Hello, > > try the script /usr/share/examples/diskless/clone_root to create copy > of the root. The procedure in > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-diskless.html > works for me. Just an idea but did you compile the diskless kernel with > "options BOOTP_NFSROOT" ? Well, I checked, and no those options are there. However, I was able to 'boot' to a working system on one piece of hardware, but not on another. While there could be a hardware problem, the place where it fails is not in a 'hardware intensive' place, such as initing the PCI bus, accessing i/o devices, but just after the initial rc script starts up. I've enabled the debug option in 'rc.initdiskless, and it gets to the point of remounting '/' as read/write. Now of course in a multiple client setup this would not be good, but in a single client, while it may not be the best thing to do, it shouldn't halt the init process and go to the /bin/sh mode... And any attempt to 'ls /', or 'ls /bin' cause a 'bad file descriptor' message. I'm at the moment recompiling the world on the working setup, and have put into a DISKLESS conf file the appropriate options, but I don't think that is the ultimate problem in this case. John Clark.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46157721.90707>