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

Unlock on SSC Enterprise fails with INVALID_PARAMETER #29

Open
bluecmd opened this issue May 31, 2021 · 0 comments
Open

Unlock on SSC Enterprise fails with INVALID_PARAMETER #29

bluecmd opened this issue May 31, 2021 · 0 comments
Labels
bug Something isn't working

Comments

@bluecmd
Copy link
Collaborator

bluecmd commented May 31, 2021

Not sure about this one right now, so filing an issue:

$ sedlockctl  /dev/sde unlock-all
2021/05/31 19:05:13 Read unlock range 0 failed: method returned status INVALID_PARAMETER
2021/05/31 19:05:13 Write unlock range 0 failed: method returned status INVALID_PARAMETER
2021/05/31 19:05:13 Read unlock range 1 failed: method returned status NOT_AUTHORIZED
2021/05/31 19:05:13 Write unlock range 1 failed: method returned status NOT_AUTHORIZED
2021/05/31 19:05:13 Read unlock range 2 failed: method returned status NOT_AUTHORIZED
2021/05/31 19:05:13 Write unlock range 2 failed: method returned status NOT_AUTHORIZED
2021/05/31 19:05:13 Read unlock range 3 failed: method returned status NOT_AUTHORIZED
...

The only other Set I have is the MBRControl which my SSC Enterprise disk does not implement, so can't use it to check if the Set() is generically bad for Enterprise or specifically for MBRControl.

@bluecmd bluecmd added the bug Something isn't working label May 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant