Problem with NFS setup Not functioning properly
Problem with NFS setup Not functioning properly
Hello, your issue involves compatibility between different OS setups for NFS access. The advice you received suggests alternatives like using SMB on a Windows laptop, which might help if OpenMediaVault is configured correctly. However, ensure your Android phone and ODROID HC4 are properly configured for NFS support. Differences in OS versions can affect performance or stability, so test thoroughly and consider updating drivers if needed.
I'm not familiar with Android, but on another Linux-based MacOS system you can check if the server is reachable using sudo showmount -e ip.address.of.server. If it appears, mount it locally before using it. I wrote about this on my own site, though I don't use OMV. It might be better to use SMB for Android.
Consider where to place this comment. Since you're using a Windows PC and see 'sudo' in the command, try running it on your NAS's Armbian. That seems confusing. Running showmount for its own IP address works fine on Android and Windows. You mentioned NFS—what does that involve? I'm not sure how to handle it. Otherwise, SMB is reliable on Android phones and Windows PCs. Still, I need to test Kodi later on LibreElec. Someone said SMB is a major issue you can't really avoid. Plus, it doesn't integrate well with Linux file systems like EXT4. They're right about that. I saw an error message (image from the web) saying something about properties not storing necessary data. If I understand correctly...it doesn't matter, though some documents can keep essential info in their properties.
Mmm, unclear about their approach, SMB functions adequately now. The main challenge arises with Windows because the Windows SMB server is proprietary and doesn't match 1-to-1 with Samba. SMB works well with ext4, but file permissions differ between Windows (DOS) and Linux (Unix-like), making them quite incompatible. Typically, permissions are stripped away to resolve the issue, which triggers the error message you see.
I don’t expect any problems to arise. My goal is to keep your filesystem safe and ensure everything functions properly. I’ve tested connecting the Kodi box to NFS and SMB, and while saving files via NFS didn’t work as expected, it did save correctly in the folder you specified. Samba performed well. It seems the issue might be with how NFS is configured. I followed some guidance about making it writable, but I wasn’t sure if that would resolve the problem. The main advantage of NFS is that it uses minimal resources on both sides. I’m still trying to understand this fully.
NFS could offer better performance too. I probably don’t rely on it much for mounting my home directories on the newer Linux systems near my house. My home network runs at 2.5gbps using a powerful SSD server, which means my experience would differ greatly from yours. For file corruption, most modern file systems handle basic checks, so you should be safe. Network issues usually stem from hardware problems or unusual usage—like streaming to Kodi in read-only mode—so there’s little risk of data loss. If efficiency matters, consider a more recent server instead of ARM-based options; using an old Raspberry Pi isn’t ideal. Comparing Linux efficiency by memory use isn’t very useful, since CPU performance is far more important.
The final note... yes, I'm using an ARM-based machine (Odroid HC4 – I chose it mainly for cost, but it has a proper SATA controller with good connections, unlike some Raspberry Pi setups). To my defense, I’m limited by budget. But I’m starting to grasp the complexities of full systems like Synology. It’s really frustrating trying to manage certain configurations. For instance, I can’t reliably use a folder for a Docker container I built; it behaves unpredictably. Plus, I discovered I’m not fully grasping permissions and how everything is managed. Using Samba with Windows and mixing platforms isn’t helping either.
I believe I can assist with this final issue, having dealt with similar problems on my Synology setup. I'll describe the situation as it appeared on my device and I hope you can compare it to your own. Docker must operate under the same user account as the folder owner when mounting containers. Typically, this isn't a problem during normal Docker installations because Docker creates its own user and adds it to the admin group. However, on NAS systems it seems Docker struggles to form the required account and gain admin privileges, causing it to either hang or shut down after short periods. The solution involves searching for containers that accept UID & GID settings (User ID & Group ID). You then need to connect via SSH, fetch the admin user and group IDs, and input them as environment variables on the container's configuration page. This lets Docker run the container under the appropriate account/group, ensuring proper access to the root filesystem. Additionally, I've personally used SAMBA on Linux for years to store Windows data on Linux machines without facing permission conflicts between EXT4, ZFS, and NTFS. It’s unclear if you’re familiar with this, but SAMBA is the Linux service that enables Linux servers to function as Windows Domain Controllers. It’s designed to manage permissions between Linux and Windows environments.
We could discuss it on Discord or another platform. English isn’t my main language, so I’d appreciate it if we avoided unnecessary chats and clarifications. I get it—sometimes a simple explanation helps. Of course you can share the solution from our conversation (or at least what we tried and what didn’t work), so others can benefit. My setup is a bit tricky, and I’m trying to combine different guides without fully grasping everything. Linux isn’t forgiving, just like Windows—thanks a lot!
I don't own a Discord account, but it's actually quite straightforward once you understand how it works. For instance, if you're setting up a Valve Source Engine dedicated server, you can use a specific Steam CMD container that supports UID and GID assignments. The official one is available at the provided link, but it doesn't allow those parameters directly. I found another suitable version at a different registry that does support them. Then connect via SSH to your NAS, run the ID command to see all available UIDs and GIDs, pick the admin ones, and input them into the container's configuration page. That completes the setup.