Caduceus

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

3 Neutral

About Caduceus

  • Rank
    Newbie

Recent Profile Visitors

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

  1. I tried to follow these instructions to the letter... unfortunately, every time I restart the container or just restart splunkd, all of my indexed data seems to no longer be searchable on restart. The index data can still be seen in the persistant shares (ie. /splunkdata and /splunkcold). If I stop splunk and delete everything in /splunkdata and /splunkcold, then splunk start. Everything will re-index again. If I don't delete the data, I cannot search the data whether I restart or not. So some record of the files being indexed remains persistant in fishbucket db. I have not idea why my
  2. I was mistaken. This change doesn't seem to fix it. But in $splunk_home/etc/apps/journald_input/local/app.conf if we add: [install] state = disabled That seems to fix it by disabling the app.
  3. This message is persistent in my Messages. Is this error expected?
  4. unraid is currently on kernel 4.19.56 . I've read about the patches but haven't attempted anything. I was going to wait it out for the next AGESA. I did try both UEFI and legacy when I had F32 and F40. It didn't matter. Plus I read there could be problems with Windows using Nvidia cards if you booted unraid with the UEFI mode. I have no idea. I'm really happy with the way everything is working for the moment. I picked up some g.skill dual channel 3200mhz 32gb kit for $109 and a bunch of IronWolf 4TB hdds for $95.
  5. I was able to use the Radeon 5770 as the primary display by configuring the bios to use card two as primary. I was able to pass 1660Ti to VM, but only with the F5 bios. I got the 2700 because I was able to get the motherboard and chip for about $220 total. I planned on upgrading to 3700x in a year or two when the prices come down. Yes, if you get that chip, unless Gigabyte fixes their bios, you won't be able to pass through the 1660Ti. Also, I was able to pass through both videocards, 1 to each vm by running unRaid headless. It's a little more complicated, but you can use a vbios rom with a
  6. I recently built an unRaid server with almost this exact setup. Same motherboard, same cpu, I have the 1660ti (Gigabyte 1660ti mini-itx) setup in the primary pcix16 slot) but I have an old Radon 5770 in the second slot. The only caveat is, I need to run the F5 version of the bios. I had upgraded to F32 and F40. Both gave me serious issues that would not allow Windows VMs to start with those bios revisions. I did a full post in the VM Troubleshooting section. I hope this helps. You can see my IOMMU groups here:Post with IOMMU groups
  7. Well it looks like this was due to the bios on my motherboard. I had the latest revision F40. I tried downgrading to F32 but had the same problem. I then downgraded to F5 and I am now able to pass-through successfully. Ugh. I will be reluctant to update my bios now.
  8. Hi all, I'm running the latest version of unraid 6.7.2. I have 2 gpu's in my system, an old radeon 5770 and a gigabyte rtx 1660ti. I have a Ryzen 7 2700 and a Gigabyte b450 aorus m motherboard. I have tried everything I can think of or read to get the pass through working. I watched every spaceinvader one video on any related subject but it didn't help. The nvidia card has all of it's devices in the same iommu group. I pinned them all to vfio-pci. Whenever I try to start up a windows 10 vm , passing the card through, I get: -device vfio-p