[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: f8: NFS mount problem in rescue mode



Il giorno mer, 12/12/2007 alle 10.27 -0800, Rick Stevens ha scritto:

> Can you please specify what "not work" means?  What error messages are
> you seeing?

Start PC with Fedora-8-i386-rescuecd
start network = yes
IpV4 yes, ipv6 = no, Use DHCP
Mount existing filesystem = yes
then shell is open ...

sh-3.2# ip a s dev eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
qlen 100
    link/ether 00:16:36:db:84:63 brd ff:ff:ff:ff:ff:ff
    inet 10.39.66.82/20 brd 10.39.79.255 scope global eth0
    inet6 fe80::216:36ff:fedb:8463/64 scope link 
       valid_lft forever preferred_lft forever
sh-3.2# ip r
10.39.64.0/20 dev eth0  proto kernel  scope link  src 10.39.66.82
default via 10.39.64.10 dev eth0 
sh-3.2# ping 10.39.66.100
PING 10.39.66.100 (10.39.66.100) 56(84) bytes of data.
64 bytes from 10.39.66.100: icmp_seq=1 ttl=64 time=0.074 ms
64 bytes from 10.39.66.100: icmp_seq=2 ttl=64 time=0.066 ms
64 bytes from 10.39.66.100: icmp_seq=3 ttl=64 time=0.068 ms
64 bytes from 10.39.66.100: icmp_seq=4 ttl=64 time=0.062 ms

--- 10.39.66.100 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.062/0.067/0.074/0.009 ms

sh-3.2# ssh 10.39.66.100
The authenticity of host '10.39.64.100 (10.39.64.100)' can't be
established.
RSA key fingerprint is 3x:4x:2x:x7:dx:x1:4d:c8:16:b4:x7:45:97:d4:8d:a6.
Are you sure you want to continue connecting (yes/no)? no
sh-3.2# mkdir /tmp/f8
sh-3.2# ls -ld /tmp/f8
drwxr-xr-x 2 root root 4096 13 dic 10:33 /tmp/f8
sh-3.2# mount -tnfs 10.39.66.100:/u/f8 /tmp/f8
(wait 20/30 seconds.....)
mount: mounting 10.39.66.100:/u/f8 on /tmp/f8 failed

If I "tcpdump -i eth0 host 10.39.66.87" on host 10.39.66.100 I see
nothing.

This is the error: mount in rescue mode not work. 
(note which mount is a s-link to busybox)


For resolve the problem I must run this command:

sh-3.2# /mnt/sysimage/sbin/mount.nfs 10.39.66.100:/u/f8 /tmp/f8 -onolock
sh-3.2# df /tmp/f8
Filesystem        blocchi di   1K   Usati Disponib. Uso% Montato su
10.39.66.100:/u/f8    30726144  28232448    907776  97% /tmp/f8
sh-3.2# sed 1q /tmp/f8/RPM-GPG-KEY
The following public key can be used to verify RPM packages built and

In this way, my nfs is mounted, but is this the right way to do that?

>  a) the network isn't started
Network is started

>  b) your IP address isn't set properly
IP is set properly

>  or c) the DNS system isn't responding so you're getting "unknown host" errors.
I not use DNS in this case, it's not necessary.

> - Rick Stevens
Thanks Rick!

Now I work around my problem (PXE+kickstart setup) to copy the mount.nfs
into f8 structure, then use this command for mount my needed fs.
 
Some other suggest?

Thanks to all!

-- 
Dario Lesca <d lesca solinos it>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]