Good morning,

 

I  just noticed I have a drive that has the red "X" with the above message in the Array Devices list.  I have attached the current diagnostics.

 

How I got here (some info might not be needed, but I figured I'd include all):

- Current array drives all have passed short, long, and preclear tests

- Data has been copied to drives

- Server was shut down

- I added drives to the case that were going to be precleared and added to the array (WD60EFRX drives, s/n's ending in 0F7Z, 3H5P, & V8ZY)

- Above drive with s/n 3H5P failed post read, other two passed fine; will be removing that one from case

- Stopped array to add the two passing drives to the array

- Noticed the red "X" on ST8000VN0022 with s/n ending in C4YD (SDL)

- Ran short test; passed

- Started array in maint mode

- Ran XFS check (without modify flag) and everything appears ok

- Started Read Check

- Pulled current diagnostics

 

I'd like to try to figure out why the drive went disabled.  I've searched here and on Google and reviewed a bunch of results here and on Reddit.  Seems like a rebuild in place is the final fix, but not sure why this dropped or if I can trust this drive.

 

I will be checking cabling shortly, but is there anything else I need to do?

 

Sorry for the need for so much handholding during these past few weeks, but I'm new to UnRAID.

 

Thanks in advance!

 

nasbox-u1-diagnostics-20250114-0836.zip

The disk dropped offline, just before the array stopped, possibly when the disk was spinning up, I'm seeing other errors related to spin up, for that and the other dissk, and some Seagate disks have issues with spin up on LSI controllers, so it may be worth retesting with that disabled.

What setting would that be?

 

Under Settings...Disk Settings, I have Auto-Start disabled, Default Spindown Delay 30 mins, and Spinup Groups disabled.

 

Sorry, I can be a bit dense.  Pretend I'm a 6 year old! LOL!  (And I appreciate your efforts to help me out!)

Also, is this the LSI/Seagate issue you mentioned?

 

51 minutes ago, SickPup404 said:

Also, is this the LSI/Seagate issue you mentioned?

Yes.

 

1 hour ago, SickPup404 said:

Default Spindown Delay 30 mins

Set this to never.

OK, a couple more questions before I attempt changing these settings later today...  I've been reading several threads on these both here and on r/unRAID & r/DataHoarder and maybe I'm getting them mixed up...

 

- Seems like varying opinions on applying the "disable" changes to three features: EPCfeature, lowCurrentSpinup, & powerBalanceFeature

- Also seems like some think it's just IronWolf drives (8TB/10TB?), while others mention Exos drives as well

 

Should I be applying only EPC & LowCurrentSpinup, or all three?

Since I have both IronWolf and Exos drives, should I be applying the changes to both?

 

Thanks!

I don't really have experience with those settings, recommend asking in that thread.

OK, wanted to save mucking about in the Seagate HD settings to use only as a last resort.

 

Steps I've done:

- Reset the spindown delay to Never

- Stop the array

- Unassign the disk

- Started the array in maint mode again to have the drive drop

- Stopped it again

- Reassigned the drive

- Started the array in main mode once more

- Started a resync

 

Estimate is a little over 12 hours, so I'll see how it goes and post back tomorrow with diags again for your review for power issues.

 

Thanks!!

Good morning,

 

Data rebuild finished this morning.  The drive with s/n C4YD returned to normal operation.

 

I stopped the array from maint mode, added in the two good WD Reds (leaving out the one that failed preclear), started the array, and formatted the two new drives.

 

New diagnostics attached.

 

Two questions:

- Do you see anything jumping out in the diags that are red flags for you?

- I only noticed the drive dropped from the array yesterday when I stopped it to add those two drives.  Is there someplace that it should have shown up elsewhere?  Maybe in the fix common problems (I run it on a daily schedule).  I would hate to have a drive drop from the array and not notice a problem.

 

Thanks very much!!

nasbox-u1-diagnostics-20250115-0830.zip

Everything looks good so far.

 

1 hour ago, SickPup404 said:

I only noticed the drive dropped from the array yesterday when I stopped it to add those two drives. 

The drive disabled during array stop, so probably no time to send a notification, assuming they are enabled, but you would get one at next array start.

Ah!  Makes sense.

 

Thanks again for all your assistance during my learning curve - really appreciate it!!