Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Loss off network shares on 8.2
#51
(09-22-2022, 09:01 PM)Tim Curtis Wrote:
(09-22-2022, 08:38 PM)didier573 Wrote:
(09-22-2022, 08:24 PM)Tim Curtis Wrote: Could be useful. What format is the file system on the attached USB drive?

ExFAT

Looks like exfat format is not supported by NFS
https://forums.raspberrypi.com/viewtopic.php?t=309384

My drives are mostly fat32 (VFAT) which apparently works with NFS. I'm guessing that formats like NTFS etc are not supported by NFS either. 

I'll update the help for upcoming 8.2.1

Interesting. To test this I reformatted a USB thumbdrive to exfat and wrote some tracks to it.

Here's a snippet from the moOde 8.2.0 syslog when I started the NFS service with this USB drive mounted.


Code:
Sep 22 20:44:05 m82arm64 systemd[1]: Starting NFS Mount Daemon...
Sep 22 20:44:05 m82arm64 systemd[1]: Condition check resulted in RPC security service for NFS client and server being skipped.
Sep 22 20:44:05 m82arm64 systemd[1]: Condition check resulted in RPC security service for NFS server being skipped.
Sep 22 20:44:05 m82arm64 systemd[1]: Started NFSv4 ID-name mapping service.
Sep 22 20:44:05 m82arm64 rpc.mountd[2564751]: Version 1.3.3 starting
Sep 22 20:44:05 m82arm64 systemd[1]: Started NFS Mount Daemon.
Sep 22 20:44:05 m82arm64 systemd[1]: Starting NFS server and services...
Sep 22 20:44:05 m82arm64 exportfs[2564752]: exportfs: /media/B00F-155D does not support NFS export
Sep 22 20:44:05 m82arm64 systemd[1]: nfs-server.service: Control process exited, code=exited, status=1/FAILURE
Sep 22 20:44:05 m82arm64 systemd[1]: nfs-server.service: Failed with result 'exit-code'.
Sep 22 20:44:05 m82arm64 systemd[1]: Stopped NFS server and services.
Sep 22 20:44:05 m82arm64 systemd[1]: Stopping NFSv4 ID-name mapping service...
Sep 22 20:44:05 m82arm64 systemd[1]: Stopping NFS Mount Daemon...
Sep 22 20:44:05 m82arm64 systemd[1]: nfs-idmapd.service: Succeeded.
Sep 22 20:44:05 m82arm64 rpc.mountd[2564751]: Caught signal 15, un-registering and exiting.
Sep 22 20:44:05 m82arm64 systemd[1]: Stopped NFSv4 ID-name mapping service.
Sep 22 20:44:05 m82arm64 systemd[1]: nfs-mountd.service: Succeeded.
Sep 22 20:44:05 m82arm64 systemd[1]: Stopped NFS Mount Daemon.

So service flags the drive as not supporting NFS export. Too bad the service then fails and stops. This accounts for the behavior which was puzzling me.

OTOH. I then reformatted the USB drive as NTFS and wrote some tracks to it.

Here's the relevant syslog snippet this time.

Code:
Sep 22 21:52:30 m82arm64 systemd[1]: Starting NFS Mount Daemon...
Sep 22 21:52:30 m82arm64 systemd[1]: Condition check resulted in RPC security service for NFS client and server being skipped.
Sep 22 21:52:30 m82arm64 systemd[1]: Condition check resulted in RPC security service for NFS server being skipped.
Sep 22 21:52:30 m82arm64 systemd[1]: Started NFSv4 ID-name mapping service.
Sep 22 21:52:30 m82arm64 rpc.mountd[2584612]: Version 1.3.3 starting
Sep 22 21:52:30 m82arm64 systemd[1]: Started NFS Mount Daemon.
Sep 22 21:52:30 m82arm64 systemd[1]: Starting NFS server and services...
Sep 22 21:52:31 m82arm64 kernel: [345002.572959] NFSD: Using UMH upcall client tracking operations.
Sep 22 21:52:31 m82arm64 kernel: [345002.572983] NFSD: starting 90-second grace period (net f0000000)
Sep 22 21:52:31 m82arm64 systemd[1]: Finished NFS server and services.

