thither

Members
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

0 Neutral

About thither

  • Rank
    Newbie

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. This is maybe a dumb question, I just can't remember. Is the source code for videosort/VideoSort.py included in this docker image, or is it something that is downloaded and installed separately from the docker image itself? (I installed nzbget a long time ago and several versions of Unraid back, so I honestly can't remember.) If it's in the image it should be patchable (by running it through the 2to3 script as @Merson suggested, at a minimum). If not, does anyone have a link to wherever the official source is, or else an alternative script written in Python 3? The reaso
  2. Hi all, I have a question. I've got a machine that I put together back in 2016 which used this now-discontinued 660W PSU, the Seasonic SS-660XP2. The PSU recently failed, and I'm wondering if I might have been running too much hardware on it. When I first set this up, it was running 4 WD Reds (6GB) plus a NVidia GeForce GTX 970 (not used often, just for gaming in a VM). Everything worked fine. Then a while back my motherboard failed and I wound up uninstalling the GPU. Recently after a disk failure I decided to add in a 5th HDD and pop the GPU back in. I started it up and everythin
  3. I'm seeing something (maybe) similar, but I gave up on it after about 5 minutes assuming it was frozen. However, I can boot into GUI mode and everything works fine, boot takes maybe a minute or so. I had similar problems with 6.3.2: the GUI mode booted up with no problems but everything would hang when I tried to boot into headless mode. For 6.3.2 I was able to fix this problem via a firmware upgrade of my ASRock motherboard. For 6.3.3 I'm again unable to boot headless - the terminal prints "Loading bzImage... ok" and then it seems to freeze up, no response from the NIC or the keyb
  4. Ok, so I updated my firmware BIOS to version 7.30 and was able to boot up normally in non-GUI mode again. Not sure what the deal is, but everything seems to be kosher now. Thanks for the advice! (Also I have an ASRock board, not an Asus one, just for the record.)
  5. Just to confirm, I also see these same checksums on my Asus Z170 board, and my syslinux.cfg is the same as the one @JonUKRed posted above (and I'm also not able to boot into non-GUI mode). Don't have time for a BIOS upgrade now but I'll try it sometime in the next few days and report back.
  6. After upgrading from 6.3.1 I'm seeing some odd behavior where I can boot into GUI mode, but when I try to boot into regular (OS) mode the server freezes after it loads /bzImage and is not pingable. I run headless most of the time with my monitor plugged into a different GUI card for VMs, so this isn't ideal. Anything I can try to diagnose this?
  7. I had the exact same issue upgrading from rc3 to rc4. I didn't change anything explicitly, bt when I went to my WM settings, I found that there were two sound cards being passed through - the onboard one and the GPU one. I disabled the onboard one (set "first sound card" to the GPU sound card and the second to "none") and then I was able to boot my VM as before, and sound (through HDMI) works fine again.
  8. Aha - so after digging around a little more, I realized I can just make a separate vdisk image to pass into Windows, so I did that instead. It's not really as good as using a share since I need to specify the image size manually and then I lose that space out of my cache, but it's good enough for my purposes and once I had mounted the image in Windows and done an NTFS format, I was able to get the installer to use it correctly.
  9. Just as an addendum to this, I have just tried unsuccessfully to solve the problem by doing this: Added a "windows" user in unRaid Set the SMB security on both shares to "secure" From the Windows VM, disconnected both shares and rebooted Reconnected to the shares from Windows and using the "windows" user and password to connect Verified that I could still write files to the drives Tried the installer again. No dice - same behavior as above. On the unRaid box, did "chown -R windows" on both of the shares, then rebooted Windows and tried again - still no dice. I'm beginning t
  10. Hi! I've got a Win 10 VM set up with unRaid 6.2b20 and most things are working really well. I've got the main OS installed on a 30GB vdisk on my cache drive and it boots up just fine. Then inside the OS I have mapped two network shares for storing games (G:) and data (U:) respectively. I set up these shares in unRaid in the usual way and didn't change any defaults (save for marking the Games one as cache-only). I installed Steam and had it set up with a games library on the G: drive and have been able to download and run my games through the client that way and everything works great. How
  11. Oops, just realized I actually forgot to post this... Cool, makes sense. If that's the case your stock fan should be fine. For my build I'm running a Windows VM for gaming, and the PC is in my office right next to my desk, so having low noise was more important to me. I don't generally watch movies in the office, for that I'm running Plex media server on the unRaid box and then using a ChromeCast in the living room for playback most of the time, which works great but I kind of miss having a more traditional remote-control experience. My old setup was Kodi running on a mac mini going
  12. Ok, yeah, using the 8.1 drivers from 0.1.105 was able to get me up and running and I completed the install without any hitches following the instructions in the YouTube video. (For my setup I also needed to mess with my BIOS so that it uses the integrated GPU for the host OS rather than the external video card I'm passing through, but I'm not actually sure that's a requirement.) In case it's helpful, I'll paste the XML used for the VM below. <domain type='kvm'> <name>Windows 10</name> <uuid>4e4f9451-b000-546c-e32d-321632571701</uuid> <metadat
  13. Aha - I was able to make some progress by using the Win8.1 drivers from virtio-win-0.1.105.iso - I've at least got to the part where the drivers install and I'm able to select the vdisk to install to now. Progress! I was not able to use any of the following virtio ISOs: virtio-win-0.1.102.iso virtio-win-0.1.112-1.iso virtio-win-0.1.113.iso
  14. I'm seeing this issue as well running the built-in Windows 10 template in unRaid 6.2b18. I've tried virtio-win-0.1.112-1.iso (win10/amd64 folder) and virtio-win-0.1.102.iso (win8.1/amd64 folder). I get the same behavior as described: the drivers don't show up as "compatible," and if I install them anyways Win 10 can't find any media to install on. I'm giving the VM 16GB of RAM and 6 cores. One thing I've noticed is that my install screens are slightly different from the ones in this youtube video showing a Win10 install on unRaid (I have an option saying "I don't have a product key" inste