My mistake, this was a side effect from trying to chmod -R 777 the roach_boot directory. Logging in as root works now. Glenn
On Fri, Dec 11, 2009 at 6:58 PM, G Jones <[email protected]> wrote: > All, > Thanks for the help, the /24 solved the problem. This is missing from > the guide, so I'll update the wiki. > Next problem: what's the login for the etch file image? I downloaded > the 2009-11-30 image. trying to log in as root yields: Login incorrect > without prompting for a password. I looked at roach_root/etc/passwd > and don't see any other obvious choices. > Thanks again, > Glenn > > On Fri, Dec 11, 2009 at 6:20 PM, John Ford <[email protected]> wrote: >> Hi Glenn. I managed to get ours working with the guide. Our exports file >> says: >> >> Yes, Master<1002> more /etc/exports >> /export/home/tofu/cicadaroots 169.254.128.0/24(sync,rw,no_root_squash) >> >> And: >> >> Yes, Master<1003> ls /export/home/tofu/cicadaroots/ >> bee2Guppi filesystem_etch_nfs_2009_07_07.tar.gz roach_2 tftpboot >> bee2Unused roach_1 roach_3 >> Yes, Master<1004> >> >> Where roach_1 contains the etch filesystem: >> >> Yes, Master<1005> ls /export/home/tofu/cicadaroots/roach_1 >> etch >> >> You have to be sure your export points to an actual directory and not a >> link, also. >> >> We also had a problem with routes on one of our machines with multiple >> networks. Make sure that the route to your host is OK, and that the DHCP >> host knows about it. >> >> Yes, Master<1004> route >> Kernel IP routing table >> Destination Gateway Genmask Flags Metric Ref Use Iface >> 10.16.96.0 * 255.255.255.0 U 0 0 0 eth0 >> 192.168.3.0 * 255.255.255.0 U 0 0 0 eth2 >> 169.254.0.0 * 255.255.0.0 U 0 0 0 eth1 >> default vlan96-gw.gb.nr 0.0.0.0 UG 0 0 0 eth0 >> Yes, Master<1005> >> >> >> Good luck! >> >> John >> >> >>> Hello, >>> Sorry to bother you all with this, but I'm having trouble getting my >>> ROACH to mount the network file system. I followed the guide, and the >>> DHCP seems to work as well as the TFTP portion. However, when it's >>> time to mount the root file system, I get: >>> >>> Sending DHCP requests ., OK >>> IP-Config: Got DHCP answer from 192.168.0.1, my address is 192.168.0.8 >>> IP-Config: Complete: >>> device=eth0, addr=192.168.0.8, mask=255.255.0.0, gw=255.255.255.255, >>> host=192.168.0.8, domain=, nis-domain=(none), >>> bootserver=192.168.0.1, rootserver=192.168.0.1, >>> rootpath=/srv/roach_boot/etch >>> Looking up port of RPC 100003/2 on 192.168.0.1 >>> Looking up port of RPC 100005/1 on 192.168.0.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.0.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?) >>> ... >>> >>> 1f05 384 mtdblock5 (driver?) >>> Kernel panic - not syncing: VFS: Unable to mount root fs on >>> unknown-block(2,0) >>> Rebooting in 180 seconds..System Hardware Reset >>> >>> >>> I've tried googling a while on the "error -13" message and see that it >>> means that my nfs server is saying access denied. However, I can't >>> figure out why this is. >>> I've tried doing chmod -R 777 /srv/roach_boot/etch but no change. >>> My /etc/exports file is as follows: >>> /srv/roach_boot/etch 192.168.0.0(rw,subtree_check,no_root_squash,insecure) >>> >>> I've also tried exporting /srv/roach_boot >>> >>> $sudo exportfs >>> /srv/roach_boot/etch >>> 192.168.0.0 >>> /srv/roach_boot >>> 192.168.0.0 >>> >>> >>> I appreciate any help solving what I'm sure is a silly linux problem. >>> My server is debian lenny if it matters. >>> >>> Thanks, >>> Glenn >>> >> >> >> >
