similar to: PXE/NFS Root Problem

Displaying 20 results from an estimated 10000 matches similar to: "PXE/NFS Root Problem"

2002 Apr 27
1
NFS Kernel Panic (can't find init)
Hello, I appreciate the help. I am able to mount the nfs root share to a directory and then chroot to it and pull up a shell. Everything seems fully functional from there and I can run all the programs I checked. Wasn't sure how to manually test the init command. When I type /sbin/int it prints the proper format for an init command and when I type /sbin/init S, I just get a carriage return.
2005 Aug 23
6
NFS-root problem
I have been googling and searching the archive , haven''t got anything helpful. Would appreciate any help. Got the follow error when trying to start a domain using NFS root IP-Config: Incomplete network configuration information. Looking up port of RPC 100003/2 on 10.10.24.141 <http://10.10.24.141> RPC: sendmsg returned error 101 portmap: RPC call returned error 101 Root-NFS:
2002 Jun 12
7
VFS: Cannot open root device, pxelinux nfsroot
Hi everyone, I got the error: NET4: Unix domain sockets 1.0/smp for linux NET4.0 ds: no socket drivers loaded request_module[block-major-8]: root fs not mounted VFS: Cannot open root device ""or 08:03 Please append a correct "root"boot option The strange thing is that it tries to mount from harddisk. This I got somewhere else: "the kernel looks like it is trying to
2003 Sep 13
0
PXELinux Kernel NFS Root Errors
Hi This is a PXELinux problem that I'm facing. The problem, in brief, is that I have a set of diskless nodes (AMD Athlon XP 1800+ with 256MB RAM) connected via an internal 172.20.0.0/24 network to a dual AMD Opteron running SuSE Linux 8.3 for AMD64. I want the remote machines to diskless boot off the main server and run independently. The diskless machines have a PXE-compliant BIOS for
2002 May 14
3
network boot nfs as root
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
2009 Nov 30
3
NFS new security requirements?
Hi I've suddenly lost access to some permanent cross-server shares. I think this was following the Nov 5 new kernel, rather than the Centos version upgrade. I don't see any difference to man mount.nfs I have:- [root at hs6 ~]# mount hs8:/data /sysback/hs8-data -v mount: no type was given - I'll assume nfs because of the colon mount: trying 172.26.0.8 prog 100003 vers 3 prot tcp port
2008 Nov 04
1
Reexporting glusterfs to nfs fail
Hi, I have a machine that must to reexport glusterfs to nfs. CONFIGURATION 2 glusterfs servers | ?| ? | 1 gluterfs client 1 nfs server ?| ?| ?| 1 nfs client #*********************************************** # GLUSTERFS SERVER ?#*********************************************** # Export with glusterfs $ glusterfs -f /etc/glusterfs/glusterfs-server.vol $ cat
2010 Apr 21
3
Help with NFSV4 server
Hi Everyone, I have been trying to setup an NFS v4 File Server but have come across an odd issue. Mounting the /nfs4exports/share appears to be successful and the information displayed about partition size and free space seem correct but if I try to do anything inside the mounted directory the client will just hang. Does anyone have any idea what I am missing?? I have try disabling all
2008 Feb 26
1
PXE client is root squashing ...
Hello all, Though the question is NFS-related, it is in conjunction with the PXE booting. Issue/Scenario: - PXE/DHCP/NFS and tFTP server running CentOS51 and is configured per PXE/Syslinux and RHEL diskless workstation documentation. 1. Attempt to test ability for client to PXE boot over the network and run Root-NFS 2. NFS export in the PXE server is: # # NFS Export Files for qatest1 host #
2008 Feb 25
1
NFS options on kernel parameters
Hello, I am running an NFS server/PXE on a Cent OS 5.1 server. I have defined an NFS export with "no_root_squash" option in my /etc/exports file: # # NFS Export Files # /export/images *(rw,sync,no_root_squash) ... A client PXE boots as a diskless station to the above server into a root-NFS directory underneath the above /export/images export. When the client boots;
2019 Oct 28
1
NFS shutdown issue
Hi all, I have an odd interaction on a CentOS 7 file server. The basic setup is a minimal 7.x install. I have 4 internal drives (/dev/sd[a-d]) configured in a RAID5 and mounted locally on /data. This is exported via NFS to ~12 workstations which use the exported file systems for /home. I have an external drive connected via USB (/dev/sde) and mounted on /rsnapshot. I use rsnapshot to back up
2020 Nov 12
1
nfs root kerberos
On 12/11/2020 14:19, Jason Keltz via samba wrote: > > On 11/12/2020 8:52 AM, Rowland penny via samba wrote: >> On 12/11/2020 13:27, Jason Keltz via samba wrote: >>> >>> On 11/12/2020 8:17 AM, Rowland penny via samba wrote: >>>> On 11/11/2020 10:54, Jason Keltz via samba wrote: >>>>> Hi Louis, >>>>> I've looked into that
2009 Aug 11
1
[PATCH server] remove appliance bits
This removes the appliance configuration bits from the installer and associated files since it has been deprecated --- installer/modules/ovirt/files/cobbler-import | 6 - .../modules/ovirt/files/ovirt-appliance-setup | 4 - installer/modules/ovirt/files/ovirt-storage | 73 ---------- installer/modules/ovirt/manifests/appliance.pp | 152 -------------------- 4 files
2020 Nov 09
2
nfs root kerberos
Hi. I have Samba AD configured correctly, and can mount kerberized NFS from all the CentOS 7 clients.? I'm not able to use "root" on the client even though the nfs export specifies the option: no_root_squash option. I completely understand that in order to use the "root" identity (which doesn't exist as a user in the domain) on the NFS client, this identity has to
2020 Nov 12
2
nfs root kerberos
On 12/11/2020 13:27, Jason Keltz via samba wrote: > > On 11/12/2020 8:17 AM, Rowland penny via samba wrote: >> On 11/11/2020 10:54, Jason Keltz via samba wrote: >>> Hi Louis, >>> I've looked into that and I'm not sure how this would be done? >>> By the way, even with your NFS translation fix (which doesn't work >>> for me because
2010 Feb 18
3
NFS client firewall config?
Hi all, Which ports do I need to have open on an NFS client's firewall to allow it to connect to a remote NFS servers? When I disable iptables (using ConfigServerFirewall), it connects fine, but as soon as I enable it, NFS gives me this error: root at saturn:[~]$ mount master1.mydomain.co.za:/saturn /bck mount: mount to NFS server 'master1.mydomain.co.za' failed: RPC Error: Unable to
2002 Mar 22
1
PXE: Some basic questions
First of all it works great!! I have my 3Com cards booting off the network and it grabs the linux kernel just fine. My next problem is more of me not understanding the rules. Is the /tftpboot directory just like /? My though was to take a Linux rescue disk that had some imaging tools and then just put the whole thing in /tftpboot and tell it to boot the kernel in that directory. But I always
2006 Feb 28
1
vpopmail over NFS not seeing new messages.
Hi all. We've just migrated our back-end NFS mailstore from FC1 systems to CentOS4 and are experiencing problems/delays with vpopmail and user Maildirs. IMAP is fine, it's just POP access that causes us problems. Now, NFS mounts successfully, the clients can see /home/vpopmail and serve content as we would expect. IMAP works perfectly and sees new messages as soon as they're
2011 Aug 22
2
btrfs over nfs
I have been experimenting exporting btrfs subvolumes over nfs. Main subvolume is filesys1 mounted at /filesys1. Below this is subvolume base, user1 is in base and documents is in user1. documents is mounted at /documents. /etc/exports is: /filesys1/base/user1 172.16.0.0/24(rw,no_acl,no_root_squash,fsid=0) /filesys1/user1-snapshot 172.16.0.0/24(rw,no_acl,no_root_squash,fsid=0)
2009 Dec 18
1
mountd and statd at specific ports - nfs firewall
Hi, I am configuring firewall for NFS. I see that statd and mountd start at random port. Is there any way to force it to start at specific port each time. The '-p ' option would work, but how do I configure it to start at specific port number each time. I mean where do statd and mountd look for default configuration options? Any clues? - CS.