I know my hdd is kind of failing now. It has 13 current pending sectors. I'm just waiting for my ssd and I'll replace it with that. But since I'm still waiting for the ssd, I want to know if there's still some hope on booting up Windows.
Here's what happened. HD Sentinel notified me one day that it found some current pending sectors. I've got them before and I usually just run Disk Repair to clear them out. So, I ran Disk Repair to try fixing those. I restarted my PC after it finished. That was when the "Critical Process Died" started showing up. Every time I start up my computer, that error shows up then it goes to Automatic Repair but that fails to fix anything so it just suggests to restart. When I restart, the whole thing repeats. My computer is basically unbootable right now.
I acknowledge that my drive is not safe to run an OS anymore, but as I've mentioned, I still want to try and find out if the Windows inside can still be fixed. I've tried 3 recovery methods. First is the onboard Windows Recovery, second is the one on the bootable drive that I made using the Windows 8.1 ISO I downloaded from Microsoft, then last is Hiren's Boot.
For both the onboard and the bootable drive's Windows Recovery
Then along the way on finding possible solutions, I discovered Hiren's Boot. And so I tried it, mostly for the console functions.
There are the results for Hiren's chkdsk
I already ran it before and it was able to repair some stuff so it didn't find anything when I ran it this time. I noticed though that the number of data inside the bad blocks grew from 4kb when I ran chkdsk /r last December 2020 to 104kb now.
For the second partition. This was when I first ran it.
I've also used SeaTool's bootable repair program. I used its Fix All - Long function and it was able to fix all the bad blocks it found. It just says "Pass" whenever I run it now.
I found a similar post to mine here and the person from sysnative who responded instructed the poster to do some tests on GSmartControl (using Hiren's Boot) so I did that too.
Logs from GSmartControl
Here's what happened. HD Sentinel notified me one day that it found some current pending sectors. I've got them before and I usually just run Disk Repair to clear them out. So, I ran Disk Repair to try fixing those. I restarted my PC after it finished. That was when the "Critical Process Died" started showing up. Every time I start up my computer, that error shows up then it goes to Automatic Repair but that fails to fix anything so it just suggests to restart. When I restart, the whole thing repeats. My computer is basically unbootable right now.
I acknowledge that my drive is not safe to run an OS anymore, but as I've mentioned, I still want to try and find out if the Windows inside can still be fixed. I've tried 3 recovery methods. First is the onboard Windows Recovery, second is the one on the bootable drive that I made using the Windows 8.1 ISO I downloaded from Microsoft, then last is Hiren's Boot.
For both the onboard and the bootable drive's Windows Recovery
- chkdsk /r always fails
- these dism commands fail too
- dism /image:c:\ /cleanup-image /restorehealth /scratchdir:c:\scratch /source:c:\winwork\mount2\windows /limitaccess
- dism /image:c:\ /cleanup-image /restorehealth /scratchdir:c:\scratch /source:wim:c:\winwork\iso\install.wim:1
- Windows Refresh just gives an error basically saying it can't do a Refresh
- Startup Repairs fail as well
Then along the way on finding possible solutions, I discovered Hiren's Boot. And so I tried it, mostly for the console functions.
- chkdsk /r was able to run and fix all problems for all partitions. I'm not sure why but Hiren's command prompt was miles better compared to the one on the onboard and bootable drive. Hiren's chkdsk only ran for like 3-4 hours for each of the 2 biggest partitions and it was able to fix the problems. The ones on the onboard and bootable drive took almost 24 hours just to throw out an error in the end saying they couldn't continue due to an error.
- I tried the dism commands from above but it just gives the same error I'm getting from before which was 0x800f081f the source files could not be found. I attached the logs from DISM.
There are the results for Hiren's chkdsk
I already ran it before and it was able to repair some stuff so it didn't find anything when I ran it this time. I noticed though that the number of data inside the bad blocks grew from 4kb when I ran chkdsk /r last December 2020 to 104kb now.
x:\windows\system32>chkdsk /r /x c:
The type of the file system is NTFS.
Volume dismounted. All opened handles to this volume are now invalid.
Volume label is Windows8_OS.
Stage 1: Examining basic file system structure ...
1958144 file records processed.
File verification completed.
40332 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
2322242 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
182050 data files processed.
CHKDSK is verifying Usn Journal...
34378768 USN bytes processed.
Usn Journal verification completed.
Stage 4: Looking for bad clusters in user file data ...
1958128 files processed.
File data verification completed.
Stage 5: Looking for bad, free clusters ...
15878183 free clusters processed.
Free space verification is complete.
Windows has scanned the file system and found no problems.
No further action is required.
467414015 KB total disk space.
401210888 KB in 923778 files.
564548 KB in 182051 indexes.
104 KB in bad sectors.
2125743 KB in use by the system.
65536 KB occupied by the log file.
63512732 KB available on disk.
4096 bytes in each allocation unit.
116853503 total allocation units on disk.
15878183 allocation units available on disk.
For the second partition. This was when I first ran it.
x:\windows\system32>chkdsk /r /x d:
The type of the file system is NTFS.
Volume dismounted. All opened handles to this volume are now invalid.
Volume label is [....].
Stage 1: Examining basic file system structure ...
255488 file records processed.
File verification completed.
3387 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
Correcting sparse file record segment 5895.
Correcting sparse file record segment 41438.
Deleting index entry 008.jpg in index $I30 of file 115714.
Deleting index entry 009.jpg in index $I30 of file 115714.
Deleting index entry 010.jpg in index $I30 of file 115714.
Deleting index entry 011.jpg in index $I30 of file 115714.
Deleting index entry 016.jpg in index $I30 of file 115714.
Deleting index entry 017.jpg in index $I30 of file 115714.
Deleting index entry 018.jpg in index $I30 of file 115714.
Deleting index entry 019.jpg in index $I30 of file 115714.
Deleting index entry 028.jpg in index $I30 of file 115714.
Deleting index entry 029.jpg in index $I30 of file 115714.
Deleting index entry 030.jpg in index $I30 of file 115714.
Deleting index entry 031.jpg in index $I30 of file 115714.
Deleting index entry 006.jpg in index $I30 of file 116755.
Deleting index entry 007.jpg in index $I30 of file 116755.
Deleting index entry 008.jpg in index $I30 of file 116755.
Deleting index entry 009.jpg in index $I30 of file 116755.
Deleting index entry 010.jpg in index $I30 of file 116755.
Deleting index entry 011.jpg in index $I30 of file 116755.
Deleting index entry 012.jpg in index $I30 of file 116755.
Deleting index entry 013.jpg in index $I30 of file 116755.
Deleting index entry 014.jpg in index $I30 of file 116755.
Deleting index entry 015.jpg in index $I30 of file 116755.
Deleting index entry 016.jpg in index $I30 of file 116755.
Deleting index entry 017.jpg in index $I30 of file 116755.
306124 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
25318 data files processed.
Stage 4: Looking for bad clusters in user file data ...
255472 files processed.
File data verification completed.
Stage 5: Looking for bad, free clusters ...
4137043 free clusters processed.
Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.
No further action is required.
491426815 KB total disk space.
474418204 KB in 187487 files.
123380 KB in 25320 indexes.
24 KB in bad sectors.
337035 KB in use by the system.
65536 KB occupied by the log file.
16548172 KB available on disk.
4096 bytes in each allocation unit.
122856703 total allocation units on disk.
4137043 allocation units available on disk.
I've also used SeaTool's bootable repair program. I used its Fix All - Long function and it was able to fix all the bad blocks it found. It just says "Pass" whenever I run it now.
I found a similar post to mine here and the person from sysnative who responded instructed the poster to do some tests on GSmartControl (using Hiren's Boot) so I did that too.
Logs from GSmartControl
smartctl 6.6 2017-11-05 r4594 [x86_64-w64-mingw32-w10-1607] (sf-6.6-1)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Samsung SpinPoint M8 (AF)
Device Model: ST1000LM024 HN-M101MBB
Serial Number: S30YJ9BG109704
LU WWN Device Id: 5 0004cf 20f0481fd
Firmware Version: 2BA30001
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 6
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Mon Jun 28 21:52:51 2021 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Disabled
APM level is: 128 (minimum power consumption without standby)
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, frozen [SEC2]
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (12660) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 211) minutes.
SCT capabilities: (0x003f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-K 100 100 051 - 54417
2 Throughput_Performance -OS--K 056 055 000 - 11553
3 Spin_Up_Time PO---K 092 088 025 - 2494
4 Start_Stop_Count -O--CK 096 096 000 - 4704
5 Reallocated_Sector_Ct PO--CK 252 252 010 - 0
7 Seek_Error_Rate -OSR-K 252 252 051 - 0
8 Seek_Time_Performance --S--K 252 252 015 - 0
9 Power_On_Hours -O--CK 100 100 000 - 26797
10 Spin_Retry_Count -O--CK 252 252 051 - 0
11 Calibration_Retry_Count -O--CK 098 098 000 - 2168
12 Power_Cycle_Count -O--CK 096 096 000 - 4559
191 G-Sense_Error_Rate -O---K 100 100 000 - 1622
192 Power-Off_Retract_Count -O---K 100 100 000 - 140
194 Temperature_Celsius -O---- 062 045 000 - 38 (Min/Max 23/55)
195 Hardware_ECC_Recovered -O-RCK 100 100 000 - 0
196 Reallocated_Event_Count -O--CK 252 252 000 - 0
197 Current_Pending_Sector -O--CK 100 100 000 - 13
198 Offline_Uncorrectable ----CK 252 252 000 - 0
199 UDMA_CRC_Error_Count -OS-CK 200 200 000 - 0
200 Multi_Zone_Error_Rate -O-R-K 100 100 000 - 63669
223 Load_Retry_Count -O--CK 098 098 000 - 2168
225 Load_Cycle_Count -O--CK 046 046 000 - 549598
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning
General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 2 Comprehensive SMART error log
0x03 GPL R/O 2 Ext. Comprehensive SMART error log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 2 Extended self-test log
0x08 GPL R/O 2 Power Conditions log
0x09 SL R/W 1 Selective self-test log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xc0-0xdf GPL,SL VS 16 Device vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer
SMART Extended Comprehensive Error Log Version: 1 (2 sectors)
Device Error Count: 58076 (device log contains only the most recent 8 errors)
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 58076 [3] occurred at disk power-on lifetime: 26756 hours (1114 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 01 00 00 72 f6 f6 38 e0 00 Error: UNC 1 sectors at LBA = 0x72f6f638 = 1928787512
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 01 00 00 72 f6 f6 38 e0 08 00:00:11.616 READ DMA EXT
25 00 00 00 01 00 00 72 f6 f6 37 e0 08 00:00:11.616 READ DMA EXT
25 00 00 00 01 00 00 72 f6 f6 36 e0 08 00:00:11.616 READ DMA EXT
25 00 00 00 01 00 00 72 f6 f6 35 e0 08 00:00:11.616 READ DMA EXT
25 00 00 00 01 00 00 72 f6 f6 34 e0 08 00:00:11.616 READ DMA EXT
Error 58075 [2] occurred at disk power-on lifetime: 26756 hours (1114 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 48 00 00 72 f6 f6 38 e0 00 Error: UNC 72 sectors at LBA = 0x72f6f638 = 1928787512
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 80 00 00 72 f6 f6 00 e0 08 00:00:11.614 READ DMA EXT
25 00 00 00 80 00 00 72 f6 f5 80 e0 08 00:00:11.614 READ DMA EXT
25 00 00 00 80 00 00 72 f6 f5 00 e0 08 00:00:11.614 READ DMA EXT
25 00 00 00 80 00 00 72 f6 f4 80 e0 08 00:00:11.614 READ DMA EXT
25 00 00 00 80 00 00 72 f6 f4 00 e0 08 00:00:11.614 READ DMA EXT
Error 58074 [1] occurred at disk power-on lifetime: 26756 hours (1114 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 01 00 00 38 66 90 b0 e0 00 Error: UNC 1 sectors at LBA = 0x386690b0 = 946245808
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 01 00 00 38 66 90 b0 e0 08 00:00:04.933 READ DMA EXT
25 00 00 00 01 00 00 38 66 90 af e0 08 00:00:04.933 READ DMA EXT
25 00 00 00 01 00 00 38 66 90 ae e0 08 00:00:04.933 READ DMA EXT
25 00 00 00 01 00 00 38 66 90 ad e0 08 00:00:04.933 READ DMA EXT
25 00 00 00 01 00 00 38 66 90 ac e0 08 00:00:04.933 READ DMA EXT
Error 58073 [0] occurred at disk power-on lifetime: 26756 hours (1114 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 01 00 00 38 66 90 a8 e0 00 Error: UNC 1 sectors at LBA = 0x386690a8 = 946245800
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 01 00 00 38 66 90 a8 e0 08 00:00:04.930 READ DMA EXT
25 00 00 00 01 00 00 38 66 90 a7 e0 08 00:00:04.930 READ DMA EXT
25 00 00 00 01 00 00 38 66 90 a6 e0 08 00:00:04.930 READ DMA EXT
25 00 00 00 01 00 00 38 66 90 a5 e0 08 00:00:04.930 READ DMA EXT
25 00 00 00 01 00 00 38 66 90 a4 e0 08 00:00:04.930 READ DMA EXT
Error 58072 [7] occurred at disk power-on lifetime: 26756 hours (1114 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 01 00 00 38 66 90 a0 e0 00 Error: UNC 1 sectors at LBA = 0x386690a0 = 946245792
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 01 00 00 38 66 90 a0 e0 08 00:00:04.927 READ DMA EXT
25 00 00 00 01 00 00 38 66 90 9f e0 08 00:00:04.927 READ DMA EXT
25 00 00 00 01 00 00 38 66 90 9e e0 08 00:00:04.927 READ DMA EXT
25 00 00 00 01 00 00 38 66 90 9d e0 08 00:00:04.927 READ DMA EXT
25 00 00 00 01 00 00 38 66 90 9c e0 08 00:00:04.927 READ DMA EXT
Error 58071 [6] occurred at disk power-on lifetime: 26756 hours (1114 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 60 00 00 38 66 90 a0 e0 00 Error: UNC 96 sectors at LBA = 0x386690a0 = 946245792
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 80 00 00 38 66 90 80 e0 08 00:00:04.920 READ DMA EXT
25 00 00 00 80 00 00 38 66 90 00 e0 08 00:00:04.916 READ DMA EXT
25 00 00 00 80 00 00 38 66 8f 80 e0 08 00:00:04.916 READ DMA EXT
25 00 00 00 80 00 00 38 66 8f 00 e0 08 00:00:04.916 READ DMA EXT
25 00 00 00 80 00 00 38 66 8e 80 e0 08 00:00:04.916 READ DMA EXT
Error 58070 [5] occurred at disk power-on lifetime: 26756 hours (1114 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 01 00 00 38 66 88 90 e0 00 Error: UNC 1 sectors at LBA = 0x38668890 = 946243728
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 01 00 00 38 66 88 90 e0 08 00:00:04.911 READ DMA EXT
25 00 00 00 01 00 00 38 66 88 8f e0 08 00:00:04.911 READ DMA EXT
25 00 00 00 01 00 00 38 66 88 8e e0 08 00:00:04.911 READ DMA EXT
25 00 00 00 01 00 00 38 66 88 8d e0 08 00:00:04.911 READ DMA EXT
25 00 00 00 01 00 00 38 66 88 8c e0 08 00:00:04.911 READ DMA EXT
Error 58069 [4] occurred at disk power-on lifetime: 26756 hours (1114 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 70 00 00 38 66 88 90 e0 00 Error: UNC 112 sectors at LBA = 0x38668890 = 946243728
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 80 00 00 38 66 88 80 e0 08 00:00:04.906 READ DMA EXT
25 00 00 00 01 00 00 38 66 88 7f e0 08 00:00:04.906 READ DMA EXT
25 00 00 00 01 00 00 38 66 88 7e e0 08 00:00:04.906 READ DMA EXT
25 00 00 00 01 00 00 38 66 88 7d e0 08 00:00:04.906 READ DMA EXT
25 00 00 00 01 00 00 38 66 88 7c e0 08 00:00:04.906 READ DMA EXT
SMART Extended Self-test Log Version: 1 (2 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 26797 -
# 2 Extended offline Aborted by host 90% 26778 -
# 3 Short offline Completed without error 00% 26778 -
# 4 Vendor (0x50) Completed without error 00% 26417 -
# 5 Short offline Completed without error 00% 26417 -
# 6 Short offline Completed without error 00% 26384 -
# 7 Vendor (0x50) Completed without error 00% 26059 -
# 8 Short offline Completed without error 00% 26059 -
# 9 Vendor (0x50) Completed without error 00% 25396 -
#10 Short offline Completed without error 00% 25396 -
#11 Vendor (0x50) Completed without error 00% 25038 -
#12 Short offline Completed without error 00% 25038 -
#13 Short offline Aborted by host 90% 24663 -
#14 Vendor (0x50) Completed without error 00% 24274 -
#15 Short offline Completed without error 00% 24274 -
#16 Short offline Completed without error 00% 24266 -
#17 Short offline Completed without error 00% 24255 -
#18 Short offline Completed without error 00% 24214 -
#19 Short offline Aborted by host 90% 24213 -
#20 Extended offline Aborted by host 90% 24213 -
#21 Short offline Completed without error 00% 24205 -
SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Completed [00% left] (0-65535)
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
SCT Status Version: 2
SCT Version (vendor specific): 256 (0x0100)
SCT Support Level: 1
Device State: Active (0)
Current Temperature: 38 Celsius
Power Cycle Min/Max Temperature: 36/51 Celsius
Lifetime Min/Max Temperature: 23/55 Celsius
Under/Over Temperature Limit Count: 0/0
SCT Temperature History Version: 2
Temperature Sampling Period: 5 minutes
Temperature Logging Interval: 5 minutes
Min/Max recommended Temperature: -5/80 Celsius
Min/Max Temperature Limit: -10/85 Celsius
Temperature History Size (Index): 128 (51)
Index Estimated Time Temperature Celsius
52 2021-06-28 11:15 38 *******************
53 2021-06-28 11:20 35 ****************
54 2021-06-28 11:25 33 **************
55 2021-06-28 11:30 33 **************
56 2021-06-28 11:35 33 **************
57 2021-06-28 11:40 35 ****************
58 2021-06-28 11:45 37 ******************
... ..( 2 skipped). .. ******************
61 2021-06-28 12:00 37 ******************
62 2021-06-28 12:05 39 ********************
63 2021-06-28 12:10 41 **********************
64 2021-06-28 12:15 42 ***********************
65 2021-06-28 12:20 42 ***********************
66 2021-06-28 12:25 43 ************************
67 2021-06-28 12:30 43 ************************
68 2021-06-28 12:35 38 *******************
69 2021-06-28 12:40 36 *****************
70 2021-06-28 12:45 39 ********************
71 2021-06-28 12:50 42 ***********************
72 2021-06-28 12:55 44 *************************
73 2021-06-28 13:00 45 **************************
74 2021-06-28 13:05 36 *****************
75 2021-06-28 13:10 40 *********************
76 2021-06-28 13:15 42 ***********************
77 2021-06-28 13:20 44 *************************
78 2021-06-28 13:25 45 **************************
79 2021-06-28 13:30 46 ***************************
80 2021-06-28 13:35 46 ***************************
81 2021-06-28 13:40 47 ****************************
82 2021-06-28 13:45 48 *****************************
83 2021-06-28 13:50 48 *****************************
84 2021-06-28 13:55 48 *****************************
85 2021-06-28 14:00 49 ******************************
... ..( 4 skipped). .. ******************************
90 2021-06-28 14:25 49 ******************************
91 2021-06-28 14:30 50 *******************************
... ..( 15 skipped). .. *******************************
107 2021-06-28 15:50 50 *******************************
108 2021-06-28 15:55 51 ********************************
109 2021-06-28 16:00 50 *******************************
... ..( 7 skipped). .. *******************************
117 2021-06-28 16:40 50 *******************************
118 2021-06-28 16:45 51 ********************************
... ..( 6 skipped). .. ********************************
125 2021-06-28 17:20 51 ********************************
126 2021-06-28 17:25 50 *******************************
... ..( 4 skipped). .. *******************************
3 2021-06-28 17:50 50 *******************************
4 2021-06-28 17:55 49 ******************************
... ..( 5 skipped). .. ******************************
10 2021-06-28 18:25 49 ******************************
11 2021-06-28 18:30 48 *****************************
... ..( 4 skipped). .. *****************************
16 2021-06-28 18:55 48 *****************************
17 2021-06-28 19:00 49 ******************************
18 2021-06-28 19:05 48 *****************************
19 2021-06-28 19:10 46 ***************************
20 2021-06-28 19:15 45 **************************
21 2021-06-28 19:20 44 *************************
22 2021-06-28 19:25 41 **********************
23 2021-06-28 19:30 42 ***********************
24 2021-06-28 19:35 43 ************************
25 2021-06-28 19:40 45 **************************
26 2021-06-28 19:45 46 ***************************
27 2021-06-28 19:50 46 ***************************
28 2021-06-28 19:55 47 ****************************
29 2021-06-28 20:00 47 ****************************
30 2021-06-28 20:05 43 ************************
31 2021-06-28 20:10 37 ******************
32 2021-06-28 20:15 44 *************************
33 2021-06-28 20:20 47 ****************************
34 2021-06-28 20:25 48 *****************************
35 2021-06-28 20:30 48 *****************************
36 2021-06-28 20:35 48 *****************************
37 2021-06-28 20:40 49 ******************************
38 2021-06-28 20:45 49 ******************************
39 2021-06-28 20:50 48 *****************************
... ..( 2 skipped). .. *****************************
42 2021-06-28 21:05 48 *****************************
43 2021-06-28 21:10 47 ****************************
44 2021-06-28 21:15 47 ****************************
45 2021-06-28 21:20 46 ***************************
46 2021-06-28 21:25 46 ***************************
47 2021-06-28 21:30 46 ***************************
48 2021-06-28 21:35 45 **************************
49 2021-06-28 21:40 45 **************************
50 2021-06-28 21:45 45 **************************
51 2021-06-28 21:50 38 *******************
SCT Error Recovery Control:
Read: Disabled
Write: Disabled
Device Statistics (GP/SMART Log 0x04) not supported
SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x0001 4 0 Command failed due to ICRC error
0x0002 4 0 R_ERR response for data FIS
0x0003 4 0 R_ERR response for device-to-host data FIS
0x0004 4 0 R_ERR response for host-to-device data FIS
0x0005 4 0 R_ERR response for non-data FIS
0x0006 4 0 R_ERR response for device-to-host non-data FIS
0x0007 4 0 R_ERR response for host-to-device non-data FIS
0x0008 4 0 Device-to-host non-data FIS retries
0x0009 4 153601 Transition from drive PhyRdy to drive PhyNRdy
0x000a 4 3 Device-to-host register FISes sent due to a COMRESET
0x000b 4 0 CRC errors within host-to-device FIS
0x000d 4 0 Non-CRC errors within host-to-device FIS
0x000f 4 0 R_ERR response for host-to-device data FIS, CRC
0x0010 4 0 R_ERR response for host-to-device data FIS, non-CRC
0x0012 4 0 R_ERR response for host-to-device non-data FIS, CRC
0x0013 4 0 R_ERR response for host-to-device non-data FIS, non-CRC
0x8e00 4 0 Vendor specific
0x8e01 4 0 Vendor specific
0x8e02 4 0 Vendor specific
0x8e03 4 0 Vendor specific
0x8e04 4 0 Vendor specific
0x8e05 4 0 Vendor specific
0x8e06 4 0 Vendor specific
0x8e07 4 0 Vendor specific
0x8e08 4 0 Vendor specific
0x8e09 4 0 Vendor specific
0x8e0a 4 0 Vendor specific
0x8e0b 4 0 Vendor specific
0x8e0c 4 0 Vendor specific
0x8e0d 4 0 Vendor specific
0x8e0e 4 0 Vendor specific
0x8e0f 4 0 Vendor specific
0x8e10 4 0 Vendor specific
0x8e11 4 0 Vendor specific
