cds8410

I didn't have a spare sata power cable extender, so for now I just had to reuse the one I had. But I did move it to another Sata power cable directly from the PSU, rather than daisy chaining them this time. Not ideal, but making due. The old drive is showing its still disabled, so I'm going to put another drive in the array and I'll rebuild the disk. I guess I'll just see if this holds out. If not, I'll try a few other combinations and see what it yields.

Unless you are referring to the power connection to the entire computer. In which case, its also connected to a power strip. I'll move it to another wall just in case.

I have my drives powered by some daisy chained sata power cables. Interestingly, the drives further down the chain appear to be totally fine. But let me see how I have this configured and see if I can do away with the daisy chaining for testing.

Version 7.1.4 Plugins: -Unassigned Devices -Community Applications -Tailscale -Unassigned Devices Plus -Unraid Connect Motherboard: Micro-Star International Co., Ltd B450 GAMING PLUS MAX (MS-7B86) , Version 3.0 American Megatrends International, LLC., Version H.H0 BIOS dated: Thu 27 Apr 2023 12:00 AM SAS Controller: Dell 47MCV PERC H200 I've been tailing an issue off and on for the past few months. I'm running an array of about 8 4TB spinner disks (mixed brands between Seagate and WD) running in a RAID 6. If I remember right (this is an old issue, only just now posting), this started ever since I had some connection issues with my server that made it inaccessible (remedied by the use of replacing my old SATA card with a reflashed SAS controller). Specifically, Drive 1 of my array regularly disables itself. I would swap the drive out with another one, and after rebuild, it would hold for a while. Eventually, the problem would come back and the drive would be disabled ("Device Disabled, Contents Emulated"). Spinning it up doesn't do anything. In the past, I would get some file corruption that would get removed after putting the array in maintenance mode and running a cleanup. However, this time I can put the array in maintenance, scan the offending disk, and it won't pickup anything. I also just tried to use a different SATA cable just in case that was the culprit. That didn't change anything though, and it also showed that it wasn't the SAS card either, as this cable connected directly to my motherboard. So different drives have no lasting effect, different SATA cables don't, different drive ports on the computer, and it always has issues with disk 1 of the array. Let me know if there's anything else to check. It has been a while of me troubleshooting this off and on, so I might have forgotten to say something. Thanks! ham-vanderhuge-diagnostics-20251124-2019.zip

That looks to have been the culprit. Didn't even think of an issue at that level. Thanks again!

Hello! For context, I only started using Unraid today, so I'm about as green as it gets. I've been chasing an issue specifically with a set of SSDs that I'm trying to create a pool with for caching. However, I've been wrestling with them all day, as they refuse to mount with the error Unmountable: No pool uuid. I've tried formatting them about a dozen times now, rebooting, unmounting and remounting them, swapping disk order, and it all yields about the same results. I'll attach syslog and smart info related to this. If any other information is needed, just let me know. Thanks! smart-20230128-1918.zip smart-20230128-1917.zip syslog-20230129-0356.zip smart-20230128-1919.zip