Hello!

 

I am looking to see if i cant get some help identifying why 3 of my drives aren't spinning down. I got these three off eBay not to long ago and put them in and they formatted just fine. My original drives all spin down with no issues, but these three show active still, except the log for the drive shows "Apr 3 14:04:24 HOMESERVER emhttpd: spinning down /dev/sde". Ive checked the spin down time and they all are set to the default which i set to 2 hours.

 

Ive attached some screenshots and also my diagnostic log, there is nothing installed on these drives as i just put them in and formatted them like 3 days ago.

homeserver-diagnostics-20220403-1405.zip

12 minutes ago, simpleace said:

why 3 of my drives aren't spinning down

looking at the model numbers they are SAS drivers and not SATA. You will need to install SAS spindown plugin. But it may not work we your drives.

 

The current version of smartctl may also spin up the Seagate ones, i have asked for this to be updated in 6.10 but I can provide a fixed version if that helps, as I have it on one of my drives.

 

 

 

Edited April 3, 20224 yr by SimonF

Sorry missed the diags.

 

[1:0:0:0]    disk    SEAGATE  ST4000NM0295     DT31  /dev/sdb   /dev/sg1 
  state=running queue_depth=254 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/1:0:0:0  [/sys/devices/pci0000:00/0000:00:02.2/0000:02:00.0/host1/port-1:0/expander-1:0/port-1:0:0/end_device-1:0:0/target1:0:0/1:0:0:0]
[1:0:1:0]    disk    SEAGATE  ST4000NM0295     DT31  /dev/sdc   /dev/sg2 
  state=running queue_depth=254 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/1:0:1:0  [/sys/devices/pci0000:00/0000:00:02.2/0000:02:00.0/host1/port-1:0/expander-1:0/port-1:0:1/end_device-1:0:1/target1:0:1/1:0:1:0]
[1:0:2:0]    disk    ATA      ST4000VN008-2DR1 SC60  /dev/sdd   /dev/sg3 
  state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/1:0:2:0  [/sys/devices/pci0000:00/0000:00:02.2/0000:02:00.0/host1/port-1:0/expander-1:0/port-1:0:2/end_device-1:0:2/target1:0:2/1:0:2:0]
[1:0:3:0]    disk    WD       WD4001FYYG       D1R5  /dev/sde   /dev/sg4 
  state=running queue_depth=254 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/1:0:3:0  [/sys/devices/pci0000:00/0000:00:02.2/0000:02:00.0/host1/port-1:0/expander-1:0/port-1:0:3/end_device-1:0:3/target1:0:3/1:0:3:0]

SATA have ATA for the vendor, but the three have Vendor name which indicate SAS.

Edited April 3, 20224 yr by SimonF

3 minutes ago, SimonF said:

Sorry missed the diags.

 

[1:0:0:0]    disk    SEAGATE  ST4000NM0295     DT31  /dev/sdb   /dev/sg1 
  state=running queue_depth=254 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/1:0:0:0  [/sys/devices/pci0000:00/0000:00:02.2/0000:02:00.0/host1/port-1:0/expander-1:0/port-1:0:0/end_device-1:0:0/target1:0:0/1:0:0:0]
[1:0:1:0]    disk    SEAGATE  ST4000NM0295     DT31  /dev/sdc   /dev/sg2 
  state=running queue_depth=254 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/1:0:1:0  [/sys/devices/pci0000:00/0000:00:02.2/0000:02:00.0/host1/port-1:0/expander-1:0/port-1:0:1/end_device-1:0:1/target1:0:1/1:0:1:0]
[1:0:2:0]    disk    ATA      ST4000VN008-2DR1 SC60  /dev/sdd   /dev/sg3 
  state=running queue_depth=32 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/1:0:2:0  [/sys/devices/pci0000:00/0000:00:02.2/0000:02:00.0/host1/port-1:0/expander-1:0/port-1:0:2/end_device-1:0:2/target1:0:2/1:0:2:0]
[1:0:3:0]    disk    WD       WD4001FYYG       D1R5  /dev/sde   /dev/sg4 
  state=running queue_depth=254 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/1:0:3:0  [/sys/devices/pci0000:00/0000:00:02.2/0000:02:00.0/host1/port-1:0/expander-1:0/port-1:0:3/end_device-1:0:3/target1:0:3/1:0:3:0]

SATA have ATA for the vendor, but the three and Vendor name which indicate SAS.

Thank you for the quick response! I do remember that they were SAS not SATA and i should have included that, but didnt think that would be an issue.

 

I ran the command and results are below.

 

root@HOMESERVER:~# lsblk -So NAME,TRAN
NAME TRAN
sda  usb
sdb  sas
sdc  sas
sdd  sas
sde  sas
sdf  sas
sdg  sas
sdh  sas
sdi  sas
sdj  sas
sdk  sas
root@HOMESERVER:~# 

 

I don't get why the SATA drives would show up as SAS under this TRAN as i'm assuming this is the "transfer method" the drive is currently using?

5 minutes ago, simpleace said:

Thank you for the quick response! I do remember that they were SAS not SATA and i should have included that, but didnt think that would be an issue.

 

I ran the command and results are below.

 

root@HOMESERVER:~# lsblk -So NAME,TRAN
NAME TRAN
sda  usb
sdb  sas
sdc  sas
sdd  sas
sde  sas
sdf  sas
sdg  sas
sdh  sas
sdi  sas
sdj  sas
sdk  sas
root@HOMESERVER:~# 

 

I don't get why the SATA drives would show up as SAS under this TRAN as i'm assuming this is the "transfer method" the drive is currently using?

Will be the HBA is a SAS Controller.

 

 

 

Ah ok. I looked into the plugin that you mentioned and that helped the issue, i can now spin down my SAS drives and also my SATA drives after installing this. Hopefully this gets implemented in 6.10! I appreciate the help!

8 minutes ago, SimonF said:

Will be the HBA is a SAS Controller.

 

 

 

 

27 minutes ago, SimonF said:

looking at the model numbers they are SAS drivers and not SATA. You will need to install SAS spindown plugin. But it may not work we your drives.

 

The current version of smartctl may also spin up the Seagate ones, i have asked for this to be updated in 6.10 but I can provide a fixed version if that helps, as I have it on one of my drives.

 

 

 

 

11 minutes ago, simpleace said:

Ah ok. I looked into the plugin that you mentioned and that helped the issue, i can now spin down my SAS drives and also my SATA drives after installing this. Hopefully this gets implemented in 6.10! I appreciate the help!

 

 

You can test smartctl by running the following.

 

smartctl -n standby /dev/sdb to see if that spins up the disk.

 

25 minutes ago, SimonF said:

You can test smartctl by running the following.

 

smartctl -n standby /dev/sdb to see if that spins up the disk.

 

When I run that command I get the following. Is that what is supposed to happen? Or is it supposed to spin the disk up based on that command.

 

root@HOMESERVER:~# smartctl -n standby /dev/sdb
SAS Assist Plugin: /dev/sdb is in standby mode (spun down), smartctl exits(2)

 

4 minutes ago, simpleace said:

When I run that command I get the following. Is that what is supposed to happen? Or is it supposed to spin the disk up based on that command.

 

root@HOMESERVER:~# smartctl -n standby /dev/sdb
SAS Assist Plugin: /dev/sdb is in standby mode (spun down), smartctl exits(2)

 

yes that is expected, -n standby will not run smartctl is the disk is in standby.