If I boot Fedora 8 with DVD in rescue mode I can't mount a NFS share.
The problem also happened if I use Fedora 7 Respin, but NON if I use
Fedora 7 std. or Fedora Core [6-1].
If I boot with options rescue + askmetod then do an NFS install,
Anaconda mount /mnt/source correctly, but from shell if I try to mount
another NFS share the mount not work
All these problem happened also if I work on VMware-server.
Some suggest?
--
Dario Lesca <d.lesca@solinos.it>
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
12-12-2007, 09:02 AM
Dario Lesca
f8: NFS mount problem in rescue mode
If I boot Fedora 8 with DVD in rescue mode I can't mount a NFS share.
The problem also happened if I use Fedora 7 Respin, but NON if I use
Fedora 7 std. or Fedora Core [6-1].
If I boot with options rescue + askmetod then do an NFS install,
Anaconda mount /mnt/source correctly, but from shell if I try to mount
another NFS share the mount not work
All these problem happened also if I work on VMware-server.
Some suggest?
--
Dario Lesca <d.lesca@solinos.it>
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
12-12-2007, 03:23 PM
Dario Lesca
f8: NFS mount problem in rescue mode
Il giorno mer, 12/12/2007 alle 11.02 +0100, Dario Lesca ha scritto:
> If I boot Fedora 8 with DVD in rescue mode I can't mount a NFS share.
Please, someone can do this test and tell me if the problem happened
only to me?
Thanks.
--
Dario Lesca <d.lesca@solinos.it>
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
12-12-2007, 03:23 PM
Dario Lesca
f8: NFS mount problem in rescue mode
Il giorno mer, 12/12/2007 alle 11.02 +0100, Dario Lesca ha scritto:
> If I boot Fedora 8 with DVD in rescue mode I can't mount a NFS share.
Please, someone can do this test and tell me if the problem happened
only to me?
Thanks.
--
Dario Lesca <d.lesca@solinos.it>
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
12-12-2007, 04:09 PM
Karel Zak
f8: NFS mount problem in rescue mode
On Wed, Dec 12, 2007 at 05:23:30PM +0100, Dario Lesca wrote:
> Il giorno mer, 12/12/2007 alle 11.02 +0100, Dario Lesca ha scritto:
> > If I boot Fedora 8 with DVD in rescue mode I can't mount a NFS share.
>
> Please, someone can do this test and tell me if the problem happened
> only to me?
do you have /sbin/mount.nfs (in rescue mode)?
Karel
--
Karel Zak <kzak@redhat.com>
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
12-12-2007, 05:27 PM
Rick Stevens
f8: NFS mount problem in rescue mode
On Wed, 2007-12-12 at 11:02 +0100, Dario Lesca wrote:
> If I boot Fedora 8 with DVD in rescue mode I can't mount a NFS share.
>
> The problem also happened if I use Fedora 7 Respin, but NON if I use
> Fedora 7 std. or Fedora Core [6-1].
>
> If I boot with options rescue + askmetod then do an NFS install,
> Anaconda mount /mnt/source correctly, but from shell if I try to mount
> another NFS share the mount not work
Can you please specify what "not work" means? What error messages are
you seeing?
If you're trying this via rescue mode, the odds are that a) the network
isn't started, b) your IP address isn't set properly, or c) the DNS
system isn't responding so you're getting "unknown host" errors.
----------------------------------------------------------------------
- Rick Stevens, Principal Engineer rstevens@internap.com -
- CDN Systems, Internap, Inc. http://www.internap.com -
- -
- Microsoft Windows: Proof that P.T. Barnum was right -
----------------------------------------------------------------------
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
12-12-2007, 09:23 PM
"Xavier Lamien"
f8: NFS mount problem in rescue mode
2007/12/12, Karel Zak <kzak@redhat.com>:
On Wed, Dec 12, 2007 at 05:23:30PM +0100, Dario Lesca wrote:
> Il giorno mer, 12/12/2007 alle 11.02 +0100, Dario Lesca ha scritto:
> > If I boot Fedora 8 with DVD in rescue mode I can't mount a NFS share.
>
> Please, someone can do this test and tell me if the problem happened
> only to me?
do you have /sbin/mount.nfs (in rescue mode)?
Also, paste your output error
****Karel
--
Karel Zak**<kzak@redhat.com
>
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
--
Xavier.t Lamien
--
French Fedora Ambassador
Fedora/EPEL Contributor******| http://fedoraproject.org/wiki/XavierLamien
Il giorno mer, 12/12/2007 alle 18.09 +0100, Karel Zak ha scritto:
> On Wed, Dec 12, 2007 at 05:23:30PM +0100, Dario Lesca wrote:
> > Il giorno mer, 12/12/2007 alle 11.02 +0100, Dario Lesca ha scritto:
> > > If I boot Fedora 8 with DVD in rescue mode I can't mount a NFS share.
> >
> > Please, someone can do this test and tell me if the problem happened
> > only to me?
>
> do you have /sbin/mount.nfs (in rescue mode)?
>
> Karel
Karel, all guys NOT have this command in rescue mode.
sh-3.2# ls -l /sbin/mount.nfs
ls: cannot access /sbin/mount.nfs: No such file or directory
Thanks
--
Dario Lesca <d.lesca@solinos.it>
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
12-13-2007, 09:54 AM
Dario Lesca
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>
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
12-13-2007, 09:54 AM
Dario Lesca
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>
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
f8: NFS mount problem in rescue mode
