soana

Members
  • Posts

    242
  • Joined

  • Last visited

Report Comments posted by soana

  1. On 3/25/2022 at 10:58 AM, wgstarks said:

    Did you add server multi channel support = no?

    Made no difference for me - using Catalina macOS - not sure if that matters.

     

    Edit: I had a typo in my smb-settings.conf file, after fixing it the shares seem to be working OK but the TimeMachine share is not working with macOS

  2. On 11/3/2021 at 3:24 PM, Toskache said:

    Problem with macOS Monterey?

     

    I updated from 6.9.2 to 6.10.0-rc2. At first everything looked fine...
    But then when I tried to copy two larger files from a macOS (Monterey) to a samba share, the copy process did not start. The share was even ejected. The share was mounted via simple "network browsing" (smb://nas._smb._tcp.local/data). The whole thing is reproducible. It seems that copying smaller files works. I reverted back to 6.9.2.

     

    There is the following "Samba extra configuration":

     

    [global]
    #unassigned_devices_start
    #Unassigned devices share includes
       include = /tmp/unassigned.devices/smb-settings.conf
    #unassigned_devices_end
    
    #vfs_recycle_start
    #Recycle bin configuration
       syslog only = No
       syslog = 0
       logging = 0
       log level = 0 vfs:0
    #vfs_recycle_end
    

     

    I have a similar issue with Catalina, samba is on and off. Reverted back to rc1 and everything seems to be OK.

    In my case the connection to the Tower samba shares will drop on a random basis. Not sure how to reproduce this issue.

    • Like 2
  3. On 11/5/2019 at 2:02 PM, trurl said:

     

    
    Nov  3 10:21:43 Tower emhttpd: unclean shutdown detected
    

    The array stopped/started status is stored on flash. If for some reason flash can't be written when shutting down, or if power is removed before stopping the array, then you get an unclean shutdown which results in a parity check.

     

    Put flash in PC and let it checkdisk.

    Hmm, I did not perform a checkdisk yet but I did a array stop/start and then a reboot followed by another stop/start array and no more parity checks started. Will run a checkdisk next and keep an eye on it.