This time the NFS service is running and the USB drive is exported, can be detected in a second player, mounted as a music source, etc.

Regards,
Kent
Reply
#52
(09-23-2022, 02:03 AM)TheOldPresbyope Wrote:
(09-22-2022, 09:01 PM)Tim Curtis Wrote:
(09-22-2022, 08:38 PM)didier573 Wrote:
(09-22-2022, 08:24 PM)Tim Curtis Wrote: Could be useful. What format is the file system on the attached USB drive?

ExFAT

Looks like exfat format is not supported by NFS
https://forums.raspberrypi.com/viewtopic.php?t=309384

My drives are mostly fat32 (VFAT) which apparently works with NFS. I'm guessing that formats like NTFS etc are not supported by NFS either. 

I'll update the help for upcoming 8.2.1

Interesting. To test this I reformatted a USB thumbdrive to exfat and wrote some tracks to it.

Here's a snippet from the moOde 8.2.0 syslog when I started the NFS service with this USB drive mounted.


Code:
Sep 22 20:44:05 m82arm64 systemd[1]: Starting NFS Mount Daemon...
Sep 22 20:44:05 m82arm64 systemd[1]: Condition check resulted in RPC security service for NFS client and server being skipped.
Sep 22 20:44:05 m82arm64 systemd[1]: Condition check resulted in RPC security service for NFS server being skipped.
Sep 22 20:44:05 m82arm64 systemd[1]: Started NFSv4 ID-name mapping service.
Sep 22 20:44:05 m82arm64 rpc.mountd[2564751]: Version 1.3.3 starting
Sep 22 20:44:05 m82arm64 systemd[1]: Started NFS Mount Daemon.
Sep 22 20:44:05 m82arm64 systemd[1]: Starting NFS server and services...
Sep 22 20:44:05 m82arm64 exportfs[2564752]: exportfs: /media/B00F-155D does not support NFS export
Sep 22 20:44:05 m82arm64 systemd[1]: nfs-server.service: Control process exited, code=exited, status=1/FAILURE
Sep 22 20:44:05 m82arm64 systemd[1]: nfs-server.service: Failed with result 'exit-code'.
Sep 22 20:44:05 m82arm64 systemd[1]: Stopped NFS server and services.
Sep 22 20:44:05 m82arm64 systemd[1]: Stopping NFSv4 ID-name mapping service...
Sep 22 20:44:05 m82arm64 systemd[1]: Stopping NFS Mount Daemon...
Sep 22 20:44:05 m82arm64 systemd[1]: nfs-idmapd.service: Succeeded.
Sep 22 20:44:05 m82arm64 rpc.mountd[2564751]: Caught signal 15, un-registering and exiting.
Sep 22 20:44:05 m82arm64 systemd[1]: Stopped NFSv4 ID-name mapping service.
Sep 22 20:44:05 m82arm64 systemd[1]: nfs-mountd.service: Succeeded.
Sep 22 20:44:05 m82arm64 systemd[1]: Stopped NFS Mount Daemon.

So service flags the drive as not supporting NFS export. Too bad the service then fails and stops. This accounts for the behavior which was puzzling me.

OTOH. I then reformatted the USB drive as NTFS and wrote some tracks to it.

Here's the relevant syslog snippet this time.

Code:
Sep 22 21:52:30 m82arm64 systemd[1]: Starting NFS Mount Daemon...
Sep 22 21:52:30 m82arm64 systemd[1]: Condition check resulted in RPC security service for NFS client and server being skipped.
Sep 22 21:52:30 m82arm64 systemd[1]: Condition check resulted in RPC security service for NFS server being skipped.
Sep 22 21:52:30 m82arm64 systemd[1]: Started NFSv4 ID-name mapping service.
Sep 22 21:52:30 m82arm64 rpc.mountd[2584612]: Version 1.3.3 starting
Sep 22 21:52:30 m82arm64 systemd[1]: Started NFS Mount Daemon.
Sep 22 21:52:30 m82arm64 systemd[1]: Starting NFS server and services...
Sep 22 21:52:31 m82arm64 kernel: [345002.572959] NFSD: Using UMH upcall client tracking operations.
Sep 22 21:52:31 m82arm64 kernel: [345002.572983] NFSD: starting 90-second grace period (net f0000000)
Sep 22 21:52:31 m82arm64 systemd[1]: Finished NFS server and services.

