After the Scan command, Result was not a SED drive even though it is opal complaint

[mallikarjunasai995]

Hi All

while executing the windows sedutil-cli with --scan command option , primary SED drive which is connected to it was returning as "No" \.\PhysicalDrive0 No instead of "\.\PhysicalDrive0 2" which refers to the SED DRIVE and OPAL Compliant

Do I need to install any pre-requisites for the same?

Note : I have just downloaded the sedutil-cli binary for windows and executed the above command

[dtasupport]

Is it a NVMe drive? The Windows version doesn’t support NVMe

On Mon, Nov 30, 2020 at 16:03 'mallik' via Drive Trust Alliance - Support < dtasupport@ka.je> wrote:

Hi All

while executing the windows sedutil-cli with --scan command option , primary SED drive which is connected to it was returning as "No" .\PhysicalDrive0 No instead of ".\PhysicalDrive0 2" which refers to the SED DRIVE and OPAL Compliant

Do I need to install any pre-requisites for the same?

Note : I have just downloaded the sedutil-cli binary for windows and executed the above command

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Drive-Trust-Alliance/sedutil/issues/342, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD52TFFVGOJ24MNYCTWZSOTSSQXGBANCNFSM4UIIPJQA .

--

Mike

[mallikarjunasai995]

Hi Mike

Yes, this a NVMe Drive. I have booted this NVMe Drive as primary with secure boot off option.

Is the windows version of SED UTIL doesn't support NVMe ?

I have got the same error while trying the same in LINUX Machine (Ubuntu 18.04) - I have downloaded the linux sedutil-cli binary

[maenpaa24]

Being able to boot Windows does not have anything to do with the Windows support of sedutil.

I was going to recommend you to try the binaries from the forks that do support NMVe drives in windows, such as (if I am not wrong):

https://github.com/ChubbyAnt/sedutil

and

https://github.com/lukefor/sedutil/tree/windows_nvme

Anyway, if it fails in ubuntu... I think the issue is not on sedutil's side.

[dtasupport]

Sedutil just sets up opal on the drive it doesn’t run any other time, all the processing takes place on the drive once you set it up.

On Mon, Nov 30, 2020 at 17:26 'mallik' via Drive Trust Alliance - Support < dtasupport@ka.je> wrote:

Yes,this a NVMe Drive. I have booted this NVMe Drive as primary with secure boot off option.

If the windows version doesn't support NVMe , then how am able to boot the OS ?

I have got the same error while trying the same in LINUX Machine (Ubuntu 18.04)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Drive-Trust-Alliance/sedutil/issues/342#issuecomment-736156185, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD52TFDB5PT5FSMGD3K3ZI3SSRA4JANCNFSM4UIIPJQA .

--

Mike

[mallikarjunasai995]

Being able to boot Windows does not have anything to do with the Windows support of sedutil.

I was going to recommend you to try the binaries from the forks that do support NMVe drives in windows, such as (if I am not wrong):

https://github.com/ChubbyAnt/sedutil

and

https://github.com/lukefor/sedutil/tree/windows_nvme

Anyway, if it fails in ubuntu... I think the issue is not on sedutil's side.

Hi

Could you please let me know the path for sedutil-cli binary from the below windows version git link :

https://github.com/lukefor/sedutil/tree/windows_nvme/windows

Do I need to compile any code through visual studio before executing the sedutil-cli command line ?

Previously I have just downloaded the windows sedutil-cli (1.5.1) and from that path I have executed the commands and getting failure status .. I have not downloaded the whole code as well.

Thanks

[maenpaa24]

I can not find lukefor's binaries. But chubbyant's are in

https://github.com/ChubbyAnt/sedutil/releases

I guess you could compile lukefor's code in visual studio.

Just in case, I believe the windows command line where you execute sedutil must have root privileges. That may be the reason why it threw an error

[mallikarjunasai995]

Hi

I can not find lukefor's binaries. But chubbyant's are in

https://github.com/ChubbyAnt/sedutil/releases

I guess you could compile lukefor's code in visual studio.

Just in case, I believe the windows command line where you execute sedutil must have root privileges. That may be the reason why it threw an error

Hi

I have executed this with administrator privileges only even then same issue. Will check any pre-requisites needs to be compiled or executed before executing the sedutil-cli binary

Thanks

[mallikarjunasai995]

Hi @r0m30 @dtasupport @maenpaa24

The same issue is not seen when we loaded the OS with GPT partition for both Linux and Windows Operation Systems

Now the drives were detecting as SED drives with GPT partition.

Thanks