yadd nfs problem

Anlaufschwierigkeiten? Was ist was? Worum geht's?
garfield7554
Neugieriger
Neugieriger
Beiträge: 17
Registriert: Sonntag 2. Januar 2005, 14:51

yadd nfs problem

Beitrag von garfield7554 »

Hallo zusammen!

Ich versuche mich jetzt schon einige Zeit daran meine dbox übers Netz zu booten. Allerdings bekomme ich es nicht hin. So wie ich das sehe kann die Box nicht über NFS mounten. Allerdings kann ich die Verzeichnisse von einem anderen Rechner aus mounten und ich habe das Verzeichnis für alle IPs im Netz freigegeben.
Hier mal das Log von der Box:

Code: Alles auswählen

 debug: DDF: Calibrating delay loop... debug: DDF: 66.76 BogoMIPS
debug: BMon V1.0  mID 03
debug: feID 00    enxID 03
debug: fpID 52     dsID 01-e4.ad.58.07.00.00-a9
debug: HWrev 01  FPrev 0.23
debug: B/Ex/Fl(MB) 32/00/08
WATCHDOG reset enabled
dbox2:root> debug: 
BOOTP/TFTP bootstrap loader (v0.3)
debug: 
debug: Transmitting BOOTP request via broadcast
debug: Unknown RFC1048-tag debug: 11 debug: e debug: 2f debug: 64 debug: 62 debug: 6f debug: 78 debug: 32 debug: 2f debug: 63 debug: 64 debug: 6b debug: 72 debug: 6f debug: 6f debug: 74 debug: 

debug: Got BOOTP reply from Server IP 192.168.2.32, My IP 192.168.2.22
debug: Sending TFTP-request for file u-boot
debug: Got Block #0050
debug: Got Block #0100
debug: Got Block #0150
debug: Got Block #0200
debug: Got Block #0250
will verify ELF image, start= 0x800000, size= 142732
verify sig: 262
boot net: boot file has no valid signature
Branching to 0x40000


U-Boot 1.2.0 (Tuxbox) (Nov 19 2008 - 20:54:00)

CPU:   PPC823ZTnnB2 at 66 MHz: 2 kB I-Cache 1 kB D-Cache
Board: DBOX2, Sagem, BMon V1.0
       Watchdog enabled
I2C:   ready
DRAM:  32 MB
FLASH:  8 MB
FB:    ready
LCD:   ready
In:    serial
Out:   serial
Err:   serial
Net:   SCC ETHERNET
BOOTP broadcast 1
DHCP client bound to address 192.168.2.22
Using SCC ETHERNET device
TFTP from server 192.168.2.32; our IP address is 192.168.2.22
Filename 'kernel-cdk'.
Load address: 0x100000
Loading: *Using SCC ETHERNET device
File transfer via NFS from server 192.168.2.32; our IP address is 192.168.2.22
Filename '/dbox2/cdkroot/var/tuxbox/boot/boot.conf'.
Load address: 0x100000
Loading: **** ERROR: Cannot mount
Timeout
can't find boot.conf
BOOTP broadcast 1
DHCP client bound to address 192.168.2.22
Using SCC ETHERNET device
TFTP from server 192.168.2.32; our IP address is 192.168.2.22
Filename 'kernel-cdk'.
Load address: 0x100000
Loading: *Using SCC ETHERNET device
TFTP from server 192.168.2.32; our IP address is 192.168.2.22
Filename 'logo-lcd'.
Load address: 0x100000
Loading: *
TFTP error: 'File not found' (1)
can't find logo
BOOTP broadcast 1
DHCP client bound to address 192.168.2.22
Using SCC ETHERNET device
TFTP from server 192.168.2.32; our IP address is 192.168.2.22
Filename 'kernel-cdk'.
Load address: 0x100000
Loading: *Using SCC ETHERNET device
TFTP from server 192.168.2.32; our IP address is 192.168.2.22
Filename 'logo-fb'.
Load address: 0x100000
Loading: *########
done
Bytes transferred = 36157 (8d3d hex)

Options:
  1: console on ttyS0
  2: console on fb0
  3: console on null
Select option (1-3), other keys to stop autoboot:  1  0 
BOOTP broadcast 1
DHCP client bound to address 192.168.2.22
Using SCC ETHERNET device
TFTP from server 192.168.2.32; our IP address is 192.168.2.22
Filename 'kernel-cdk'.
Load address: 0x100000
Loading: *Using SCC ETHERNET device
TFTP from server 192.168.2.32; our IP address is 192.168.2.22
Filename 'kernel-cdk'.
Load address: 0x100000
Loading: *#################################################################
	 #################################################################
	 ################################
done
Bytes transferred = 824388 (c9444 hex)
............................................................... done
Un-Protected 63 sectors
## Booting image at 00100000 ...
   Image Name:   dbox2
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    824324 Bytes = 805 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
Linux version 2.4.36.6-dbox2 (sebastian@d630) (gcc version 3.4.6) #1 Mi 19. Nov 20:54:48 CET 2008

