Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sedutil for SAS drives has inconsistent behavior for --scan and --printDefaultPassword #368

Closed
ganeshram93 opened this issue Aug 10, 2021 · 1 comment

Comments

@ganeshram93
Copy link

ganeshram93 commented Aug 10, 2021

I tried the sedutil-cli for multiple SAS drives and I see inconsistent output every time I run it.

Issue 1:
Command used: sedutil-cli --scan
Output 1: (expected output)
root@ssd-Z270X-Gaming-K7:~/ssd/sedutil_backup# ./sedutil-cli --scan
Scanning for Opal compliant disks
/dev/sda E xyz xyz
/dev/sdb No
/dev/sdc No

Output 2: (failed)
root@ssd-Z270X-Gaming-K7:~/ssd/sedutil_backup# ./sedutil-cli --scan
Scanning for Opal compliant disks
/dev/sda No
/dev/sdb No
/dev/sdc No

Output 3: (failed)
root@ssd-Z270X-Gaming-K7:~/ssd/sedutil_backup# ./sedutil-cli --scan
Scanning for Opal compliant disks
/dev/sda No xyz xyz
/dev/sdb No
/dev/sdc No

Issue 2:
Command used: sedutil-cli --printDefaultPassword /dev/sda

Output 1: (failed)
root@ssd-Z270X-Gaming-K7:~/ssd/sedutil_backup# ./sedutil-cli --printDefaultPassword /dev/sda
One or more header fields have 0 length
Properties exchange failed
Command failed on send 255
Command failed on exec 255
Session start failed rc = 255
Unable to start Unauthenticated session /dev/sda
Command failed on send 255
Command failed on exec 255
EndSession Failed
unable to retrieve MSID

Output 2: (failed)
root@ssd-Z270X-Gaming-K7:~/ssd/sedutil_backup# ./sedutil-cli --printDefaultPassword /dev/sda
sedutil-cli: Common/DtaDevEnterprise.cpp:168: DtaDevEnterprise::DtaDevEnterprise(const char*): Assertion `isEprise()' failed.
Aborted (core dumped)

Output: (failed)
root@ssd-Z270X-Gaming-K7:~/ssd/sedutil_backup# ./sedutil-cli --printDefaultPassword /dev/sda
One or more header fields have 0 length
Session start failed rc = 136
Unable to start Unauthenticated session /dev/sda
One or more header fields have 0 length
EndSession Failed
unable to retrieve MSID

However, when I tried with NVMe drives, it works well.
Is this a known issue / is there a fix available?

@ganeshram93 ganeshram93 changed the title sedutil for SAS drives - inconsistent behavior scan and printDefaultPassword sedutil for SAS drives - inconsistent behavior for --scan and --printDefaultPassword Aug 10, 2021
@ganeshram93 ganeshram93 changed the title sedutil for SAS drives - inconsistent behavior for --scan and --printDefaultPassword sedutil for SAS drives has inconsistent behavior for --scan and --printDefaultPassword Aug 10, 2021
@ganeshram93
Copy link
Author

Closing it.
It was an HBA adapter issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant