mort78

Initially I thought I had done something, after I cleaned my system for dust. So I took the CPU cooler off and reapplied some new thermal paste. All was great, and was running cool. But after about 6hrs of running, the CPU fan stopped and the system started getting rather hot under no load. I'm using a Intel® Xeon® CPU E3-1268L v5 @ 2.40GHz in the system.

Is this still an issue on the current stable version of Unraid?? The reason I ask is.... I have the following MB - Supermicro X11SSH-CTF. The CPU fan also stops after a random time. I have gone into the Supermicro BIOS, but there are no fan controls in there!

Good Morning Ich, Yes, I was able to solve the problem. I had another look at it yesterday, as I've been away from home with work. I feel like a prize idiot.... So the issue was staring me straight in the face. In the DOCKER container, instead of having the NVIDIA_DRIVER_CAPABILITIES in the KEY field, I had mine in the NAME field. I simply must have forgotten to copy it into the key field as well. All of the other parameters were in the correct place already. Kind regards, Mort

Hi Dom, I had that in already. I got mine working. I'll post below what I did wrong. I feel like such a muppet. 🤦‍♂️

Thx Ich, I'll have a look now. Thank you!

Unfortunately, it doesn't appear to have solved it for me. It's still using 100% of the CPU. FYI, I have been using Tdarr and I've had zero issues with Unraid using my GPU. It's simply Plex that I can't get to work.

It isn't.... I will try do this tonight. Thanks mate. I'll post what I find

I wish that was the issue. I've checked that several times, and there are no spaces anywhere

Hi all, Firstly, I just want to say sorry in advance, for yet another Plex Transcoding discussion. I know there have been a bunch in the past, which I've read through, but I still can't get mine working, using the GPU. It's constantly maxing out the CPU. I have attached a bunch of screen captures to show you my setup. If anyone has any clue as to what is going on, it would be greatly appreciated. Thank you very much, Mort

Thanks gents... I got it back! Appreciate all the help.

Thanks JorgeB. Just to make sure I don't do anything else incorrectly, I have copied over the libvirt file from the old cache disk to the /domains folder. I have removed the libvirt file from the /mnt/cache/system/libvirt folder. I think that was what you meant, correct??? Also, I haven't started the VM Service yet. Your comment above suggests that you just want the diagnostic file after I have the libvirt file in the domains folder? I have also included a screen shot of my settings in the VM Manager. Can you confirm these are correct? Thank you so much for your assistance.... it's really greatly appreciated. I honestly don't find a lot of the inner workings of UnRaid very intuitive. Cheers, Mort unraid-diagnostics-20221201-0930.zip

Hey JorgeB.... I do. I plugged it in, and I can mount it. I copied it over to the /mnt/cache/system/libvirt/ & the /domains folder, but the VM manager isn't liking it! It's not running! Any ideas? Thanks, Mort

Hi all, As the subject matter mentions, I'm unable to get VM's to work anymore. I upgraded my cache disk. I followed the steps with regards to shutting down the dockers. But I completely forgot shutdown the VM services. There were NO VMS's running at the time I used the mover etc. I then installed the new cache drive and did the reverse of the previous steps... Initially I had problems getting the Dockers working, but I was able to recover those. But the VM's are still causing me issues. So I wanted to know if there's a way to get the previous VM's back, or did I screw it all up by not turning off VM manager? I have linked my diagnostics, and a file search for the libvirt file. Many thanks for the help! Mort unraid-diagnostics-20221130-1637.zip

Hi Trurl, I wasn't aware of that! Hadn't noticed it before. Just as well I'm not an investigator Regards, Mort

Hi JorgeB, Many thanks for the reply. Much appreciated. Hmmmm.... I did clean this entire computer out, about 3 weeks ago, using a portable air blower to get rid of all the dust collected inside the case. Perhaps it got slightly dislodged during the cleaning. Weird it only pops up with the error every week or so, and not more frequent. I'll open the case up tomorrow and give everything the once over. I'll report back what I find. Many thanks, Mort

btw, I just noticed that there is no temperature readouts since the error messages have popped up!!! Also, I noticed the parity drive didn't change to the orange triangle. I did a simple shutdown and restarted the array up again and it was back to normal! No idea why the errors are being posted in the first place!

