Diskless NFS boot stopping at rootfs
I'm trying to adapt a working 2.2.6 diskless booting arrangement to 3.0, for both clients and the server. The client machines load the kernel just fine, then I see NFS ROOT: 10.0.0.1:/export/boot/fs which is correct, but the process stops there. It doesn't get any further. I'm not sure if the machine is successfully mounting the root fs or not. There is no error after timeout, the client's IP does respond to pings. I have no configured swap, and while all the configurations I have seen did have nfs swap, my setup worked under 2.2.6 without it and I'd prefer to avoid it. Following is all the info that seemed pertinent. These configs are with very few changes (IP numbers and such) the ones that worked under 2.2.6. If you reply, please reply to me directly, I'm not subscribed to the list. Thank you in advance for your help. --- My 3.0 kernel config for the clients: machine "i386" cpu "I586_CPU" identSNX maxusers 16 options NO_SWAPPING options BOOTP options BOOTP_NFSROOT options INET#InterNETworking options FFS #Berkeley Fast Filesystem options MFS #Memory Filesystem options NFS #Network Filesystem options NFS_ROOT#NFS usable as root device, "NFS" req'ed options PROCFS #Process filesystem options "COMPAT_43"#Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE#Allow users to grab the console options FAILSAFE#Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor config kernel root on wd0 controller isa0 controller eisa0 controller pci0 device sc0 at isa? port "IO_KBD" conflicts tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr device ed0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector edintr pseudo-device loop pseudo-device ether pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's options KTRACE #kernel tracing options SYSVSHM --- A sample entry from my bootptab: dslsupport01:\ :ht=ether:\ :ha=00400568cd52:\ :sm=255.255.255.0:\ :hn:\ :ip=10.0.0.31:\ :gw=10.0.0.1:\ :rp=/export/boot/fs:\ :bf=kernel:\ :td=/export/boot/fs:\ :vm=rfc1048: --- A sample tftp config file: rootfs 10.0.0.1:/export/boot/fs hostname dslsupport01 --- The contents of the clients /etc/rc file: #!/bin/sh PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin export PATH TERM=vt100 export TERM clear echo; echo; echo echo "Please be patient while the system comes up..." echo; echo; echo #/sbin/ldconfig /usr/lib /usr/lib/compat /usr/X11R6/lib ifconfig lo0 127.0.0.1 #mount -t nfs -u 10.0.0.1:/export/boot/fs / mount -a #if [ -f /dev/audio ]; then /usr/X11R6/bin/au :8086 -aa & echo "Starting auserver on port 8086..." #fi while [ 1 -eq 1 ]; do /usr/X11R6/bin/XF86_S3V -bpp 16 -query deimos done --- The contents of the clients /etc/fstab: 10.0.0.1:/export/boot/fs/ nfs ro 0 0 10.0.0.1:/export/boot/dev /devnfs rw 0 0 /dev/null /tmpmfs rw,-T=tmp 0 0 --- Nicholas Esborn | www.azstarnet.com | StarNet (520) 618-RTFM | To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Diskless boot stopping at "NFS ROOT:..."
This is a problem I have had on two seperate systems, running 3.0-RELEASE and now 3.1-STABLE built about a week ago. The systems were brought up seperately. Unfortunately since this machine never comes up to any usable state, I don't have detailed logs of its boot output. I'll try to summarize: I compiled the 3.1-S kernel with KERNFORMAT=aout and placed it in /usr/local/netboot/fs/, my NFS rootfs. The following dirs were cpio'd from the host system: drwxr-xr-x 2 root wheel 512 Mar 13 17:51 bin drwxr-xr-x 2 root wheel 1024 Mar 13 17:52 lkm drwxr-xr-x 2 root wheel 1536 Mar 13 17:52 sbin drwxr-xr-x 4 root wheel 512 Mar 13 17:52 stand I made usr and cpio'd the following dirs into it: drwxr-xr-x 2 root wheel 6144 Mar 13 18:03 bin drwxr-xr-x 3 root wheel 512 Mar 13 18:03 compat drwxr-xr-x 4 root wheel 3584 Mar 13 18:05 lib drwxr-xr-x 9 root wheel 512 Mar 13 18:05 libdata drwxr-xr-x 7 root wheel 1024 Mar 13 18:07 libexec drwxr-xr-x 2 root wheel 3584 Mar 13 18:07 sbin drwxr-xr-x 26 root wheel 512 Mar 13 18:15 share I made etc and copied ttys into it. I made the following rc: #!/bin/sh echo 'STARTING UP' PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin export PATH ifconfig lo0 inet 127.0.0.1 netmask 0x mount -t nfs -u 10.0.0.1:/export/boot/fs / mount -a /sbin/ldconfig -elf /usr/lib /usr/lib/compat /usr/X11R6/lib while [ 1 -eq 1 ]; do /usr/X11R6/bin/XF86_S3 -bpp 16 -query deimos done The mounting stuff may be problematic, but it doesn't look like rc is even running... The clients find the kernel and start booting, goes through its bootpc configuration obtaining all the right numbers, prints: NFS ROOT: 10.0.0.1:/usr/local/netboot/fs and stops. I have to hard power cycle the client. The kernel is GENERIC with BOOTP, BOOTP_NFSROOT, "BOOTP_NFSV3", and BOOTP_COMPAT. I can't tell if the nfs flags are getting set in the kernel, as the machine never comes up to a shell. Here's the irony: I can currently get 2.2.x booting through almost the same procedures and setups (only differing where 2.2.x and 3.x features differ). Any ideas? Thank you for your time either way. Please respond to me by email as I'm not on the mailing lists. Nick Esborn To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Diskless boot stopping at "NFS ROOT:..."
Thanks for the pointer. This seems to have been the problem and I have it booting now. As a followup, is it possible to specify boot parameters (i.e. splash screen, pnp config, etc) on a machine that is net booting? Thanks for the help. Nick On Sun, 14 Mar 1999, Matthew Dillon wrote: > I had a very weird problem with the new parallel port device that caused > this to occur. It turned out to be speculative probing by the parallel > device causing the system to go unstable. > > Try disabling the new parallel port device(s)/controllers and see if you > can boot again. > > -Matt > > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD 5.0 and Dell notebooks
:37 assisi kernel: miibus0: detached Jan 14 21:39:37 assisi kernel: xl0: detached Jan 14 21:39:37 assisi kernel: wakeup from sleeping state (slept 00:00:23) Jan 14 21:39:37 assisi kernel: ata0: resetting devices .. Jan 14 21:39:37 assisi kernel: done Jan 14 21:39:37 assisi kernel: ata1: resetting devices .. Jan 14 21:39:37 assisi kernel: done Jan 14 21:39:37 assisi kernel: Manufacturer ID: 01015752 Jan 14 21:39:37 assisi kernel: Product version: 5.0 Jan 14 21:39:37 assisi kernel: Product name: 3Com Corporation | 3CCFE575CT | LAN Cardbus Card | 004 | Jan 14 21:39:37 assisi kernel: Functions: Network Adaptor, Memory Jan 14 21:39:37 assisi kernel: CIS reading done Jan 14 21:39:37 assisi kernel: cardbus0: Resource not specified in CIS: id=14, s ize=80 Jan 14 21:39:37 assisi kernel: cardbus0: Resource not specified in CIS: id=18, s ize=80 Jan 14 21:39:37 assisi kernel: xl0: <3Com 3c575C Fast Etherlink XL> port 0x1000- 0x103f mem 0x88002000-0x8800207f,0x88002080-0x880020ff irq 11 at device 0.0 on c ardbus0 Jan 14 21:39:37 assisi kernel: xl0: Ethernet address: 00:01:02:79:29:d4 Jan 14 21:39:37 assisi kernel: miibus0: on xl0 Jan 14 21:39:37 assisi kernel: tdkphy0: on miibus0 Jan 14 21:39:37 assisi kernel: tdkphy0: 10baseT, 10baseT-FDX, 100baseTX, 100bas eTX-FDX, auto I hope this info helps. -nick On Wed, Jan 15, 2003 at 03:23:56AM +0300, Kirill Bezzubets wrote: > On Tue, Jan 14, 2003 at 01:34:09PM -0800, Lars Eggert wrote: > > I'm afraid it's not ATI-related. I have Latitude CPi with NeoMagic2160 - > suspend works ok, but at resume screen goes on for a second and then off. > ... > Machine is live after resume too, blind reboot works ok. > ... > Another note: after resume I tried to work with the machine using ssh > consoles - after some time (not so long - about minute or so) it completely > hangs repeating some strange ACPI error. Sorry, can't repeat it for now > and no traces left in dmesg/messages.. > -- Nicholas Esborn Unix Systems Administrator Berkeley, California To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Serve NFS from within a jail?
Hello, I'm hoping to configure NFS service within a jail on a 5.1-CURRENT box. The host envjailedment isn't running any services except ssh, and the jail(8) man page leads me to believe the author thought NFS service would work from within a jail. However, neither mountd nor nfsd are happy running inside the jail: Oct 22 23:32:06 jailed mountd[1249]: can't delete exports for /: Operation not permitted Oct 22 23:32:06 jailed mountd[1249]: can't delete exports for /tmp: Operation not permitted Oct 22 23:32:06 jailed mountd[1249]: can't delete exports for /usr: Operation not permitted Oct 22 23:32:06 jailed mountd[1249]: can't delete exports for /var: Operation not permitted Oct 22 23:32:06 jailed mountd[1249]: can't delete exports for /foo: Operation not permitted Oct 22 23:32:06 jailed mountd[1249]: can't change attributes for /foo/share Oct 22 23:32:06 jailed mountd[1249]: bad exports list line /foo/share -maproot Oct 22 23:32:06 jailed nfsd[1255]: nfssvc: Operation not permitted Oct 22 23:32:06 jailed nfsd[1256]: nfssvc: Operation not permitted Oct 22 23:32:06 jailed nfsd[1257]: nfssvc: Operation not permitted Oct 22 23:32:06 jailed nfsd[1254]: nfssvc: Operation not permitted Oct 22 23:32:06 jailed nfsd[1252]: can't Add UDP socket Any suggestions? Thanks, -nick ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
