HrtAttK

Ok, so after reinstalling 3 times it's been stable and I think I found an issue with the naming convention of a share where docker didn't like the syntax. Not sure what triggered this as the share was in use for the past two years but I have upgraded the OS recently so potentially the new version of docker may not like the naming there on the share (removing spaces and white spaces).

Good morning all, While troubleshooting 100% docker RAM usage I started to remove unused dockers and after removing them plex became orphaned. Attempted to reinstall and was running for about 5 minutes before being orphaned again. Any thoughts on how to proceed? I've attached the diagnostics file and hopefully I haven't lost the settings. Thanks in advance and let me know if there's any more information I can provide. unhrtattk-diagnostics-20221020-0820.zip

@DoesItHimself Hey, I'm still having issues. Sometimes it works and sometimes it doesn't. Reading the above post I may try running the "New Permissions" script again. Now, I have directories I deleted and went through removing them from dockers, etc. But, directories keep reappearing with random users not set like "linux user". ---------------------------------------------------------------------------- I just checked again and deleted more paths and libraries internal to plex so hoping that's the culprit. We'll see.....

@Frank1940 Thanks for those links! Will be going over them later this evening. Thanks again everyone for all the help!

All, can't tell if this is a Windows 10 issue or not but here it goes..... Recently had to re-install Windows 10 Pro and everything connecting to shares were fine for a few days. Then in the last two days I noticed that MusicBee was unable to edit files. After searching here and on MusicBee forums it turned out to be a permissions issue. I fixed it by using Spaceinvader One's videos (Thank you!) and this forum (Thanks for everyone's posts!) by switching all shares to private where now MusicBee is able to edit files and other applications don't appear to have issues accessing files again. Now I've run into another issue. I'm trying to delete files over SMB using Windows 10 file explorer and receiving an error that the directory or file is owned by "nobody". I've tried flipping all shares back to public and disconnecting and reconnecting network drives to no avail. The 'smbstatus' command on the terminal is showing all files as read only and thus not able to sometimes move or delete files. Here's my current SMB settings on unraid: [global] comment = Fix to read/write security = USER guest account = nobody public = no guest ok = no map to guest = bad user #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end And here are logs related to samba after my last unraid reboot about a little while ago..... Mar 21 15:14:07 unHRTATTK root: Starting Samba: /usr/sbin/smbd -D Mar 21 15:14:07 unHRTATTK root: /usr/sbin/nmbd -D Mar 21 15:14:07 unHRTATTK root: /usr/sbin/wsdd Mar 21 15:14:07 unHRTATTK root: /usr/sbin/winbindd -D Mar 21 15:14:13 unHRTATTK emhttpd: shcmd (408): smbcontrol smbd close-share 'Video' I have a feeling this may be a Windows 10 permissions issue but have no idea how to fix it. I've been through Microsoft's forums and other sites to see how to change ownership with no success. I've also reestablished connectivity initially by joining the workgroup and that worked for a short while although I think I would like to keep the shares in a private state. Does anyone have any ideas as what else to do so that I have full control over the shares/files from my windows 10 machine? Update 1: So when I come to a folder that I can't manipulate in windows explorer I have been going through the terminal and chown'ing each folder recursively in order to either move files or delete folders I couldn't previously. Does this make sense? Is this something that can be done in unraid I'm not aware of?

Thinking the same but that wasn't the drive I was trying to replace. It was the parity drive. So interestingly enough, after leaving the server off for the past 6 hours and now turning it back shows the configuration has been restored. The parity drive needs to rebuild but I'll let that go until the morning and see. Next step is to figure out why my new 10TB drive is not being recognized. Thanks everyone for the help!

I see, when I unassigned my cache drive and reassigned it the drive showed as if it was a new drive and not my previous parity drive. I just went through and checked one of my array disks and see that the data is still there which is good! But, it appears that I'll need to reestablish my parity drive before all of the shares and dockers appear again. PS, I mispoke in initial post. It was the parity drive drive I wanted to upgrade and not cache. Editing now.... Been a long day....

Hello all, I have attempted to replace my parity drive from a 4TB to a 10TB. The 10TB drive was not showing up so learned that I may need to update the MB BIOS which I won't be able to do for a bit so decided to reinstall my 4TB which I have unassigned and now reassigned. Since I will now have to rebuild the drive (approximately 8.5 hours) I have noticed that the shares do not show up anymore and my docker service has failed to start. Please tell me I didn't lose my data! I am unable to browse the existing drives in the GUI but the shares show up in the configuration files on my USB but I don't see anything under /mnt. Should I wait until the rebuild is finished or is there something else I need to do first before rebuilding the array. Thanks for the help (please help!)

Hello everyone! Anyone install GNS3 on unraid successfully? I am looking to use this and needed an informational if anyone has successfully done this. It seems they are pushing VMWare as their platform of choice but I would like to use my server without spending anymore money

Hello all, I am trying to allow a local windows 10 VM running on unraid 'see' the shares that are also built on the same unraid server. Wondering if there is a way around adding a SMB share? If I add the share will it 'leave' the VM and hit the network card? Trying to parse out how that would work. Thanks

OK, just replaced a single drive, removed an array disk and rebuilding parity now. So far, all data's good as I have tested random files and things are going smoothly. Thanks for helping.

Hello all, Need some clarification to ensure the "New Config" tool does as is intended. I am removing a disk from the array (not replacing). The instructions indicate to go to Tools and run the New Config utility. I have already moved the data off of the drive. What I want to know is when the disk is removed and parity is rebuilt, what happens to the data that is on the disks that will be remaining? There's no mention of how that is handled. My guess is that I would be able to reassign the disks back to where they were and the parity would rebuild off of the remaining disks without data loss. The page indicates that the disks would show up as "New" which I assume would mean they would need to be formatted. Am I thinking about this correctly or to remove the disk I can run the tool and reassign the disks to where they were without data loss? Thanks for helping clear this up.

That was it! ACS setting did it. Thanks Jon!

Hello Jon, I'm running into the same issue as well. I have added a PCIe USB card to be able to pass through an USB controller so I would be able to pass through some USB devices. If there's anything here I can change, please let me know. Execution error internal error: early end of file from monitor: possible problem: 2016-04-07T00:31:53.820617Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: error, group 1 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver. 2016-04-07T00:31:53.820639Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 1 2016-04-07T00:31:53.820647Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed 2016-04-07T00:31:53.820655Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized What is ACS override and how do I know if it's enabled? I don't see a toggle in the GUI advanced settings. I did try rebooting as well but that didn't work. Here's some more data if it helps: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Windows</name> <uuid>e26b3528-9945-9c04-0b1e-e3ba46aec785</uuid> <description>Windows</description> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>7</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='5'/> <vcpupin vcpu='6' cpuset='6'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='7' threads='1'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/vDisks/Gaming PC/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISO/Windows.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISO/virtio-win-0.1.112.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:12:26:f0'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Windows.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/> </qemu:commandline> </domain> PCI Devices 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06) 00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller 00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V 00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2 00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller 00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 (rev d0) 00:1c.3 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 (rev d0) 00:1d.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1 00:1f.0 ISA bridge: Intel Corporation 9 Series Chipset Family Z97 LPC Controller 00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode] 00:1f.3 SMBus: Intel Corporation 9 Series Chipset Family SMBus Controller 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aac8 02:00.0 USB controller: ASMedia Technology Inc. Device 1242 04:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) IOMMU Groups /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.1 /sys/kernel/iommu_groups/1/devices/0000:01:00.0 /sys/kernel/iommu_groups/1/devices/0000:01:00.1 /sys/kernel/iommu_groups/1/devices/0000:02:00.0 /sys/kernel/iommu_groups/2/devices/0000:00:14.0 /sys/kernel/iommu_groups/3/devices/0000:00:16.0 /sys/kernel/iommu_groups/4/devices/0000:00:19.0 /sys/kernel/iommu_groups/5/devices/0000:00:1a.0 /sys/kernel/iommu_groups/6/devices/0000:00:1b.0 /sys/kernel/iommu_groups/7/devices/0000:00:1c.0 /sys/kernel/iommu_groups/7/devices/0000:00:1c.3 /sys/kernel/iommu_groups/7/devices/0000:04:00.0 /sys/kernel/iommu_groups/8/devices/0000:00:1d.0 /sys/kernel/iommu_groups/9/devices/0000:00:1f.0 /sys/kernel/iommu_groups/9/devices/0000:00:1f.2 /sys/kernel/iommu_groups/9/devices/0000:00:1f.3 USB Devices Bus 002 Device 002: ID 8087:8001 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8009 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 0930:6544 Toshiba Corp. TransMemory-Mini / Kingston DataTraveler 2.0 Stick (2GB) Bus 003 Device 004: ID 046d:c24e Logitech, Inc. G500s Laser Gaming Mouse Bus 003 Device 003: ID 03f0:064a Hewlett-Packard Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub System Log after reboot: Apr 6 20:52:04 unHRTATTK logger: Updating templates... Updating info... Done. Apr 6 20:52:04 unHRTATTK kernel: EXT4-fs (loop1): mounted filesystem with ordered data mode. Opts: (null) Apr 6 20:52:04 unHRTATTK emhttp: Starting libvirt... Apr 6 20:52:04 unHRTATTK logger: Starting libvirtd... Apr 6 20:52:04 unHRTATTK kernel: tun: Universal TUN/TAP device driver, 1.6 Apr 6 20:52:04 unHRTATTK kernel: tun: (C) 1999-2004 Max Krasnyansky <[email protected]> Apr 6 20:52:04 unHRTATTK kernel: Ebtables v2.0 registered Apr 6 20:52:04 unHRTATTK kernel: device virbr0-nic entered promiscuous mode Apr 6 20:52:04 unHRTATTK avahi-daemon[1763]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Apr 6 20:52:04 unHRTATTK avahi-daemon[1763]: New relevant interface virbr0.IPv4 for mDNS. Apr 6 20:52:04 unHRTATTK avahi-daemon[1763]: Registering new address record for 192.168.122.1 on virbr0.IPv4. Apr 6 20:52:04 unHRTATTK kernel: virbr0: port 1(virbr0-nic) entered listening state Apr 6 20:52:04 unHRTATTK kernel: virbr0: port 1(virbr0-nic) entered listening state Apr 6 20:52:04 unHRTATTK dnsmasq[4321]: started, version 2.72 cachesize 150 Apr 6 20:52:04 unHRTATTK dnsmasq[4321]: compile time options: IPv6 GNU-getopt no-DBus i18n IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-DNSSEC loop-detect Apr 6 20:52:04 unHRTATTK dnsmasq-dhcp[4321]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h Apr 6 20:52:04 unHRTATTK dnsmasq-dhcp[4321]: DHCP, sockets bound exclusively to interface virbr0 Apr 6 20:52:04 unHRTATTK dnsmasq[4321]: reading /etc/resolv.conf Apr 6 20:52:04 unHRTATTK dnsmasq[4321]: using nameserver 8.8.8.8#53 Apr 6 20:52:04 unHRTATTK dnsmasq[4321]: using nameserver 8.8.4.4#53 Apr 6 20:52:04 unHRTATTK dnsmasq[4321]: read /etc/hosts - 1 addresses Apr 6 20:52:04 unHRTATTK dnsmasq[4321]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses Apr 6 20:52:04 unHRTATTK dnsmasq-dhcp[4321]: read /var/lib/libvirt/dnsmasq/default.hostsfile Apr 6 20:52:04 unHRTATTK kernel: virbr0: port 1(virbr0-nic) entered disabled state Apr 6 20:52:06 unHRTATTK ntpd[1571]: Listen normally on 3 docker0 172.17.42.1:123 Apr 6 20:52:06 unHRTATTK ntpd[1571]: new interface(s) found: waking up resolver Apr 6 20:52:17 unHRTATTK kernel: docker0: port 1(vethf6dbeb6) entered forwarding state Apr 6 20:54:08 unHRTATTK php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php Apr 6 20:54:15 unHRTATTK kernel: device vnet0 entered promiscuous mode Apr 6 20:54:15 unHRTATTK kernel: br0: port 2(vnet0) entered forwarding state Apr 6 20:54:15 unHRTATTK kernel: br0: port 2(vnet0) entered forwarding state Apr 6 20:54:15 unHRTATTK kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 6 20:54:16 unHRTATTK kernel: br0: port 2(vnet0) entered disabled state Apr 6 20:54:16 unHRTATTK avahi-daemon[1763]: Withdrawing workstation service for vnet0. Apr 6 20:54:16 unHRTATTK kernel: device vnet0 left promiscuous mode Apr 6 20:54:16 unHRTATTK kernel: br0: port 2(vnet0) entered disabled state Apr 6 21:10:57 unHRTATTK emhttp: shcmd (63): /usr/sbin/hdparm -y /dev/sdc &> /dev/null Apr 6 21:10:57 unHRTATTK emhttp: shcmd (64): /usr/sbin/hdparm -y /dev/sdg &> /dev/null Apr 6 21:11:01 unHRTATTK kernel: mdcmd (25): spindown 9 Apr 6 21:11:34 unHRTATTK kernel: kvm: already loaded the other module Apr 6 21:12:47 unHRTATTK kernel: mdcmd (26): spindown 2 Apr 6 21:12:47 unHRTATTK kernel: mdcmd (27): spindown 3 Apr 6 21:13:21 unHRTATTK kernel: mdcmd (28): spindown 0 Apr 6 21:13:21 unHRTATTK kernel: mdcmd (29): spindown 1

Thanks but found the issue. Make sure to read the correct manual version of your motherboard before posting questions that are answered in it. The Maximus VII appears to have hardware pass-through capabilities but now need to test it. Thanks again

That's great! I have a Maximus VII HERO and the system info tab shows that IOMMU is disabled while HVM is enabled. Any settings you had to enable in BIOS? I have vt-d enabled but that appears to be it for virtualization. Model: N/A M/B: ASUSTeK COMPUTER INC. - MAXIMUS VII HERO CPU: Intel® Core™ i7-4790K CPU @ 4.00GHz HVM: Enabled IOMMU: Disabled Cache: 256 kB, 1024 kB, 8192 kB Memory: 16384 MB (max. installable capacity 32 GB) Network: eth0: 1000Mb/s - Full Duplex Kernel: Linux 4.1.7-unRAID x86_64 OpenSSL: 1.0.1p

Ah, I see. Thanks for the link to the website and information!

Thanks for the clarification, I would have expected the drive labeled as "Cache 2" to show the "Used" and "Free" indicators as well. I guess the pool reads like a parity drive? Where as the largest drive would be the only one present? I installed two 120GB SSDs so if I were to install say another drive that was 256GB the screen would display 256GB as my cache but the total would be 496GB I believe.

Well, if that's the case I am wondering if anyone else viewing would be able to verify if my cache pool is implemented correctly? Thanks for the replies by the way.

I am running through the same process at the moment and since you're in the middle of this does your cache drive (pool?) appear the same way mine does? The attached is a screen shot of what the system is reporting through the GUI.

Hello Mike, Thanks for looking at this for me. It seems the 4790k and the asus motherboard both support vt-d which is great! Hope to get this soon! Thanks

Hello all, could use your help.... Here's my prospective build: http://pcpartpicker.com/p/NpcrQ7 This is to upgrade my aging system that I had built years ago. I recently upgraded to 6.0.1 and noticed that with Dockers, VM functionality built in I would like to make use of those features. I picked MicroCenter as my vendor of choice as they are pretty close to me and have everything I was looking for in stock. I will be moving my existing drives to this new build but that appears to be all that I can move from my current setup. The uses are for running multiple 1080p Plex streams (passmark score for the cpu seems able to handle this), Linux VM for GNS3, handbrake encoder and music server. Is there anything else you all can think of that would be a problem here? The MB allows for virtualization but couldn't find anything is regards to graphics card pass through if I wanted to run a full-blown gaming PC out of this thing. I could also upgrade the memory so that wouldn't be much of an issue price wise. Thanks all for your input.

SNAP, OK. I'll check that out. Thanks for the heads up.

After reading this thread and thinking about the data I have that's important to me (music files) I would like to start to backup my drives. Is there a way to plug an external HDD directly to the chassis where the unRAID system resides and copy the drives locally? I think I would rather do this than copy the files over the network.

So, after upgrading and looking a little deeper I was able to get this to work. This time I set a min. space of 1000. This worked although not sure why as I have not needed to set it before. Thanks all for the help!