Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Constantly losing connection to server when transferring

Featured Replies

I am constantly losing connection to my server when transferring files to it. It is not a network/cable issue. It seems, the fuller the hard drive is, the higher the chance for it to time out. I can transfer to 50% full hard drives all day long, but if I transfer to a <20% full hard drive.. theres a high chance to lose connection to my server. These are large files 20+ GB each.

 

Here's the syslog. I just cold booted the server in an attempt to fix it, and it still is happening. No errors are produced in the syslog. I'm transferring files from Windows 7 64-bit and I'm assuming thats the issue. I've tried using TeraCopy as well and it produces the same results.

syslog.txt

chart.png.80e705a846d3486ede6483376631857e.png

I thought I was the only one having this issue. Yes, it's crazy that there's nothing from the log when that happens. I think I got more "unable to access...disk" error with Win7 64bit more then 32bit. Is your screensaver/power saving set to 10 minutes? I think I see less copying issues when I set it to 3hrs. Are your copying files directly to disk or share folder?

 

 

 

Hey,

 

I'm having the exact same problem. The difficulty in getting the logs though is when you reboot, the logs are lost.

 

Try adding this in your go file:

 

mv -f /boot/syslog.current /boot/syslog.last 2>/dev/null
cat /var/log/syslog > /boot/syslog.current
echo "*.debug  /boot/syslog.current" >> /etc/syslog.conf
/etc/rc.d/rc.syslog restart

 

Replicate the problems and then post the "syslog.last" file. Basically what that code does is put the log file in /boot/syslog.current, then when you reboot it gets copied to /boot/syslog.last before it starts logging again.

 

(Make sure to remove this code after you replicate the problem because excessive writing to your flash drive is not a good thing).

 

My logs showed that i would be losing memory, i'm still trying to figure out where the leak occurs though;

 

My syslog

 

