View previous topic :: View next topic |
Author |
Message |
floydalbert n00b
Joined: 06 Jan 2013 Posts: 4
|
Posted: Mon Jan 21, 2013 1:40 pm Post subject: Diskless: not mount NFS root (solved) |
|
|
Problem: It will not mount the NFS root! Is it due to DHCP or NFS. On the NFS server is working. I have root mounted from a Ubuntu. With fall on the after load of bzImage no DHCP request is being transmitted. I've searched the forum for similar entries. Could not solve my problem.
I have installed the server according to these instructions:
http://www.gentoo.org/doc/en/diskless-howto.xml
Messages:
VFS: Unable to mount root fs via NFS. trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2.0): error -6
Please append a correct "root:" boot option: here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknwn-block(2.0)
Code: | tail -f /var/log/messages
Jan 21 13:54:31 server dhcpd: DHCPDISCOVER from 00:50:56:31:8a:1b via eth0
Jan 21 13:54:31 server dhcpd: DHCPOFFER on 10.10.1.21 to 00:50:56:31:8a:1b via eth0
Jan 21 13:54:33 server dhcpd: DHCPREQUEST for 10.10.1.21 (10.10.1.101) from 00:50:56:31:8a:1b via eth0
Jan 21 13:54:33 server dhcpd: DHCPACK on 10.10.1.21 to 00:50:56:31:8a:1b via eth0
Jan 21 13:54:33 server in.tftpd[17202]: RRQ from 10.10.1.21 filename pxelinux.0
Jan 21 13:54:33 server in.tftpd[17202]: tftp: client does not accept options
Jan 21 13:54:33 server in.tftpd[17203]: RRQ from 10.10.1.21 filename pxelinux.0
Jan 21 13:54:33 server in.tftpd[17204]: RRQ from 10.10.1.21 filename pxelinux.cfg/564da66c-52c9-0218-beb7-9557184d314e
Jan 21 13:54:33 server in.tftpd[17205]: RRQ from 10.10.1.21 filename pxelinux.cfg/01-00-50-56-31-8a-1b
Jan 21 13:54:33 server in.tftpd[17206]: RRQ from 10.10.1.21 filename pxelinux.cfg/0A0A0115
Jan 21 13:54:33 server in.tftpd[17207]: RRQ from 10.10.1.21 filename pxelinux.cfg/0A0A011
Jan 21 13:54:33 server in.tftpd[17208]: RRQ from 10.10.1.21 filename pxelinux.cfg/0A0A01
Jan 21 13:54:33 server in.tftpd[17209]: RRQ from 10.10.1.21 filename pxelinux.cfg/0A0A0
Jan 21 13:54:33 server in.tftpd[17210]: RRQ from 10.10.1.21 filename pxelinux.cfg/0A0A
Jan 21 13:54:33 server in.tftpd[17211]: RRQ from 10.10.1.21 filename pxelinux.cfg/0A0
Jan 21 13:54:33 server in.tftpd[17212]: RRQ from 10.10.1.21 filename pxelinux.cfg/0A
Jan 21 13:54:33 server in.tftpd[17213]: RRQ from 10.10.1.21 filename pxelinux.cfg/0
Jan 21 13:54:33 server in.tftpd[17214]: RRQ from 10.10.1.21 filename pxelinux.cfg/default
Jan 21 13:54:33 server in.tftpd[17215]: RRQ from 10.10.1.21 filename /bzImage
|
Code: | grep NFS /usr/src/linux/.config_slave
CONFIG_NFS_FS=y
CONFIG_NFS_V2=y
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
# CONFIG_NFS_V4 is not set
CONFIG_ROOT_NFS=y
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
# CONFIG_NFSD_FAULT_INJECTION is not set
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y
CONFIG_NCPFS_NFS_NS=y
|
Code: | grep DHCP /usr/src/linux/.config_slave
CONFIG_IP_PNP_DHCP=y
|
Code: |
cat /diskless/pxelinux.cfg/default
DEFAULT /bzImage
APPEND ip=dhcp root=/dev/nfs nfsroot=10.10.1.101:/diskless/10.10.1.21
|
Last edited by floydalbert on Tue Jan 22, 2013 3:11 pm; edited 1 time in total |
|
Back to top |
|
|
BasketCase n00b
Joined: 02 Sep 2003 Posts: 67 Location: Orlando, FL
|
Posted: Mon Jan 21, 2013 8:56 pm Post subject: |
|
|
Is there any useful information before the VFS lines? |
|
Back to top |
|
|
floydalbert n00b
Joined: 06 Jan 2013 Posts: 4
|
Posted: Tue Jan 22, 2013 8:54 am Post subject: |
|
|
Thanks for the help!
The screen output in more detail.
Code: | registered taskstats version 1
input: AT Translatet Set 2 keyboard as /device/platform/i8042/serial0/input/input0
input: ImPs/2 Generic Wheel Maouse as /devices/platform/i8042/serial0/input/input1
md: Waiting for all devices to be available before autodetect
md: Id you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: autorun DONE.
VFS: Unable to mount root fs via NFS. trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2.0): error -6
Please append a correct "root:" boot option: here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknwn-block(2.0)
Pid: 1, comm swapper/0 Not tainted 3.5.7-gentoo #3
Call Trace:
[<c045417e>] panic+0x7d/0x179
[<c05f8d0e>] mount_block_root+0x15e/0x16d
[<c01cafc8>] ? sys_mknod+0x15/0x17
[<c05f8e9c>] mount_root+0xc6/0xd1
[<c05f8fec>] prepare_namespace+0x145/0x16c
[<c05f8a6a>] kernel_init+0x180/0x18f
[<c05f88ea>] ? start_kernel+0x2d8/0x2d8
[<c045bf76>] kernel_thread_helper+0xc/0xd |
tcpdump host 10.10.1.101 and 10.10.1.21
Code: |
...
09:23:20.932511 IP 10.10.1.21.49163 > 10.10.1.101.45026: UDP, length 4
09:23:24.929759 ARP, Request who-has 10.10.1.21 tell 10.10.1.101, length 28
09:23:25.929794 ARP, Request who-has 10.10.1.21 tell 10.10.1.101, length 28
09:23:26.929829 ARP, Request who-has 10.10.1.21 tell 10.10.1.101, length 28
The "... ARP, Request who-has ..." Messages are available when the screen message
"input: ImPS / 2 Generic Wheel Maouse as / devices/platform/i8042/serial0/input/input1" |
|
|
Back to top |
|
|
floydalbert n00b
Joined: 06 Jan 2013 Posts: 4
|
Posted: Tue Jan 22, 2013 12:12 pm Post subject: More troubleshooting: |
|
|
Have the file "/diskless/pxelinux.cfg/default" and change "Prompt 1" inserted:
Code: | DEFAULT /bzImage
PROMPT 1
APPEND ip=dhcp root=/dev/nfs nfsroot=10.10.1.101:/diskless/10.10.1.21
|
Then I can enter boot parameters. After that I found by the command: "tcpdump host 10.10.1.101 and 10.10.1.21"
the issue:
"... ARP, Request who-has 10.10.1.101 tell 10.10.1.21, ..."
Even before the coming of bzImage boot so the boot from "pxelinux.0". That means it will boot from after the "bzImage" no dhcp request is sent.
As input in the prompt I typed the following line:
Code: | boot: bzImage ip=dhcp root=/dev/nfs nfsroot=10.10.1.101:/diskless/10.10.1.21 |
I do not know if the syntax is correct? The behavior is as always!
It is probably the kernel? |
|
Back to top |
|
|
floydalbert n00b
Joined: 06 Jan 2013 Posts: 4
|
Posted: Tue Jan 22, 2013 3:10 pm Post subject: solved |
|
|
Thanks for your interest! I found the error. It was compiled not the driver in the kernel. |
|
Back to top |
|
|
|