On node 0 totalpages: 8192

zone(0): 8192 pages.

zone(1): 0 pages.

zone(2): 0 pages.

Kernel command line: root=/dev/nfs rw nfsroot=/dbox2/cdkroot ip=192.168.2.22:192.168.2.32::255.255.255.0:::off console=ttyS0,9600

Decrementer Frequency = 247500000/60

m8xx_wdt: active wdt found (SWTC: 0xFFFF, SWP: 0x1)

m8xx_wdt: keep-alive trigger installed (PITC: 0x2000)

Console: colour dummy device 80x25

Calibrating delay loop... 65.74 BogoMIPS

Memory: 30452k available (1400k kernel code, 444k 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. (NAND) (C) 2001-2003 Red Hat, Inc.

squashfs: version 3.0 (2006/03/15) Phillip Lougher

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

half-duplex mode enabled

eth0: CPM ENET Version 0.2.dbox2 on SCC2, 00:50:9c:30:6f:05

loop: loaded (max 8 devices)

D-Box 2 flash driver (size->0x800000 mem->0x10000000)

D-Box 2 flash memory: Found 2 x16 devices at 0x0 in 32-bit bank

 Intel/Sharp Extended Query Table at 0x0035

cfi_cmdset_0001: Erase suspend on write enabled

Creating 6 MTD partitions on "D-Box 2 flash memory":

0x00000000-0x00020000 : "BR bootloader"

0x00020000-0x00040000 : "FLFS (U-Boot)"

0x00040000-0x006a0000 : "root (rootfs)"

0x006a0000-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)

IP-Config: Complete:

      device=eth0, addr=192.168.2.22, mask=255.255.255.0, gw=255.255.255.255,

     host=192.168.2.22, domain=, nis-domain=(none),

     bootserver=192.168.2.32, rootserver=192.168.2.32, rootpath=

NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.

Looking up port of RPC 100003/2 on 192.168.2.32

Looking up port of RPC 100005/1 on 192.168.2.32

RPC: call_verify: program 100005, version 1 unsupported by server 192.168.2.32

Root-NFS: Server returned error -5 while mounting /dbox2/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..
und meine dhcpd.conf

Code: Alles auswählen

ddns-update-style none;
subnet 192.168.2.0 netmask 255.255.255.0{
  default-lease-time 14400;
  max-lease-time 172800;
}

host dbox {
  option root-path "/dbox2/cdkroot";
  next-server 192.168.2.32;
  hardware ethernet 00:50:9C:30:6F:05;
  fixed-address 192.168.2.22;
  allow bootp;
  server-name "192.168.2.32";
  if exists vendor-class-identifier {
    filename "kernel-cdk";
    option root-path "/dbox2/cdkroot";
  } else {
    filename "u-boot";
  }
}
Habe ne Sagem Dbox und auf dem Server als Distribution ArchLinux.
Wäre super wenn mir jemand helfen könnte hab echt keine Idee mehr.
P.S. Wenns jemand was hilft kann ich auch noch den Trace vom Netzwerk posten.
rhabarber1848
CDK-Experte
Beiträge: 4335
Registriert: Donnerstag 3. April 2008, 14:05

Re: yadd nfs problem

Beitrag von rhabarber1848 »

Wie sehen die NFS-exports aus?
garfield7554
Neugieriger
Neugieriger
Beiträge: 17
Registriert: Sonntag 2. Januar 2005, 14:51

Re: yadd nfs problem

Beitrag von garfield7554 »

hallo rhabarber1848,

hier meine /etc/exports:

Code: Alles auswählen

/dbox2 *(rw,no_root_squash,no_subtree_check,sync)
/dbox2/cdk *(rw,no_root_squash,no_subtree_check,sync)
/dbox2/cdkflash *(rw,no_root_squash,no_subtree_check,sync)
/dbox2/cdkroot *(rw,no_root_squash,no_subtree_check,sync)
/dbox2/tftpboot *(rw,no_root_squash,no_subtree_check,sync)
garfield7554
Neugieriger
Neugieriger
Beiträge: 17
Registriert: Sonntag 2. Januar 2005, 14:51

Re: yadd nfs problem

Beitrag von garfield7554 »

So wies aussieht hab ich mein Problem gelöst.
Falls jemand mal das selbe Problem haben sollte hier die Lösung:

der mountd des Servers muss Version 1 oder 2 unterstützen. man kann dies mit

Code: Alles auswählen

rpcinfo -p IpDesServers
überprüfen (der NFS Server muss gestartet sein.

Unterstützt der mountd nur die Version 3 kann die DBox das Verzeichnis nicht mounten. Um dies zu umgehen startet man den mountd mit der Option -N3. Das heißt der mountd soll die NFS Version 3 unterstützen. Das hat zur folge, dass der mountd mit der Version 1 und 2 umgehen kann.