when I goto 'Main' and then 'Flash' and then click 'flash backup' it then says 'creating flash backup' . it just says 'Please wait... creating Flash backup zip file (this may take several minutes)' 

 

but it never completes.  

 

here is what the log say.  

 

Apr 15 17:58:52 WORK-PC nginx: 2019/04/15 17:58:52 [error] 8187#8187: *3235 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.109, server: , request: "POST /webGui/include/Download.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.107", referrer: "http://192.168.1.107/Main/Flash?name=flash"

 

i made sure that popups blocker and ad blockers were disabled and enabled flash etc, so that the page should be able to do whatever it wants.

 

i should also note i have tried from three different computers, two windows 10 , and one mac mojave. and i have tried rebooting the unraid server and trying again with minimal dockers and no vm's running.

 

i have taken a backup using the Backup/Restore appdata plugin but i really want the zip file version that i could use with the usb creation tool if it ever became necessary. 

 

any help would be greatly appreciated.

How much RAM do you have?

Model: Custom

M/B: LENOVO - SHARKBAY

CPU: Intel® Core™ i5-4570 CPU @ 3.20GHz

HVM: Enabled

IOMMU: Enabled

Cache: 1024 kB, 256 kB, 6144 kB

Memory: 32 GB (max. installable capacity 32 GB) .   <----------------------- DDR3 though i think.

Network: eth0: 1000 Mb/s, full duplex, mtu 1500

Kernel: Linux 4.18.20-unRAID x86_64

OpenSSL: 1.1.1a

Uptime: 0 days, 02:48:02

You obviously have plenty then. There are several things that won't work if there isn't enough RAM since things get zipped/unzipped there, such as Unraid upgrades, getting diagnostics, and getting flash backups.

 

Since that doesn't appear to be your problem, go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.

thanks

 

work-pc-diagnostics-20190415-2302.zip

there doesn't seem to be anything in that diagnostic, anyone tell me what they would be looking for?

i tried changing the following, then killing nginx and starting it back up again and it didn't help at all.  same as original error and the file possibly regenerates as per the first line; negating the changes.

root@WORK-PC:/etc/nginx/conf.d# head emhttp-servers.conf.backup 

# Generated by /etc/rc.d/rc.nginx

#

# set root directory for requests

#

root /usr/local/emhttp;

#

# limit the amount of failed auth requests per IP address

#

limit_req_zone $binary_remote_addr zone=authlimit:1m rate=30r/m;

#

root@WORK-PC:/etc/nginx/conf.d# head emhttp-servers.conf

# Generated by /etc/rc.d/rc.nginx

#

# set root directory for requests

#

root /usr/local/emhttp;

#

# limit the amount of failed auth requests per IP address

#

limit_req_zone $binary_remote_addr zone=authlimit:10m rate=1r/s;

#

i looked in /etc/php-fpm/php-fpm.conf found nothing i wanted to mess with. so going back to .. i found ...

grep '/usr/local/emhttp' /etc/nginx/conf.d/emhttp-servers.conf

root /usr/local/emhttp;

looking in  /usr/local/emhttp/ i found ...

root@WORK-PC:/usr/local/emhttp# ls -latrh

total 28K

lrwxrwxrwx  1 root root   15 Jun 19  2016 webGui -> plugins/dynamix/

lrwxrwxrwx  1 root root   17 Jun 19  2016 state -> /var/local/emhttp/

lrwxrwxrwx  1 root root    4 Jun 19  2016 mnt -> /mnt/

lrwxrwxrwx  1 root root    8 Jun 19  2016 log -> /var/log/

lrwxrwxrwx  1 root root    5 Jun 19  2016 boot -> /boot/

-rw-r--r--  1 root root 4.3K Mar 13  2018 update.php

-rw-r--r--  1 root root   26 Sep  6  2018 robots.txt

-rw-r--r--  1 root root  330 Sep 27  2018 logout.htm

-rw-r--r--  1 root root 6.9K Sep 28  2018 logging.htm

-rw-r--r--  1 root root 3.4K Nov  1 22:42 update.htm

lrwxrwxrwx  1 root root   39 Apr 15 17:59 work-pc-flash-backup-20190415-1756.zip -> /work-pc-flash-backup-20190415-1756.zip

lrwxrwxrwx  1 root root   55 Apr 15 18:58 work-pc-flash-backup-20190415-1853.zip -> /mnt/user/system/work-pc-flash-backup-20190415-1853.zip

drwxr-xr-x 31 root root  620 Apr 15 21:20 plugins/

drwxr-xr-x 10 root root  200 Apr 15 21:20 ../

lrwxrwxrwx  1 root root   55 Apr 19 12:58 work-pc-flash-backup-20190419-1251.zip -> /mnt/user/system/work-pc-flash-backup-20190419-1251.zip

lrwxrwxrwx  1 root root   55 Apr 19 13:07 work-pc-flash-backup-20190419-1301.zip -> /mnt/user/system/work-pc-flash-backup-20190419-1301.zip

lrwxrwxrwx  1 root root   55 Apr 19 13:13 work-pc-flash-backup-20190419-1308.zip -> /mnt/user/system/work-pc-flash-backup-20190419-1308.zip

lrwxrwxrwx  1 root root   55 Apr 19 17:41 work-pc-flash-backup-20190419-1734.zip -> /mnt/user/system/work-pc-flash-backup-20190419-1734.zip

lrwxrwxrwx  1 root root   55 Apr 19 17:49 work-pc-flash-backup-20190419-1743.zip -> /mnt/user/system/work-pc-flash-backup-20190419-1743.zip

lrwxrwxrwx  1 root root   55 Apr 19 17:56 work-pc-flash-backup-20190419-1750.zip -> /mnt/user/system/work-pc-flash-backup-20190419-1750.zip

lrwxrwxrwx  1 root root   55 Apr 19 18:01 work-pc-flash-backup-20190419-1754.zip -> /mnt/user/system/work-pc-flash-backup-20190419-1754.zip

drwxr-xr-x  3 root root  440 Apr 19 18:01 ./

so i temporarily enabled the system share and copied the latest usb backup off and deleted the rest.

 

its not a perfect fix, but a good enough workaround for me.

 

Edited April 20, 20197 yr by xtrap225

On 4/17/2019 at 9:24 PM, xtrap225 said:

there doesn't seem to be anything in that diagnostic, anyone tell me what they would be looking for?

Your syslog was filling up with these:

Apr 15 22:00:05 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write
Apr 15 22:00:05 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5
Apr 15 22:00:06 WORK-PC kernel: mdcmd (466): spindown 9
Apr 15 22:00:07 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write
Apr 15 22:00:07 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5
Apr 15 22:00:07 WORK-PC kernel: mdcmd (467): spindown 10
Apr 15 22:00:08 WORK-PC kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Apr 15 22:00:08 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write

which suggests a problem communicating with disks 9,10

 

In fact, not getting any SMART for any of your array disks. Probably a controller issue.

seems that unraid doesn't love my awesome setup as much as i do.