There was a very long thread about this new problem a few weeks ago. Bottom line is that it's likely that your host isn't exporting the filesystem correctly, there's a typo in the DHCP offer, or some other such host problem. Look in the mail archives...
John > So I plugged my other Roach1 that's in the lab into where the troubled > Roach1 was sitting and started up the netboot. The uImage transferred fine > this time, but I got another problem: *VFS: Unable to mount root fs via > NFS, trying floppy.* > *VFS: Cannot open root device "192.168.40.1:/srv/roach_boot/etch" or > unknown-block(2,0)* > *Please append a correct "root=" boot option; here are the available > partitions:* > > Full boot up dump below: > > Hit any key to stop autoboot: 10 \0x08\0x08\0x08 0 > > => run netboot > > Waiting for PHY auto negotiation to complete.. done > > ENET Speed is 100 Mbps - FULL duplex connection (EMAC0) > > BOOTP broadcast 1 > > DHCP client bound to address 192.168.100.51 > > Using ppc_4xx_eth0 device > > TFTP from server 192.168.40.1; our IP address is 192.168.100.51 > > Filename 'uImage'. > > Load address: 0x400000 > > Loading: > *\0x08################################################################# > > \0x09 ################################################################# > > \0x09 ################################################################# > > \0x09 ################################################################# > > \0x09 ############ > > done > > Bytes transferred = 1390149 (153645 hex) > > ## Booting kernel from Legacy Image at 00400000 ... > > Image Name: Linux-2.6.25-svn3489 > > Image Type: PowerPC Linux Kernel Image (gzip compressed) > > Data Size: 1390085 Bytes = 1.3 MB > > Load Address: 00000000 > > Entry Point: 00000000 > > Verifying Checksum ... OK > > Uncompressing Kernel Image ... OK > > > id mach(): done > > > > MMU:enter > > > > MMU:hw init > > > > MMU:mapin > > > > MMU:setio > > > > MMU:exit > > > > setup_arch: enter > > > > setup_arch: bootmem > > > > ocp: exit > > > > arch: exit > > > Linux version 2.6.25-svn3489 (dave@lapster) (gcc version 4.2.2) #6 Fri Aug > 12 09:36:28 SAST 2011 > > AMCC PowerPC 440EPx Roach Platform > > Zone PFN ranges: > > DMA 0 -> 131071 > > Normal 131071 -> 131071 > > Movable zone start PFN for each node > > early_node_map[1] active PFN ranges > > 0: 0 -> 131071 > > Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 > > Kernel command line: console=ttyS0,115200 > mtdparts=physmap-flash.0:1792k(linux),256k@0x1c0000(fdt),8192k@0x200000 > (root),54656k@0xa00000(usr),256k@0x3f60000(env),384k@0x3fa0000(uboot)fdt_addr=0xfc1c0000 > root=192.168.40.1:/srv/roach_boot/etch ip=dhcp > > PID hash table entries: 2048 (order: 11, 8192 bytes) > > console [ttyS0] enabled > > Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) > > Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) > > Memory: 516608k available (2084k kernel code, 720k data, 132k init, 0k > highmem) > > Mount-cache hash table entries: 512 > > BORPH version CVS-$Revision: 1.10 $ Initialized > > net_namespace: 152 bytes > > NET: Registered protocol family 16 > > > > PCI: Probing PCI hardware > > SCSI subsystem initialized > > usbcore: registered new interface driver usbfs > > usbcore: registered new interface driver hub > > usbcore: registered new device driver usb > > NET: Registered protocol family 2 > > IP route cache hash table entries: 4096 (order: 2, 16384 bytes) > > TCP established hash table entries: 16384 (order: 5, 131072 bytes) > > TCP bind hash table entries: 16384 (order: 4, 65536 bytes) > > TCP: Hash tables configured (established 16384 bind 16384) > > TCP reno registered > > hwrtype_roach version CVS-$Revision: 1.1 $ registered > > JFFS2 version 2.2. (NAND) \0xc2\0xa9 2001-2006 Red Hat, Inc. > > io scheduler noop registered (default) > > Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled > > serial8250: ttyS0 at MMIO 0x0 (irq = 0) is a 16550A > > serial8250: ttyS1 at MMIO 0x0 (irq = 1) is a 16550A > > serial8250: ttyS2 at MMIO 0x0 (irq = 35) is a 16550A > > serial8250: ttyS3 at MMIO 0x0 (irq = 36) is a 16550A > > brd: module loaded > > PPC 4xx OCP EMAC driver, version 3.54 > > mal0: initialized, 2 TX channels, 2 RX channels > > rgmii0: input 0 in RGMII mode > > eth0: emac0, MAC 02:00:00:02:01:02 > > eth0: found Generic MII PHY (0x1e) > > rgmii0: input 1 in RGMII mode > > emac1: can't find PHY! > > tun: Universal TUN/TAP device driver, 1.6 > > tun: (C) 1999-2004 Max Krasnyansky <[email protected]> > > Driver 'sd' needs updating - please use bus_type methods > > physmap platform flash device: 04000000 at fc000000 > > physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank > > Amd/Fujitsu Extended Query Table at 0x0040 > > physmap-flash.0: CFI does not contain boot bank location. Assuming top. > > number of CFI chips: 1 > > cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness. > > mtd: bad character after partition (f) > > 6 cmdlinepart partitions found on MTD device physmap-flash.0 > > Creating 6 MTD partitions on "physmap-flash.0": > > 0x00000000-0x001c0000 : "linux" > > 0x001c0000-0x00200000 : "fdt" > > 0x00200000-0x00a00000 : "root" > > 0x00a00000-0x03f60000 : "usr" > > 0x03f60000-0x03fa0000 : "env" > > 0x03fa0000-0x04000000 : "uboot" > > ppc-soc-ohci ppc-soc-ohci.0: USB Host Controller > > ppc-soc-ohci ppc-soc-ohci.0: new USB bus registered, assigned bus number 1 > > ppc-soc-ohci ppc-soc-ohci.0: irq 21, io mem 0xe0000400 > > usb usb1: configuration #1 chosen from 1 choice > > hub 1-0:1.0: USB hub found > > hub 1-0:1.0: 1 port detected > > usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 > > usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 > > usb usb1: Product: USB Host Controller > > usb usb1: Manufacturer: Linux 2.6.25-svn3489 ohci_hcd > > usb usb1: SerialNumber: PPC-SOC USB > > Initializing USB Mass Storage driver... > > usbcore: registered new interface driver usb-storage > > USB Mass Storage support registered. > > i2c /dev entries driver > > IBM IIC driver v2.1 > > ibm-iic0: using standard (100 kHz) mode > > ibm-iic1: using standard (100 kHz) mode > > rmon: found Roach Monitor - Rev 6.5.1429 > > rmon_sensors: initialized 23 sensors > > rmon 0-000f: rtc core: registered rmon as rtc0 > > roach_mmc: Roach MMC/SD driver > > rmmc: initialized mmc > > TCP cubic registered > > NET: Registered protocol family 1 > > NET: Registered protocol family 17 > > rmmc: performing card initialization > > RPC: Registered udp transport module. > > RPC: Registered tcp transport module. > > rmon 0-000f: setting system clock to 2067-10-01 16:30:56 UTC (3084712256) > > mmc0: new high speed SDHC card at address 63fd > > mmcblk0: mmc0:63fd RP04G 3870720KiB > > mmcblk0: p1 > > eth0: interrupt coalescing (RX:count=8 time=1000, TX:count=8 time=1000) > > eth0: link is down > > eth0: link is up, 100 FDX, pause enabled > > Sending DHCP requests ., OK > > IP-Config: Got DHCP answer from 192.168.40.1, my address is 192.168.100.51 > > IP-Config: Complete: > > device=eth0, addr=192.168.100.51, mask=255.255.0.0, gw=255.255.255.255, > > host=roach1-3, domain=, nis-domain=(none), > > bootserver=192.168.40.1, rootserver=192.168.40.1, > rootpath=/srv/roach_boot/etch > > Looking up port of RPC 100003/2 on 192.168.40.1 > > Looking up port of RPC 100005/1 on 192.168.40.1 > > Root-NFS: Server returned error -13 while mounting /srv/roach_boot/etch > > VFS: Unable to mount root fs via NFS, trying floppy. > > VFS: Cannot open root device "192.168.40.1:/srv/roach_boot/etch" or > unknown-block(2,0) > > Please append a correct "root=" boot option; here are the available > partitions: > > 0100 4096 ram0 (driver?) > > 0101 4096 ram1 (driver?) > > 0102 4096 ram2 (driver?) > > 0103 4096 ram3 (driver?) > > 0104 4096 ram4 (driver?) > > 0105 4096 ram5 (driver?) > > 0106 4096 ram6 (driver?) > > 0107 4096 ram7 (driver?) > > 0108 4096 ram8 (driver?) > > 0109 4096 ram9 (driver?) > > 010a 4096 ram10 (driver?) > > 010b 4096 ram11 (driver?) > > 010c 4096 ram12 (driver?) > > 010d 4096 ram13 (driver?) > > 010e 4096 ram14 (driver?) > > 010f 4096 ram15 (driver?) > > 1f00 1792 mtdblock0 (driver?) > > 1f01 256 mtdblock1 (driver?) > > 1f02 8192 mtdblock2 (driver?) > > 1f03 54656 mtdblock3 (driver?) > > 1f04 256 mtdblock4 (driver?) > > 1f05 384 mtdblock5 (driver?) > > b300 3870720 mmcblk0 driver: mmcblk > > b301 3866624 mmcblk0p1 > > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(2,0) > > Rebooting in 180 seconds..System Hardware Reset > > > Brad Dober > Ph.D. Candidate > Department of Physics and Astronomy > University of Pennsylvania > Cell: 262-949-4668 > > On Wed, May 27, 2015 at 1:09 PM, David MacMahon > <[email protected]> > wrote: > >> Hi, Brad, >> >> On May 27, 2015, at 9:37 AM, Brad Dober wrote: >> >> > I have no issues with the Roach2 that is also connected to this host >> computer. >> >> No issues meaning that you can tftp the uImage file from the server to >> the >> roach2? Does tcpdump/wireshark show any clues vis a vis the ROACH1's >> attempted tftp transfer? >> >> > I switched the Roach1's and Roach'2 ethernet cables and still have the >> same problem on the Roach1 and Roach2 is still working fine. >> >> Did this also swap the switch ports? >> >> > Which pins / voltages should I be checking on the power supply? >> >> I'd check all of them. I think it's a standard ATX power supply, but >> the >> wiki might have more details. >> >> Maybe try reseating (or replacing) the ROACH1 PPC's DIMM module? I >> guess >> it was working OK with soloboot/usbboot until the root filesystem got >> corrupted, so maybe this isn't really relevant? >> >> > U-Boot 2008.10-svn3231 (Jul 15 2010 - 14:58:38) >> >> I don't know of any specific problems, but you might want to consider >> updating uboot... >> >> https://casper.berkeley.edu/wiki/ROACH_kernel_uboot_update >> >> https://casper.berkeley.edu/wiki/LatestVersions >> >> Dave >> >> >
