check with "mount" how the hd is mounted. Maybe it is mounted "read only" ?
Hi,
I've been occupied for a bit but I have a few spare moments to try and help out
What issue are you experiencing?
-Tim
FYI it seems another user has exact same issue and gave up on a fix
Old Yesterday, 02:02 PM #10216
etimalandain is offline etimalandain France
diyAudio Member
Moode is a great piece of software and, as you said, the price is very reasonable.
However, same issue here with my pi3 and attached USB drive. Works perfectly with the other solutions I tested (Volumio, Runeaudio ...) but there's no way I can upload music to the HDD via my network with Moode.
Asked for help on this forum some time ago, appears my case was unknown and none of the suggested solutions worked. By the way, FTP uploading doesn't work either (probably for the same reasons).
Tried to modify the rights on the drive, without any success.
I got tired of spending more time on this than on listening to music, so now I just unplug the drive from the pi3 and plug it to my computer when I want to transfer new music (much faster transfer, anyway ...)
Not a totally satisfying solution but it's the only one I found. If you ever solve the problem, please tell us about it !
Etienne
Hi,
I need more detail than that in order to be able to troubleshoot.
For example:
1) What client (Windows, Mac, etc)?
2) What method are you using to connect to the drive?
3) Whats the text of any error messages that you receive?
4) What type of disk and whats the disk label name?
-Tim
Ah - so you didn't bother following a suggestion based on sound advice that was made days ago.
That figures.....
You are assuming to much, I will recheck for the new SD image from the countless images rebuilds I have checked this.
and also did acknowledge maybe I don't check correctly the reason why with fresh info I will recheck.
Last edited:
Details that I explained before but fair to say got lost in the noise
windows 10 pro
using file explorer - the only method I am really interested to use
exact error - there is not enough space on usb. you need additional space
hdd is a hgst 1tb laptop drive with label "storage"
trying to access via \\moode\USB\storage or \\ip address\USB\storage
should mention have access to all shares moode creates nas, radio, sdcard, usb
output from fdisk -l
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 8192 93596 85405 41.7M c W95 FAT32 (LBA)
/dev/mmcblk0p2 94208 5419007 5324800 2.6G 83 Linux
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6a86893e
Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 1953521663 1953519616 931.5G 7 HPFS/NTFS/exFAT
output on mount
/dev/mmcblk0p2 on / type ext4 (rw,noatime,data=ordered)
devtmpfs on /dev type devtmpfs (rw,relatime,size=470176k,nr_inodes=117544,mode=7 55)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmod e=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xa ttr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatim e,cpu,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blki o)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,mem ory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,de vices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,fr eezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,ne t_cls)
tmpfs on /etc/machine-id type tmpfs (ro,mode=755)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=22,pgrp=1,time out=300,minproto=5,maxproto=5,direct)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/var/local/moode.sqsh on /var/www type squashfs (ro,relatime)
/dev/mmcblk0p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=43 7,iocharset=ascii,shortname=mixed,errors=remount-ro)
/dev/sda1 on /media/storage type fuseblk (rw,nosuid,nodev,noexec,noatime,sync,us er_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=94960k,mode=70 0,uid=1000,gid=1000)
Last edited:
Hi Mike,
USB is a symlink to /media so //moode/USB/storage is correct.
The root of the problem though is that moOde3 series does not create Samba share blocks in /etc/samba/smb/conf for the disk_lable folder.
-Tim
MS has virtual disk systems for web developers that might help:
Microsoft Edge Developer website - Microsoft Edge Development
You can use virtual box which is free (Oracle VM VirtualBox) or a trial of one of the commercial vm applications.
I resolved issue to copy my files trought network with the expansion of the filesystem, so there is more space on system to handle filecopy.
Try this way
Hi,
It's more of a time issue that a technical issue. I can barely keep up with whats on my plate currently :-0
-Tim
Fair enough.
It's probably worth remembering that while we've paid a small amount to help compensate Tim for his time it's undoubtedly nowhere near enough that he'd be able to do it full time, even though it must seem like it some times.
AFAIK windows 10 is no more supporting unc paths \\pcname\share.
Maybe it is a problem with samba share and win 10 ?
just google for "windows 10 unc path disabled"
Windows 10 denying UNC Paths
Maybe it is a problem with samba share and win 10 ?
just google for "windows 10 unc path disabled"
Windows 10 denying UNC Paths
Thanks for looking into it.
I hope in the future all knowing people around here just not jump to the conclusion the new guys are just stupid because they seen it all.
I think that is a grossly unfair accusation to throw about.
All those who have chipped in have been trying to help by sharing their own experiences in the hope of cracking your problem while you were waiting for Tim to have the time to look into it.
I am far from 'all knowing' but have had my fair share of frustrations trying to get software to work on the Pi and also learned a lot the hard way about some of the limitations that hardware can throw up.
You posted a couple of questions and other posters have responded - thats how forums work !!!
Quite honestly, at times you have been downright rude and insulting to people who were simply trying to help -- rather than showing at least some thanks for their efforts and respecting them for at least trying.
Good morning from sunny Queensland
This was my workaround as well. The issue for me was that the free space reported for the USB attached storage was the same as the free space reported for the SD card. Without expanding the filesystem on the SD card, my USB drives appeared to have only MBs of free space and therefore I could not copy files of a reasonable size. After expanding the filesystem there were GBs of reported free space and that was sufficient for my needs as long as each copy job was within that size restriction. Interestingly, copying files didn't seem to change the reported free size for the USB disks, so I have copied quite a lot of files in batches which are cumulatively much more data than the reported free space (i.e. the free space on the SD card).
I observed this using Win 7 Ultimate and Ubuntu 16.04. I now also have Win 10 but have not attempted any copying over the network from that. If I get a chance in the next couple of days, I'll revisit this issue in my setup.
A lot happening over on the Moode website. Tim is working very hard at the moment. Ganbare!
Richard
This was my workaround as well. The issue for me was that the free space reported for the USB attached storage was the same as the free space reported for the SD card. Without expanding the filesystem on the SD card, my USB drives appeared to have only MBs of free space and therefore I could not copy files of a reasonable size. After expanding the filesystem there were GBs of reported free space and that was sufficient for my needs as long as each copy job was within that size restriction. Interestingly, copying files didn't seem to change the reported free size for the USB disks, so I have copied quite a lot of files in batches which are cumulatively much more data than the reported free space (i.e. the free space on the SD card).
I observed this using Win 7 Ultimate and Ubuntu 16.04. I now also have Win 10 but have not attempted any copying over the network from that. If I get a chance in the next couple of days, I'll revisit this issue in my setup.
A lot happening over on the Moode website. Tim is working very hard at the moment. Ganbare!
Richard
As a bystander I'm with biotronik on this. He asked a legitimate question, interacted well, but was faced with some silly answers and rude insistence from some contributors. I can see that Tim is struggling with the requirements of requiring payment for his work. Some level of support is reasonable to expect, and he delivered that.
Good morning from sunny Queensland
This was my workaround as well. The issue for me was that the free space reported for the USB attached storage was the same as the free space reported for the SD card. Without expanding the filesystem on the SD card, my USB drives appeared to have only MBs of free space and therefore I could not copy files of a reasonable size. After expanding the filesystem there were GBs of reported free space and that was sufficient for my needs as long as each copy job was within that size restriction. Interestingly, copying files didn't seem to change the reported free size for the USB disks, so I have copied quite a lot of files in batches which are cumulatively much more data than the reported free space (i.e. the free space on the SD card).
I observed this using Win 7 Ultimate and Ubuntu 16.04. I now also have Win 10 but have not attempted any copying over the network from that. If I get a chance in the next couple of days, I'll revisit this issue in my setup.
A lot happening over on the Moode website. Tim is working very hard at the moment. Ganbare!
Richard
Hi,
Yes, changes are being made that will allow moOde to move forward and continue to be enjoyed. Just hang in there with me through the transition
The root cause of the free space issue is that moOde 3 series does not create Samba share blocks for each disk_label thats auto-mounted.
What ends up happening is Samba reports only the free space of the root partition where /media folder resides. Even if u expand SD card, Samba only reports this as max free space and not the actual free space available on the attached USB drive. This is fixed in moOde 4
-Tim