gekoch

yep I had already figured it out currently only the drivers 550.40.07 do work Andy

Great, thx 550.40.07 is working well Andy

When I check the website for the same card I see this driver version: After installing 550.54.14 on unraid 6.12.8 transcoding with emby is not working anymore. switching back to 535.154.05 is solving the problem but why? Andy

Hy It took me several days to figure this one out but I'm still not sure what causes the problem. My Setup: I have an nvidia T1000 in my unraid server used to transcode movies especialy when using emby. When I start an mkv file with emby it starts transcoding with ffmpeg. On Unraid 6.12.6 this works flawless. However after updating to 6.12.8 emby can't transcode it using ffmpeg. Attached two log files. Both with the same movie one with the old and one with the new unraid version. In the log file running the new unraid version you can see the error: 17:25:44.862 [h264_nvenc @ 0x114dd40] Failed locking bitstream buffer: invalid param (8): ~hfE? 17:25:44.862 Error submitting video frame to the encoder 17:25:44.872 [libmp3lame @ 0x10c74c0] 3 frames left in the queue on closing 17:25:45.121 Conversion failed! I'm not sure what exactly causes the problem so I hope someone can help me.... Thx Andy new OS 6.12.8.txt old OS 6.12.6.txt

after 48h of uptime no crash! Thx a lot for the help, seems resolved with the ipvlan setting.

ok thx for the explanation. In an earlier post I did add the syslog file directly from the log file folder. So the system is currently running on 6.12.2 for the past 2 hours, fingers crossed

ok thx did switch it to ipvlan, now udpate again to 6.12.2 and test it if the server is stable?

here is the file the crash should be around 01:30 in the morning of the 27.06.2023 syslog

so this is not the file in the diagnostic file?

i thought it should be in the log folder? i set it up like this

same here, can't reboot it via SSH and that's really bad, hope someone can look at the logs and figure out what the problems might be...

so here we go. After around 10h again a crash with 6.12.2. Now with syslog server activated nas-diagnostics-20230627-0518.zip

As soon as the first new release (6.12) was out I updated to the latest version from 6.11.5 . But just after 2 hours of runtime the server crashed without any reasons so I had to reboot with the reset button on the server itself and tried again. After 5 hours another crash. So I reverted back to 6.11.5. Again with 6.11.5 I had no problems at all for several days. Then 6.12.1 was released and I thought they might have solved an issue that I had with my setup. So I just did the update and after 2 hours again a crash.... So 6.12.1 is again not stable on my machine but I have no Idea why. The 6.11.5 version was stable for several months without any issue. Here is the diagnostic files I took before reverting back to 6.11.5. Any Ideas? Thx Andy nas-diagnostics-20230625-1934.zip

hy Just had something weird happen and I hope someone can explain this to me. My UNRAID system just rebooted without notice. After the reboot my 2 cache protected SSD were not recognized as the correct SSD. The old SSD that I exchanged a few weeks a go were displayed instead. I tried to start the array but the cache protected device was marked as disabled. So I stopped the array set the devices to "not installed", started the array, stopped it again and chosen the newer larger SSD and started the array again. Now everything is back working as nothing would have happend. But can someone explain to me what exactly happed. Attached to log files: nas-diagnostics-20230510-2149.zip

I have the same problem. i had to revert back to 4.5.2-1-01 which solved it for me