Good evening.... As I expected, it happened again. Haven't touched the array since doing the parity check the other day.... ie: haven't installed or messed with it. I just logged in and was greeted with the errors I have attached the diagnostics of the current situation. As always, I really appreciate your time, in helping out. Kind regards, Mort unraid-diagnostics-20220124-1909.zip

Hi Trurl, The reason I had Appdata etc all over, was simply because I tried to move it to cache only, but wasn't able to get it moved. That is until today..... I thought I'd have another crack at it, and I came across a post you replied to. I realized that I too was doing it slightly wrong. I had tried using the "cache only" option, but as you mentioned, then the mover can't touch it. I also hadn't turned the Dockers/VM's off in the settings, then hit the move function. I however followed your instructions on that thread, whereby I turned those 3 shares (appdata/domains/system) to 'prefer cache'. Then turned off the docker and vm function. Then hit the move function. It worked like a treat. So now all those files are on the cache disk. I initiated the common trouble shoot app, and it came back with no issues. Thanks for the tip. So far my server hasn't showed any read errors since the parity check yesterday, so we'll see how it goes. Many thanks again, Mort

OK... so the Parity check finished. As expected, it came out error free. I have attached a fresh diagnostic for your perusal. Many thanks, Mort unraid-diagnostics-20220120-1453.zip

Yes, it has 3 hrs to go and so far all is fine. 0 errors on ANY drive. This is what happened the last 2 times also. It would complete with 0 errors and run fine for several days.... but then out of the blue, it would get errors. I'll attach the final diagnostics for your perusal, once it's finished. If the errors pop up again, I'll take a diagnostic in the "error state", and link that too. Again, many thanks for your time! Much appreciated.

Good morning Trurl, Thanks for the reply. The rebuild is still ongoing, but I thought I'd get the diagnostics now. If I need to wait until the Parity is resynced, I'll throw another one up in about 6 hours when it's complete. Many thanks for your time. Kind regards, Mort unraid-diagnostics-20220120-0746.zip

Good evening everyone, I was hoping someone might know what's the situation with my server. So I was cleaning up my study, and I wanted to clean underneath my server. My server was running at the time, when I lifted the bottom of the computer up, so that I could get the dust etc. Later that evening, I logged into my server, and I noticed that Unraid was warning me of read errors, and that the parity disk had been disconnected from the array. This was surprising to me, as it is basically a new drive (3 months old). It's an Exos 8TB drive. As I didn't believe the drive was an issue, I went through the process to get that drive working again... so I : 1. Deselected that drive as the Parity 2. Restarted the array 3. Stopped the array 4. Selected the same parity drive again 5. Let the Unraid server do a self check on that Parity. After about 20hrs, the Parity check was done, and 0 errors were found. The server continued to run flawlessly, as always, for about another week, when I suddenly got the exact same thing happen again. I went through the above mentioned steps, and again, 0 errors found. That was about 4 days ago. But it happened again tonight. So I'm just wondering what I can do to fix this situation. Did I "hurt" the drive by tilting/moving the server whilst it was running, when I was cleaning underneath the computer? Any thoughts would be greatly appreciated. Kind regards, Mort

Hi Charlie, Welcome to Unraid. Don't stress, there are some extremely clever people on here, that'll know exactly what the problem is. Just looking at a glance though, I notice you have A LOT of errors on those disks. I recently had a disk that had some bad sectors on it. As soon as I saw it, I bought a new drive to replace it. Whilst I was waiting for the new drive to arrive, more bad sectors started appearing. It got to a point where unraid literally unmounted the disk, as it clearly wasn't in great shape anymore. Perhaps this is the issue??? Did you get those drives with the system? Sorry I can't be more help to you, but again, someone on here will sort your issue for you I'm sure. All the best, Mort

Hi Johnathan, You're 100% correct in saying that the 3TB drive is in fact the extra drive I decided to throw in. I completely agree with what Frank and yourself have mentioned. I will remove that drive now. As you say, I don't really need the space just yet anyway. No point having further wear and tear on it. Thank you both very much for all your help. Couldn't have done it without you. You guys rock!!! Thanks, Morten

OK... All good and I believe I know which is the parity drive. But I'll include the picture here, just to confirm. SDE is the PARITY drive correct? Thanks, Morten