Displaying 20 results from an estimated 4000 matches similar to: "PXE boot question"
2003 Dec 30
4
NFS error 101, again
Hi,
I've got another one... NFS error 101 with NFSROOT has been discussed a
lot, and hpa gave an answer to it which appears right. It's ENETUNREACH,
and I suspect my diskless box does not set its IP parameters right.
PXElinux is set up as follows:
label linvdr
kernel kernel-linvdr
append initrd=initrd-linvdr acpi=off root=/dev/nfs \
2008 Feb 27
2
NFSroot is acting strange in CentOS5
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
2003 Feb 03
1
Problems booting PXE-Client
Hi list,
I have installed DHCP, PXE and the TFTP-Server tftp-hpa. I'm running Debian
Woody on my server and I want to boot a PXE-Client with this server. I have
installed all as it is described in the docs found on the net.
Under root:
/tftpboot/
/tftpboot/X86PC/linux
/tftpboot/X86PC/linux/messages
/tftpboot/X86PC/linux/linux.0
/tftpboot/X86PC/linux/vmlinuz
2003 May 22
0
[PATCH 2.5.69 2/3] Remove NFS root support from the kernel
This patch removes support for use of NFS as a root filesystem from the
kernel. It also updates the documentation to reflect this.
b/Documentation/nfsroot.txt | 97 +++---
b/arch/arm/def-configs/a5k | 1
b/arch/arm/def-configs/adi_evb | 1
b/arch/arm/def-configs/adsbitsy | 1
b/arch/arm/def-configs/anakin | 1
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
2006 Apr 03
2
probs running stuff from initrd
Hello all
Now I may be way of whack here, so please forgive me.
I''m trying to merge xen with redhat''s config-netboot. The idea being a
kinda stateless domU. For those that haven''t seen you share a rootfs and
then bind mount all the individual files over then top, and the redhat
gui builds all the pxeboot config and stuff for you if you want a
diskless client. I
2002 Jul 03
1
syslinux 1.75
Hi all,
I'm setting up a diskless linux system using pxelinux. I have reached the
point where the kernel boots and init starts. However, I'am getting this
message:
INIT: version 2.78 booting
can't create lock file /etc/mtab~14: Read-only file system (use -n flag to
override)
INIT: Entering runlevel: 2
INIT: Id "1" respawning too fast: disabled for 5 minutes
INIT: no more
2006 Aug 23
1
CONFIG_ROOT_NFS?
I''m trying to build a linux/xen kernel that will run with an NFS root,
with out much luck.
I''ve edited src/xen-3.0.2-2/linux-2.6.16-xen/.config to include
CONFIG_NFS_FS=y (was =m)
CONFIG_ROOT_NFS=y (wasn''t there)
after running "make kclean" and make "kernels" CONFIG_ROOT_NFS is gone
(though the edit to CONFIG_NFS_FS remains):
#
# Network File
2005 Jan 05
1
[PATCH] kinit/nfsmount.c path from bootp
kinit/nfsmount.c:mount_nfs_root() should use the bootpath specified by
bootp/dhcp. If the "nfsroot" option is specified then it overrides the
boot server bootpath and a message indicating the override is printed.
--- klibc-0.194/kinit/nfsroot.c.orig 2005-01-05 04:13:47.043897880 -0700
+++ klibc-0.194/kinit/nfsroot.c 2005-01-05 04:13:09.316633296 -0700
@@ -66,34 +66,21 @@
const int
2015 Feb 05
0
Unable to PXE boot
> /diskless/pxelinux.cfg/default
> ---
> DEFAULT /gentoo-x86_64/boot/kernel-3.14.14-gentoo
> APPEND ip=dhcp ro rootfstype=nfs root=/dev/nfs
> nfsroot=10.0.0.11:/diskless/gentoo-x86_64
> init=/linuxrc
That pxelinux.cfg/default seems "tolerable" for older versions, but not
for Syslinux 5+.
Is this an inadequate copy of the actual content? Or is it really a
2003 Jul 17
2
PXE: Booting Diskless Node
Hi,
I have refered to ur documents for creating a Diskless
node in linux ,but could not get through the
installation .
The exact problem that i am facing is mention below ,
also, there r few queries, which i would be greatfull
if u can answer
First let me explain u what i have done .
I am trying the configuration with one server machine
and one client.
server configuration
256mb ram
AMD Athlon
2015 Feb 05
5
Unable to PXE boot
I'm replacing the master node in a cluster and having issues PXE booting
the diskless nodes. The current master works fine, but the new node to
replace the current node which has the same setup is having the issues.
The hardware is:
Dell r920 (new master node, UEFI)
Dell r620's (diskless, BIOS)
Dell 1950's (diskless, BIOS)
When trying to boot, the 1950 node displays (though both
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 15
1
RE: SYSLINUX digest, Vol 1 #102 - 4 msgs
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
2004 Sep 24
0
Client can't boot
Hi,
I'm trying to configure PXE syslinux to boot a diskless client but the
client can't find the PXE boot image. I've configured the DHCP server
as follows:
----------------------------
# cat /etc/dhcp3/dhcpd.conf
option domain-name "cluster.net";
option domain-name-servers 10.0.0.1;
default-lease-time 6048;
max-lease-time 604800;
log-facility local7;
subnet 10.0.0.0
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
#
2004 Mar 15
0
problems with pxelinux
Hi. I'm quite new in Linux under-the-hood. I'm trying to net-boot a
tablet Pc with no CD and FD. I successfully installed and configured
DHCP and TFTP.
I wrote a /tftpboot/pxelinux.cfg/default config file as follows:
> label linux_test
> kernel vmlinuz
> append root=initrd
but it seems to ignore the two directives "kernel" and "append" as
2002 Sep 04
2
PXE-E55 ProxyDHCP - No reply to request on port 4011
Hi:
First - pxelinux works great - got it up and running
with few problems.
However - I ran into a snag, I am assuming I have
a configuration issue. Here are the details.
Using: syslinux-1.75
dhcp-3.0pl1
tftp-hpa-0.29
A lot of what I have done is from:
http://frank.harvard.edu/~coldwell/diskless
dhcpd.conf:
# DHCP configuration file for DHCP ISC 3.0
ddns-update-style
2015 Aug 25
2
Looking for ways to save space - AKA how to boot multiple machines from the same root
I have several machines, same hardware and config, but one tiny little
change.. the hostname. Each one of these diskless machines needs its own
hostname.
Presently my pxelinux.cfg is setup like:
prompt 1
default Gentoo
timeout 10
label Gentoo
kernel boot/kernel-3.16.5-gentoo
APPEND root=/dev/nfs rw ip=dhcp
nfsroot=192.168.1.10:/RAID/diskless/XXXXX-mythtv-0.27-fixes,tcp,rsize=131072
2005 Jul 25
4
"missing" directories
Running Samba 3.0.14a under kernal 2.6.11-1.1369 (Fedora core 4)
I'm trying to set up a file server for use with XP network. I have an
interesting problem that came to light when I had difficulty connecting from
Windows.
I can set up a shared directory exactly as detailed in the troubleshooting
guide (setting up /tmp as tmp) and can connect from my account on the
server.
If I try to