Jump to content

ViperSuicide

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ViperSuicide

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. “Ifyou let me know which other parts of the diagnostic zip you want to see i'll post them? Posting the whole zip would expose a large amount of secure info.”
  2. Just tried the backup again and its frozen again. Nothing in the syslog other than a timeout when i try and load the unassigned devices page root@Tower:~# tail -f /var/log/syslog May 23 09:46:32 Tower nginx: 2020/05/23 09:46:32 [error] 6881#6881: *2034262 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.23, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.0.18", referrer: "http://192.168.0.18/Main" And via ssh the /mnt/disks ls hangs root@Tower:~# ls -la /mnt/disks/ ---HANGS--- As soon as i unplug the usb drive it all returns to normal. May 23 10:02:46 Tower kernel: usb 3-2.1: USB disconnect, device number 5
  3. These are the errors im getting in syslog. If you let me know which other parts of the diagnostic zip you want to see i'll post them? Posting the whole zip would expose a large amount of secure info. May 16 19:32:35 Tower unassigned.devices: Error: shell_exec(/usr/bin/dd bs=446 count=1 if=/dev/sdk 2>/dev/null | /bin/sum | /bin/awk '{print }') took longer than 5s! May 16 19:33:16 Tower kernel: mdcmd (39): set md_num_stripes 1280 May 16 19:33:16 Tower kernel: mdcmd (40): set md_queue_limit 80 May 16 19:33:16 Tower kernel: mdcmd (41): set md_sync_limit 5 May 16 19:33:16 Tower kernel: mdcmd (42): set md_write_method May 16 19:33:16 Tower kernel: mdcmd (43): set spinup_group 0 0 May 16 19:33:16 Tower kernel: mdcmd (44): set spinup_group 1 0 May 16 19:33:16 Tower kernel: mdcmd (45): set spinup_group 2 0 May 16 19:33:37 Tower unassigned.devices: Error: shell_exec(/usr/bin/dd bs=1 count=1 skip=449 if=/dev/sde 2>/dev/null | /bin/sum | /bin/awk '{print }') took longer than 2s! May 16 19:33:40 Tower unassigned.devices: Error: shell_exec(/usr/bin/dd bs=1 count=1 skip=450 if=/dev/sde 2>/dev/null | /bin/sum | /bin/awk '{print }') took longer than 2s! May 16 19:33:42 Tower unassigned.devices: Error: shell_exec(/usr/bin/dd bs=1 count=1 skip=451 if=/dev/sde 2>/dev/null | /bin/sum | /bin/awk '{print }') took longer than 2s! May 16 19:33:50 Tower unassigned.devices: Error: shell_exec(/usr/bin/dd bs=1 count=1 skip=460 if=/dev/sde 2>/dev/null | /bin/sum | /bin/awk '{print }') took longer than 2s! May 19 21:28:26 Tower ntfs-3g[12391]: Version 2017.3.23 integrated FUSE 27 May 20 19:30:04 Tower ntfs-3g[4890]: Version 2017.3.23 integrated FUSE 27 May 21 23:39:23 Tower nginx: 2020/05/21 23:39:23 [error] 6881#6881: *1760428 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.23, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.0.18", referrer: "http://192.168.0.18/Main" May 21 23:45:24 Tower kernel: traps: lsof[13685] general protection ip:148d174bbb8e sp:80f7be55bc258d0f error:0 in libc-2.30.so[148d1749c000+16b000]
  4. Hi, I have an issue which other seem to have reported too where unassigned devices section becomes unresponsive and smb shares to usb devices hang. Usually when copying a large amount of data to an smb share of a usb disk. Other shares on the main array are fine when this happens. it means I currently can’t backup my PC as there is not enough space on the array to complete the backup so needs to go direct to the usb share. When it hangs the fix is to unplug the usb and remount. When it stops the wave symbol on the whole unassigned devices section just shows loading forever and the smb shares do not respond but via ssh the usbs are still mounted and accessible. please help.
  5. Hi, is there a way to limit an smb folder size. For example if a backup tries to use too much space a limit can be applied to the folder?
  6. I also have the same issue. Does anyone have the link to the main thread please?