slizz

Members
  • Posts

    37
  • Joined

  • Last visited

Posts posted by slizz

  1. I was lazy recently and changed PSUs without removing the SATA power cables from my array and plugging the modular end into the PSU.  I never realized that these were specific to the PSU and assumed they were standardized.  Well that proved to be a costly mistake as all four of my WD Red 3TB drives are now dead.  I don't know if they are able to be fixed with a PCB replacement.  My Samsung SSD Cache drive is still good and detected by unRaid.

     

    In the event I have to replace all of my hard drives what kind of trouble am I looking at as far as setting everything back up...dockers, vms, etc.....I am pretty sure all of the dockers and VMS are in the cache.  I know my data is long gone if the PCBs can't be replaced.  Am I going to have to set up all new shares?  Is it salvageable or should I just go nuclear and start with a clean install?  Thanks guys.

  2. I recently changed from a Seasonic 450w PSU to a EVGA G2 750w to support a GPU.  Initially I had trouble getting the PC to boot after the change.  The LE6 light was an amber color and I couldn't figure out what was going on.  Then magically it booted and I had no further issues.  Now I decided to build a gaming PC rather than virtualizing it.  I transferred the EVGA to my new build and put the seasonic back into my unRaid box.  Now I am having the same amber colored LE6 light.  I have tried both PSUs with the same result.  I can not get the unRaid box to power on and it had been working perfectly.  I removed all of the components including the motherboard and ran it on the original box to eliminate the chance that an unintentional ground was causing this.  I removed RAM and tried each DIMM with each individual stick, every possible combination, and still had the same issue.  I am at a loss and looking for suggestions.

     

    If I have to replace the motherboard I would like to go to something full ATX.  I was looking at the ASRock z97 Extreme6.  I have a Xeon 1246v3.  I just want to make sure that board can handle virtualization without issue.  What kind of pain am I going to be in for moving unRaid to a new motherboard.  Will I have to redo all of my VMs or will they just work?  I'd rather not replace the motherboard but getting all of the questions out of the way now.  If I do have to replace the motherboard I want Full ATX with virtualization support.  If there are any other recommended boards please let me know.  Thanks!

  3. I was able to assign the devices in xml by bus and device number as outlined in the sticky in this forum.  When I launch the VM the Oculus software detects all sensors.  Then for some reason during setup the device numbers keep getting changed.  When I check Tools/System Devices the device number assigned to the device is off a couple of digits making the address useless in a matter of seconds.  Is there anyway to prevent this?

  4. I am trying to pass through two sensors for an Oculus Rift.  Obviously they are the same vendor etc.. causing a conflict.  I am getting error

     

    operation failed: Multiple USB devices for 2833:211, use <address> to specify one

     

    I only have the on board controller and am reluctant to pass it through out if fear of messing up the unraid install.  I can not add a PCI card as my GPU blocks the only open slot.  Is there a way to somehow just rename it to resolve the conflict?  Thanks in advance for any assistance. 

  5. Well folks...turns out I'm just not very smart.  I had assigned a static IP when accessing in VNC.  When I changed to the GPU it changed the static connection back to DHCP which is why RDP was not working.  I realized this after a restart of the VM while sitting at my TV which is connected to the GPU rather than doing it from the other room....Doh!  Thanks for all of the help as always. 

  6. Here is the log from the VM:

     

     

    2016-11-28 21:17:38.694+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: unLIZZIO

    LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'Windows 10' -S -machine pc-i440fx-2.5,accel=kvm,usb=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/ed964547-aba4-4f97-5843-3e308a11416e_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 8192 -realtime mlock=on -smp 6,sockets=1,cores=3,threads=2 -uuid ed964547-aba4-4f97-5843-3e308a11416e -nographic -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 -device ich9-usb-uhci2,mastbvirt/qemu/channel/target/domain-Windows 10/org.qemu.guest_agent.0,server,nowait' -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device vfio-pci,host=01:00.0,id=hostdev0,bus=pci.0,addr=0x5 -device vfio-pci,host=01:00.1,id=hostdev1,bus=pci.0,addr=0x6 -device usb-host,hostbus=3,hostaddr=3,id=hostdev2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on

    Domain id=1 is tainted: high-privileges

    Domain id=1 is tainted: host-cpu

    char device redirected to /dev/pts/0 (label charserial0)

  7. 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3 Processor DRAM Controller [8086:0c08] (rev 06)

    00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06)

    00:01.1 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller [8086:0c05] (rev 06)

    00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 05)

    00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d] (rev 05)

    00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 [8086:8c10] (rev d5)

    00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 [8086:8c14] (rev d5)

    00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 [8086:8c16] (rev d5)

    00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] (rev 05)

    00:1f.0 ISA bridge [0601]: Intel Corporation C222 Series Chipset Family Server Essential SKU LPC Controller [8086:8c52] (rev 05)

    00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c02] (rev 05)

    00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22] (rev 05)

    00:1f.6 Signal processing controller [1180]: Intel Corporation 8 Series Chipset Family Thermal Management Controller [8086:8c24] (rev 05)

    01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798]

    01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti HDMI Audio [Radeon HD 7870 XT / 7950/7970] [1002:aaa0]

    02:00.0 Serial Attached SCSI controller [0107]: LSI Logic / Symbios Logic SAS2308 PCI-Express Fusion-MPT SAS-2 [1000:0086] (rev 05)

    03:00.0 PCI bridge [0604]: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge [1a03:1150] (rev 03)

    04:00.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30)

    05:00.0 Ethernet controller [0200]: Intel Corporation I210 Gigabit Network Connection [8086:1533] (rev 03)

    06:00.0 Ethernet controller [0200]: Intel Corporation I210 Gigabit Network Connection [8086:1533] (rev 03)

    IOMMU Groups

     

    Warning: Your system has booted with the PCIe ACS Override setting enabled. The below list doesn't not reflect the way IOMMU would naturally group devices. To see natural IOMMU groups for your hardware, go to the VM Settings page and set the PCIe ACS Override setting to No.

    /sys/kernel/iommu_groups/0/devices/0000:00:00.0

    /sys/kernel/iommu_groups/1/devices/0000:00:01.0

    /sys/kernel/iommu_groups/2/devices/0000:00:01.1

    /sys/kernel/iommu_groups/3/devices/0000:00:14.0

    /sys/kernel/iommu_groups/4/devices/0000:00:1a.0

    /sys/kernel/iommu_groups/5/devices/0000:00:1c.0

    /sys/kernel/iommu_groups/6/devices/0000:00:1c.2

    /sys/kernel/iommu_groups/7/devices/0000:00:1c.3

    /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

    /sys/kernel/iommu_groups/9/devices/0000:00:1f.6

    /sys/kernel/iommu_groups/10/devices/0000:01:00.0

    /sys/kernel/iommu_groups/10/devices/0000:01:00.1

    /sys/kernel/iommu_groups/11/devices/0000:02:00.0

    /sys/kernel/iommu_groups/12/devices/0000:03:00.0

    /sys/kernel/iommu_groups/12/devices/0000:04:00.0

    /sys/kernel/iommu_groups/13/devices/0000:05:00.0

    /sys/kernel/iommu_groups/14/devices/0000:06:00.0

    CPU Thread Pairings

     

    cpu 0 <===> cpu 4

    cpu 1 <===> cpu 5

    cpu 2 <===> cpu 6

    cpu 3 <===> cpu 7

    USB Devices

     

    Bus 002 Device 002: ID 8087:8000 Intel Corp.

    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    Bus 001 Device 002: ID 8087:8008 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 005: ID 0557:2419 ATEN International Co., Ltd

    Bus 003 Device 004: ID 0557:7000 ATEN International Co., Ltd Hub

    Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver

    Bus 003 Device 002: ID 0781:5571 SanDisk Corp. Cruzer Fit

    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    SCSI Devices

     

    [0:0:0:0]    disk    SanDisk  Cruzer Fit      1.00  /dev/sda  8.00GB

    [2:0:0:0]    disk    ATA      Samsung SSD 850  1B6Q  /dev/sdb    250GB

    [4:0:0:0]    disk    ATA      WDC WD30EFRX-68E 0A82  /dev/sdc  3.00TB

    [5:0:0:0]    disk    ATA      WDC WD30EFRX-68E 0A82  /dev/sdd  3.00TB

    [6:0:0:0]    disk    ATA      WDC WD30EFRX-68E 0A82  /dev/sde  3.00TB

    [7:0:0:0]    disk    ATA      WDC WD30EFRX-68E 0A82  /dev/sdf  3.00TB

  8. I have a Windows 10 install that is working well.  I can RDP into it when assigning the VM to VNC.  Once I assign my GPU (AMD RADEON 7970) it doesn't show up on a connected monitor and I can no longer RDP into the VM.  It may not even be booting.  I had a Windows 10 VM working fine with this GPU and pass through yesterday.  I just decided to get rid of that VM and do a clean install because of some errors that I made.  HVM and IOMMU are enabled.  PCIe ACS override is on.  The previous working VM I had was set up originally in unRaid 6.1.  I am currently using version 6.2.4.  Thanks for any insight. 

     

     

  9. I am getting the following when trying to install.  Any suggestions?

     

    Pulling image: pducharme/unifi-video-controller:latest

    IMAGE ID [latest]: Pulling from pducharme/unifi-video-controller.

    IMAGE ID [6ffe5d2d6a97]: Already exists.

    IMAGE ID [f4e00f994fd4]: Already exists.

    IMAGE ID [e99f3d1fc87b]: Already exists.

    IMAGE ID [a3ed95caeb02]: Already exists.

    IMAGE ID [ededd75b6753]: Already exists.

    IMAGE ID [1ddde157dd31]: Already exists.

    IMAGE ID [5851290e7315]: Pulling fs layer. Download complete. Extracting. Pull complete.

    IMAGE ID [ace1c0154b69]: Pulling fs layer. Downloading 100% of 22 MB. Verifying Checksum. Download complete. Extracting. Pull complete.

    IMAGE ID [65f6e3b332e9]: Pulling fs layer. Downloading 100% of 929 KB. Verifying Checksum. Download complete. Extracting. Pull complete.

    IMAGE ID [a45914d79836]: Pulling fs layer. Downloading 100% of 772 B. Verifying Checksum. Download complete. Extracting. Pull complete.

    IMAGE ID [fa2e1f43e6f8]: Pulling fs layer. Downloading 100% of 13 KB. Verifying Checksum. Download complete. Extracting. Pull complete.

    IMAGE ID [4e6520aae5dc]: Pulling fs layer. Downloading 100% of 15 KB. Verifying Checksum. Download complete. Extracting. Pull complete.

    IMAGE ID [b2c8e7aaede9]: Pulling fs layer. Downloading 100% of 45 MB. Verifying Checksum. Download complete. Extracting. Pull complete.

    IMAGE ID [fc21329cfd66]: Pulling fs layer. Downloading 100% of 137 MB. Download complete. Extracting. Pull complete.

    IMAGE ID [26222c8ac9bd]: Pulling fs layer. Downloading 100% of 78 MB. Verifying Checksum. Download complete. Extracting. Pull complete.

    IMAGE ID [dbe54fa0bbc0]: Pulling fs layer. Downloading 100% of 80 MB. Verifying Checksum. Download complete. Extracting. Pull complete.

    IMAGE ID [208a7f0d29e7]: Pulling fs layer. Downloading 100% of 421 B. Verifying Checksum. Download complete. Extracting. Pull complete.

    IMAGE ID [564e9fd55734]: Pulling fs layer. Downloading 100% of 420 B. Verifying Checksum. Download complete. Extracting. Pull complete.

     

    TOTAL DATA PULLED: 363 MB

     

    Error: layers from manifest don't match image configuration

     

  10. When trying to update to the newest version of Crashplan I get the following warning.  Everything was working until this and I am able to install other docker apps.  What is up with this?

     

    Warning: DOMDocument::load(): EntityRef: expecting ';' in /var/lib/docker/unraid/templates-community-apps/249.xml, line: 5 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 379 Warning: DOMDocument::load(): EntityRef: expecting ';' in /var/lib/docker/unraid/templates-community-apps/249.xml, line: 5 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 379

     

  11. I keep getting this error when I try to install the desktop.  Are the files gone or the server down?

     

    root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="CrashPlan-Desktop" --net="bridge" -e TZ="America/New_York" -p 3389:3389/tcp --volumes-from CrashPlan gfjardim/crashplan-desktop

    Unable to find image 'gfjardim/crashplan-desktop:latest' locally

    Pulling repository gfjardim/crashplan-desktop

    Error: image gfjardim/crashplan-desktop:latest not found

     

    The command failed.

  12. I only have one PCI slot that will support it.  I'm currently using am e3-1246v3.

     

    /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:1a.0

    /sys/kernel/iommu_groups/4/devices/0000:00:1c.0

    /sys/kernel/iommu_groups/5/devices/0000:00:1c.2

    /sys/kernel/iommu_groups/6/devices/0000:00:1c.3

    /sys/kernel/iommu_groups/7/devices/0000:00:1d.0

    /sys/kernel/iommu_groups/8/devices/0000:00:1f.0

    /sys/kernel/iommu_groups/8/devices/0000:00:1f.2

    /sys/kernel/iommu_groups/8/devices/0000:00:1f.3

    /sys/kernel/iommu_groups/8/devices/0000:00:1f.6

    /sys/kernel/iommu_groups/9/devices/0000:03:00.0

    /sys/kernel/iommu_groups/9/devices/0000:04:00.0

    /sys/kernel/iommu_groups/10/devices/0000:05:00.0

    /sys/kernel/iommu_groups/11/devices/0000:06:00.0

     

    I don't fully understand the risks with ACS override so I am treading lightly.

  13. Here are the PCI devices in System/Tools

     

    00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3 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 8 Series/C220 Series Chipset Family USB xHCI (rev 05)

    00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)

    00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)

    00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5)

    00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5)

    00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)

    00:1f.0 ISA bridge: Intel Corporation C222 Series Chipset Family Server Essential SKU LPC Controller (rev 05)

    00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)

    00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)

    00:1f.6 Signal processing controller: Intel Corporation 8 Series Chipset Family Thermal Management Controller (rev 05)

    01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]

    01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT HDMI Audio [Radeon HD 7970 Series]

    02:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2308 PCI-Express Fusion-MPT SAS-2 (rev 05)

    03:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 03)

    04:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 30)

    05:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

    06:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

  14. I keep getting this error when trying to start the VM:

     

    internal error: early end of file from monitor: possible problem:

    2015-11-08T02:08:42.633996Z 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.

    2015-11-08T02:08:42.634022Z 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

    2015-11-08T02:08:42.634029Z 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

    2015-11-08T02:08:42.634036Z 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

     

    Any assistance would be greatly appreciated.