![]() |
[SOLVED] 9.1.x: NVME samba share size wrong when mounted on Windows - Printable Version +- Moode Forum (https://moodeaudio.org/forum) +-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3) +--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7) +--- Thread: [SOLVED] 9.1.x: NVME samba share size wrong when mounted on Windows (/showthread.php?tid=7102) |
9.1.x: NVME samba share size wrong when mounted on Windows - Matter - 11-17-2024 Hey community, I've been using moode since version 5.x. After testing various commercial streamers I am super happy to have found a setup that offers what I like and need. Thank you very much Tim and team! Recently, I moved from a RPi4 setup to the Pi4 Compute Module & official IO board with an NVME disk (via IO board's PCIe slot) as internal music storage. The previous micro SD card via USB adapter had become too small, so I decided to go for an 4TB SSD which could also function as a small file server for this and that. Moode version is 9.1.4, fresh setup but also happened with a system clone of my previous Pi4 setup. Here comes the trouble:
When I tried to mount the NVME disk via /etc/fstab (after unmounting it in the Library section) moode didn't come back after the reboot. Since the system runs headless, I had no chance to debug. Maybe this is a Samba settings or config issue. Or maybe I should mount the NVME disk via fstab right away instead of using moode Library's option. Does anyone have an idea or has gone through a similar issue with a RPi5 setup with NMVE ssd? Cheers, Matt RE: 9.1.x: NVME samba share size wrong when mounted on Windows - Tim Curtis - 11-17-2024 Try editing /etc/samba/smb.conf and add a share block like below then restart SMB (Samba) [NVMe3600] comment = NVMe 3600 Mount path = /mnt/NVME/3600 read only = No guest ok = Yes Then connect to the "NVMe3600" share from Windows and see if the correct size is reported. RE: 9.1.x: NVME samba share size wrong when mounted on Windows - Matter - 11-17-2024 Creating an extra entry in smb.conf solved the problem. Size in Windows is now reported correctly. So simple... Thank you very much, Tim! Kind regards, Matt |