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:

found the issue .. it is browser. Firefox does not show the user share. Chrome is fine.

thx.. sorry for late update. i had to move the usb to the back port and now it boot again ok. weird that internal usb stop working suddenly. thx for looking into this

Tried the suggested tweak at this thread but no change.

just recently upgraded to v6.4.1 (from v6.3.5) and now the user share page is empty. it only show the disk share. If I click "Add Share" it will only show empty webpage. I can still access all the user share via smb from my laptops. I already changed the following to 1 and 2 (from the default 10 and 20): diagnostice file: 10.10.10.31-diagnostics-20180223-2156.zip Thx

i have the same problem too.. my rig is AMD FX 8320E. upgraded from 6.3.5 to 6.4.0 and now the system will not boot . i already tried unplug the usb stick and re-run make_bootable.bat but still same issue. I only see blinking underscore "_" after BIOS searched thru bootable devices - BIOS is set to only boot from unraid usb stick.

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

Thanks. I did that last night and it seems to be stable now. edit the docker.cfg so it will not auto start. Restart, and then delete the img and btrfs folder manually. then recreate it again.

All: I have been getting this kernel panic related to btrfs (assuming Docker is the only using this file system?). Trying to reboot the system now as the web GUI is completely froze/unreachable. Unraid v6.1.9 ------------[ cut here ]------------ kernel BUG at fs/btrfs/ctree.h:2578! invalid opcode: 0000 [#1] PREEMPT SMP Modules linked in: xt_nat veth xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables iptable_filter ip_tables kvm_amd kvm vhost_net vhost macvtap macvlan tun md_mod k10temp i2c_piix4 pata_atiixp e1000e ahci libahci tg3 ptp pps_core acpi_cpufreq CPU: 1 PID: 29749 Comm: btrfs-transacti Not tainted 4.1.18-unRAID #1 Hardware name: HP ProLiant MicroServerr, BIOS O41 07/29/2011 task: ffff88007b9be480 ti: ffff8803f8fbc000 task.ti: ffff8803f8fbc000 RIP: 0010:[<ffffffff8129392b>] [<ffffffff8129392b>] lookup_inline_extent_backref+0x1bb/0x524 RSP: 0018:ffff8803f8fbfa98 EFLAGS: 00010297 RAX: 0000000000000090 RBX: ffff8802748f55a0 RCX: ffff8802b4a70000 RDX: 0000000000003000 RSI: ffff880000000000 RDI: ffff8800d8ab69d8 RBP: ffff8803f8fbfb38 R08: 0000000000004000 R09: ffff8803f8fbfa50 R10: 0000000000000003 R11: 000000000000381b R12: 0000000000000090 R13: 000000000000379d R14: 000000000000381a R15: ffff8800d8ab69d8 FS: 00002ad54b604700(0000) GS:ffff88041fc80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 00000000027beb74 CR3: 00000000d07b1000 CR4: 00000000000006e0 Stack: ffff8803f8fbfbd8 0000000000000850 ffff8803f8fbfac8 0000000000003823 0000000037d2c000 ffff8803e2a57800 0000000000000021 000000b0ffffffff ffff88040ce79e40 c0008803e76461f0 00a90000000037d2 0000000000000000 Call Trace: [<ffffffff812963fd>] __btrfs_free_extent+0x140/0x8dc [<ffffffff81292084>] ? block_group_cache_tree_search+0xb7/0xc6 [<ffffffff8129c585>] __btrfs_run_delayed_refs+0x9ce/0xd3a [<ffffffff8100a4a9>] ? __switch_to+0x43c/0x4c8 [<ffffffff8129e77c>] btrfs_run_delayed_refs+0x69/0x21c [<ffffffff812acbf2>] btrfs_commit_transaction+0x47/0xa81 [<ffffffff812ad996>] ? start_transaction+0x36a/0x496 [<ffffffff810829f9>] ? __internal_add_timer+0xb5/0xb5 [<ffffffff812a93ce>] transaction_kthread+0xfa/0x1cb [<ffffffff812a92d4>] ? btrfs_cleanup_transaction+0x461/0x461 [<ffffffff8105c74a>] kthread+0xd6/0xde [<ffffffff8105c674>] ? kthread_create_on_node+0x172/0x172 [<ffffffff815f7f12>] ret_from_fork+0x42/0x70 [<ffffffff8105c674>] ? kthread_create_on_node+0x172/0x172 Code: 94 c6 84 c0 74 27 45 84 f6 0f 85 6d 03 00 00 be 0c 06 00 00 48 c7 c7 bc 22 76 81 41 bf fb ff ff ff e8 fe 3e db ff e9 00 01 00 00 <0f> 0b 48 63 73 40 31 c9 ba 15 00 00 00 4c 8b 3b 48 6b f6 19 4c RIP [<ffffffff8129392b>] lookup_inline_extent_backref+0x1bb/0x524 RSP <ffff8803f8fbfa98> ---[ end trace b375fec2ca735b86 ]--- Thanks

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