padioca

I'm going to drop this here in case anyone needs it. I have an i5-11400 with an ASUS PRIME H570-PLUS motherboard. I couldn't figure out how to get both a discrete card and the iGPU working. I wasn’t able to boot from the USB without turning on some compatibility mode (called CSM), and if I turn on CSM I lose the option to use both the iGPU and the discrete GPU. To fix, I had to go into /boot and change the "EFI-/" directory name to "EFI". This would then allow for UEFI booting, which then allowed me to set it to use iGPU multi monitor, which allowed for both the iGPU and discrete card to be used concurrently.

I'm going to drop this here in case anyone needs it. I have an i5-11400 with an ASUS PRIME H570-PLUS motherboard. I couldn't figure out how to get both a discrete card and the iGPU working. I wasn’t able to boot from the USB without turning on some compatibility mode (called CSM), and if I turn on CSM I lose the option to use both the iGPU and the discrete GPU. To fix, I had to go into /boot and change the "EFI-/" directory name to "EFI". This would then allow for UEFI booting, which then allowed me to set it to use iGPU multi monitor, which allowed for both the iGPU and discrete card to be used concurrently.

I there, me again. I changed out the hardware and rebuilt parity on the drive that been giving me problems, and it appeared to work properly. Went to change out an older drive with a new one that I purchased and as it was being rebuilt from parity the errors came back on the parity, and the rebuild failed. I then took the new drive I was trying to install and put that in as a new parity drive. It rebuilt and seems to have worked, but I don't have another drive so I can't test a rebuild process at this point. So, long story short, I'm back up and running with a new parity drive, but the old drive still returns an extended SMART test with no errors. At this point I'm thinking it might be an issue with a bad SATA cable, so I'm going to track that down and replace it tonight. But wanted to check back and see if there are any other thoughts on what could be going on. Also attaching a new diagnostics report. Thanks! tower-diagnostics-20220321-0942.zip

I have most of that stuff on a second cache pool drive, but I will double check to make sure it is moved over before replacing the hardware. Although I just started the array again and the cache is showing as unmountable, so it may be toast. The server is super old, so I decided to work with stuff that has been produced in the last decade, hence the rebuild. Hopefully this will help clear up some of the issues I'm experiencing with the drives, and who knows, maybe the cache will decide to come back around. I'll holler back here if I continue to experience issues, thanks again for your help!

Ok, I can look into that. Can you clarify on what I should do differently or point me to some documentation? I don't use the VMs at all, but use Docker for the Arrs and Plex. Seemed to be working well enough until issues with the excessive logging a few weeks ago, and now these issues. Also, just to be clear, it seems like you are indicating that you wouldn't suggest any further action before replacing the hardware. Is that correct? Also, thanks again for your help. I'm reasonably good at figuring stuff out, but I'm thankful for people like you that are willing to jump in when I run into a dead end.

Sorry, should have clarified. Yes, I did, both when I was having issues with the cache drive a few days ago as well as yesterday when issues with the parity drive started to happen.

I just tried to run a SMART short self-test and it immediately stopped, giving me a message reading, "A mandatory SMART command failed:exiting. To continue, add one or more '-T permissive' options.". I have purchased a new motherboard, RAM, CPU, and NVMe drive (intended to replace that cache drive), so if the parity drive looks fine I might just start the process of replacing those parts to see if it helps the issues. If that seems like a bad idea, please let me know.

Here's the latest and greatest... tower-diagnostics-20220317-0843.zip

I thought I did, but I may have done it incorrectly. That being said, I just checked and the extended SMART from overnight finished without error.

Tried running the extended SMART and it got over to 80%. Checked back, thinking it would be done, and it had a message reading "Interrupted (host reset)" and no results from the test. I'm attaching the most recent diagnostics, but it appears as though the SMART reports have stayed the same. I've stopped the array completely and will rerun the extended SMART to see if I can have some results by the morning. Thanks for all your help! tower-diagnostics-20220316-2152.zip

Got it, running the extended SMART now. Can you let me know how you are seeing the connection issue on the cache drive? I looked through the diagnostic files the other day but wasn't sure what I should be looking for or where I should be looking.

Hey there. Been running Unraid for quite a while with far more ups than downs. However, I've run into some bumps in the past week or so. First it started out with problems with a Docker container writing continually to the log, which then filled up my docker.img. I deleted and rebuilt the docker.img, so seems like that is taken care. However, when I restarted the server I began to run into issues with a stale configuration. I've had this problem in the past, but have typically been able to fix it by rebooting until the array starts. I used the same method here (not great, I realize) and finally got the array back online. However, once I got the array started I realized my cache drive was not online any longer. I then shut down the server, rechecked all the cables, restarted the server and the cache drive was back. What I'm running to now is my parity drive went offline last night with an error reading "Parity disk in error state (disk dsbl)". I have shut the server down, rechecked all the cables again, and then brought it back up. Stopped the array, took the parity drive out of the array, started it again, shut it down again, and then put the parity drive back in the array. At this point the parity rebuild process starts but almost immediately fails with errors. I've run SMART on the drive and it comes back fine, but things are clearly not working. I've attached the diagnostics, happy to provide any other information that could be helpful. tower-diagnostics-20220316-1424.zip