53 minutes ago, Cessquill said:

Did you restart your server after making changes to the disk?

 

The issue this thread covers is where disks are disabled on spinup.  If you're saying yours don't spin down, something else is going on.  Cables OK?  Big enough power supply?  Hopefully somebody can point you in the right direction.

Cables are SAS to Backplane, the server has been restarted several times since then.

 

My PSU is 500W (if i remember correctly) with no graphics card:

- i9 9900k

- HBA Card

- 10gbit Dual SFP+ Card

- 9 Disks for the time being.

 

It "should" be fine in terms of Power.

 

Issues started after I put the HBA card in my server, and it is only that one Disk which gets disabled. The disk Smart readings are totally fine. I will put that disk in the 3.5" cage today and directly connect it with a SATA cable and will observe.

 

I will set up an automatic parity check after that and look if it happens again. Because it ONLY happens when starting the parity check. Maybe a crossover issue with the Mover, which starts at the same time like the parity check. Parity check will get paused as long as the mover runs and resume after that. After resuming the parity check i have read errors on my system logs.

 

I will open a support ticket for that. When it happens again after my modifications.

Edited August 1, 20241 yr by MrSliff

I'm on 6.12.13

I have 8 of these drives and just had this issue

Is this still an issue even on newer versions?

Should I disable spindown altogether?

9 hours ago, loyalsnoopdoge said:

Is this still an issue even on newer versions?

 

As far as I'm aware, yes.  I follow the steps in this thread for each new Ironwolf (although I haven't changed drives for a while)

 

Quote

Should I disable spindown altogether?

 

I wouldn't, no.  One of the key selling points to me is the ability to spin down drives when there's no activity.  Just follow the steps in the first post - you could do all eight at once if you prep your commands in a text editor beforehand.

Hello, I'm pretty new to Unraid, tried it for a day and liked it so much i bought it. I think my issue is similar to what this post proposes to fix (not certain though) but I have 3 x Seagate EXOS X16 which i have in a usb 3.1 Enclosure (this enclosure to be exact: (https://www.orico.cc/usmobile/product/detail/id/8541) connected to a SFF pc.

 

The problem I'm having is sometimes randomly the HDD either goes to sleep or its dropped somehow that causes the array to stop (The enclosure description on the website does say that it can go to sleep if its not being used!). the particular drive will then have a cross next to it (Device is Disabled, Contents Emulated). Yesterday I setup spin down delay on disk settings and everytime the drives spins down the array stops and i get the Device is Disabled msg again. I have noticed when i restart the enclosure and the drive reconnects, sometimes one of the drives will change their serial no from the usual number to something like (ST12000N_M001G-2MV103_000000123AE8-0:0 (sdd)) and become unassigned other times the serial is correct. so regardless of whether the drives spins down or i restart the unraid server entirely i get one of the drives as Device is Disabled, Contents Emulated msg. So far I feel like its only happening to this one specific drive in my array. 

Would this fix potentially fix my problems? I know its specifically for Ironwolf HDDs but has anyone with EXOS version tried this or had this problem?

Your problems are entirely due to USB.

 

These symptoms and other problems are why USB is not recommended for assigned disks. 

Yeah most likely but I have seen people with great success as well, would you recommend upgrading to version 7 to help with some usb related problems?

Hello. First of all thank you for the guide. It seemed to fix my problem for now. But for some reason one one of my drives (8 TB Ironwolf) does not keep the settings after a full reboot/powering down. Is there anything I can do to fix that? Any help would be very much appreciated as I'm new to unraid.

Edited February 17, 20251 yr by c0rr3h

Great ideas here's. For those of you who struggling after applying the previous settings, there's one more setting on the drives that resolved the matter for me.

Since the drives never even appeared I attached them via USB and issued the setting changes thru the usb interface then re-slotted them into the SAS backplane.

this was on LSI SAS3008 PCI-Express Fusion-MPT SAS-3 and 8TB Ironwolf

Using Seachest set the following

./SeaChest_PowerControl_XXXX -d /dev/sgYY --EPCfeature disable

./SeaChest_Configure_XXXX -d /dev/sgYY --lowCurrentSpinup disable

./SeaChest_PowerControl_XXXX -d /dev/sgYY --puisFeature disable  #disabled power up in standby. 

Edited March 7Mar 7 by Lonewolfnight