vw-kombi

I guess we just hope a future release/kernel fixes this.

I don't have that plugin myself...... I can cause these issues by running an rsync to an unassigned mounted nfs disk to another unraid server. Any other time they dont happen. Not a memtest issue.

Mine is also an rsync to an nfs share - an unassigned mounted drive on another unraid server.

Brand new mobo, cpu and ram today. Memtest done for a few hours before booted into it. Same issues in old one also.

I have a user script that backs up to a backup unraid server and when that runs :

No lockup and/or reboots overnight. I think this issue can be put to bed now.

Even the parity build is over 200 MB/sec instead of in the 180MB's range. And the GPU conversions in tdarr are doing 650+ fps - before is was 20 ish on my one allocated cpu thread!!!!! There is a load I have been missing since 2019 I guess.

Oh - what a knob I am!!!!!!!

I have no idea how to do it any other way........

I cant see anything in there for this :

Hardware in. Seems quite a bit snappier. Enabled GPU transcoding in emby which is something I have not had before. Started up everything, nothing strange as yet - fingers crossed!!!!!!

I only just installed this for the first time, as now I have a CPU that can do this (quicksync), but nothing on my dashboard like the pictures here.

Dead again on wakeup too - hardware install today - fingers crossed.

Well, I know I can break it by pushing more and more tdarr conversion threads at it - which finally caused the lockup/crash..... Guess I was being greedy - So - new hardware will be installed tomorrow........

Well - it may be early days, but after the reboot without that realtek plugin. I had clean logs after a few hours, so in attempt to 'break' the system, I started a parity check. 6 hours later, still cleans logs, so I started up all my containers, and even the cpu killing tdarr with an extra CPU thread configured in tdarr to try and stress out the CPU's to breaking point. They have never seen this amount of activity before - and so far - clean logs, no lockups, no reboots : If I wake up to a healthy system, with a good parity check and no crashes/reboots, and a clean log, then I will be really pissed as there were no 'hardware issues' at all - with me having close to $500 of equipment sitting here that will be not needed. And all seemingly related to this realtek driver!