May 28 04:26:22 kenny kernel:  [<c104aae9>] oom_kill_process+0x59/0x1cd
May 28 04:26:22 kenny kernel:  [<c104af41>] __out_of_memory+0xef/0x102
May 28 04:26:22 kenny kernel:  [<c104afb2>] out_of_memory+0x5e/0x83
May 28 04:26:29 kenny kernel:  [<c104cf71>] __alloc_pages_nodemask+0x375/0x42f
May 28 04:26:29 kenny kernel:  [<c104d03a>] __get_free_pages+0xf/0x21
May 28 04:26:29 kenny kernel:  [<c1022bf2>] copy_process+0xa4/0xde3
May 28 04:26:29 kenny kernel:  [<c10396ad>] ? ktime_get_ts+0xc3/0xcd
May 28 04:26:29 kenny kernel:  [<c113361c>] ? copy_to_user+0x33/0x3c
May 28 04:26:29 kenny kernel:  [<c1023ac6>] do_fork+0x11d/0x251
May 28 04:26:29 kenny kernel:  [<c1221303>] ? sys_socketcall+0x15d/0x170
May 28 04:26:38 kenny kernel:  [<c1001626>] sys_clone+0x24/0x2b
May 28 04:26:38 kenny kernel:  [<c1002935>] syscall_call+0x7/0xb
May 28 04:26:38 kenny kernel: Mem-Info:
May 28 04:26:38 kenny kernel: DMA per-cpu:
May 28 04:26:38 kenny kernel: CPU    0: hi:    0, btch:   1 usd:   0
May 28 04:26:38 kenny kernel: CPU    1: hi:    0, btch:   1 usd:   0
May 28 04:26:38 kenny kernel: CPU    2: hi:    0, btch:   1 usd:   0
May 28 04:26:38 kenny kernel: CPU    3: hi:    0, btch:   1 usd:   0
May 28 04:26:38 kenny kernel: Normal per-cpu:
May 28 04:26:38 kenny kernel: CPU    0: hi:  186, btch:  31 usd:   0
May 28 04:26:38 kenny kernel: CPU    1: hi:  186, btch:  31 usd:   0
May 28 04:26:38 kenny kernel: CPU    2: hi:  186, btch:  31 usd:   0
May 28 04:26:38 kenny kernel: CPU    3: hi:  186, btch:  31 usd:   0
May 28 04:26:39 kenny kernel: HighMem per-cpu:
May 28 04:26:39 kenny kernel: CPU    0: hi:  186, btch:  31 usd:   0
May 28 04:26:39 kenny kernel: CPU    1: hi:  186, btch:  31 usd:   0
May 28 04:26:39 kenny kernel: CPU    2: hi:  186, btch:  31 usd:   0
May 28 04:26:39 kenny kernel: CPU    3: hi:  186, btch:  31 usd:   0
May 28 04:26:39 kenny kernel: active_anon:3751 inactive_anon:3261 isolated_anon:0
May 28 04:26:39 kenny kernel:  active_file:69987 inactive_file:64449 isolated_file:193
May 28 04:26:39 kenny kernel:  unevictable:52245 dirty:3339 writeback:11 unstable:0
May 28 04:26:39 kenny kernel:  free:152304 slab_reclaimable:21453 slab_unreclaimable:49972
May 28 04:26:39 kenny kernel:  mapped:2928 shmem:26 pagetables:314 bounce:0
May 28 04:26:39 kenny kernel: DMA free:3532kB min:64kB low:80kB high:96kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB
unevictable:36kB isolated(anon):0kB isolated(file):0kB present:15804kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaim
able:536kB slab_unreclaimable:7328kB kernel_stack:4464kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unrecla
imable? no
May 28 04:26:39 kenny kernel: lowmem_reserve[]: 0 867 2006 2006
May 28 04:26:39 kenny kernel: Normal free:136984kB min:3732kB low:4664kB high:5596kB active_anon:3520kB inactive_anon:8728kB active_file:7108
kB inactive_file:6228kB unevictable:47712kB isolated(anon):0kB isolated(file):772kB present:887976kB mlocked:0kB dirty:60kB writeback:40kB ma
pped:3580kB shmem:0kB slab_reclaimable:85276kB slab_unreclaimable:192560kB kernel_stack:348704kB pagetables:484kB unstable:0kB bounce:0kB wri
teback_tmp:0kB pages_scanned:0 all_unreclaimable? no
May 28 04:26:39 kenny kernel: lowmem_reserve[]: 0 0 9114 9114
May 28 04:26:39 kenny kernel: HighMem free:468700kB min:512kB low:1736kB high:2964kB active_anon:11484kB inactive_anon:4316kB active_file:272
840kB inactive_file:251568kB unevictable:161232kB isolated(anon):0kB isolated(file):0kB present:1166672kB mlocked:0kB dirty:13296kB writeback
:4kB mapped:8132kB shmem:108kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:772kB unstable:0kB bounce:0kB writebac
k_tmp:0kB pages_scanned:0 all_unreclaimable? no
May 28 04:26:39 kenny kernel: lowmem_reserve[]: 0 0 0 0
May 28 04:26:40 kenny kernel: DMA: 5*4kB 113*8kB 1*16kB 1*32kB 0*64kB 0*128kB 0*256kB 1*512kB 0*1024kB 1*2048kB 0*4096kB = 3532kB
May 28 04:26:40 kenny kernel: Normal: 33780*4kB 131*8kB 3*16kB 1*32kB 0*64kB 0*128kB 1*256kB 1*512kB 0*1024kB 0*2048kB 0*4096kB = 137016kB
May 28 04:26:40 kenny kernel: HighMem: 51322*4kB 23534*8kB 4268*16kB 208*32kB 4*64kB 1*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 468
888kB
May 28 04:26:40 kenny kernel: 186900 total pagecache pages
May 28 04:26:40 kenny kernel: 0 pages in swap cache
May 28 04:26:40 kenny kernel: Swap cache stats: add 0, delete 0, find 0/0
May 28 04:26:40 kenny kernel: Free swap  = 0kB
May 28 04:26:40 kenny kernel: Total swap = 0kB
May 28 04:26:40 kenny kernel: 521984 pages RAM
May 28 04:26:40 kenny kernel: 294146 pages HighMem
May 28 04:26:40 kenny kernel: 5720 pages reserved
May 28 04:26:40 kenny kernel: 80515 pages shared
May 28 04:26:40 kenny kernel: 249525 pages non-shared
May 28 04:26:40 kenny kernel: Out of memory: kill process 22447 (smbd) score 228 or a child
May 28 04:26:40 kenny kernel: Killed process 22447 (smbd)

 

as you can see, since i run out of memory "oom" comes in and randomly starts killing processes, eventually it reaches samba and i lose connection to the server.

 

If you guys have the same problem, maybe it's a bug we can address.

 

 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.