Usb server mode
Answered
-
Official comment
The drive is mounted as a Guest account with no password. However, depending on the original drive format, various PC security scenarios may result in the drive as read-only so you cannot drag and drop music to it.
-
various PC security scenarios may result in the drive as read-only so you cannot drag and drop music to it.
Which begs the question: What format or security scenario would allow network read and write access?
0 -
...such as macOS devices can read but not write to NTFS drives...
0 -
What format would allow this network write access?
0 -
Please answer
Thank you
0 -
Same question here. My drive is Read and Write from my computer, but it becomes Read only when connected from my computer to my Bluesound device in server mode as Guest. So the OP's question remain: could we get a way to connect to the drive in such a way that it becomes Read AND Write. I don't know, say Admin + 1234, if the Guest access prevents Write?
Regards0 -
In my Node2, BluOS mounts the shares as "CIFS ro" meaning read only. As it is in the firmware I guess this is the way Bluesound works in all devices. Unless they change the mounting procedure, writing to the share in server mode will remain impossible.
0 -
Thanks Alain. This clarifies the situation. Would be nice if this limitation could be modified through a future firmware update. This way, I could automate updates/syncs of the USB drive from my computer. I also tried sharing my computer library over network to the Node, but it never works. The player's indexing scan jams after about 4000 songs, sometimes 5000. On another streamer from a rival company, the network sharing works flawlessly. I have over 30k songs.
0 -
Hi Nick
Your index is crashing due to a corrupt file as BluOS can index over 200,000 songs. Please select Settings, Send Support Request so we may review the log file and help find the issue.
See here for more details; https://support.bluos.net/hc/en-us/articles/360000235328
0 -
Tony/Nick, and herein lies one of my core issues with re-indexing and support ... WHY don't you provide ANY kind of diagnostic reports to us the users ... regarding re-indexing and issues ... when the re-index stops, at some point before it is complete it would be very helpful to US, the user to know where ... at least that way we could remove the file/album from our library, at least on a temp basis, to see if that is the cause of the issue ... if it is, then we can, check the album files, reload the album, etc. Not having ANY idea where the index got to, where it stopped, the album name where it stopped is extremely frustrating for the user, I speak for my self but I am sure that other users feel the same ... and giving an error log to the user should NOT be difficult ... Please consider adding some form of diagnostics to the user interface ... Thank you
2 -
Excellent suggestion. Currently, troubleshooting indexing errors by searching for the offending file is hit and miss.
1 -
You might try
<IP address of Node>/diag?print=1
and search for "corrupted" in the output, I got this on a trial:
No filetype -- scan gone wrong /tmp/mnt/36EE4FBCEE4F7363/corrupted/front.png.m4a
Obviously, it would have been appropriate if some sensible message would be relayed to the user
0 -
Tony: I eventually solved my problem of indexing my shared files from my Mac, this morning. I went to Diagnotic/Rebuilt index instead of reindexing from the Music library. After several tries, it finally went through my 30K+ files. So I guess I don't need my USB drive for that need, anymore. But a few interesting suggestions came from the thread, nevertheless.
Best0
Please sign in to leave a comment.
Comments
13 comments