Surface test on NVMe drive in HDS 6.0.0 Pro

How, what, where and why - when using the software.
tired
Posts: 18
Joined: 2019.05.11. 06:45

Surface test on NVMe drive in HDS 6.0.0 Pro

Post by tired »

I have a Seagate FireCuda 520 SSD (NVMe) drive. I just installed HDS Pro 6.00 on my Win10 21H1 system.

I initiated a short self-test on the NVMe drive. My comments:

- The red color in the progress bar is a little alarming. I would suggest making it green instead, since red typically indicates that a problem exists.
- I hit "Cancel", and the progress window closed, but the self-test proceeded anyway.
- The the release notes say "option to schedule short / extended self test on NVMe SSDs too (registered Hard Disk Sentinel Pro version)", but I can't see a way to schedule self-tests in the UI.
User avatar
hdsentinel
Site Admin
Posts: 3115
Joined: 2008.07.27. 17:00
Location: Hungary
Contact:

Re: Surface test on NVMe drive in HDS 6.0.0 Pro

Post by hdsentinel »

Thanks for your message and your comments.

1) Sorry for the possible confusion. I can confirm that no, the red color does not indicate any problems. This kind of bar (red->yellow->green) is used in Hard Disk Sentinel for 10+ years in several locations. Not sure if this will be changed, maybe... The information in the test window confirms / shows if there is any error.


2) Yes, this can be completely normal and expected in some cases, for example if Windows Standard NVMe controller driver used (you can verify on the Information page) to manage the SSD.

Hard Disk Sentinel attempts to send STOP command to the SSD if you click the Cancel button. But the Windows Standard NVMe controller driver (for an unknown reason) does not allow sending NVMe test-related commands (including the start of a new test or stopping the test) to the same drive too frequently: if you attempt to start too frequent tests, you may receive an error message (which is caused by the Windows Standard NVMe controller driver).

Generally the short/extended self tests are "internal" tests of the drives: they run inside the SSD. We can only send a command to start, stop and read the results. But (similarly as for other SSDs/HDDs) the disk controller driver may affect the use of these special commands.


3) You can do this way:
- please open Configuration -> Operations page. There you can create a New project and specify that the Project type = Test hard disk(s). Select the disk(s) to be tested (eg. the NVMe SSD) and the test type (eg. Short/Extended)
- optional: you can create a direct shortcut on the Desktop to launch the test any time manually if preferred
- select the Schedule tab on this page to specify on which day(s) and when exactly the test should run.

Please refer to the Help:
- about hardware self tests: https://www.hdsentinel.com/help/en/58_test.html
- about disk tests in general: https://www.hdsentinel.com/help/en/62_testfaq.html
- about the projects: https://www.hdsentinel.com/help/en/33_op1.html
- about the schedule: https://www.hdsentinel.com/help/en/35_op2.html
tired
Posts: 18
Joined: 2019.05.11. 06:45

Re: Surface test on NVMe drive in HDS 6.0.0 Pro

Post by tired »

Yes, my drive is using the Windows Standard NVMe controller driver. Thank you for the explanation.

Whenever we create something--whether an email, an essay, or an application--we become blind to how it is perceived by others. This is why it is important to have other (competent) people proofread, test, or otherwise review our work. I know you are very used to the red progress bars, but I am telling you from the perspective of a user (an advanced user, at that) who was not expecting it, the red is alarming at first.

The funny thing is that now that I'm used to the red progress bars, I don't care so much about it. I will expect it whenever I see them--no big deal. And yet new users will likely be alarmed by it just as I was.

No response expected!

Thank you very much for the reply.
Hmmm888
Posts: 8
Joined: 2021.09.26. 06:47

Re: Surface test on NVMe drive in HDS 6.0.0 Pro

Post by Hmmm888 »

tired wrote: Whenever we create something--whether an email, an essay, or an application--we become blind to how it is perceived by others. This is why it is important to have other (competent) people proofread, test, or otherwise review our work. I know you are very used to the red progress bars, but I am telling you from the perspective of a user (an advanced user, at that) who was not expecting it, the red is alarming at first.

The funny thing is that now that I'm used to the red progress bars, I don't care so much about it. I will expect it whenever I see them--no big deal. And yet new users will likely be alarmed by it just as I was.
I agree completely with everything you wrote.

The rooted issue is our own ego, arrogance, and one dimensional mindset. This is absurdly pronounced now more than ever. We see it amongst developers and "entities" like Google. They only accept feedback from like-minded people and are resistant/dismissive to anyone's opinion other than them. We see this now especially with this pandemic and how governments and media labelled COVID safety protocols as restrictions. Confirmation bias is very real.
Post Reply