cannot mount File Storage on Redhat 8 VM
Hello
I got this message when trying to mount Azure File storage on Redhat 8 VM
mount -vvv -t nfs
Azure Files
Azure Red Hat OpenShift
-
Keshavulu Dasari 1,925 Reputation points • Microsoft Vendor
2024-11-29T23:43:06.8566667+00:00 Hi Mostafa ,
Welcome to Microsoft Q&A Forum, thank you for posting your query here!
I have seen that your original poster question has been made changes, if you have any questions, please post in comments, to mount an Azure File Storage using NFS on a Red Hat 8 VM. I suggest few steps you can take to troubleshoot the issue.
Verify NFS Support: Ensure that your Azure File Storage is configured to support NFS. Azure Files supports both SMB and NFS, but the configuration might differ.
Install NFS Utilities: Make sure the necessary NFS utilities are installed on your Red Hat 8 VM. You can install them using:
Check Network Configuration: Ensure that your VM has network access to the Azure File Storage. This might involve configuring virtual network (VNet) and firewall rules.
Mount Command: Use the correct mount command. For NFS, it might look something like this:
Permissions: Ensure that the directory where you are mounting the file share has the correct permissions:
Logs and Errors: Check the detailed logs for more information on the error. You can use the-vvv
option with the mount command to get verbose output:
For more information:
https://learn.microsoft.com/en-us/troubleshoot/azure/azure-storage/files/connectivity/files-troubleshoot-smb-connectivity?tabs=windows
https://learn.microsoft.com/en-us/azure/storage/files/storage-how-to-use-files-linux?tabs=Ubuntu%2Csmb311
If you are still facing issues, please provide some screenshots and details in the "comments" and I would be happy to help you,
-
Keshavulu Dasari 1,925 Reputation points • Microsoft Vendor
2024-12-02T01:34:25.02+00:00 Hi Mostafa ,
Checking in to see if the response helped. If you are still facing issues, please provide some screenshots and details in the "comments" and I would be happy to help you. -
Mostafa 20 Reputation points
2024-12-02T12:57:14.3533333+00:00 Hi @Keshavulu Dasari thank you for your update , yes I still have issue with File storage mount mount.nfs: timeout set for Mon Dec 2 12:47:54 2024
mount.nfs: trying text-based options 'vers=4,sec=sys,nconnect=4,vers=4.1,addr=20.60.243.38,clientaddr=<client IP>'
mount.nfs: mount(2): Connection timed out
mount.nfs: trying text-based options 'vers=4,sec=sys,nconnect=4,vers=4.1,addr=20.60.243.240,clientaddr=<client IP>'
mount.nfs: mount(2): Input/output error
mount.nfs: mount system call failed
and connection to port 2049 seems ok
nc -v -z <file storage FQDN> 2049
Ncat: Version 7.70 ( https://nmap.org/ncat )
Ncat: Connected to 20.60.242.208:2049.
Ncat: 0 bytes sent, 0 bytes received in 0.03 seconds.
could you help please with this issue
Thank you
-
Mostafa 20 Reputation points
2024-12-02T13:22:30.72+00:00 Hi @Keshavulu Dasari Thank you for your update
mount -vvv -t nfs <file storage name>.file.core.windows.net:/<file storage name>/share /repo -o vers=4,minorversion=1,sec=sys,nconnect=4
mount.nfs: timeout set for Mon Dec 2 13:14:54 2024
mount.nfs: trying text-based options 'vers=4,sec=sys,nconnect=4,vers=4.1,addr=20.60.243.240,clientaddr=<client ip>'
mount.nfs: mount(2): Connection timed out
mount.nfs: trying text-based options 'vers=4,sec=sys,nconnect=4,vers=4.1,addr=20.60.242.208,clientaddr=<client ip>'
mount.nfs: mount(2): Input/output error
mount.nfs: mount system call failed
-
Mostafa 20 Reputation points
2024-12-02T13:25:03.0533333+00:00 the connection to port 2049 on File storage seems ok
nc -v -z <file storage name>.file.core.windows.net 2049
Ncat: Version 7.70 ( https://nmap.org/ncat )
Ncat: Connected to 20.60.242.208:2049.
Ncat: 0 bytes sent, 0 bytes received in 0.05 seconds.
but still getting during the File storage mount
any suggestion please to fix this issue
Thank you
-
deherman-MSFT 37,666 Reputation points • Microsoft Employee
2024-12-02T23:14:47.1266667+00:00 @Mostafa How are you connecting to the NFS file share is this from a VM, on premise machine, or over the internet? The most common issue is Request originates from a client in an untrusted network/untrusted IP. Can you double check your configuration and make sure you are connecting over a supported network?
Sign in to comment