ez2002

Thanks the above suggestions worked.

I just upgraded to unraid v6.8.2 and notice that now there is "colored status indicator" - see below snapshop with red arrow on most of the pages. I remember in previous version this info will pop-up when you hover certain things. It goods information .. but takes a lot of screen real-estate. Anybody can advise how to hide this? Been looking in "display" settings menu but cannot find anything that will work.

Just wanted to share my recent experience migrating from physical server to ESXi for unraid. It took me quite significant time gathering and reading tips/documents on the internet before making the move. My hesitation was whether unraid really need "hw-passthrough" or "disk RDM" is sufficient. From what I have experienced .. as long your CPU support virtualization then it is enough to jump on the virtualization wagon. I hope this will help others that wanted to move to ESXi and does not want to upgrade their Motherboard to passthrough/iommu capable. Physical setup: Unraid v6.8.1 Motherboard M5A78L-M-PLUS-USB3 CPU AMD FX8320E LSI 9207-8i [in hba/IT mode] 1x SSD for cache disk 7x HDD Powersupply 380W unraid license on 4GB usb stick New ESXi setup: ESXi v6.7-U3 - reuse all the hw from above Motherboard M5A78L-M-PLUS-USB3 have to add Realtek ethernet driver [https://vibsdepot.v-front.de/wiki/index.php/List_of_currently_available_ESXi_packages] I cannot passthru LSI 9207-8i as the motherboard does not support iommu Verify that in unraid vm settings, SCSI Controller 0 = "VMware Paravirtual" - this is important so the HDD Serial Number can be passthru to unraid (otherwise you will need to rebuilt your parity disk) 7x HDD connect to LSI 9207-81 and configure them as RDM directly from ESXi a. esxi > VM > Edit Settings > Add harddisk > New Raw disk > b. on the "Hard disk" setting .. configure: Controller location = "SCSI Controller 0" and Disk Compatibility = Physical and Disk Mode = "Independent - persistent" for the Cache drive - SSD, I connect it to the motherboard SATA port. There is a known issue with LSI 9207-8i not supporting TRIM (unless LSI downgraded to fw P16). use this link to passthrough the indvidual SSD drive to unraid as RDM - [https://gist.github.com/Hengjie/1520114890bebe8f805d337af4b3a064]. I cannot use the method i use for the HDD. use plopkexec iso to boot unraid via the usb stick (so I can keep the license) - download here https://www.plop.at/en/plopkexec/download.html - choose "all precompiled versions, 32/64 bit, EFI, ISO." extract the tar and copy the iso to your ESXi datastore. back to the VM edit settings > CD/DVD Drive 1 > Datastore ISO file > CD/DVD Media = plopkexec64.iso also set your VM to boot to BIOS and change the boot device to CD/DVD passthrough your unraid usb stick by adding a new USB device download unraid specific vmwaretool from appspace "openVMTools_compiled" after you have successfully boot your unraid Result: after reboot, plopkexec will auto search for usb device and boot from it if you use SCSI Paravirtual, the disks will reallign as the serial numbers got passthru as-is as before remember to install "openVMTools_compiled" upgraded unraid to v6.8.2 and it finished successfully on unraid Main page, SMART and spin up/down are reflected correctly. I am glad I made the change to ESXi .. a better use of the FX8320 cpu ==== Some screenshot of the configuration ==== HDD RDM and SCSI controller setting: SSD rdm: Plopkexec and USB stick passthru: Unraid dashboard: Disk spun down: Disk spun up: Temp work for the HDD on LSI: Though Temp is not working for cache SSD that passthrough via MB sata port:

Also if anybody have the issue issue with my query log showing up in GMT time zone? my unraid is setup to EST. tried several different things from Google but has no impact. here is the output from pihole docker: bash-4.3# env WEBLOGDIR=/var/log/nginx IPv6=False HOSTNAME=70fe0ff4fde4 HOST_OS=unRAID DNS2=208.67.220.220 PATH=/opt/pihole:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin DNS1=208.67.222.222 PWD=/ TZ=America/New_York SHLVL=1 HOME=/root PHP_CONFIG=/etc/php5/php-fpm.conf TINI_VERSION=v0.13.0 IMAGE=alpine PHP_ERROR_LOG=/var/log/nginx/error.log PHP_ENV_CONFIG=/etc/php5/fpm.d/envs.conf setupVars=/etc/pihole/setupVars.conf ServerIP=10.10.10.61 PIHOLE_INSTALL=/tmp/ph_install.sh _=/usr/bin/env bash-4.3# bash-4.3# bash-4.3# bash-4.3# date Wed May 17 03:07:18 EDT 2017 Log in pihole: 2017-05-17 UTC 07:04:25 A registry.hub.docker.com 10.10.10.203 OK Blacklist 2017-05-17 UTC 07:04:17 A m.irrigationcaddy.com 10.10.10.1 OK

Is this docker still being updated directly from pihole? I just started using it and notice that the version installed are as followed: Pi-hole Version v2.13.2(Update available!) Web Interface Version v2.5.2(Update available!) But there is version 3.0.1 available at: https://github.com/pi-hole/pi-hole/releases

Thx, I changed my cache to XFS and now splunk will launch. Thanks again for the effort creating the docker and support.

So no way to use with Docker/Unraid then. ... dmaxwell... how you get it to install on unraid with docker? I thought docker in unraid always use btrfs (or highly recommended).

Looks like btrfs related??? http://answers.splunk.com/answers/9035/can-i-run-splunk-on-btrfs.html -- see last thread

I just install this on my unraid 6.0-beta14b. Installation seems to be ok... but I cannot access the mgmt page from http://ip_address:8000 I keep getting "webpage is not available". Is this a known issue? Here is the docker log for Splunk: /usr/bin/docker logs --tail=350 -f splunk 2>&1 *** Running /etc/rc.local... Copying '/opt/splunk/etc/openldap/ldap.conf.default' to '/opt/splunk/etc/openldap/ldap.conf'. Generating RSA private key, 1024 bit long modulus ................++++++ .++++++ e is 65537 (0x10001) writing RSA key Generating RSA private key, 1024 bit long modulus ........++++++ .++++++ e is 65537 (0x10001) writing RSA key Moving '/opt/splunk/share/splunk/search_mrsparkle/modules.new' to '/opt/splunk/share/splunk/search_mrsparkle/modules'. This appears to be your first time running this version of Splunk. Splunk> 4TW Checking prerequisites... Checking http port [8000]: open Checking mgmt port [8089]: open Checking appserver port [127.0.0.1:8065]: open Checking kvstore port [8191]: Checking configuration... Done. homePath='/opt/splunk/var/lib/splunk/audit/db' of index=_audit on unusable filesystem. Checking critical directories... Done Checking indexes... Validating databases (splunkd validatedb) failed with code '1'. If you cannot resolve the issue(s) above after consulting documentation, please file a case online at http://www.splunk.com/page/submit_issue open *** Booting runit daemon... *** Runit started as PID 39 Mar 10 23:10:57 1b54b56c2bce syslog-ng[44]: syslog-ng starting up; version='3.5.3' Mar 10 23:17:01 1b54b56c2bce /USR/SBIN/CRON[51]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Thanks in advance.

is there a way to limit memory size that VBOX can grab for its use? I have a 8GB UNRAID then before vbox will have about 6GB free but after vbox running, all memory is used up.