[Tdarr and nvidia encoding not working on my GPU]

On 4/1/2022 at 1:17 AM, dewey962 said:

Ok I'll preface with I'm a novice with these things but I found that if you go to your libraries tab and then scroll down to transcode options uncheck "Tdarr_Plugin_MC93_Migz1FFMPEG_CPU
Migz-Transcode Using CPU & FFMPEG"

 

then check "Tdarr_Plugin_MC93_Migz1FFMPEG
Migz-Transcode Using Nvidia GPU & FFMPEG"

 

boom it started to use my Nvidia T600

This fixed it for me thx ❤️

[Got new motherboard, then got issues]

Ok, thanks for really super fast support ❤️

[Got new motherboard, then got issues]

Ok, now it is started. And now, for the first time, everything mounted fine. And fast. Maybe it was enough, just to contact the experts (c:

 

I have attached the new diagnostic here.

 

unraid-diagnostics-20210521-1640.zip

[Got new motherboard, then got issues]

It is restarted, yes. Not started. If i try to start it, it do try to mount the disks but after a while it fails and tells me the first disk is unmountable, then the next and so it goes on and really slow. Do You want me to let it go through all the disks and post a new diagnosics afterwards?

 

 

[Got new motherboard, then got issues]

Hi friends,

 

I have trouble when mounting the disks after i exchanged the motherboard. Can anybody help me fix this? I have attached the diagnostics-file.

unraid-diagnostics-20210521-1605.zip

[Abnormal amount of writes to one of the disks]

15 minutes ago, johnnie.black said:

That usually happens when a disk drops offline or there was another controller related issue, you should post the diags.

Ok, that's why, now i don't have to worry about it. I was mocking about changing a fan and accidentally knocked out one of the sata cables. Super thanks for the fast answer 😊

[Abnormal amount of writes to one of the disks]

One of my disks indicates a huge mount of writes, how can this be? Arrays health seems ok.

 

[Unable to start Win10 VM after reboot]

On 6/15/2019 at 8:21 AM, kzisme said:

 

 

 

 

 

Hello,

 

After my last server reboot I am now unable to start my Windows 10 VM that was previously working.  

 

The current error when I attempt to start the VM is: 

Cannot access storage file '/mnt/user/domains/001 Windows 10/vdisk1.img': No such file or directory

I don't think permissions have changed on a reboot, and vdisk1.img does exist at that path.

 

Any ideas on what might be going on?  

 

I have attached my system diagnostics.

tower-diagnostics-20190615-0110.zipUnavailable

The same thing happened to me today. Did You find a solution?