I can confirm that the support of TRIM is displayed (and was displayed too in previous versions), see the Information page:ĭataset Management Command. Glad to hear things are working now correctly, TRIM is reported active as should 🙂 Reply from HDS Technical Team (the English is as received!): I sent HDS a new test Report and received the following response:
I had not known that “Data Set Management Commands” also refer to the status of Trim (never too old to learn!). I installed the new test version of HDS as provided to me by their technical personnel and it reported that Trim is enabled for my M.2 NVMe SSD. They certainly make it clear that Trim being reported as ENABLED does NOT necessarily mean it is actually functioning! You may try – and performĪ complete re-detect in Hard Disk Sentinel to show the changed TRIM status).” So the updated Hard Disk Sentinel version should display TRIM status: both if workingĪnd if not working (if we really disable by fsutil at the OS level. – if fsutil may be used to really disable TRIM – the message should notify about it to change setting – if we see TRIM status for simpler/cheaper SATA SSDs, we may expect for NVMe SSDs too. – this information may be assuring (as it would confirm things are working as should) But I completely understand and agree that
This is why until now Hard Disk Sentinel did not display such information for this type
INDEX OF HARD DISK SENTINEL PRO 5.0.1.13 DRIVER
And if we consider that it is enabled by the OS and the driver can’t cause problems, then we can assume TRIM is always working for the NVMe SSD. Generally fsutil always shows TRIM = enabled, even if there is no SSD in the system. Personally I see no reason and never saw situation when TRIM was disabled by the user (by using fsutil). Should be always working – there is no similar situation – except if we really disable However, with NVMe SSDs, things are different: due to design of the driver, TRIM Please note that most other tools only checks fsutil and always show TRIM = workingįor SATA SSDs too, when it may be not working at all. There may be a problem – even if fsutil would show that TRIM is enabled. This is why Hard Disk Sentinel focused to verify and show TRIM status for these SSDs where Or it may be blocked by the disk controller or its driver – which is a common situation You may know, with fsutil we can check if the OS uses TRIM command at all,īut it shows absolutely no info if the TRIM command would really “reach” the device Where there can be problem with TRIM at all. “To be honest, displaying the TRIM status is designed to work with SATA SSDs only, (Cudos and many thanks to the HDS development team!!)įeedback from HDS Technical Team.
INDEX OF HARD DISK SENTINEL PRO 5.0.1.13 UPDATE
Under “Feedback” below, you will see that I tested a trial version of the new update before it was released to the general public, and it reflected the TRIM status of M.2 NVMe SSDs correctly. I was impressed that my query to the developer triggered a modification to HDS which resulted in a new version being rolled out. (The text in italics is my own doing for emphasis). I received the following reply (the English is as received!). I sent a test report to HDS and queried why HDS did not report the Trim status of my M.2 NVMe SSD.
I use Hard Disk Sentinel (HDS) to monitor my hard drives.
0 kommentar(er)
