$iFlag - If set to 1, the array size must to a multiple of $iCols. $iEnd - Index of array to stop the transformation. $iStart - Index of array to start the transformation. $iCols - Number of columns to transform the array to. : _Array1DTo2D($avArray, $iCols]]) Parameters. They had packed the drives in a very loose package and the hdd (although protected by bubble wraps) could easily move in the outer packaging.Expand collapse popup #RequireAdmin needed #Include just for _ArrayDisplay $sSmartPath = & "\smart.exe" Downloaded from here : Run Smart.exe and get the result Local $iPid = Run ( $sSmartPath, ,, 2 ) ProcessWaitClose ( $iPid ) Local $sResult = StdoutRead ( $iPid ) Get all infos from the output string Local $aRegExResult = StringRegExp ( $sResult, "(?m)^\\]\h(\N+?)\h+(\w+)\h+(\d+)\h+(\d+)\h+(\d+)\h+(-?\d+)\h+(\w+)", 3 ) Parse the elements in an array If Then Exit MsgBox ( 16, "Error", "No result found" ) Local $aSmartInfos = _Array1DTo2D ( $aRegExResult, 7 ) Converts the 1D array to a 2D array _ArrayDisplay ( $aSmartInfos ) Get the "Power On Hours Count" value : $iPOHC = StringRegExp ( $sResult, "Power On Hours Count\N+?(\d+)\h+\w+\R", 1 ) now get the Power On Hours Count value If Then Exit MsgBox ( 16, "Error", "Unable to retrieve the Power On Hours Count value" ) MsgBox ( 0, "", "Power On Hours Count : " & $iPOHC ) #FUNCTION# = Name. What the hell is going on?! This drive isn't even in use and reacts to what the other drive is doing? Because the sounds are on the right side of the laptop where I have the caddy installed. I know for sure that the noises come from the HDD.
I must say that I have not even partitioned the HDD yet and I'm only using the SSD to write/read data (sth I didn't have in mind until now).Īnyway, I was installing Adobe Photoshop on the SSD and after 15% of the progress, the HDD started to make noises (about 10 times!) which is weird considering that I was working with SSD. the hex value for power on hours is x'000000011E16'.
CRYSTALDISKINFO POWERONHOURS WRONG 32 BIT
The 32 bit version of crystal diskinfo reports the correct number of power on hours as 1220. And actually, something really weird happened right now. Details Version 6.5.2 圆4 reports power on hours for Toshiba MQ01ABD100 1000.2 gb hdd as 73238 hours. It cannot be a regular thing, 'cause it happens on specific occasions. You can use Bing or Google's calculator for hex/decimal conversion:
Normal SATA SMART Attribute Behavior (Seagate): I would write a 1GiB file to the SSD and then compare attribute F1 before and after. The actual number of host writes would depend on the write amplification. Seek Error Rate, Read Error Rate and Hardware ECC Recovered SMART attributes: The SSD has recorded an average wear levelling count of 19 ( 0x13 in hexadecimal), so this means that the total writes to NAND amount to 256GiB x 19 5.2TB. In fact the actual number of seek errors is 0. The Read Error Rate and Seek Error Rate raw values are sector counts, not error counts. These correspond to the max, min and current temperature values for the current power cycle. Those look like 3 temperature values, namely 22C, 21C and 22C. I suspect that the upper 16 bits (or 20 bits) might be the fractional part of an hour, say milliseconds. The lower number is 0x20 which is 32 in decimal. They can consist of two or more values.įor example, Power On Hours appears to consist of two numbers: The raw values in many cases are not single values. I couldn't believe that someone would be able to make sense of hex values.
0 kommentar(er)
