Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Liam_Galt

  • Rank
  1. I get massive hanging when running this, I'm wondering what could be causing it. I notice it when I'm downloading via sabnzbd, mostly using my Windows VM (running on a dedicated NVMe SSD passed through). sabnzbd downloads to and extracts from cache drive. I have it pinned to CPUs my Windows VM doesn't use. Any ideas on flags that I could change to try to fix the issue?
  2. I'm setting up Organizr and was wondering how to set up authentication as described on the wiki. It seems to me that this would require an entire custom Nginx config for each subdomain, but I'm not positive. Anyone happen to know?
  3. I actually figured out how to do this, so I'll post a quick write-up in case others wonder about this. Warrentheo: I wanted it to be installed to the NVMe itself, not inside a vdisk on NVMe bastl: What you suggested is more or less what I did. My process for this was: 1) Attach NVMe to Windows VM as PCI device and boot into Windows. 2) Download/install some sort of disk cloning software. I used AOMEI, but EaseUs or software provided by manufacturers (e.g. Samsung) should work just as well. 3) Convert NVMe from MBR to GPT if necessary and if software doesn't do this automatically for you. 4) Clone Windows "disk" (really the vdisk but Windows of course sees it as just a disk) onto NVMe. 5) Shut down VM + Unraid. 6) Choose NVMe device as boot device when booting -> should boot into Windows no problem. Do any bare metal type config that you want here. Make sure to get UUID for drive (see: https://youtu.be/fnIn6GnA87c?t=675) 7) Boot into Unraid. Create new VM as described in SpaceInvaderOne's video (from the timestamp linked above).
  4. I currently have a Windows 10 VM installed on an SSD inside a vdisk that spans the whole SSD. I have an unused NVMe SSD of the same capacity. I want to migrate my Windows install to the NVMe SSD such that it's not on a vdisk and just the NVMe SSD itself (think bare metal install). Is there a documented procedure for this sort of operation? Would this be as simple as cloning the vdisk onto the NVMe SSD and then creating a VM to boot from that? Thanks for any input!
  5. I just did some testing and hard links appear to be working when created manually, it just seems to be with Sonarr that things aren't working as expected. Feel free to disregard anything here.
  6. I understand that the contents are the same, it's the storage calculation that is the concern. If I create a file and then create a hard link to it, the space appears to be calculated when viewed in both Shares and Main (for whatever disk the file and its link are on). Is this expected behavior? What happens if the calculations of these links exceeds my actual storage space?
  7. I noticed that my Media share (to which Deluge downloads, and Sonarr/Radarr create hard links to corresponding folders for Plex to read in from) was roughly double the size I was expecting it to be when looking at unRAID Web GUI. I looked into it a bit more and it seems that hard links aren't working as expected, and instead are creating new inodes (despite appearing to point to the same file). Example: /mnt/user/Media/Test# touch foo /mnt/user/Media/Test# ln foo bar /mnt/user/Media/Test# ls -li total 0 660391 -rw-rw-rw- 2 root root 0 Dec 22 09:15 bar 660390 -rw-rw-rw- 2 root root 0 Dec 22 09:15 foo It was my understanding that hard links worked fine within a user share, but this appears to be creating new inodes. If I do the same thing on /mnt/diskX/... it works, so is something possibly misconfigured with my share?