This time the NFS service is running and the USB drive is exported, can be detected in a second player, mounted as a music source, etc.

Regards,
Kent

Hello, I've just tried with a FAT USB SSD and it works !!!  Smile
I had to restart everything and update the library but here it is.

My SSD was in ExFAT when I bought it and NTFS is not really compatible with my iMac. 

Thank you so much Tim and Kent for your support  Cool
Reply
#53
(09-23-2022, 06:10 AM)didier573 Wrote:
(09-23-2022, 02:03 AM)TheOldPresbyope Wrote:
(09-22-2022, 09:01 PM)Tim Curtis Wrote:
(09-22-2022, 08:38 PM)didier573 Wrote:
(09-22-2022, 08:24 PM)Tim Curtis Wrote: Could be useful. What format is the file system on the attached USB drive?

ExFAT

Looks like exfat format is not supported by NFS
https://forums.raspberrypi.com/viewtopic.php?t=309384

My drives are mostly fat32 (VFAT) which apparently works with NFS. I'm guessing that formats like NTFS etc are not supported by NFS either. 

I'll update the help for upcoming 8.2.1

Interesting. To test this I reformatted a USB thumbdrive to exfat and wrote some tracks to it.

Here's a snippet from the moOde 8.2.0 syslog when I started the NFS service with this USB drive mounted.


Code:
Sep 22 20:44:05 m82arm64 systemd[1]: Starting NFS Mount Daemon...
Sep 22 20:44:05 m82arm64 systemd[1]: Condition check resulted in RPC security service for NFS client and server being skipped.
Sep 22 20:44:05 m82arm64 systemd[1]: Condition check resulted in RPC security service for NFS server being skipped.
Sep 22 20:44:05 m82arm64 systemd[1]: Started NFSv4 ID-name mapping service.
Sep 22 20:44:05 m82arm64 rpc.mountd[2564751]: Version 1.3.3 starting
Sep 22 20:44:05 m82arm64 systemd[1]: Started NFS Mount Daemon.
Sep 22 20:44:05 m82arm64 systemd[1]: Starting NFS server and services...
Sep 22 20:44:05 m82arm64 exportfs[2564752]: exportfs: /media/B00F-155D does not support NFS export
Sep 22 20:44:05 m82arm64 systemd[1]: nfs-server.service: Control process exited, code=exited, status=1/FAILURE
Sep 22 20:44:05 m82arm64 systemd[1]: nfs-server.service: Failed with result 'exit-code'.
Sep 22 20:44:05 m82arm64 systemd[1]: Stopped NFS server and services.
Sep 22 20:44:05 m82arm64 systemd[1]: Stopping NFSv4 ID-name mapping service...
Sep 22 20:44:05 m82arm64 systemd[1]: Stopping NFS Mount Daemon...
Sep 22 20:44:05 m82arm64 systemd[1]: nfs-idmapd.service: Succeeded.
Sep 22 20:44:05 m82arm64 rpc.mountd[2564751]: Caught signal 15, un-registering and exiting.
Sep 22 20:44:05 m82arm64 systemd[1]: Stopped NFSv4 ID-name mapping service.
Sep 22 20:44:05 m82arm64 systemd[1]: nfs-mountd.service: Succeeded.
Sep 22 20:44:05 m82arm64 systemd[1]: Stopped NFS Mount Daemon.

So service flags the drive as not supporting NFS export. Too bad the service then fails and stops. This accounts for the behavior which was puzzling me.

OTOH. I then reformatted the USB drive as NTFS and wrote some tracks to it.

Here's the relevant syslog snippet this time.

