A Few drives will not spin down

[SavellM]

Hi all,

 

So I have spin down delay set to 1 hour, and all drives on default. 

For whatever reason a subset of mixed drives will not spin down, they are all connected to the same SAS controller, and they are not on the same breakout cables either.

 

Diagnostics attached.

Screen shot too: 

 

Also I am suffering from a random issue where I restart and some drives show as Wrong, even tho they are the exact same drives selected in the drop down so the array doesnt start.

Fortunately its only been 2 drives so I've been able to rebuild parity.

 

Once when I just set it up, it was EVERY drive.

Nothing changed hardware wise. I literally just rebooted. 

 

Really hoping to get these 2 issues ironed out...

namek-diagnostics-20230910-2114.zip

[itimpi]

1 hour ago, SavellM said:

even tho they are the exact same drives selected in the drop down so the array doesnt start.

Something must have changed.  Sometimes it is something not obvious such as the drive not reporting the same size for some reason (even 1 byte off will cause this).

[SavellM]

3 minutes ago, itimpi said:

Something must have changed.  Sometimes it is something not obvious such as the drive not reporting the same size for some reason (even 1 byte off will cause this).

 

I mean they are all formatted and part of the pool, so if its changing thats hella scary.

Is there anything I can do to prevent this? 
Is it something to do with BTRFS or needing scrubs or something? 

 

I mean all I did was click restart and it came back and array wouldnt start multiple times and different drives.

[itimpi]

Just now, SavellM said:

 

I mean they are all formatted and part of the pool, so if its changing thats hella scary.

Is there anything I can do to prevent this? 
Is it something to do with BTRFS or needing scrubs or something? 

 

I mean all I did was click restart and it came back and array wouldnt start multiple times and different drives.

 

It tends to mean that something changed at the hardware and/or bios level so it is definitely something I would be worried about.

[SavellM]

9 hours ago, itimpi said:

 

It tends to mean that something changed at the hardware and/or bios level so it is definitely something I would be worried about.

 

Is there any specific bios settings I should check?

It's the first time I'm having this after running OMV for ages. 

 

Also any help from anyone on the drive spin down?

 

I just tried to stop all dockers, and shutdown my only VM.

Clicked spin down and same thing, no dice.

Edited September 11, 2023 by SavellM

[itimpi]

3 hours ago, SavellM said:

Is there any specific bios settings I should check?

Afraid not.   his is the first time I can remember this happening without there being some outside factor to explain it, and even then it is a one-off thing.

 

It is possible someone else may have a suggestion.

 

[SavellM]

3 hours ago, itimpi said:

Afraid not.   his is the first time I can remember this happening without there being some outside factor to explain it, and even then it is a one-off thing.

 

It is possible someone else may have a suggestion.

 

So good news, I shut down all dockers, and VM's and did a restart.

It restarted and array came to life and no missing disks

 

So thats good... now just to figure out why some drives are not spinning down... Can anyone help with this? 

[SavellM]

If anyone at all could help further that would be amazing.

 

Here is the disk logs for one of the drives not spinning down:

[SavellM]

Bump @JorgeB do you have any ideas?

[JorgeB]

If it happens again post diags before rebuilding, or we can't see why they were "wrong", for the spin down issue try stopping cache dirs, or rebooting in safe mode.

[SavellM]

2 hours ago, JorgeB said:

If it happens again post diags before rebuilding, or we can't see why they were "wrong", for the spin down issue try stopping cache dirs, or rebooting in safe mode.

 

Hey thanks. 

 

I will post again if it happens with wrong drives. 

 

For spin down I have stopped that app and no change in behaviour. 

I have restarted multiple times and no change there either. 

 

Will try safe mode tonight and report back. Thank you

[SavellM]

Ok so I dug into this more...

 

Ran safemode, didnt help either.

 

I then looked if there was a new Firmware for my 9300-16i and funnily there was, but also I noticed that I hadnt flashed BOTH sides of the controller.

Num   Ctlr            FW Ver        NVDATA        x86-BIOS         PCI Addr
----------------------------------------------------------------------------

0  SAS3008(C0)  16.00.10.00    0e.01.00.03    08.37.00.00     00:19:00:00
1  SAS3008(C0)  05.00.00.00    05.00.00.01    08.11.00.00     00:1b:00:00

 

So I flashed them both this time to the latest 16.00.12.00 & BIOS.

Restarted and testing seems good now.

 

Voila: 

Edited September 13, 2023 by SavellM