esaru

Members
  • Posts

    23
  • Joined

  • Last visited

Recent Profile Visitors

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

esaru's Achievements

Noob

Noob (1/14)

5

Reputation

1

Community Answers

  1. Only thing that worked for me was nuking my VM and doing a clean windows installation. Quite unsatisfying as far as solutions go..
  2. Thank you! Some people mentioned that this guide breaks their dockers. Could this be the reason that my jackett docker randomly stopped working? It boots up alright, log seems fine but I can't access the webui.
  3. Ok so this is what I need to do? 1. Remove the swTPM binaries from /boot/extra. Do I need to uninstall them somehow? If so, how? 2. Delete the script (or at least change it so that it doesn't run at startup). Do I need to undo any changes made by the script manually or is this solved by just rebooting? 3. Undo the changes in the VM xml. I'm not really worried about any effects on the VM itself. I can easily just do a clean install if needed. I just want my unraid install to be pristine
  4. Hey, I followed the swTPM guide (link below) and installed Windows 11. Could someone explain what parts I need to undo (and how) when the new unraid version hits and we have this functionality built in? I don't have Bitlocker activated. Really don't want to break anything or leave some problematic stuff behind. https://www.linkedin.com/pulse/swtpm-unraid-zoltan-repasi/
  5. Nope, sorry. I had to create a new VM to get rid of this, unfortunately.. I still have no idea what caused the log spam. Please post here if you find a solution!
  6. I see. Is there any duct tape solution available? Perhaps changing the nginx conf to just refuse this type of connection or something? Should I reboot the server when log hits 100%? Are there any risks involved with leaving it at 100%? I can live with not being able to get fresh log messages, but if there are harsher potential consequences I'd be more motivated to adress the issue by reinstalling windows or something.
  7. I deleted a whole bunch of apps, including Cryptomator which is the only one that I know uses WebDAV. It's still happening. Am I correct to assume that it must be an app/program on my VM that is contacting my servers webui? Could it be some aspect of Windows itself doing this stuff? Some more instructions for troubleshooting would be very appreciated.
  8. Your CPU does indeed have the AES-NI instruction set. I'd just go ahead and encrypt! https://ark.intel.com/content/www/us/en/ark/products/52214/intel-core-i7-2600k-processor-8m-cache-up-to-3-80-ghz.html Intel® AES New Instructions - Yes
  9. Tried putting my VM to sleep, just to try something. When the VM is sleeping, this error shows instead: Does this possibly lead to some conclusion?
  10. Rebooted tower again, it's still ongoing. Not sure what to do next, I've been shutting down pretty much every app/service I could find in task manager. Let's see if that has an impact, otherwise I'm just clueless. Edit: it's still happening. Seems like nuking my VM and leaving windows forever is like the only viable option at this point..
  11. Could it be the infamous Plex health check? AFAIK that issue is resolved in later versions of Unraid. May I ask why you are not upgrading? It seems like an easy thing to apply if you're having issues.
  12. I did reboot the tower around 10 yesterday, however only the VM was rebooted after exiting Cryptomator etc in the afternoon. When I took those measures the log was not full at all, it filled during the late evening/night. tower-diagnostics-20210504-1040.zip
  13. Yesterday i exited Cryptomator and a bunch of other services for good measure (Veeam, google drive sync). I also uninstalled a bunch of unused apps and updated Windows. No dice, the log is 100% again this morning. Any other advice/pointers? Is there some additional information I could provide for further troubleshooting? Thanks.
  14. I run Cryptomator, I think it utilizes WebDAV. I’ll check it out!