Hi Deepak,

Thanks for reporting this. This behavior is new to me. The June release with Windows Server 2016 are the first version of StorScore and Windows that support sending secure erase to the drive. (So you may be uncovering a latent issue in the drive or OS.)

Does StorScore state that the secure erase operation completed successfully? The NVMe command that is sent is the "Format NVM" command with the secure erase bit set. Do you know if the drive implements this command correctly?

-Laura

from storscore.

Thanks for the response Laura,
yes the crypto erase is successfull. I have tried to erase it via storagetool separately aswell and see a successfull message and also no issues seen from our drive. But when there is a partition/FS and during storscore purge phase, I am not sure exactly the sequence of event. When I look at my drive, I do see the message popping up in the eventvwr around the time when crypto erase is being issues which corelates to the timing.

Attaching a few snapshots.

PS C:\Software\StorScore\bin> .\StorageTool.exe -Secureerase disk 1
Disk #1 : [NVME ] [SSD] [01 00 00 00]
Secure erase was successful
PS C:\Software\StorScore\bin>

I have verified that this issue is mostly seen with Corners recipe, on windows 2016 Server and with any Enterprise grade NVMe SSD.

However, If I just issue a secure Erase by itself, I dont see this corruption message being generated.
Thanks
Deepak

from storscore.

Interesting -- thanks for the extra info. Is the issue correlated with the corners recipe or with the existing partition? Have you tried running the storage tool on the drive when it has a partition and file on it?

The sequence of purge and disk preparation starts in lib\target.pm around line 350. The first step (if it's supported) is to secure erase the drive. Then diskpart "cleans" the drive, creates a partition, and creates a file. Is it possible the secure erase doesn't complete within the drive before the host creates the file system (and then the remaining work of secure erase deletes something that was later written to establish the file system)?

from storscore.

I have tried to SecureErase when the FS/Partition is on but I dont see the issue. It is something that is being done during purge phase,(Probably what you explained could be happening), where the secure erase may not be completing buy the time the FS is being created.

but here is an easy way to recreate it. I have also verified that its not specific to Corners recipe. It occurs with other recipe files aswell.

steps:

• Start the storscore corners recipe or any other recipe. (.\StorScore.cmd --recipe=.\recipes\4k_RR.rcp --target=\.\Physicaldrive1)
• once the storscore partition has been created(purge and initialization completed), (ctrl +c) and stop the run. Do not delete the storscore partition.
• re-execute the same command and you should be able to see the corruption message in eventvwr right away during the purge phase.

Thanks
Deepak

from storscore.

Hi Laura,
Any update on this issue. All tests are consistently failing.

Thanks
Deepak

from storscore.