Jump to content

xtrap225

Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About xtrap225

  • Rank
    Member
  1. i want to ask if we can change the layout and generally make adjustments to the 'dashboard'. specifically i installed and setup 'disk layout' once it became compatible with Version 6.7.0 2019-05-08. it works now just as before. however it showed up on the dashboard which is fine, but its waaaaay down on the left column with a bunch of blank space above it before the next block of info, which happens to be power UPS.
  2. seems that unraid doesn't love my awesome setup as much as i do.
  3. 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.
  4. there doesn't seem to be anything in that diagnostic, anyone tell me what they would be looking for?
  5. fair enough, thank you for the response. does anyone have any experience talking to the iom6 controller from a non-netapp server. i believe i would telnet into it? no that can't be right, just connect on a serial terminal, maybe?
  6. thanks work-pc-diagnostics-20190415-2302.zip
  7. I wonder if anyone has any experience with this. so when i have spin down disabled i do not get these errors. i am running a Lenovo desktop, connected to NetApp DS4246 72TB 24x 3TB 7.2K SATA X308A-R5 with a Dell LSI SAS 9202-16e 6Gb/s SAS Host Bus Adapter. I am hoping to be able to figure out how to spin down drives without the error. (ill have to find my serial adapter and try to connect to the storage shelf but i also want to figure out how to properly send shutdown command to the shel when the ups shuts down the server in case of power outage). i only bring that up because i am wondering if they two could be solved with a similar fix. that is connecting usb to serial adapter to the server and figuring out how to tell unraid (or slackware) to issue commands to the netapp. Commands like spinning down and up drives, or shutting down or turning on the whole shelf. desktop details 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) Network: eth0: 1000 Mb/s, full duplex, mtu 1500 Kernel: Linux 4.18.20-unRAID x86_64 OpenSSL: 1.1.1a Uptime: 0 days, 04:34:28 system log errors ErrorWarningSystemArrayLogin Apr 15 21:45:49 WORK-PC kernel: mdcmd (49): spindown 9 Apr 15 21:45:50 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:45:50 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:45:51 WORK-PC kernel: mdcmd (50): spindown 9 Apr 15 21:45:52 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:45:52 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:45:53 WORK-PC kernel: mdcmd (51): spindown 9 Apr 15 21:45:54 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:45:54 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:45:55 WORK-PC kernel: mdcmd (52): spindown 9 Apr 15 21:45:56 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:45:56 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:45:57 WORK-PC kernel: mdcmd (53): spindown 9 Apr 15 21:45:58 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:45:58 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:45:59 WORK-PC kernel: mdcmd (54): spindown 9 Apr 15 21:46:00 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:00 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:01 WORK-PC kernel: mdcmd (55): spindown 9 Apr 15 21:46:02 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:02 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:03 WORK-PC kernel: mdcmd (56): spindown 9 Apr 15 21:46:04 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:04 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:05 WORK-PC kernel: mdcmd (57): spindown 9 Apr 15 21:46:06 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:06 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:07 WORK-PC kernel: mdcmd (58): spindown 9 Apr 15 21:46:08 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:08 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:09 WORK-PC kernel: mdcmd (59): spindown 9 Apr 15 21:46:10 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:10 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:11 WORK-PC kernel: mdcmd (60): spindown 9 Apr 15 21:46:13 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:13 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:14 WORK-PC kernel: mdcmd (61): spindown 9 Apr 15 21:46:15 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:15 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:16 WORK-PC kernel: mdcmd (62): spindown 9
  8. 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
  9. 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.