ec911

Members
  • Posts

    6
  • Joined

  • Last visited

ec911's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Ok what I did tonight is just click the mount button next to the drive in unassigned devices (I am still a noob) and I've changed the access mode of the /media/frigate folder in the docker configuration to read/write slave and everything booted up correctly! Finger crossed and I'll see if everything is still ok tomorrow
  2. Hi, I'm having problems with the Frigate Docker container. I've tried to troubleshoot as much as I can but I can't fix it. Everytime I start a fresh install it seems to work fine (detection with Coral and recording) but after a couple hours I get this storage error in the log : Errno 28 - No space left om device. I am passing a freshly formated 2 TB hard drive that is clearly not full. I also tried tweaking the tmpfs size from 1gb to 3gb for the /tmp/cache folder and it isn't working. I don't know what to do next
  3. Display port yes I did try CRU and cannot force the refresh rate at 3840 x 2160 to 60hz. If I drop the resolution to 2560 x 1440 I can change it to 60hz no problem. I don't have another monitor I can try. If I run Windows on bare metal (windows is installed on a dedicated nvme drive), refresh rates are ok @ 4k.. I really don't understand, I even tried on unraid 6.10.3 and I got the same problem. Guess I will have to downgrade to 6.9 again..
  4. Hello, I just updated unraid from 6.9.2 to 6.11.0-rc5. When I restarted my Win10 VM, I noticed that my two 4k monitors are capped at 30hz instead of 60hz now. Cannot raise it any higher in the display settings. I tried reinstalling my geforce drivers and I also created a new VM with the same settings and passthroughs (passing a geforce gtx970 and nvme drive with win10 installed on it) and it's not working. I downgraded back to 6.9.2 and the monitors are behaving correctly. I'm not sure what to try next before attempting to reinstall windows. Does anyone had an issue with this? Thanks tower-diagnostics-20220915-1637.zip
  5. The only change I've made along with the changes you've mentionned was to turn on XMP profile 1 to clock the ram to 3200 mhz. I put it back to 2400 mhz after but the error happened again. I didn't overclock the cpu. I'm running a Corsair RM850w. Couple months of use. I was using it on my other system without any issue. I will try to replace the ram if the error comes back with the default clock settings in bios. Here's the log that I was getting: Jan 26 15:34:10 Tower kernel: mce: [Hardware Error]: Machine check events logged Jan 26 15:34:10 Tower kernel: #13 Jan 26 15:34:10 Tower kernel: x86/cpu: Activated the Intel User Mode Instruction Prevention (UMIP) CPU feature Jan 26 15:34:10 Tower kernel: mce: [Hardware Error]: CPU 12: Machine Check: 0 Bank 0: baa0000000010145 Jan 26 15:34:10 Tower kernel: #14 Jan 26 15:34:10 Tower kernel: x86/cpu: Activated the Intel User Mode Instruction Prevention (UMIP) CPU feature Jan 26 15:34:10 Tower kernel: mce: [Hardware Error]: TSC 0 MISC d012000100000000 SYND 4d00002e IPID b000000000 Jan 26 15:34:10 Tower kernel: #15 Jan 26 15:34:10 Tower kernel: x86/cpu: Activated the Intel User Mode Instruction Prevention (UMIP) CPU feature Jan 26 15:34:10 Tower kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1580070829 SOCKET 0 APIC 1 microcode 8701013 I also noticed this but I don't know what it is Jan 26 15:34:10 Tower kernel: tsc: Fast TSC calibration failed
  6. Hi! I am new in this community and this is my first post. I've been running unraid on trial on my old i7-4970k system without any issues. I then recently upgraded my system (and bought a Plus license) for a Ryzen 3900x running on a Gigabyte Aorus Elite x570 with 32gb of ram (Kingston Fury 3200mhz) Everything seemed to be ok, I refered to a post on this forum for tips and tricks on this particular motherboard to passthrough gpu for vms. 2 days ago, I woke up and server was frozen. Rebooted everything and I started to get Machine check events from Fix Common Problems plugin. Everything seems to be running fine, but the error keeps coming back. Unless I miss something, can anyone help me out with the error? Is this common on newer Ryzen CPU running on unRaid? I'm running version 6.8.1. tower-diagnostics-20200126-1555.zip