Hello,
first of all very much thanks for such a good tool.
I am a bit unsure how accurate SSD monitoring is.
I have an Samsung SSD 850 Pro which has 24 TB Lifetime writes and was used 966 Days and has 330 days left.
HDSentinel tells me that there are 491 Bad Sectors and the status is at 62%.
TRIM is enabled and active.
Well this SSD is the operating system disk inside a windows server which is online 24/7 but that this Pro SSD seems to be in such bad state makes me nervous.
How much can I / should I trust this information?
Thanks for any thoughts and infos on this.
Greetings, saschadd
How accurate is SSD monitoring?
-
hdsentinel
- Site Admin
- Posts: 3128
- Joined: 2008.07.27. 17:00
- Location: Hungary
- Contact:
Re: How accurate is SSD monitoring?
Hello,
Thanks for your message and question.
I can confirm the SSD monitoring, error detection and health reporting is completely accurate.
Generally Hard Disk Sentinel designed to detect any kind of problems, show them, report possible new issues / degradations and allow users to decide what to do by the information, for example when it may be prepared for a replacement - to make sure that the server should run uninterrupted and safely.
The TRIM function and lifetime writes have no real effect on bad sectors.
Yes, I can confirm SSDs can have bad sectors as well, exactly as hard disks.
After write to a specific sector, the SSD verifies the contents of the sector and if it can't be read back correctly (or the ECC correction mechanism indicates that) the SSD automatically writes the data again to a spare sector and re-directs all further reads and writes to that sector, instead of the original sector.
This is exactly what hard disks do - just on SSDs the whole process is much quicker and there are no noticeable signs, for example no "clicking" or other weird noises, no retries / substantial delays, freezes and so.
Manufacturers prepared for this, allocated special spare area for this purpose which is used - and as the the bad sector is not accessible by any means, it will never cause further problems. Ideally the user should never notice anything about this - until the amount of bad sector begin increasing dramatically and may data corruption / data loss / disk failure happens.
Personally in such situations (when the status is not perfect) I always recommend testing to verify if the SSD has further problem(s) or if the status is now stable and the device could be used without problems.
For more information about these bad sectors and further steps about how to examine and improve the situation, please visit
http://www.hdsentinel.com/faq.php#health and
http://www.hdsentinel.com/faq.php#tests
http://www.hdsentinel.com/faq_repair_ha ... _drive.php
If the tests show no problems, which mean all bad sectors already found and fixed and they can't cause any further troubles, it is possible to clear the count of bad sectors in Hard Disk Sentinel, to acknowledge these issues and only focus on possible further changes, problems, degradations. This would restore the health too. The last link gives information about this procedure generally but if you use Report menu -> Send test report to developer option, it is possible to examine the current situation and can help step-by-step about the proper way.
Personally, considering that it is a 24/7 server, it is already used for some time and not perfect, even if the tests show no problems, I'd consider replacement in a year (considering the estimated remaining lifetime too). If the tests show problems then much sooner.
Thanks for your message and question.
I can confirm the SSD monitoring, error detection and health reporting is completely accurate.
Generally Hard Disk Sentinel designed to detect any kind of problems, show them, report possible new issues / degradations and allow users to decide what to do by the information, for example when it may be prepared for a replacement - to make sure that the server should run uninterrupted and safely.
The TRIM function and lifetime writes have no real effect on bad sectors.
Yes, I can confirm SSDs can have bad sectors as well, exactly as hard disks.
After write to a specific sector, the SSD verifies the contents of the sector and if it can't be read back correctly (or the ECC correction mechanism indicates that) the SSD automatically writes the data again to a spare sector and re-directs all further reads and writes to that sector, instead of the original sector.
This is exactly what hard disks do - just on SSDs the whole process is much quicker and there are no noticeable signs, for example no "clicking" or other weird noises, no retries / substantial delays, freezes and so.
Manufacturers prepared for this, allocated special spare area for this purpose which is used - and as the the bad sector is not accessible by any means, it will never cause further problems. Ideally the user should never notice anything about this - until the amount of bad sector begin increasing dramatically and may data corruption / data loss / disk failure happens.
Personally in such situations (when the status is not perfect) I always recommend testing to verify if the SSD has further problem(s) or if the status is now stable and the device could be used without problems.
For more information about these bad sectors and further steps about how to examine and improve the situation, please visit
http://www.hdsentinel.com/faq.php#health and
http://www.hdsentinel.com/faq.php#tests
http://www.hdsentinel.com/faq_repair_ha ... _drive.php
If the tests show no problems, which mean all bad sectors already found and fixed and they can't cause any further troubles, it is possible to clear the count of bad sectors in Hard Disk Sentinel, to acknowledge these issues and only focus on possible further changes, problems, degradations. This would restore the health too. The last link gives information about this procedure generally but if you use Report menu -> Send test report to developer option, it is possible to examine the current situation and can help step-by-step about the proper way.
Personally, considering that it is a 24/7 server, it is already used for some time and not perfect, even if the tests show no problems, I'd consider replacement in a year (considering the estimated remaining lifetime too). If the tests show problems then much sooner.
Re: How accurate is SSD monitoring?
Wasn't sure if I should create a new topic or just continue the discussion in this thread as my question is pretty similar to the TS's one. Hopefully, it's OK to ask here...
Recently I have bought a used Intel 710 Series 100GB SSD for my aging Samsung R528 laptop from 2010. I choose this drive because it had a pretty good price-to-capacity-to-performance-to-endurance ratio. The drive I got had "only" 16.5TB of data written to it. Whereas manufacturer states 500-900 TBW endurance for a 100GB variant of this model.
As far as I can tell, the drive seems to be OK. But what made me curious is why despite having 100% of "performance" and 100% of "health" and a pretty low lifetime writes figures (compared to rated endurance), why the program reports less than 1000 days of an estimated remaining lifetime? And why this figure keeps decreasing? Last week it was saying 634 days left, and now it dropped to 632. By which S.M.A.R.T. attribute this figure gets calculated? And why other programs, like SSD Life, estimate far greater remaining life for this drive?
Recently I have bought a used Intel 710 Series 100GB SSD for my aging Samsung R528 laptop from 2010. I choose this drive because it had a pretty good price-to-capacity-to-performance-to-endurance ratio. The drive I got had "only" 16.5TB of data written to it. Whereas manufacturer states 500-900 TBW endurance for a 100GB variant of this model.
Code: Select all
-- General Information --
Application Information
-------------------------
Installed Version . . . . . . . . . . . . . . . : Hard Disk Sentinel 4.00 PRO
Registered To . . . . . . . . . . . . . . . . . : Hard Disk Sentinel Pro
Current Date And Time . . . . . . . . . . . . . : 1/1/2018 1:59:32 AM
Health Calculation Method . . . . . . . . . . . : Analyse data field (default)
Computer Information
----------------------
Computer Name . . . . . . . . . . . . . . . . . : Unknown
User Name . . . . . . . . . . . . . . . . . . . : Unknown
Computer Type . . . . . . . . . . . . . . . . . : Mobile
IP Address . . . . . . . . . . . . . . . . . . . : Unknown
MAC Address . . . . . . . . . . . . . . . . . . : Unknown
System Uptime . . . . . . . . . . . . . . . . . : 0 days, 10 hours, 5 minutes, 36 seconds
System Up Since . . . . . . . . . . . . . . . . : 12/31/2017 3:53:57 PM
CPU Usage . . . . . . . . . . . . . . . . . . . : CPU #1: 6 %, CPU #2: 35 %
Virtual Memory . . . . . . . . . . . . . . . . . : 8119 MB, Used: 5489 MB (68 %)
System Information
--------------------
Windows Version . . . . . . . . . . . . . . . . : Windows 7 Ultimate Server (Terminal Server Edition)
CPU Type & Speed #1 . . . . . . . . . . . . . . : Intel(R) Core(TM)2 Duo CPU P9600 @ 2.66GHz, 2660 MHz
CPU Type & Speed #2 . . . . . . . . . . . . . . : Intel(R) Core(TM)2 Duo CPU P9600 @ 2.66GHz, 2660 MHz
BIOS Manufacturer . . . . . . . . . . . . . . . : Phoenix
Physical Memory Size . . . . . . . . . . . . . . : 4061 MB, Used: 3201 MB (79 %)
Display Adapter . . . . . . . . . . . . . . . . : NVIDIA GeForce 310M
Display Resolution . . . . . . . . . . . . . . . : 1366 x 768 (32 bit)
Printer #1 . . . . . . . . . . . . . . . . . . . : Fax
Printer #2 . . . . . . . . . . . . . . . . . . . : Microsoft XPS Document Writer
Network Controller #1 . . . . . . . . . . . . . : Marvell Yukon 88E8040 Family PCI-E Fast Ethernet Controller
Network Controller #2 . . . . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6200 AGN
Optical Drive #1 . . . . . . . . . . . . . . . . : E: TSSTcorp CDDVDW TS-L633C / SC00 (DVD-RAM, DVD-RW, CD-RW)
PCI Device Information
------------------------
PCI Bus 0; Device 0; Function 0 . . . . . . . . : Mobile Intel(R) 4 Series Chipset Processor to DRAM Controller - 2A40
PCI Bus 0; Device 1; Function 0 . . . . . . . . : Mobile Intel(R) 4 Series Chipset PCI Express Root Port - 2A41
PCI Bus 0; Device 26; Function 0 . . . . . . . . : Intel(R) ICH9 Family USB Universal Host Controller - 2937
PCI Bus 0; Device 26; Function 1 . . . . . . . . : Intel(R) ICH9 Family USB Universal Host Controller - 2938
PCI Bus 0; Device 26; Function 2 . . . . . . . . : Intel(R) ICH9 Family USB Universal Host Controller - 2939
PCI Bus 0; Device 26; Function 7 . . . . . . . . : Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293C
PCI Bus 0; Device 27; Function 0 . . . . . . . . : High Definition Audio Controller
PCI Bus 0; Device 28; Function 0 . . . . . . . . : Intel(R) ICH9 Family PCI Express Root Port 1 - 2940
PCI Bus 0; Device 28; Function 3 . . . . . . . . : Intel(R) ICH9 Family PCI Express Root Port 4 - 2946
PCI Bus 0; Device 29; Function 0 . . . . . . . . : Intel(R) ICH9 Family USB Universal Host Controller - 2934
PCI Bus 0; Device 29; Function 1 . . . . . . . . : Intel(R) ICH9 Family USB Universal Host Controller - 2935
PCI Bus 0; Device 29; Function 2 . . . . . . . . : Intel(R) ICH9 Family USB Universal Host Controller - 2936
PCI Bus 0; Device 29; Function 7 . . . . . . . . : Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293A
PCI Bus 0; Device 30; Function 0 . . . . . . . . : Intel(R) 82801 PCI Bridge - 2448
PCI Bus 0; Device 31; Function 0 . . . . . . . . : Intel(R) ICH9M LPC Interface Controller - 2919
PCI Bus 0; Device 31; Function 2 . . . . . . . . : Standard AHCI 1.0 Serial ATA Controller
PCI Bus 0; Device 31; Function 3 . . . . . . . . : Intel(R) ICH9 Family SMBus Controller - 2930
PCI Bus 1; Device 0; Function 0 . . . . . . . . : NVIDIA GeForce 310M
PCI Bus 1; Device 0; Function 1 . . . . . . . . : High Definition Audio Controller
PCI Bus 2; Device 0; Function 0 . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6200 AGN
PCI Bus 4; Device 0; Function 0 . . . . . . . . : Marvell Yukon 88E8040 Family PCI-E Fast Ethernet Controller
-- Physical Disk Information - Disk: #0: INTEL SSDSA2BZ100G3 --
Hard Disk Summary
-------------------
Hard Disk Number . . . . . . . . . . . . . . . . : 0
Interface . . . . . . . . . . . . . . . . . . . : S-ATA II
Disk Controller . . . . . . . . . . . . . . . . : Standard AHCI 1.0 Serial ATA Controller (AHCI)
Disk Location . . . . . . . . . . . . . . . . . : Channel 0, Target 0, Lun 0, Device: 0
Hard Disk Model ID . . . . . . . . . . . . . . . : INTEL SSDSA2BZ100G3
Firmware Revision . . . . . . . . . . . . . . . : 6PB10362
Hard Disk Serial Number . . . . . . . . . . . . : CVLV20500032100AGN
Total Size . . . . . . . . . . . . . . . . . . . : 95393 MB
Power State . . . . . . . . . . . . . . . . . . : Active
Logical Drive(s) . . . . . . . . . . . . . . . . : C: [] D: []
Current Temperature . . . . . . . . . . . . . . : 32 °C
Maximum Temperature (Ever Measured) . . . . . . : 42 °C, 12/29/2017 3:00:59 AM
Minimum Temperature (Ever Measured) . . . . . . : 17 °C, 12/29/2017 1:46:00 PM
Maximum Temperature (During Entire Lifespan) . . : 50 °C
Power On Time . . . . . . . . . . . . . . . . . : 1192 days, 13 hours
Estimated Remaining Lifetime . . . . . . . . . . : more than 632 days
Health . . . . . . . . . . . . . . . . . . . . . : #################### 100 % (Excellent)
Performance . . . . . . . . . . . . . . . . . . : #################### 100 % (Excellent)
The status of the solid state disk is PERFECT. Problematic or weak sectors were not found.
The TRIM feature of the SSD is supported and enabled for optimal performance.
The health is determined by SSD specific S.M.A.R.T. attribute(s): #233 Media Wearout Indicator
No actions needed.
ATA Information
-----------------
Hard Disk Cylinders . . . . . . . . . . . . . . : 193821
Hard Disk Heads . . . . . . . . . . . . . . . . : 16
Hard Disk Sectors . . . . . . . . . . . . . . . : 63
ATA Revision . . . . . . . . . . . . . . . . . . : ATA8-ACS version 4
Transport Version . . . . . . . . . . . . . . . : SATA Rev 2.6
Total Sectors . . . . . . . . . . . . . . . . . : 195371568
Bytes Per Sector . . . . . . . . . . . . . . . . : 512
Multiple Sectors . . . . . . . . . . . . . . . . : 16
Error Correction Bytes . . . . . . . . . . . . . : 0
Unformatted Capacity . . . . . . . . . . . . . . : 95396 MB
Maximum PIO Mode . . . . . . . . . . . . . . . . : 4
Maximum Multiword DMA Mode . . . . . . . . . . . : 2
Maximum UDMA Mode . . . . . . . . . . . . . . . : 300 MB/s (6)
Active UDMA Mode . . . . . . . . . . . . . . . . : 300 MB/s (6)
Minimum Multiword DMA Transfer Time . . . . . . : 120 ns
Recommended Multiword DMA Transfer Time . . . . : 120 ns
Minimum PIO Transfer Time Without IORDY . . . . : 120 ns
Minimum PIO Transfer Time With IORDY . . . . . . : 120 ns
ATA Control Byte . . . . . . . . . . . . . . . . : Valid
ATA Checksum Value . . . . . . . . . . . . . . . : Valid
Acoustic Management Configuration
-----------------------------------
Acoustic Management . . . . . . . . . . . . . . : Not supported
Acoustic Management . . . . . . . . . . . . . . : Disabled
Current Acoustic Level . . . . . . . . . . . . . : Default (00h)
Recommended Acoustic Level . . . . . . . . . . . : Default (00h)
ATA Features
--------------
Read Ahead Buffer . . . . . . . . . . . . . . . : Supported, Enabled
DMA . . . . . . . . . . . . . . . . . . . . . . : Supported
Ultra DMA . . . . . . . . . . . . . . . . . . . : Supported
S.M.A.R.T. . . . . . . . . . . . . . . . . . . . : Supported
Power Management . . . . . . . . . . . . . . . . : Supported
Write Cache . . . . . . . . . . . . . . . . . . : Supported
Host Protected Area . . . . . . . . . . . . . . : Supported
Advanced Power Management . . . . . . . . . . . : Not supported
Extended Power Management . . . . . . . . . . . : Not supported
Power Up In Standby . . . . . . . . . . . . . . : Not supported
48-Bit LBA Addressing . . . . . . . . . . . . . : Supported
Device Configuration Overlay . . . . . . . . . . : Supported
IORDY Support . . . . . . . . . . . . . . . . . : Supported
Read/Write DMA Queue . . . . . . . . . . . . . . : Not supported
NOP Command . . . . . . . . . . . . . . . . . . : Supported
Trusted Computing . . . . . . . . . . . . . . . : Not supported
64-Bit World Wide ID . . . . . . . . . . . . . . : 01507B5182B268EA
Streaming . . . . . . . . . . . . . . . . . . . : Not supported
Media Card Pass Through . . . . . . . . . . . . : Not supported
General Purpose Logging . . . . . . . . . . . . : Supported
Error Logging . . . . . . . . . . . . . . . . . : Supported
CFA Feature Set . . . . . . . . . . . . . . . . : Not supported
CFast Device . . . . . . . . . . . . . . . . . . : Not supported
Long Physical Sectors (1) . . . . . . . . . . . : Not supported
Long Logical Sectors . . . . . . . . . . . . . . : Not supported
Write-Read-Verify . . . . . . . . . . . . . . . : Not supported
NV Cache Feature . . . . . . . . . . . . . . . . : Not supported
NV Cache Power Mode . . . . . . . . . . . . . . : Not supported
NV Cache Size . . . . . . . . . . . . . . . . . : Not supported
Free-fall Control . . . . . . . . . . . . . . . : Not supported
Free-fall Control Sensitivity . . . . . . . . . : Not supported
Nominal Media Rotation Rate . . . . . . . . . . : Non-rotating Media (SSD)
SSD Features
--------------
Data Set Management . . . . . . . . . . . . . . : Supported
TRIM Command . . . . . . . . . . . . . . . . . . : Supported
Deterministic Read After TRIM . . . . . . . . . : Supported
Operating System TRIM Function . . . . . . . . . : Supported, Enabled
S.M.A.R.T. Details
--------------------
Off-line Data Collection Status . . . . . . . . : Never Started
Self Test Execution Status . . . . . . . . . . . : Successfully Completed
Total Time To Complete Off-line Data Collection : 1 seconds
Execute Off-line Immediate . . . . . . . . . . . : Supported
Abort/restart Off-line By Host . . . . . . . . . : Supported
Off-line Read Scanning . . . . . . . . . . . . . : Not supported
Short Self-test . . . . . . . . . . . . . . . . : Supported
Extended Self-test . . . . . . . . . . . . . . . : Supported
Conveyance Self-test . . . . . . . . . . . . . . : Supported
Selective Self-Test . . . . . . . . . . . . . . : Supported
Save Data Before/After Power Saving Mode . . . . : Supported
Enable/Disable Attribute Autosave . . . . . . . : Supported
Error Logging Capability . . . . . . . . . . . . : Supported
Short Self-test Estimated Time . . . . . . . . . : 1 minutes
Extended Self-test Estimated Time . . . . . . . : 1 minutes
Conveyance Self-test Estimated Time . . . . . . : 1 minutes
Last Short Self-test Result . . . . . . . . . . : Never Started
Last Short Self-test Date . . . . . . . . . . . : Never Started
Last Extended Self-test Result . . . . . . . . . : Never Started
Last Extended Self-test Date . . . . . . . . . . : Never Started
Last Conveyance Self-test Result . . . . . . . . : Never Started
Last Conveyance Self-test Date . . . . . . . . . : Never Started
Security Mode
---------------
Security Mode . . . . . . . . . . . . . . . . . : Supported
Security Erase . . . . . . . . . . . . . . . . . : Supported
Security Erase Time . . . . . . . . . . . . . . : 1 minutes
Security Enhanced Erase Feature . . . . . . . . : Supported
Security Enhanced Erase Time . . . . . . . . . . : 1 minutes
Security Enabled . . . . . . . . . . . . . . . . : No
Security Locked . . . . . . . . . . . . . . . . : No
Security Frozen . . . . . . . . . . . . . . . . : Yes
Security Counter Expired . . . . . . . . . . . . : No
Security Level . . . . . . . . . . . . . . . . . : High
Serial ATA Features
---------------------
S-ATA Compliance . . . . . . . . . . . . . . . . : Yes
S-ATA I Signaling Speed (1.5 Gps) . . . . . . . : Supported
S-ATA II Signaling Speed (3 Gps) . . . . . . . . : Supported
S-ATA Gen3 Signaling Speed (6 Gps) . . . . . . . : Not supported
Receipt Of Power Management Requests From Host . : Not supported
PHY Event Counters . . . . . . . . . . . . . . . : Supported
Non-Zero Buffer Offsets In DMA Setup FIS . . . . : Not supported
DMA Setup Auto-Activate Optimization . . . . . . : Not supported
Device Initiating Interface Power Management . . : Not supported
In-Order Data Delivery . . . . . . . . . . . . . : Not supported
Asynchronous Notification . . . . . . . . . . . : Not supported
Software Settings Preservation . . . . . . . . . : Supported, Enabled
Native Command Queuing (NCQ) . . . . . . . . . . : Supported
Queue Length . . . . . . . . . . . . . . . . . . : 32
Disk Information
------------------
Disk Information
Form Factor . . . . . . . . . . . . . . . . . . : 2.5"
Capacity . . . . . . . . . . . . . . . . . . . . : 100 GB (100 x 1,000,000 bytes)
SSD Controller . . . . . . . . . . . . . . . . . : Intel PC29AS21BA0
Disk Interface . . . . . . . . . . . . . . . . . : Serial-ATA/300
Device Type . . . . . . . . . . . . . . . . . . : Intel 25nm HET MLC NAND
Width . . . . . . . . . . . . . . . . . . . . . : 69.8 mm (2.7 inch)
Depth . . . . . . . . . . . . . . . . . . . . . : 100.0 mm (3.9 inch)
Height . . . . . . . . . . . . . . . . . . . . . : 9.5 mm (0.4 inch)
S.M.A.R.T.
------------
No. Attribute Thre.. Value Worst Data Status Flags
3 Spin Up Time 0 100 100 0 OK (Always passing) Self Preserving
4 Start/Stop Count 0 100 100 0 OK (Always passing) Self Preserving, Event Count
5 Reallocated Sectors Co.. 0 100 100 0 OK (Always passing) Self Preserving, Event Count, Statistical
9 Power On Time Count 0 100 100 28621 OK (Always passing) Self Preserving, Event Count, Statistical
12 Drive Power Cycle Count 0 100 100 51 OK (Always passing) Self Preserving, Event Count, Statistical
170 Available Reserved Space 10 100 100 0 OK Self Preserving, Event Count, Statistical, Critical
171 Program Fail Count 0 100 100 0 OK (Always passing) Self Preserving, Event Count, Statistical
172 Erase Fail Count 0 100 100 0 OK (Always passing) Self Preserving, Event Count, Statistical
174 Vendor-specific 0 100 100 29 OK (Always passing) Self Preserving, Event Count, Statistical
183 Vendor-specific 0 100 100 2 OK (Always passing) Self Preserving, Event Count
184 End-to-End Error Count 90 100 100 0 OK Self Preserving, Event Count, Statistical
187 Reported Uncorrectable.. 0 100 100 0 OK (Always passing) Self Preserving, Event Count, Statistical
190 Airflow Temperature 0 73 50 27 OK (Always passing) Self Preserving, Event Count, Statistical
192 Unsafe Shutdown Count 0 100 100 29 OK (Always passing) Self Preserving, Event Count, Statistical
194 Disk Temperature 0 100 95 32 OK (Always passing) Self Preserving, Event Count, Statistical
199 Ultra ATA CRC Error Co.. 0 100 100 0 OK (Always passing) Self Preserving, Event Count
225 Host Writes 0 100 100 17,395.22 GB [556.. OK (Always passing) Self Preserving, Event Count, Statistical
226 Timed Workload Media W.. 0 100 100 0 OK (Always passing) Self Preserving, Event Count, Statistical
227 Timed Workload Host Re.. 0 100 100 50 OK (Always passing) Self Preserving, Event Count, Statistical
228 Workload Timer 0 100 100 602 OK (Always passing) Self Preserving, Event Count, Statistical
232 Available Reserved Space 10 100 100 0 OK Self Preserving, Event Count, Statistical, Critical
233 Media Wearout Indicator 0 100 100 0 OK (Always passing) Self Preserving, Event Count, Statistical
241 Host Writes 0 100 100 17,395.22 GB [556.. OK (Always passing) Self Preserving, Event Count, Statistical
242 Host Reads 0 100 100 16,197.56 GB [518.. OK (Always passing) Self Preserving, Event Count, Statistical
Transfer Rate Information
---------------------------
Total Data Read . . . . . . . . . . . . . . . . : 7,245 MB, 405,251 MB since installation (11/30/2014)
Total Data Write . . . . . . . . . . . . . . . . : 8,205 MB, 560,028 MB since installation
Average Reads Per Day . . . . . . . . . . . . . : 359.27 MB
Average Writes Per Day . . . . . . . . . . . . . : 496.48 MB
Current Transfer Rate . . . . . . . . . . . . . : 35 KB/s
Maximum Transfer Rate . . . . . . . . . . . . . : 166819 KB/s
Current Read Rate . . . . . . . . . . . . . . . : 0 KB/s
Current Write Rate . . . . . . . . . . . . . . . : 35 KB/s
Current Disk Activity . . . . . . . . . . . . . : 0 %
-- Partition Information --
Logical Drive Total Space Free Space Free Space Used Space
C: (Disk: #0) 31.1 GB 7.8 GB 25 % ###############-----
D: (Disk: #0) 62.1 GB 7.6 GB 12 % #################--- -
hdsentinel
- Site Admin
- Posts: 3128
- Joined: 2008.07.27. 17:00
- Location: Hungary
- Contact:
Re: How accurate is SSD monitoring?
Generally this version of Hard Disk Sentinel is very old.
It should able to detect and display the status of the device you use, but personally I'd recommend to use a newer version of the software (for example 5.01)
> why the program reports less than 1000 days of an estimated remaining lifetime?
Because of the actual power on time of the device.
Please check the Help, which exactly describes this situation, how the estimated power on time determined, calculated:
https://www.hdsentinel.com/help/en/54_pot.html
The estimated lifetime is based on the actual health - and the actual usage (power on time) of the drive too in addition to other statistical information (like the lifetime writes).
Generally Hard Disk Sentinel uses 5 years (more precisely 5 x 365 = 1825 days) as total designed lifetime of the drive, considering that it's running 24 hours every day. If a drive used for 12 hours every day, then we'd need 2 x 1825 days to reach this point.
> And why this figure keeps decreasing? Last week it was saying 634 days left, and now it dropped to 632.
Even if the health is perfect, there are no problems with the device, this value is decreasing, to indicate when we may plan and consider replacement. So it is normal that you see this decreasing.
This does not mean that the disk drive will surely fail. Just can indicate when we may consider replacement in a mission criticial environment.
The device may work (even for years) after this point - so for non-critical data, it may be still used of course.
As you can see, the rate of the decrease depends on the usage, it does NOT decrease every day.
When you use a device for 8 hours a day, then you may notice that the reported power on time increases with a day (24 hours) after every 3 days.
The estimated power on time value decreases with the same rate.
However, I can confirm that it will stop: if no errors reported, it does not decrease further until there is any error with the device.
It will stop and display "more than 100 days" to indicate that the drive may still work - but as we're near the end of the lifetime nobody can be sure about how long.
> By which S.M.A.R.T. attribute this figure gets calculated?
Attribute 9 Power on time count
This determines how long the drive actually used.
> And why other programs, like SSD Life, estimate far greater remaining life for this drive?
This is excellent question. Personally I'd be curious about how somebody can estimate 8+ years for a device which already used for many years.
Why they show "T.E.C. date" (threshold exceed condition) at all?
The "Value" for the corresponding self-monitoring attributes (power on time, host writes) never changed and the "Threshold" is also zero, so the threshold will be never reached. So I wonder how somebody calculates 8 additional years and report "T.E.C. date" SURELY 8 years, 3 months, 27 days for a situation which will never happens. I mean why it is not 12, 15, 19 years or so...
Commonly saw 20+ years estimated lifetime in such other tools (on failed/damaged drives too) so I wonder how somebody can say so much...
I agree that it we want to see "everything is perfect and everything will be fine for many-many years" but I do not really agree this may be true and even possible.
For more information, please check:
www.hdsentinel.com/smart
which generally describes how the Threshold/Value comparision and T.E.C. date is a bad approach in general
https://www.hdsentinel.com/faq.php#difference
Why other software displays different health? Which is correct?
It should able to detect and display the status of the device you use, but personally I'd recommend to use a newer version of the software (for example 5.01)
> why the program reports less than 1000 days of an estimated remaining lifetime?
Because of the actual power on time of the device.
Please check the Help, which exactly describes this situation, how the estimated power on time determined, calculated:
https://www.hdsentinel.com/help/en/54_pot.html
The estimated lifetime is based on the actual health - and the actual usage (power on time) of the drive too in addition to other statistical information (like the lifetime writes).
Generally Hard Disk Sentinel uses 5 years (more precisely 5 x 365 = 1825 days) as total designed lifetime of the drive, considering that it's running 24 hours every day. If a drive used for 12 hours every day, then we'd need 2 x 1825 days to reach this point.
> And why this figure keeps decreasing? Last week it was saying 634 days left, and now it dropped to 632.
Even if the health is perfect, there are no problems with the device, this value is decreasing, to indicate when we may plan and consider replacement. So it is normal that you see this decreasing.
This does not mean that the disk drive will surely fail. Just can indicate when we may consider replacement in a mission criticial environment.
The device may work (even for years) after this point - so for non-critical data, it may be still used of course.
As you can see, the rate of the decrease depends on the usage, it does NOT decrease every day.
When you use a device for 8 hours a day, then you may notice that the reported power on time increases with a day (24 hours) after every 3 days.
The estimated power on time value decreases with the same rate.
However, I can confirm that it will stop: if no errors reported, it does not decrease further until there is any error with the device.
It will stop and display "more than 100 days" to indicate that the drive may still work - but as we're near the end of the lifetime nobody can be sure about how long.
> By which S.M.A.R.T. attribute this figure gets calculated?
Attribute 9 Power on time count
This determines how long the drive actually used.
> And why other programs, like SSD Life, estimate far greater remaining life for this drive?
This is excellent question. Personally I'd be curious about how somebody can estimate 8+ years for a device which already used for many years.
Why they show "T.E.C. date" (threshold exceed condition) at all?
The "Value" for the corresponding self-monitoring attributes (power on time, host writes) never changed and the "Threshold" is also zero, so the threshold will be never reached. So I wonder how somebody calculates 8 additional years and report "T.E.C. date" SURELY 8 years, 3 months, 27 days for a situation which will never happens. I mean why it is not 12, 15, 19 years or so...
Commonly saw 20+ years estimated lifetime in such other tools (on failed/damaged drives too) so I wonder how somebody can say so much...
I agree that it we want to see "everything is perfect and everything will be fine for many-many years" but I do not really agree this may be true and even possible.
For more information, please check:
www.hdsentinel.com/smart
which generally describes how the Threshold/Value comparision and T.E.C. date is a bad approach in general
https://www.hdsentinel.com/faq.php#difference
Why other software displays different health? Which is correct?
Re: How accurate is SSD monitoring?
Not sure if I understand you correctly. Does this mean that even if the drive will surpass 5 years (43800 hours) of uptime, and if "Health" and "Performance" will still remain at 100%, the "Reported lifetime expectancy" will not drop below 100 days?However, I can confirm that it will stop: if no errors reported, it does not decrease further until there is any error with the device.
It will stop and display "more than 100 days" to indicate that the drive may still work - but as we're near the end of the lifetime nobody can be sure about how long.
-
hdsentinel
- Site Admin
- Posts: 3128
- Joined: 2008.07.27. 17:00
- Location: Hungary
- Contact:
Re: How accurate is SSD monitoring?
> Not sure if I understand you correctly. Does this mean that even if the drive will surpass 5 years (43800 hours)
> of uptime, and if "Health" and "Performance" will still remain at 100%, the "Reported lifetime expectancy" will not drop
> below 100 days?
Yes, I can confirm that this is 100% true.
> of uptime, and if "Health" and "Performance" will still remain at 100%, the "Reported lifetime expectancy" will not drop
> below 100 days?
Yes, I can confirm that this is 100% true.
Re: How accurate is SSD monitoring?
Okay. Thanks for the clarification.