I have found a couple of similar posts but none with a resounding "cause" of this issue. I have enabled spin down for the drives in my array a couple of days ago to try and reduced power usage and heat, but I checked it today and disk 2 is disabled. After reading another post where a reboot can solve, I have tried that but it's still disabled. I realize I should have done diagnostics before restarting, but I'm attaching in case it's of any use. I'm certain the supermicro PSU breakout board, backplane, HBA adapter or cables aren't the issue because it has been running fine for years and before this recent restart it was up for 30 days straight.

If the drives never spin down, it's not an issue, but if spinning down is allowed, eventually there is a disabled drive. Why might this be and what can I do to check?

Full disclosure, I tried this in the past a couple of years ago and had the same result, so I stopped allowing spin down. I'd ideally like drives to be able to spin down due to concerns about regularly high temps.

Thank you

citadel-diagnostics-20240728-1138.zip

Looks like this issue:

 

Thank you for redirecting me. I have followed the steps (but I had to use openSeaChest as using the latest official tool would require different instructions/steps to follow) and it looks all the drives have kept those settings as disabled after the restart. I've changed the default spin-down delay back to 30min and here's hoping that fixed it! I'll come back and mark as solution if there's no issues by the end of the week.

Thanks again

EDIT: Appears to be running fine, spin ups have been few but so far no errors. I'm cautious to call it a success but with all the drives spun down the "idle" power usage has dropped 60-100W which is a pretty significant reduction for a device that's on 24/7.

Edited August 1, 20241 yr by Kurtains
Follow up at the end of the week