Mantene

Members
  • Posts

    55
  • Joined

Recent Profile Visitors

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

Mantene's Achievements

Rookie

Rookie (2/14)

9

Reputation

  1. Thanks, but starting and stopping them does not solve the issue. When I say the gui stops responding, I mean the web ui for the container. The UnRaid gui works just fine.
  2. https://www.linkedin.com/pulse/swtpm-unraid-zoltan-repasi/ That worked for me.
  3. No one has any ideas? This sucks. Having to remove and reinstall containers all the time is not fun.
  4. I have run into a problem. a few months back I started seeing Docker containers stop responding to attempts to access the gui. In order to fix it I need to remove the container and image and reinstall it. Then it works for a day or so and then stops and the only way to fix it is to remove and reinstall again. Please help. Here are some of the docker commands for the containers in question: Binhex-qBittorrent: Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-qbittorrentvpn' --net='bridge' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Eeyore" -e HOST_CONTAINERNAME="binhex-qbittorrentvpn" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='whocares' -e 'VPN_PASS'='notme' -e 'VPN_PROV'='custom' -e 'VPN_CLIENT'='wireguard' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'WEBUI_PORT'='8080' -e 'LAN_NETWORK'='192.168.1.0/24' -e 'NAME_SERVERS'='209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1' -e 'VPN_INPUT_PORTS'='9334' -e 'VPN_OUTPUT_PORTS'='9334' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8080]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png' -p '6881:6881/tcp' -p '6881:6881/udp' -p '8080:8080/tcp' -p '8118:8118/tcp' -v '/mnt/user/appdata/binhex-qbittorrentvpn/qBittorrent/data':'/data':'rw' -v '/mnt/user/appdata/firefox/Downloads/':'/monitor':'rw' -v '/mnt/user/Seeding/seeds/':'/config/qBittorrent/downloads/':'rw' -v '/mnt/cache/appdata/binhex-qbittorrentvpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn' 52111a025cd5167c57f3a87cd4d2f332debd50ce4cddb49a06560818f6a84074 Radarr: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='radarr' --net='bridge' -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Eeyore" -e HOST_CONTAINERNAME="radarr" -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:7878]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/radarr.png' -p '7878:7878/tcp' -v '/mnt/user/downloads/':'/downloads':'rw' -v '/mnt/user/Movies/':'/movies':'rw' -v '/mnt/cache/appdata/radarr':'/config':'rw' 'linuxserver/radarr:develop' 72ae1e437a47749e76f19dcd4c9f0a3181808a8464206292d9c09858bfe987a4 There are others. It seems to affect about half of all my containers :(. I have attached the qbittorent log which doesn't show any problems, yet the gui does not work unless I remove it and readd it. Also attaching a diagnostics package. eeyore-diagnostics-20210927-0915.zip binhex-qBittorrent-log.txt
  5. https://betanews.com/2021/09/18/microsoft-even-requires-tpm-2-0-for-windows-11-virtual-machines/ Microsoft has changed their policy on Virtualized Installations. Virtualized installations now require the same hardware physical installations require.
  6. I didn't realize Windows 11 was going to be pushed out to Windows 10 Dev Ring users. I now have Windows 11 on my Windows VM. It was not exactly a pleasant surprise, but I may stick with it. It says my computer does not meet the requirements for Windows 11 and that I will be required to reinstall Windows 10 when Windows 11 becomes generally available. Apparently, it requires secure boot be enabled to "comply" with the requirements. So, question - how does one enable secure boot on an existing VM?
  7. Maybe it would be worth having @limetech include swamp in the unraid kernel in future releases given that MS suggests not meeting the requirements in VMs might mean a reduced feature set. I wouldn’t think including swamp in the kernel would impose much extra work or introduce any problems into the process. I could, of course, be very very wrong here.
  8. Processor: 1 GHz or faster with 2 or more cores on a compatible 64-bit processor. (Microsoft links to a list of compatible processors for Windows 10 but has not yet updated the list for Windows 11). RAM: 4 gigabytes or more Storage: 64 GB or larger storage device (such as a hard drive or SSD) System Firmware: UEFI and Secure Boot capable TPM: Trusted Platform Module 2.0 (common on motherboards manufactured after 2016) Graphics Card: Compatible with DirectX 12 or later with WDDM 2.0 driver Display: An HD display at least 720p (1280×720) resolution larger than 9″ diagonal, 8-bits per color channel Internet Connection and Microsoft Accounts: Windows 11 Home edition requires an internet connection and a Microsoft account to set up the device on first use. Switching a device out of Windows 11 S mode also requires an internet connection. Do any of these suggest there will be issues running it in a VM? The TPM2 requirement is what I am curious about.
  9. Let me preface this by saying everything seems to be working great, so this seems like an error of no consequence at the moment, but I am seeing this:
  10. I can probably do all of those things. I am fairly sure I have a spare, though lower wattage, PSU. And just using two DIMMs is easy enough to try. However, I just started Prime95 cpu test so I will let that run for a few hours (if the PC stays up that long)! Thank you for the suggestions, I will report back when I have added information.
  11. May 5 08:58:30 Eeyore kernel: RSP: 0018:ffffc900007b78a0 EFLAGS: 00010202 May 5 08:58:30 Eeyore kernel: RAX: ffffea0005e41d80 RBX: ffffc900007b7940 RCX: 0000000000000006 May 5 08:58:30 Eeyore kernel: RDX: 0000000000000101 RSI: 17fec0817ed02b28 RDI: ffffc900007b78e8 May 5 08:58:30 Eeyore kernel: RBP: ffffc900007b7930 R08: 000000000000007f R09: ffffea0005e41d80 May 5 08:58:30 Eeyore kernel: R10: 0000000000000000 R11: ffff888103891500 R12: 000000000000000d May 5 08:58:30 Eeyore kernel: R13: ffff888103891500 R14: ffff8881026826c0 R15: 17fec0817ed02b08 May 5 08:58:30 Eeyore kernel: FS: 0000000000000000(0000) GS:ffff888ffea40000(0000) knlGS:0000000000000000 May 5 08:58:30 Eeyore kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 5 08:58:30 Eeyore kernel: CR2: 00001510c418d4e8 CR3: 000000000200a000 CR4: 0000000000350ee0 May 5 08:59:20 Eeyore kernel: mce: [Hardware Error]: Machine check events logged May 5 08:59:20 Eeyore kernel: [Hardware Error]: Corrected error, no action required. May 5 08:59:20 Eeyore kernel: [Hardware Error]: CPU:9 (17:71:0) MC2_STATUS[-|CE|MiscV|AddrV|-|-|SyndV|CECC|-|-|-]: 0x9c20400000020136 May 5 08:59:20 Eeyore kernel: [Hardware Error]: Error Addr: 0x00000001790531e0 May 5 08:59:20 Eeyore kernel: [Hardware Error]: IPID: 0x000200b000000000, Syndrome: 0x000171f21a4418f5 May 5 08:59:20 Eeyore kernel: [Hardware Error]: L2 Cache Ext. Error Code: 2, L2M Data Array ECC Error. May 5 08:59:20 Eeyore kernel: [Hardware Error]: cache level: L2, tx: DATA, mem-tx: DRD May 5 08:59:20 Eeyore kernel: mce: [Hardware Error]: Machine check events logged May 5 08:59:20 Eeyore kernel: [Hardware Error]: Corrected error, no action required. May 5 08:59:20 Eeyore kernel: [Hardware Error]: CPU:1 (17:71:0) MC14_STATUS[Over|CE|MiscV|AddrV|-|SyndV|CECC|-|-|-]: 0xdc2040000004010b May 5 08:59:20 Eeyore kernel: [Hardware Error]: Error Addr: 0x00000001790531e0 May 5 08:59:20 Eeyore kernel: [Hardware Error]: IPID: 0x000700b020f50300, Syndrome: 0x000171f21a47010a May 5 08:59:20 Eeyore kernel: [Hardware Error]: L3 Cache Ext. Error Code: 4, L3M Data ECC Error. May 5 08:59:20 Eeyore kernel: [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: GEN
  12. Yep, it still does it with the Ram at 2133. I did safemode with docker and vms disabled. it stays up for longer, but it still seems to reboot randomly. So yes, I am also of the opinion that it is hardware. I just wish I knew which component. MB, CPU, or PSU are the main suspects.
  13. Thank you, @JorgeB for moving the thread to the correct forum. Apologies to @Squid for posting in the wrong place. I was in somewhat of a panic when I created the original thread. So, to address the comments of @John_M - I let MemTest run overnight and there were no errors in the morning - also the system did not reboot at all. I am now mirroring syslog to flash. I will attach a new diags bundle. Also, I have removed the modprobe i915 now - this used to be on an intel system, and that is a remnant. @ChatNoir PSU seems to be okay, but that is one of the more difficult pieces of hardware to know for sure. Cooling also seems okay - the cpu and mb temps hover around 45, one occasionally hits 60 but only ever for a few seconds and it has always been so. These were my first thoughts too. I have seen some errors relating to L2 or L3 cache in the syslog. Could that be the issue? Is there a way to test the CPU for faults? I am at a loss here. The system stays up if I boot into safe mode and don't mount the array. Once I mount the array it just takes minutes until an unexcepted reboot. @JorgeB - as to the memory overcocking - you are right! I had the XMP turned on for my ram. I turned it off this AM and the current speed should be 2133. I deeply appreciate all the help you are all providing. Any ideas what my next steps should be? eeyore-diagnostics-20210505-1013.zip
  14. Oh, it even does it in safe mode. I am ready to throw the box out the window
  15. Oh, it even does it in safe mode. I am ready to throw the box out the window