Empty folder after setting up share to Windows machine

Max2Play Home 2016 (en) Forums Max2Play on Raspberry PI Empty folder after setting up share to Windows machine

This topic contains 12 replies, has 2 voices, and was last updated by  ih8gates 3 years, 4 months ago.

Viewing 13 posts - 1 through 13 (of 13 total)
  • 7. April 2018 at 15:59 #35046

    I’m running the Stretch-based image on an rPi B+

    When I set up a mount to my music folder on a Windows 8 machine, I get no errors, but the folder is empty. The folder is successfully created, but with no contents.

    Fields in the M2P admin:

    //192.168.1.110/music
    /mnt/music
    cifs
    username=user,password=pass,iocharset=utf8,vers=1.0

    I also tried the last field without „iocharset=utf8,vers=1.0“

    I can successfully create the mount with:

    sudo mount //192.168.1.110/music /mnt/music -t cifs -o username=user,password=pass

    Not sure if this is an issue, but my password has a ! in it.

    But not being a Linux guy (and new to Max2Play), I’m not sure how to make that persist reboots.

    Any suggestion on what I’m missing?

    • This topic was modified 3 years, 5 months ago by  ih8gates.
    9. April 2018 at 15:01 #35076

    Hi ih8gates,

    Could you try mounting a share with a different pw without special characters to rule this out as source of error? Also, please make sure the files on your mount do not have any special rights or security encryption.

    9. April 2018 at 17:04 #35080

    That didn’t work either. I created a simple user and password on the Windows machine. The mount folder is created, but it’s empty.

    9. April 2018 at 17:07 #35081

    Hmmm. I decided to reboot and now the mount is working!

    9. April 2018 at 21:15 #35089

    So, when it failed for me the 2nd time, it was after a fresh re-install. And failed the same way. I wonder if the script was creating the correct info to recreate the mount on reboot, but wasn’t properly executing the mount command when it created it the first time.

    10. April 2018 at 14:50 #35106

    Could you share the debug info log of your second error?

    10. April 2018 at 22:14 #35112

    Since I’m no longer getting the error, where would I find that log?

    11. April 2018 at 11:36 #35119

    There should be a Blue Text in the middle named Debug Info. When clicking it a window should drop down.

    13. April 2018 at 3:07 #35155

    The debug info just shows the mount info:

    
    //192.168.1.110/music /mnt/music cifs user=USER,password=PASS,sec=ntlm,iocharset=utf8,vers=1.0
    

    Same as it did when it failed.

    13. April 2018 at 10:04 #35156

    Hi ih8gates,

    Okay, if the problem happens again, please share as much info as you can in this topic and I’ll try to recreate it here.

    Glad to hear, it did not happen again, though 🙂

    13. April 2018 at 15:23 #35170

    I’m pretty sure that I checked the debug info when I first had the problem and it did the same. Debug just repeated the mount info.

    It’s easy to reproduce the issue. At least on my install. If I create a new share, the folder is create, but it’s empty. Restart the Pi and the share works correctly. Could it be an issue with the move to Stretch to support the B+?

    23. April 2018 at 10:49 #35265

    Does it only occur on the first instance or does the share disappear periodically after being created?

    23. April 2018 at 17:24 #35283

    It only happened the first instance. After a reboot, the share works consistently.

Viewing 13 posts - 1 through 13 (of 13 total)

You must be logged in to reply to this topic.

Register here