Tarcisio

Hello guys! My server's been crashing for 4 or 5 days now. I still didn't figure what could be! To make this post short. I run unRAID 6.11.5 for a long time and it was rock solid most of the time. I recently updated to 6.12.6, crashes started about this time. The thing is, I've installed 6.11.5 again and the system is still crashing. What I've done so far: - Changed flashdrive to a new one - Changed the usb port (from 3.0 to 2.0) - Installed unRAID from scratch and didn't install any plugings or anything else, left everything pretty much in default (Disabled VM and Docker service) and just let my array run. I try a parity Sync and after few minutes the system crashes. Some crashes I need to manually power the machine off and back on. Lately I get no UI response from the GUI and after few minutes I get the login page again. The server reboots byifself. It seems to be a full reboot. - I also ran a memtest86+ for 20 hours and found 0 errors - I physically unplugged and PCI USB card (just in case) - Didn't passthrough anything (didn't bind anything to VFIO). I basically installed unRAID 6.11.5, set the syslog client to send the logs to another device, disabled VM and Dockers services and then Started my array. I let the parity-sync run and after few min ~20 or so , the system rebooted by itself. Crash happened at Jan 27 14:24 `Jan 27 14:25:41 Tower webGUI: Successful login user root from 192.168.1.207` That's the first line after the crash I attached the diagnostics and syslog. Any help would be really appreciated, I really don't know what to do anymore to find the culprit of the crashes. Thank you!! tower-diagnostics-20240127-1647.zip Tower-6.11.5.log

The hours are not "incorrect", it was just a decision to use UTC, from now on. They were having problems with Daylight Saving Time, I believe. The UI will still be showing your configured time zone.

Read my post. In short, it can't be changed. It's gonna be like that from now on.

Not saying it's an issue or bug, just wondering is anybody knows how to change that. It seems the timestamp from the folders doesn't consider the time zone (UTC) thus + 5 hours for me. On previous versions this didn't happen. Gonna open a discussion there . Thank you. EDIT: Just for reference From Frigate 0.12 the folders are created in UTC by design and can't be changed. It's listed in the GitHub release notes. https://github.com/blakeblackshear/frigate/discussions/6165 https://github.com/blakeblackshear/frigate/releases/tag/v0.12.0

Did anybody find a solution for that?

Host seems to have the right config. Also -e TZ="America/Chicago" and -v '/etc/localtime':'/etc/localtime':'rw' are already included by default in the template.

Hello guys! I noticed that my recordings folder timestamp is wrong. it's 2023-04-18 > 11pm now. I'm in Central Daylight Time (GMT-5) Frigate 0.12.0 How can I fix that? Thank you!

Were you guys able to solve the problem? Performance of my Gaming VM is really bad. Stuttering/Lagging and low fps (half compared to bare metal).

Did you find out the solution? Having the same problems! VM lagging/stuttering and low fps on games! Don't know what else to do.

does it provide a rtsp for each camera? What's the purpose of it if you're already have the rtsp of the cameras? What's the link for the rtsp? Thank you!

Couldn't find the answer. What is FRIGATE_RTSP_PASSWORD used for on the template? Thank you!

Waiting on that too. I would like to passthrough my tpm. Probably the emulated tpm will be used for most of us, then we could use more then one VM with Windows 11 at the same time. Both options would be nice to have natively on Unraid.

Second day messing with this. After move my server to another room, started to get Nvidia error 43 on Windows 10. Tried disabling Hyper-v option inside VM options (nothing), tried creating another VM (nothing), changed monitors and cables (nothing) ... Then I dumped the Vbios again through Spaceinveder script https://github.com/SpaceinvaderOne/Dump_GPU_vBIOS and everything seems to be working fine again now.