• Network errors when trying to write to shares over SMB (windows)


    BrandonHoughton
    • Closed Minor

    When I initiate file transfers to shares (even public ones) the transfer seems to go through for files smaller than the initial chunk sent over (folders, 1KB files, etc.). For larger files, both windows and winscp stall and do not report any transfer statistics (such as transfer speed or bytes transferred). However, if the windows dialog is left long enough sometimes the files actually do make it to the share, although no transfer is noted by unraid's disk activity trackers.

    No parity check or other operations should be interfering and this worked well as soon as yesterday (only change would be additional docker containers)

    SCP'ing files works reliably but is incredibly slow (300KB/s) compared to typical (110MB/s)

    Please let me know if there is any additional info I should provide. There are also some weird log files:

     

    Nov 14 15:51:58 SaberStation emhttpd: Starting services...
    Nov 14 15:51:58 SaberStation emhttpd: shcmd (365): /etc/rc.d/rc.samba restart
    Nov 14 15:52:00 SaberStation root: Starting Samba: /usr/sbin/smbd -D
    Nov 14 15:52:00 SaberStation root: /usr/sbin/nmbd -D
    Nov 14 15:52:00 SaberStation root: /usr/sbin/wsdd
    Nov 14 15:52:00 SaberStation root: /usr/sbin/winbindd -D
    Nov 14 15:52:33 SaberStation emhttpd: req (3): shareNameOrig=public_data&shareName=public_data&shareComment=Share+containing+data+publicly+accessable+by+minerl+server&shareAllocator=highwater&shareFloor=0&shareSplitLevel=&shareInclude=&shareExclude=&shareUseCache=yes&cmdEditShare=Apply&csrf_token=****************
    Nov 14 15:52:33 SaberStation emhttpd: Starting services...
    Nov 14 15:52:33 SaberStation emhttpd: shcmd (376): /etc/rc.d/rc.samba restart
    Nov 14 15:52:35 SaberStation root: Starting Samba: /usr/sbin/smbd -D
    Nov 14 15:52:35 SaberStation root: /usr/sbin/nmbd -D
    Nov 14 15:52:35 SaberStation root: /usr/sbin/wsdd
    Nov 14 15:52:35 SaberStation root: /usr/sbin/winbindd -D
    Nov 14 15:52:48 SaberStation emhttpd: req (4): shareName=public_data&shareExport=e&shareSecurity=public&changeShareSecurity=Apply&csrf_token=****************
    Nov 14 15:52:48 SaberStation emhttpd: Starting services...
    Nov 14 15:52:48 SaberStation emhttpd: shcmd (387): /etc/rc.d/rc.samba restart
    Nov 14 15:52:51 SaberStation root: Starting Samba: /usr/sbin/smbd -D
    Nov 14 15:52:51 SaberStation root: /usr/sbin/nmbd -D
    Nov 14 15:52:51 SaberStation root: /usr/sbin/wsdd
    Nov 14 15:52:51 SaberStation root: /usr/sbin/winbindd -D
    Nov 14 15:52:51 SaberStation emhttpd: shcmd (396): smbcontrol smbd close-share 'public_data'
    Nov 14 16:13:56 SaberStation sshd[18652]: Accepted none for root from 192.168.1.11 port 63059 ssh2
    Nov 14 16:32:35 SaberStation kernel: veth1b0c38f: renamed from eth0
    Nov 14 16:32:35 SaberStation kernel: docker0: port 1(veth78017cd) entered disabled state
    Nov 14 16:32:35 SaberStation avahi-daemon[18802]: Interface veth78017cd.IPv6 no longer relevant for mDNS.
    Nov 14 16:32:35 SaberStation avahi-daemon[18802]: Leaving mDNS multicast group on interface veth78017cd.IPv6 with address fe80::b4af:fff:fec7:7493.
    Nov 14 16:32:35 SaberStation kernel: docker0: port 1(veth78017cd) entered disabled state
    Nov 14 16:32:35 SaberStation kernel: device veth78017cd left promiscuous mode
    Nov 14 16:32:35 SaberStation kernel: docker0: port 1(veth78017cd) entered disabled state
    Nov 14 16:32:35 SaberStation avahi-daemon[18802]: Withdrawing address record for fe80::b4af:fff:fec7:7493 on veth78017cd.

     

    saberstation-diagnostics-20191114-2124.zip




    User Feedback

    Recommended Comments

    Why did you configure bonding with LACP while only eth0 is up (eth1 is down)?

    LACP requires compatible switch support. Does your switch support LACP?

    Remove bonding and test with a single interface.

     

    Your snippet shows the normal sequence when starting docker containers, nothing unusual.

     

    Link to comment

    Thanks for the pointers - bonding was an experiment. Switch is an edgerouter 12 which indeed supports LACP, though I was unable to configure this properly (illegal loop-backs were occurring when both eth0 and eth1 were plugged in.) I rebooted the machine and now unraid is functioning properly which is strange but welcome. Only other anomaly was that I did stop an unscheduled parity check after accidental hard shutdown. If nothing here is out of the ordinary I will just close the ticket then and hope that I don't encounter this again.

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.