Code:
Sep 22 21:52:30 m82arm64 systemd[1]: Starting NFS Mount Daemon...
Sep 22 21:52:30 m82arm64 systemd[1]: Condition check resulted in RPC security service for NFS client and server being skipped.
Sep 22 21:52:30 m82arm64 systemd[1]: Condition check resulted in RPC security service for NFS server being skipped.
Sep 22 21:52:30 m82arm64 systemd[1]: Started NFSv4 ID-name mapping service.
Sep 22 21:52:30 m82arm64 rpc.mountd[2584612]: Version 1.3.3 starting
Sep 22 21:52:30 m82arm64 systemd[1]: Started NFS Mount Daemon.
Sep 22 21:52:30 m82arm64 systemd[1]: Starting NFS server and services...
Sep 22 21:52:31 m82arm64 kernel: [345002.572959] NFSD: Using UMH upcall client tracking operations.
Sep 22 21:52:31 m82arm64 kernel: [345002.572983] NFSD: starting 90-second grace period (net f0000000)
Sep 22 21:52:31 m82arm64 systemd[1]: Finished NFS server and services.

This time the NFS service is running and the USB drive is exported, can be detected in a second player, mounted as a music source, etc.

Regards,
Kent

Hello, I've just tried with a FAT USB SSD and it works !!!  Smile
I had to restart everything and update the library but here it is.

My SSD was in ExFAT when I bought it and NTFS is not really compatible with my iMac. 

Thank you so much Tim and Kent for your support  Cool

Great that you got it working!
I remember I was doubting how to format when I prepared my USB SSD. I actually cannot remember which specific format but I must have chosen wisely without knowing.... Big Grin

Enjoy your new setup!
Reply
#54
The good thing about Fat32 (VFAT) is that is also works on MacOS.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#55
Hi all,

what about Ext3 / Ext4?

I cannot try ATM, as I ve not upgraded yet.

Cheers, Al.
Reply
#56
Yes ext3 and 4 will work
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#57
Hi,
after sharing a remote HDD on another RPi, I want now to use it directly on moode and share it. I'm on 8.2.2 and I use Samba option.
On Linux Mint I can see 'MOODE' and 'moode' in the network tab of Nemo, but both ask me for user and password. 'pi' / 'moodeaudio' (like SSH) doesn't work... After some attempt, the network tab doesn't respond, even on the clients that usually work, or the 'windows network' item.
Reply
#58
(10-30-2022, 08:26 PM)rph-r Wrote: Hi,
after sharing a remote HDD on another RPi, I want now to use it directly on moode and share it. I'm on 8.2.2 and I use Samba option.
On Linux Mint I can see 'MOODE' and 'moode' in the network tab of Nemo, but both ask me for user and password. 'pi' / 'moodeaudio' (like SSH) doesn't work... After some attempt, the network tab doesn't respond, even on the clients that usually work, or the 'windows network' item.

I interpret this to mean you've plugged a USB HDD into your 8.2.2 moOde player; you've configured the player to enable the local SMB file sharing service; and you're trying to open the resulting SMB share using the Nemo file manager app on another host running Linux Mint.

If this interpretation is correct, then I don't understand your difficulty.

I am running essentially the same setup here---just with USB thumbdrives rather than HDDs. 

I have no difficulty opening and browsing through my moOde players' SMB shares using the Caja file manager in Linux Mint (I'm running the MATE desktop rather than Cinnamon, but I believe Caja and Nemo behave the same way). When challenged, I can choose either to be a registered user and enter the moOde credentials or to be a anonymous user. Either way I can open a share, browse it, read files from it, or write files to it.

Regards,
Kent
Reply
#59
(10-30-2022, 09:05 PM)TheOldPresbyope Wrote: I interpret this to mean you've plugged a USB HDD into your 8.2.2 moOde player; you've configured the player to enable the local SMB file sharing service; and you're trying to open the resulting SMB share using the Nemo file manager app on another host running Linux Mint.

If this interpretation is correct, then I don't understand your difficulty.

That's correct!
It asks me for authentification, I have no 'guest' option. With any username/pwd I get something like: 'cannot get server sharing list: invalid argument'.
Reply
#60
@rph-r

Before trying anything else, try rebooting both the Linux Mint box and the moOde player (with the HDD still connected and without turning off SMB share service). There may be a stale cache causing what you see.

Regards,
Kent
Reply


Forum Jump: