Hello,

 

I was curious on unraid 5 final how do I enable samba logging?

or how would I troubleshoot with wireshark?

 

I am having trouble with samba blocking my windows 7.1 computers on large file transfers ...

 

I've set all shares and disks public and tried it

I've set all disks and shares secure and selected all users which need access to read/write ...

 

I've run the new.perms untility multiple times ...

 

alternatively where could I find a good samba troubleshooting tutorial?

 

Happens with safemode and with plugins ... nothing lists in syslog so I was hoping I might find something in the samba logs

 

smb-extra.conf

# Debug logging information
log file = /var/log/samba/%m.log
log level = 3 
max log size = 50

 

I add this and restart samba and I get 0 byte files for all my computers that have ip addresses and access unRaid.

 

Thanks for any time and help,

Bobby

 

Here's my modified syslinux.cfg

 

gave myself two 4 GB options / regular and safemode

 

added the syslog =3 line along with changing max log size to 8191 in the smb-extra.conf file

 

default menu.c32
menu title Lime Technology LLC
prompt 0
timeout 100
label unRAID OS
  kernel bzimage
  append initrd=bzroot
label unRAID OS (Safe Mode)
  kernel bzimage
  append initrd=bzroot unraidsafemode
label unRAID OS 4GB
  menu default
  kernel bzimage
  append mem=4095M initrd=bzroot
label unRAID OS (Safe Mode) 4GB
  kernel bzimage
  append mem=4095M initrd=bzroot unraidsafemode
label Memtest86+
  kernel memtest

 

Still not working,

Is there another way to limit the ram?

 

log.smbd and log.nmdb are the only files in the /var/log/samba directory with anything in them.

 

In teracopy ... first I get a network name is no longer available error then I get a cannot overwrite file error if I retry.

Fastcopy, robocopy also error out on files larger than 2 GB.

 

Intel Pro 1000 pci-e nics in both computers

 

What should I be looking for in the smbd logs?  and do they (the syslog) rotate? (will I run out of memory?)

 

In the morning I'll post a syslog of a failed file transfer to see if there is something I'm missing.

 

I'll boot to safemode with 4GB ram

 

Thanks for your time and help,

Bobby

 

 

 

I rebooted the day before with the mem=4095 option and still had troubles ...

 

I deleted  all the credential stores on Windows 7 a few days ago ...

 

Here is my go file

 

#!/bin/bash
# Start the Management Utility

/usr/local/sbin/emhttp &

echo emhttp started

 

here is my smb-extra.conf file

 

 

# Documentation http://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html
# Forum topic http://lime-technology.com/forum/index.php?topic=5446.0
# Parameters: http://lime-technology.com/forum/index.php?topic=5446.msg135527#msg135527
# %S Samba share name (which in unRaid equals the user share name), eg. Storage
# %P User share full path, eg /mnt/user/Storage
#
# To apply changes execute: /etc/rc.d/rc.samba restart
# If the single custom bin solution is chosen, create the dir manually, and grant it g+rwx permissions

[global]

# Debug logging information
log file = /var/log/samba/%m.log
log level = 3 
syslog = 0
max log size = 8191

vfs objects = recycle 
recycle:repository = %P/.Recycle.Bin/%m
recycle:directory_mode = 777
        recycle:keeptree = Yes
        recycle:touch = Yes
        recycle:touch_mtime = false
        recycle:versions = Yes
        recycle:exclude = *.xml
        recycle:exclude_dir = .Recycle.Bin

 

I renamed the /boot/packages directory to /boot/packages.off

I renamed the /boot/config/plugins directory to /boot/config/plugins.off

 

 

I enabled syslog = 3 in the smb-extra.conf file just before attempting a transfer and disabled it after so I could get a clean initial syslog.

 

I rebooted and chose unRaid Safe Mode 4GB

 

and currently copying files over to unRaid from Windows 7 is working

 

When I rebooted all computers yesterday with all the same settings it didn't ...

 

Thanks for your time and help,

Bobby

 

once every few days I'll add a plugin or setting until I have problems again so I know what to avoid

 

 

putty-192.168.1.42-2013.09.26-111835.txt