Lost samba access

[taetae]

@fvdw
are presented in random mode the problems of writing on harddisk and when it happens there's no way to copy anything on top ....
do you think some cache problem? memory? I tried on several pc windows and gives me the same errors

I am attaching pictures ... every error but does not finish the upload restarts in loop

[Jocko]

@fvdw
are presented in random mode the problems of writing on harddisk and when it happens there's no way to copy anything on top ....
do you think some cache problem? memory? I tried on several pc windows and gives me the same errors

I am attaching pictures ... every error but does not finish the upload restarts in loop

Do these commands

Code: Select all

df -h /dev/sd?8
df -h /dev/sda

--edit--
And send us the log files present in /var/log/samba only after occurring your issue

[taetae]

Hi taetae,

That's what I feared ...

ps:
?????(you do not have a command for blue LED ?? if you want to turn off all the LEDs just that from a command ledblue off)
Sata0 Ledblue on, other Sata LED blue on ( blinking on R/W disk events)

No, in the userland there is no such command for Blue LED. In fact, the red command is a swapping between 2 modes : red/blue LED.

So, we can not switch off the sata LED and you have the last version.

Note: you don't have test the LED on/off commands from the web-interface

It controls the LEDs sull'interfacce web works great !!!

Do these commands

Code: Select all

df -h /dev/sd?8
df -h /dev/sda

Code: Select all

/$ df -h /dev/sd?8
Filesystem                Size      Used Available Use% Mounted on
/dev/sda8               455.8G    333.5M    450.8G   0% /share/1000
/dev/sdb8                 1.8T      1.8G      1.8T   0% /share/1001
/dev/sdc8                 1.8T      1.1T    718.0G  60% /share/1002
/dev/sdd8                 1.8T    162.5G      1.6T   9% /share/1003
/dev/sde8                 1.8T    206.4G      1.6T  11% /share/1004
/$ df -h /dev/sda
Filesystem                Size      Used Available Use% Mounted on
df: /dev/sda: can't find mount point

[Jocko]

So you have no issue with free space on the data partitions.

and do again

Code: Select all

df -h /dev/sda5

(I did an error !)

See also my previous post, I edited it

[taetae]

So you have no issue with free space on the data partitions.

and do again

Code: Select all

df -h /dev/sda5

(I did an error !)

See also my previous post, I edited it

Code: Select all

/$ df -h /dev/sda5
Filesystem                Size      Used Available Use% Mounted on
/dev/sda5               771.1M     17.1M    746.1M   2% /rw_fs

[Jocko]

Thank, it is ok sda5.

Currently without the samba log, I have no idea what it is the problem.
As sdc8 seems the disk most used, it may have an issue with the inode quota if you have many small files. So do

Code: Select all

df -i /dev/sd?8

[taetae]

at the moment is not doing it just makes a few mistakes you place the log I restarted the nas so I have no previous errors

Code: Select all

df -i /dev/sd?8
Filesystem              Inodes      Used Available Use% Mounted on
/dev/sda8             30351360        47  30351313   0% /share/1000
/dev/sdb8            121888768       709 121888059   0% /share/1001
/dev/sdc8            121888768      2232 121886536   0% /share/1002
/dev/sdd8            121888768     49793 121838975   0% /share/1003
/dev/sde8            121888768     40592 121848176   0% /share/1004

has returned error, but nothing appears in log.smbd
 

Code: Select all

 / rw_fs / tmp / var / log / samba $ cat log.smbd
[20.10.2014 10:01:12, 0] smbd / server.c: main (942)
   smbd version 3.0.37 started.
   Copyright Andrew Tridgell and the Samba Team 1992-2009

[Jocko]

Your issue can be also with some network settings (netbios). So you must also read the nmbd log file.

You can also increase the debug level to get samba more verbose

Code: Select all

smbcontrol smbd debug 1

Be careful, after increasing the debug level, change nothing in the web interface (edit/new user, edit/new share, install a server,...) this will overwrite your change

[Jocko]

Hi taetae,

You note no error in nmbd and smbd log for 24 hours ?

[Jocko]

HI taetae,

I looked at your log sent by pm. There is an amazing thing :
after connecting to a service (<=> a share), samba closes the connection after a short time. :scratch

Code: Select all

[2014/10/25 16:30:44, 1] smbd/service.c:make_connection_snum(1042)
  xxxxx (192.168.1.24) connect to service sharename initially as user xxxx (uid=1000, gid=1000) (pid 1726)
[2014/10/25 16:31:06, 1] smbd/service.c:close_cnum(1239)
  xxxxx (192.168.1.24) closed connection to service sharename

So lost connection only after 22'' :shocked

le Log says that it is the host xxxxx that closed connection (and not the NAS)

an usual log is with debug level 1:

Code: Select all

[2014/10/21 17:40:38, 1] smbd/service.c:make_connection_snum(1042)
  acrab (127.0.0.1) connect to service fvdw initially as user Jocko (uid=1000, gid=1000) (pid 12984)
[2014/10/21 17:54:52, 1] smbd/service.c:close_cnum(1239)
  acrab (127.0.0.1) closed connection to service fvdw


I asked to open a service on fvdw and closed it after 14 minutes.

If you did not ask to close the service then I think that you should deepen on the LAN settings side or host client side.

You can try to increase the debug level (2 or 3) to get more log