You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I have the disk mentioned in the subject connected to a Raspi4 (OS: Raspbian 11 / smartmontools-version: 7.2) via USB 3. After a few days of operation I realized that the disk got woken up (from a "self spin-down") by smartd. The according log shows entries like this one:
smartd[1280]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 123 to 122
For debugging purposes the spin-down was then set with the following command to a lower value (and I used smartctl for further testing):
sdparm --flexible -6 -l --set SCT=900 /dev/sda
After some playing around with hdparm (especially with "-y" and "-Y") it seems that setting the disk to sleep/standby-mode has different effects in regards to how smartctl handles the disk when called with "-n"-parameter. I did the following three test-scenarios with the appended output:
smartctl (and probably smartd also) "realized" when the disk is in standby and handle everything accordingly
when the disk is in sleep-mode this is not recogined and the disk is woken up
the default mode when the disk spins down itself seems to be sleep mode as it got also woken up
Therefore it would be great if you could have a short look on the output I provided (I hope it helps in debugging) and give feedback to this. If needed it would really like to provide you with some additional information to hopefully fix this issue.
All the best,
Stefan
The text was updated successfully, but these errors were encountered:
stksz
changed the title
WDC WD50NDZW-11MR8S1 spin up probelm
WDC WD50NDZW-11MR8S1 spin up problem
Jul 24, 2021
Disk set to sleep
...
Device is in ACTIVE or IDLE mode
SLEEP mode means that the ATA command GET POWER MODE fails because the drive does not reply to commands. In this case, the USB bridge firmware might detect this I/O-error, spin up the drive, retry GET POWER MODE and return its result.
Running smartctl after spin-down done by the disk itself
...
Device is in ACTIVE or IDLE mode
The command sdparm ... --set SCT=900 ... configures the SCSI Standby Condition Timer provided by the SAT layer of the USB bridge firmware. It may not configure the ATA Standby Timer. The command smartctl -s standby,12 ... would do this.
If set to STANDBY mode by SCSI/USB-layer, the firmware might always spin up the drive if the SCSI command ATA PASS-THROUGH arrives.
Hi,
I have the disk mentioned in the subject connected to a Raspi4 (OS: Raspbian 11 / smartmontools-version: 7.2) via USB 3. After a few days of operation I realized that the disk got woken up (from a "self spin-down") by smartd. The according log shows entries like this one:
For debugging purposes the spin-down was then set with the following command to a lower value (and I used smartctl for further testing):
After some playing around with hdparm (especially with "-y" and "-Y") it seems that setting the disk to sleep/standby-mode has different effects in regards to how smartctl handles the disk when called with "-n"-parameter. I did the following three test-scenarios with the appended output:
Disk set to standby
Disk set to sleep
Running smartctl after spin-down done by the disk itself
Currently the situation seem to be the following:
Therefore it would be great if you could have a short look on the output I provided (I hope it helps in debugging) and give feedback to this. If needed it would really like to provide you with some additional information to hopefully fix this issue.
All the best,
Stefan
The text was updated successfully, but these errors were encountered: