However, often the drive is unable to read data from the damaged sectors and the Retry<\/em> mode can last for a very long time before it decides to give up on a particular sector\u00a0and return an\u00a0Error<\/em>.<\/p>\n If Insight simply\u00a0waited\u00a0for\u00a0each\u00a0Read sectors\u00a0<\/em>command to be completed:<\/p>\n For these reasons, Insight issues a\u00a0Reset<\/em><\/strong>\u00a0command\u00a0whenever a drive attempts to read a block of sectors for longer\u00a0than\u00a0allowed by\u00a0the pre-configured\u00a0Timeout<\/em>.\u00a0Reset<\/em>\u00a0is a\u00a0device\u00a0interface operation, using which Insight (the host<\/em>) stops the previously sent\u00a0Read sectors<\/em> (or any other) ATA command\u00a0so that Insight continues imaging from the next planned block\u00a0on the drive.<\/p>\n If the device is still running Read Sectors<\/em> command, even after Reset <\/em>attempt, Insight will wait 3 seconds and perform another\u00a0Reset<\/em><\/strong>\u00a0command. At the moment of the second Reset, a new entry will appear in the Imaging Log\u00a0<\/em>reading\u00a0Device hangs while reading block X \u2013 Y.<\/em><\/p>\n If 20 seconds after the second Reset,<\/em> the drive has not been able to abandon the current block, Insight will perform\u00a0Power cycle<\/strong> <\/em>by forcibly cutting power to the drive for 5 seconds. At this point Insight will add two entries to the log: \u00a0Performing power cycle…<\/em>\u00a0(when the power is cut off) and\u00a0Waiting for the device to become ready\u2026<\/em> (when the power is switched back on).<\/p>\n Should Power cycle prove successful\u00a0and the drive become ready to accept the next command, there will be\u00a0a\u00a0final\u00a0log\u00a0entry for this problematic block\u00a0of sectors saying:\u00a0Cannot read block of data at\u00a0X \u2013\u00a0Y (Timeout).<\/em><\/p>\n If Power cycle<\/em>\u00a0is ineffective,\u00a0it means that the drive is still in Busy <\/i>state that prevents it from becoming ready to run the next command. After that, Insight will make one or more additional power cycles.\u00a0 In Insight\u2019s default settings the Max consecutive\u00a0Power Cycles\u00a0<\/em>option\u00a0is set to five<\/em>. <\/em>Should all five Power cycles be unsuccessful, Imaging will be automatically terminated. It can be resumed afterwards,\u00a0and Insight will continue to image all remaining sectors.<\/p>\n While users are able to change the default maximum numbers of Resets and Power cycles, these are set based on our\u00a0decades-long experience and balance the need of data retrieving with the risk of further data loss.<\/p>\n NB<\/strong>\u00a0If prior to Imaging, you applied Change Max Address temporarily (until power cycle)<\/em> option, the Power cycles performed in the course of Imaging will not affect\u00a0it. The Host Protected Area will remain accessible throughout the Imaging process. Insight will temporarily remove HPA max address restriction after each Imaging-related Power cycle.<\/p>\n The same is true for\u00a0Reset Password until power cycle<\/em> option. Insight will keep the password reset throughout the Imaging process, without regard to the Power cycles applied.<\/p>\n","protected":false},"excerpt":{"rendered":" When Atola Insight Forensic performs\u00a0Imaging, it approaches bad sectors in the most gentle yet thorough way with high overall speed. But most importantly, Insight is unbeatable at imaging severely damaged drives, while providing all the necessary tools for evidence verification and proper data storage formats. Insight’s ability to succeed even […]<\/p>\n","protected":false},"author":8,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[35],"tags":[],"yoast_head":"\nHow does Insight handle this issue?<\/h3>\n
\n
![\"Imaging](\"http:\/\/blog.atola.com\/wp-content\/uploads\/2017\/02\/Timeout-Power-Cycle.png\" "\\"Imaging")
<\/p>\n