Hi Anvil,
Good to hear that the "workaround" helped.
In the case of the hIOmon "SSD Performance Analysis" script, basically what this "workaround" does is to configure the hIOmon software so that the "physical volume" (rather than the "physical device") associated with the specified Logical Drive/Disk (i.e., logical disk "I" in your case) is monitored by the hIOmon software.
This is why you see "\Device\HarddiskVolume5" shown within the hIOmon Presentation Client display (rather than, say, "\Device\Harddisk1\DR1", which reflects "physical device/disk number 1").
There is another nuance, specifically with TRIM, that I would also like to mention here.
Basically, the software driver at the physical volume level within the I/O stack can honor a TRIM command for a physical volume whose associated physical device does not successfully process the TRIM command.
That is, the hIOmon software can observe the completion status of the TRIM I/O operations performed at the physical volume level as having been successfully performed by the software driver (and even though these TRIM commands were not actually passed downed to the physical device).
You can verify this TRIM nuance with a HDD running under Win 7. The hIOmon software can observe the "successful" completion of the TRIM commands at the physical volume level, but with the (single) attempt of a TRIM command at the physical device level observed by the hIOmon software as being unsuccessful - so consequently no additional TRIM commands will be passed down to the physical device.
BTW, this is also why the hIOmon "SSD Performance Analysis" script - by default - always configures the hIOmon software to monitor the specified "physical device" (rather than the "physical volume").





Reply With Quote
Bookmarks