Replies: 3 comments
-
|
Just an update to this. It seems the timers are working at least for stby (since I cannot check any other power mode). I also notice that sometimes a command to query the drive after a while take a bit longer which should mean the the IDLE_B and IDLE_C are probably kicking in. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @kar200, Sorry I did not see this posted earlier! The EPC feature is part of the ATA and SCSI standards, which is how this tool implements the support for them. Additionally, a lot of ATA is meant to be backwards compatible and sometimes that turns things into much more of a mess to work through.
With EPC, the drive should be reporting the exact idle condition it is in (a, b, or c) and same for standby (y or z). One of the weird things in ATA for backwards compatibility is It is possible that even though the drive is following the timers this is what they are transitioning to for some compatibility reason. Another possibility is that some other command is spinning them up from idle. There are no requirements or ways to identify exactly which commands will spin the drive up in the ATA specifications. For the standby message, the spec handled this differently. Here is a reference from the ATA spec on the reported power modes: OpenSeaChest uses these exact values to map to the message that is printed to the screen. So I would expect that the drive would report exactly these values...but maybe something else is happening in the background. One example is that on Seagate drives things like the identify device command will not spin up the drive. Other commands like reading a log page might spin up the drive, but it depends on which page it is (and what the firmware supports reading without spinup). While this does not affect you with the output you shared, another thing I found is that if software calls One thing you can try is putting both the --transitionPower & --checkPowerMode on the command line at the same time. If you collect the verbose logs from all the separate runs, I can check them to see if it tells me anything about what is causing this different output. |
Beta Was this translation helpful? Give feedback.
-
|
Hi and thank you for the answer. I run the same commands with the verbose output. I have attached the files as requested. Please let me know if you need anything else and thank you for your help. K. epcfeature_enable.txt |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I have 2 HGST Ultrastar drives bought from Amazon second hand. I found out about this tool to setup my ironwolf pro drives and it works well.
While using the tool to scan the drives I noticed that the HGST drives report EPC and APM. I started playing around witth the settings and managed to change the timers.
Changing the timers works and survives reboot. setting the EPC to enable does not survive a reboot.
Using --transitionPower works sucessfully. The issue is that the report always shows idle_b or idle_c as being "Device is in the PM0: Active state or PM1: Idle State" and for "stby_y and stby_z it reports "Device is in the PM2: Standby state and device is in the Standby_z power condition"
I tried to search online and used various AI but I can't seem to make the drives change automatically. I am thinking myabe the firmware does not allow it or maybe the reporting is not accurate (after all these are not Seagate HDD's).
The online datasheet for the Ultrastar 7K4000 does mention 5 advanced power management modes. I am gessing they are the ones?
Beta Was this translation helpful? Give feedback.
All reactions