Meldung: "Unable to mount root fs via NFS"

Kreuzuebersetzer, Diskussion über Änderungen im Tuxbox-CDK und Tuxbox-CVS
Skitoni
Interessierter
Interessierter
Beiträge: 20
Registriert: Samstag 22. November 2003, 21:53

Meldung: "Unable to mount root fs via NFS"

Beitrag von Skitoni »

Jetzt hab' ich endlich eine YADD selbst erstellen können ... leider bekomme ich beim booten aber eine mount-Fehlermeldung :-( . Als NFS-Directory hab' ich "cdkroot" angegeben (sieht man auch unten).

Linux video capture interface: v1.00
mice: PS/2 mouse device common for all mice
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 192.168.123.100
RPC: sendmsg returned error 101
portmap: RPC call returned error 101
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 192.168.123.100
RPC: sendmsg returned error 101
portmap: RPC call returned error 101
Root-NFS: Unable to get mountd port number from server, using default
RPC: sendmsg returned error 101
mount: RPC call returned error 101
Root-NFS: Server returned error -101 while mounting F/cdkroot/
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or 02:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 02:00
<0>Rebooting in 180 seconds..

Kann mir jemand weiterhelfen? DANKE!

Grüße,
Skitoni
DieMade
Oberlamer, Administrator & Supernanny
Beiträge: 10532
Registriert: Samstag 13. Juli 2002, 10:49

Beitrag von DieMade »

#define ENETUNREACH 101 /* Network is unreachable */


Wie sieht die Konfiguration Deines Netzwerks aus? Ein komplettes Log schadet auch nie.
There are 10 types of people in the world: those who know binary and those who don't
Skitoni
Interessierter
Interessierter
Beiträge: 20
Registriert: Samstag 22. November 2003, 21:53

Beitrag von Skitoni »

Ich hab folgende Konfigurationen probiert:

PC<->Router<->DBox
PC<->Switch<->DBox
PC<->CrossCable<->DBox

Betriebssystem. Windows XP
Netzwerkkarte: 10MBit Halb-Duplex eingestellt
Box: Nokia Sat

Der Log sieht wir folgt aus:

cdebug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS
debug: BMon V1.2 mID 01
debug: feID dd gtxID 0b
debug: fpID 5a dsID 01-1e.50.1c.07.00.00-b0
debug: HWrev 09 FPrev 0.81
debug: B/Ex/Fl(MB) 32/00/08
WATCHDOG reset enabled
debug: &_text 0x10000, &_etext 0x26218, &_data 0x26218, &_edata 0x29d08
debug: &_end 0x34894, &__stack 0x400000
debug: Memory tests (0x400000 -- 0x2000000)
debug: NumberTest: debug: passed
debug: MarchTest: debug: passed
debug: PermTest: debug: passed
dbox2:root> boot net
debug:
BOOTP/TFTP bootstrap loader (v0.3)
debug:
debug: Transmitting BOOTP request via broadcast
debug: Got BOOTP reply from Server IP 192.168.124.100, My IP 192.168.124.102
debug: Sending TFTP-request for file F/tftpboot/ppcboot
will verify ELF image, start= 0x800000, size= 224356
verify sig: 262
boot net: boot file has no valid signature
Branching to 0x40000


ppcboot 0.6.4 (Jan 10 2002 - 16:35:20)

Initializing...
CPU: PPC823ZTnnB2 at 67 MHz: 2 kB I-Cache 1 kB D-Cache
Board: ### No HW ID - assuming TQM8xxL
DRAM: (faked) 32 MB
Ethernet: 00-50-9c-40-27-f3
FLASH: 8 MB
LCD driver (KS0713) initialized
No LCD Logo in Flash , trying tftp
BOOTP broadcast 1
TFTP from server 192.168.124.100; our IP address is 192.168.124.102
Filename 'F/tftpboot/logo-lcd'.
Load address: 0x130000
Loading: ##
done
LCD logo at: 0x130000 (0x1FD2864 bytes)
No FB Logo in Flash , trying tftp
BOOTP broadcast 1
TFTP from server 192.168.124.100; our IP address is 192.168.124.102
Filename 'F/tftpboot/logo-fb'.
Load address: 0x120000
Loading: ###
done
FB logo at: 0x0 (0x1FC0000 bytes)
AVIA Frambuffer
Input: serial
Output: serial

Images:
1: cdk
2: yadd
3: debian
4: tiab
5: flash
Select image (1-5), other keys to stop autoboot: 0
BOOTP broadcast 1
TFTP from server 192.168.124.100; our IP address is 192.168.124.102
Filename 'F/tftpboot/kernel-cdk'.
Load address: 0x100000
Loading: #######################################################################
#########################################################################
done
## Booting Linux kernel at 00100000 ...
Image Name: dbox2
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 734846 Bytes = 717 kB = 0 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Linux version 2.4.25-dbox2 (knoppix@KnoppBox) (gcc version 3.3.3) #1 Mo Mr 15 19
:21:07 CET 2004
On node 0 totalpages: 8192
zone(0): 8192 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: console=ttyS0 root=/dev/nfs rw nfsroot=192.168.124.100:F/cd
kroot/
WARNING: Frequency is not in HZ. Please consider using a newer bootloader!
WARNING: OLD intfreq = 67 busfreq = 67
WARNING: NEW intfreq = 67000000 busfreq = 67000000
Decrementer Frequency = 251250000/60
m8xx_wdt: active wdt found (SWTC: 0xFFFF, SWP: 0x1)
m8xx_wdt: keep-alive trigger installed (PITC: 0x2000)
Warning: real time clock seems stuck!
Console: colour dummy device 80x25
Calibrating delay loop... 66.76 BogoMIPS
Memory: 30616k available (1244k kernel code, 436k data, 72k init, 0k highmem)
Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.
i2c-core.o: i2c core module version 2.6.1 (20010830)
i2c-dev.o: i2c /dev entries driver module version 2.6.1 (20010830)
CPM UART driver version 0.04
ttyS0 at 0x0280 is on SMC1 using BRGttyS1 at 0x0380 is on SMC2 using BRG2
pty: 256 Unix98 ptys configured
eth0: CPM ENET Version 0.2.dbox2 on SCC2, 00:50:9c:40:27:f3
D-Box 2 flash driver (size->0x800000 mem->0x10000000)
D-Box 2 flash memory: Found 2 x16 devices at 0x0 in 32-bit mode
Intel/Sharp Extended Query Table at 0x0035
cfi_cmdset_0001: Erase suspend on write enabled
Using word write method
Creating 6 MTD partitions on "D-Box 2 flash memory":
0x00000000-0x00020000 : "BR bootloader"
0x00020000-0x00040000 : "flfs (ppcboot)"
0x00040000-0x00720000 : "root (cramfs)"
0x00720000-0x00800000 : "var (jffs2)"
0x00020000-0x00800000 : "flash without bootloader"
0x00000000-0x00800000 : "complete flash"
Linux video capture interface: v1.00
mice: PS/2 mouse device common for all mice
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 192.168.124.100
RPC: sendmsg returned error 101
portmap: RPC call returned error 101
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 192.168.124.100
RPC: sendmsg returned error 101
portmap: RPC call returned error 101
Root-NFS: Unable to get mountd port number from server, using default
RPC: sendmsg returned error 101
mount: RPC call returned error 101
Root-NFS: Server returned error -101 while mounting F/cdkroot/
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or 02:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 02:00
<0>Rebooting in 180 seconds..

DANKE für Hilfe!!!

Grüße,
Skitoni
DieMade
Oberlamer, Administrator & Supernanny
Beiträge: 10532
Registriert: Samstag 13. Juli 2002, 10:49

Beitrag von DieMade »

Kernel command line: console=ttyS0 root=/dev/nfs rw nfsroot=192.168.124.100:F/cdkroot/
Da fehlt die IP, welche die DBox selber verwenden soll.

Zumindest bei u-boot ist die command line länger - mit dem alten ppcboot 0.6.4 und dem Bootmanager hab ich allerdings auch noch nie eine YADD gebootet.
There are 10 types of people in the world: those who know binary and those who don't