Parigot

Members
  • Posts

    48
  • Joined

  • Last visited

Posts posted by Parigot

  1. Just now, itimpi said:

    You might want to work out why the files ended up there to stop it happening again?   It can happen if something is run that can by-passes the UnRaid User Share system.

     

    you mentioned you deleted the files which removes them from the ‘media’ share as even with a ‘Use Cache’ setting of ‘No’ UnRaid would treat them as part of the User Share for read purposes.   If you wanted instead to keep the files you could have instead changed the “Use Cache” setting to “Yes” and then run mover which would have transfered them onto the array.

    Yeah I realized this after I deleted them. There wasn't that many anyway. But I'll keep your suggestion in mind for next time.

     

    To your first question, I wonder if this happens when sub-folders of a Share are created through cli or using a UI like Krusader.

  2. So this has probably been answered many times but I cannot find anything that would make sense to my issue.

     

    Last week, I've upgraded from 6.8.(don't remember) to 6.9.2. Right away after the update, my single cache drive of 500gb was almost full (64gb available).

    I didn't modified any settings on the shares regarding cache use.

     

    Does 6.9.X modifies anything that could cause this?

     

    If anyone has any idea what is happening here, I would really appreciate it. Happy to share any log/config required.

     

    Thanks community!

  3. 1 hour ago, x10ded said:

    Random question to add; How do you go about turning the VM OS off and on? Can you set up the power button on the case to do it (like normal) or do you have to log in to UnRaid online from another device to start the VM?

    Log in to Unraid from another device and start the VM...or enable auto-start on the VM so it will start as soon as your array starts (also enable auto-start on the array though)

  4. 2 hours ago, nox_uk said:

    I would not think lack of activation is the issue.

     

    Have you tried dumping the card BIOS and passing that through? (it's actually really easy, just sounds bad!)

     

    youtube search for 'spaceinvader one' and follow his guide (clearest one I found)

    I was referring to the fact that I didn't do the Windows update since it is not activated.

     

    I'll check the video from SpaceInvader definitely.

     

    Thanks

  5. Using Unraid 6.3.5

     

    Getting code 28 in device manager. Wondering if it's not because my Windows is not up to date since I didn't activate it yet...

     

    Here are the 2 events showing up once the driver installation fails:

     

    Driver Management has concluded the process to add Service nvlddmkm for Device Instance ID PCI\VEN_10DE&DEV_1401&SUBSYS_29663842&REV_A1\3&13C0B0C5&0&28 with the following status: 0.

     

    Driver Management concluded the process to install driver nv_dispi.inf_amd64_5601d21ccd639df9\nv_dispi.inf for Device Instance ID PCI\VEN_10DE&DEV_1401&SUBSYS_29663842&REV_A1\3&13C0B0C5&0&28 with the following status: 0x0.

  6. I'm running a Windows 10 Pro (not activated yet) VM with a GTX960 passed-through.

    The card is recognized by Windows and I was able to play a game without problem.

    I did try to install the latest NVIDIA drivers using the NVIDIA installer and by updating the driver in system devices but both are unable to install it and said installation failed.

     

    I attached a screenshot of it.

     

    I can't figure out what is causing the install to fail.

     

    Any thoughts?

     

    Thanks

    Screen Shot 2018-01-22 at 7.30.08 PM.png

  7. Just now, CHBMB said:

    Yeah, you need to do your research pretty thoroughly before buying an engineering sample, although some definite bargains to be had if you do so.

     

    At least you've identified the problem, any plans to change CPU?

     

    It is not an engineering sample (their S-Spec starts with a QB on this CPU). It is just the first stepping version (S-Spec: SROH8) of the CPU released by Intel and although they knew there was an issue with VT-d, they only applied the fix on the second stepping version (S-Spec: SR0KX).

     

    I'm going to try to find the second stepping of this same CPU or for either the 2670v2, 2680 or 2690 depending on the price I can find one at. Then I'll sell my current CPU.

  8. I'm pretty sure I identified the issue based on my research.

     

    My CPU is the E5-2670v1 SROH8 (C1 stepping). From the info I found, there was a bug with VT-d on that CPU that made it unusable. That was only fixed on the SR0KX version (C2 stepping).

     

    Issue is with the CPU not the motherboard or BIOS.

  9. I'm running a E5-2670v1 on an Intel DX79TO motherboard with the latest BIOS version (0650). 

    I cannot find how to enable VT-d in the BIOS. I did find and enabled VT but VT-d (IOMMU) is still showing as 'Disabled' in unRAID info tab.

    Both the CPU and motherboard support VT-d as per Intel website.

     

    If anyone has any idea about this that would be awesome! :)

     

    Thanks

  10. Hi,

     

    I setup a Windows 10 Pro VM on my unRAID v6.3.5. I access the VM using VNC Viewer 6.17.1113 from OSX 10.9. Nothing is passthrough (no PCIe or USB controller). I just remote to it using the keyboard and mouse on my MAC.

     

    I was able to do the installation fine and use it for a bit. But at one point, the mouse stopped working. I was still able to use the keyboard fine though so the VM has not froze.

    I restarted the VM and the mouse is back working fine for some time then it stops working again.

     

    I searched through the forum and found similar issues when a USB controller is passed through or using a mouse plugged into the unRAID system (which is neither the case here).

     

    Any idea what could cause this?

    Not sure what log file would help here but I'll be happy to provide anything that can help.

    Below is the XML of the VM.

     

    Thanks

     

    <domain type='kvm'>
      <name>001 Windows 10</name>
      <uuid>eb19a00d-4700-b96f-9c63-b7cf661e37ea</uuid>
      <metadata>
        <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
      </metadata>
      <memory unit='KiB'>8388608</memory>
      <currentMemory unit='KiB'>8388608</currentMemory>
      <memoryBacking>
        <nosharepages/>
      </memoryBacking>
      <vcpu placement='static'>8</vcpu>
      <cputune>
        <vcpupin vcpu='0' cpuset='2'/>
        <vcpupin vcpu='1' cpuset='3'/>
        <vcpupin vcpu='2' cpuset='4'/>
        <vcpupin vcpu='3' cpuset='5'/>
        <vcpupin vcpu='4' cpuset='6'/>
        <vcpupin vcpu='5' cpuset='7'/>
        <vcpupin vcpu='6' cpuset='8'/>
        <vcpupin vcpu='7' cpuset='9'/>
      </cputune>
      <os>
        <type arch='x86_64' machine='pc-i440fx-2.7'>hvm</type>
        <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
        <nvram>/etc/libvirt/qemu/nvram/eb19a00d-4700-b96f-9c63-b7cf661e37ea_VARS-pure-efi.fd</nvram>
      </os>
      <features>
        <acpi/>
        <apic/>
        <hyperv>
          <relaxed state='on'/>
          <vapic state='on'/>
          <spinlocks state='on' retries='8191'/>
          <vendor_id state='on' value='none'/>
        </hyperv>
      </features>
      <cpu mode='host-passthrough'>
        <topology sockets='1' cores='4' threads='2'/>
      </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/local/sbin/qemu</emulator>
        <disk type='file' device='disk'>
          <driver name='qemu' type='raw' cache='writeback'/>
          <source file='/mnt/user/domains/001 Windows 10/vdisk1.img'/>
          <target dev='hdc' bus='virtio'/>
          <boot order='1'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
        </disk>
        <disk type='file' device='cdrom'>
          <driver name='qemu' type='raw'/>
          <source file='/mnt/user/ISOs/Win10_1709_English_x64.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/ISOs/virtio-win-0.1.126-2.iso'/>
          <target dev='hdb' bus='ide'/>
          <readonly/>
          <address type='drive' controller='0' bus='0' target='0' unit='1'/>
        </disk>
        <controller type='usb' index='0' model='ich9-ehci1'>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
        </controller>
        <controller type='usb' index='0' model='ich9-uhci1'>
          <master startport='0'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
        </controller>
        <controller type='usb' index='0' model='ich9-uhci2'>
          <master startport='2'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
        </controller>
        <controller type='usb' index='0' model='ich9-uhci3'>
          <master startport='4'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' 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='0x04' function='0x0'/>
        </controller>
        <interface type='bridge'>
          <mac address='52:54:00:87:53:df'/>
          <source bridge='br0'/>
          <model type='virtio'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
        </interface>
        <serial type='pty'>
          <target port='0'/>
        </serial>
        <console type='pty'>
          <target type='serial' port='0'/>
        </console>
        <channel type='unix'>
          <target type='virtio' name='org.qemu.guest_agent.0'/>
          <address type='virtio-serial' controller='0' bus='0' port='1'/>
        </channel>
        <input type='tablet' bus='usb'>
          <address type='usb' bus='0' port='1'/>
        </input>
        <input type='mouse' bus='ps2'/>
        <input type='keyboard' bus='ps2'/>
        <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'>
          <listen type='address' address='0.0.0.0'/>
        </graphics>
        <video>
          <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
        </video>
        <memballoon model='virtio'>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
        </memballoon>
      </devices>
    </domain>

     

    • Upvote 1
  11. I just put my hands on a XEON e5-2670 v1 with an Intel DX79TO motherboard and 24GB RAM and was wondering what air CPU cooler are you guys using?

    I just want one that does the job and is as quiet as possible. It should also fit without blocking any of the memory slot.

     

    I did some research and my 2 choices so far are:

    1. Cooler Master Hyper 212 EVO

    2. be quiet! BK009 Pure Rock

     

    Feel free to join a photo of your suggestion if you are using it in a similar setup.

     

    Thanks!

  12. On 7/8/2017 at 7:44 AM, Squid said:

    It does appear that the "nag" screen to install can indeed cause problems on systems which do not work correctly or have underlying issues.

     

    This is because preclear if it does not detect that you have already dismissed the nag screen pops up the Do You Want To Install on every single page you hit within unRaid's GUI.  (Definitely not what I would want -> why not just pop it up when you're in the UI for preclear if its that important.)

     

    The problem with the way that this is currently handled basically causes an infinite loop of questions if there is an issue with the flash drive.  Some causes of the infinite loop:

    • Flash drive is perfectly ok, but has a Read Only switch on it set to be RO
    • Flash drive is full
    • Flash drive has some corruption on it resulting in it being a read-only file system.
    • Flash drive dropped offline
    • USB controller is flaky
    • You somehow inadvertently pass through the USB controller handling the flash drive to a VM.
    • Your kid / cat / free-range chicken (depending upon the location of the server and what you classify as a pet) inadvertently knocks the flash drive out.

    None of the above scenarios are by themselves fatal (unless you have the preclear plugin installed), and some of them the end-user might not ever even notice on a system, as the system will continue chugging along (although maybe with some errors being logged).  Also all of the above issues are not exactly rare in the unRaid eco-system.  (And some of the above require a reboot of the server in order to fix)

     

    All of these issues mean that it doesn't matter what you select (either install or dismiss), you will have immediately for all intents and purposes locked up the GUI.

     

    There is no recovery from this infinite nag loop.  Your only recourse as gfjardim stated above is to log in to the system (either locally, or via SSH) and then issue

    
    rm /usr/local/emhttp/plugins/preclear.disk/StatsInstall.page

     

    At which point the GUI should quit bitching at you.  You will still have the underlying problem though that caused this, and on the next reboot you will be susceptible to this problem again.  EDIT: (You might be able to also fix the lockup issue by navigating directly to the apps tab, as the first thing the apps tab does is wind up closing any/all popups that try to open.  Navigate directly to something like //Tower/Apps and then go to Installed Apps, and uninstall Preclear (and Statistics) from the display)

     

    Either way, IMHO a plugin (and one of the "must-have" plugins from a trusted author) should not be able to take down the webGUI completely if a problem with the flash drive occurs.  Simply passing the problem off to the user and not changing the underlying problem with the plugin is not the correct way to handle things.

     

     

     

    As a front line support guy around here my recommendation is (to be brutally honest) that how the preclear disk plugin is currently set up, I wouldn't have it installed unless I had an immediate need to preclear a disk (and then after the process is completed, uninstall it).  The scenarios can happen to anyone on any server.  Should it be installed, and one of the above scenario's happen, then you'll have lost access to the GUI when you need it the most.  

     

     

     

    Thanks for this reply.

     

    I already removed the StatsInstall.page but the popup keeps showing even if I click on the Apps tab.

     

    What is next here? Should I reboot the server? Should I remove the preclear plugin? If so, how to do it command-line so it is properly removed?

     

    As you mentioned, having that plugin taking over the entire GUI is a bit weird and I still can't figure out how this can be allowed by the unRAID team tbh.