Linux NFS unsupported protocol error after power failure
up vote
0
down vote
favorite
Everything was smooth until a power failure.
One of my servers and a client are both running Xubuntu 18.04. This server has
internal 4T data disk and an 8T external USB backup drive mounted at /A and /B respectively. The /etc/exports file was unchanged and has these 2 lines:
/A/a 192.168.20.101/24(rw,no_subtree_check)
/B/b1/b2 192.168.20.101/24(rw,no_subtree_check)
Command "exportfs -r -a" was issued after /A and /B were mounted. When the client tried to mount (e.g., mount 192.168.20.143:/A/a /mnt/a), I get this error
mount.nfs: requested NFS version or transport protocol is not supported
This never happened before the power failure. This error persisted even after I completely removed and re-installed nfs-kernel-server and nfs-common in both the client and the server.
What makes things more confusing is that I have another linux server and a FreeNAS server running, and my client is able to mount NFS from both of them.
I have searched Google but I am unable to find the reason and unable restore nfs service from this server.
Please help. Thank you very much !!!
mount power nfs protocol
add a comment |
up vote
0
down vote
favorite
Everything was smooth until a power failure.
One of my servers and a client are both running Xubuntu 18.04. This server has
internal 4T data disk and an 8T external USB backup drive mounted at /A and /B respectively. The /etc/exports file was unchanged and has these 2 lines:
/A/a 192.168.20.101/24(rw,no_subtree_check)
/B/b1/b2 192.168.20.101/24(rw,no_subtree_check)
Command "exportfs -r -a" was issued after /A and /B were mounted. When the client tried to mount (e.g., mount 192.168.20.143:/A/a /mnt/a), I get this error
mount.nfs: requested NFS version or transport protocol is not supported
This never happened before the power failure. This error persisted even after I completely removed and re-installed nfs-kernel-server and nfs-common in both the client and the server.
What makes things more confusing is that I have another linux server and a FreeNAS server running, and my client is able to mount NFS from both of them.
I have searched Google but I am unable to find the reason and unable restore nfs service from this server.
Please help. Thank you very much !!!
mount power nfs protocol
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Everything was smooth until a power failure.
One of my servers and a client are both running Xubuntu 18.04. This server has
internal 4T data disk and an 8T external USB backup drive mounted at /A and /B respectively. The /etc/exports file was unchanged and has these 2 lines:
/A/a 192.168.20.101/24(rw,no_subtree_check)
/B/b1/b2 192.168.20.101/24(rw,no_subtree_check)
Command "exportfs -r -a" was issued after /A and /B were mounted. When the client tried to mount (e.g., mount 192.168.20.143:/A/a /mnt/a), I get this error
mount.nfs: requested NFS version or transport protocol is not supported
This never happened before the power failure. This error persisted even after I completely removed and re-installed nfs-kernel-server and nfs-common in both the client and the server.
What makes things more confusing is that I have another linux server and a FreeNAS server running, and my client is able to mount NFS from both of them.
I have searched Google but I am unable to find the reason and unable restore nfs service from this server.
Please help. Thank you very much !!!
mount power nfs protocol
Everything was smooth until a power failure.
One of my servers and a client are both running Xubuntu 18.04. This server has
internal 4T data disk and an 8T external USB backup drive mounted at /A and /B respectively. The /etc/exports file was unchanged and has these 2 lines:
/A/a 192.168.20.101/24(rw,no_subtree_check)
/B/b1/b2 192.168.20.101/24(rw,no_subtree_check)
Command "exportfs -r -a" was issued after /A and /B were mounted. When the client tried to mount (e.g., mount 192.168.20.143:/A/a /mnt/a), I get this error
mount.nfs: requested NFS version or transport protocol is not supported
This never happened before the power failure. This error persisted even after I completely removed and re-installed nfs-kernel-server and nfs-common in both the client and the server.
What makes things more confusing is that I have another linux server and a FreeNAS server running, and my client is able to mount NFS from both of them.
I have searched Google but I am unable to find the reason and unable restore nfs service from this server.
Please help. Thank you very much !!!
mount power nfs protocol
mount power nfs protocol
asked Nov 21 at 4:33
lisprogtor
101
101
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377168%2flinux-nfs-unsupported-protocol-error-after-power-failure%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown