similar to: VFS: Cannot open root device, pxelinux nfsroot

I seem to be having trouble getting the NFS root filesystem to mount after the kernel boots. As per thread from 2002 16 January (http://www.zytor.com/pipermail/syslinux/2002-January/000028.html), I double checked my DHCP config files, but to no avail. It cannot seem to attach to the mountd port on the bootserver. Here is some output from the kernel: loop: loaded (max 8 devices) Intel(R) PRO/1000

Hello everyone, I am using pxelinux to boot kernel from network, which goes ok. But when root must be mounted from NFS, I get the following code: Looking up port 100003/2 on 192.168.1.1 RPC: sendmsg returned error 22 portmap: RPC call returned error 22 ROOT-NFS: unable to get nfsd port number from server, using default looking up port of RPC 100005/1 on 192.168.1.1 RPC: sendmsg returned error

Good morning, I try to use the last release of ext3 patch with a 2.4.10 linux kernel. I have two troubles : - when the kernel is booting, I receive : NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 208k freed Adding Swap: 128480k swap-space (priority -1) Adding Swap: 128480k swap-space (priority -2) Why my root

I ran some iperf tests today and it looks like the etherbridge is the limiting factor on throughput. In the beforetime, I saw great throughput to the VMs; over 800 Mbps. With the bridge, the numbers are in the 400s somewhere. Is this the speed I can expect from the bridge? Is there some tuning I should try, or another way to get more bandwidth into the VMs? This is with xen-2.0, 2.4.27-xen0

any comments? if nothing else, is there any way to atomically setup bridge? not on list, please cc. ---------- Forwarded message ---------- Date: Wed, 12 Jan 2005 21:08:15 -0000 From: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> To: Adam Sulmicki <adam@cfar.umd.edu>, xen-devel@lists.sourceforge.net Subject: RE: [Xen-devel] nfsroot and brige > hello, > it seems like a catch-22 to

I think this is another one of the same kind of bugs in ts: Version 0.64.1 (May 8, 1999) ... > z <- ts(matrix(1:20,10,2), start=c(1969,1), frequency=12) > (z > 5) | (z < 2) Error: invalid time series parameters specified > Paul -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list -- Read

Hy Can you tell me how i can say syslinux that the Kernel should be load the filesystem from a server? Is that possible with the syslinux.cfg timeout 0 append root=/dev/nfs ip=bootp # append initrd=rootimg.gz ? Should i load the file to first or should i load syslinux at first? Can i load a linux kernel on a partion with 31 MB? cheers Julian Sorry for my bad english! -- +++ GMX -

Hi, Thanks for your reply Josef. > In netstat -p |grep rpc I get: > dgram 56732 rpc.nfsd > dgram 55905 rpc.mountd > While client looks for socket 100003/2 or 100005/1, mine rpc.mountd is on socket 55905. Maybe it is a reason for an error 22. >The port numbers are RPC numbers, not sockets. Try 'rpcinfo -p' for these. rpcinfo -p 100005 mountd 100003 nfs So this looks

Maybe this question is a little stupid, but please help me. I am a newbie to Xen. When I tried to create a new domain "domain 1", I followed the Yan-Ching CHU''s guide on :installing quick file systems for new domains in Xen 1.2". But when I do "xc_dom_create.py -Dvmid=1", Xen seems to start to boot with some normal bootup information, but right after several

Does anyone have any good how-to's or documentation on setting up read only root NFS for pxe booting diskless computers? A few months ago I stumbled upon an official Redhat doc through a google search(not hosted by redhat and I cannot find it anywhere on the Redhat site) written by Dave Kline named "Configuring diskless clients with Red Hat Enterprise Linux" from 2011. It seemed to

Hi! Bored by previous lhype success, I tried to boot a debootstrapped debian over nfsroot, and lo, this almost works! Commandline: # drivers/lhype/lhype_add 256m 0 ./vmlinux --tunnet=192.168.1.20 root=/dev/root nfsroot=/home/ahu/lhype-root ip=192.168.1.21:192.168.1.20:192.168.1.20 This with lhype.patch current as of this message and 2.9.20-rc4. The boot process stops after: Starting periodic

Hi! Bored by previous lhype success, I tried to boot a debootstrapped debian over nfsroot, and lo, this almost works! Commandline: # drivers/lhype/lhype_add 256m 0 ./vmlinux --tunnet=192.168.1.20 root=/dev/root nfsroot=/home/ahu/lhype-root ip=192.168.1.21:192.168.1.20:192.168.1.20 This with lhype.patch current as of this message and 2.9.20-rc4. The boot process stops after: Starting periodic

Hi, I've got a task to have a small number of laptops netboot Linux over WiFi. The kernel is loaded off the USB stick of cource, it's off topic for now. The WPA-supplicant daemon is started early by dracut off initrd. It works. Mostly. The problem is that upon shutdown systemd terminates all the processes FIRST and unmounts filesystems NEXT. Guess what? Upon termination,

Hello all, I have observed a problem with a diskless PXE client I am attempting to configure. PXE/NFS/DHCP/TFTPd server is running CentOS5.1 and the Diskless workstation's root and kernel was extracted from a CentOS5.1 (custom kernel due to setting to enable Root File System support). Problem: When the diskless client boots and logs in I notice that my root user is being squashed, even if I

Hi, I'm trying to deploy some non-linux OS via pxe and I was thinking to just launch CentOS in RAM and then run dd or qemu-img or something like this in order to complete the other OS install via template imaging. My first idea was to build a custom CentOS livecd and use that in combination with pxe kernel parameters, but perhaps there's a better way to do this. Ideas? Thanks, Lucian --

Are you saying that REDIRECT hasn't been or that it has suddenly stopped working? My guess would be that it hasn't been working. Here's why: The REDIRECT target is in the NAT table because it is designed to redirect the port of packets destined for the interface they arrived on. If I understand right your situation is like this: (Users) -----> (eth2) <Bridge (192.168.0.3)>

----- Original Message ----- From: Karl Heyes <karl@pts.tele2.co.uk> To: <icecast@xiph.org> Sent: Friday, January 31, 2003 5:29 PM Subject: Re: [icecast] Re: Compiling ices <p>> On Fri, 2003-01-31 at 06:39, Marc Remijn wrote: > ... > > > Kernel output: > > > > invalid operand: 0000 > > CPU: 0 > > EIP: 0010:[<d08e25b1>]

Hi, CONFIGURATION: the important part of my setup looks like that (smb.conf): [global] interfaces = net1 net2 net3 net4 net0 ; this is a router which acts as cross-subnet domain master + wins ; server local master = yes preferred master = yes domain master = yes wins support = yes dns proxy = no os level = 99 net1 - net4 are Win95, WinNT, Linux net0 are two samba-1.9.18p1 fileservers

in Documentation/nfsroot.txt, it says: 1.) Enabling nfsroot capabilities ----------------------------- In order to use nfsroot you have to select support for NFS during kernel configuration. Note that NFS cannot be loaded as a module in this case. The configuration script will then ask you whether you want to use nfsroot, and if yes what kind of auto configuration system you want to use.

I made a diskless node centos. the pxelinux.cfg/default file : default centos label centos kernel vmlinuz-2.6.18-194.el5 append initrd=initrd-2.6.18-194.el5.nfs.img nfsroot=10.10.10.1:/srv/centos ip=dhcp rw I can successfull*y boot-strap the system with no error.* *But when i shutdown or reboot it . It will show in the screen :* *Unmounting NFS filesystems* *INIT:no more process