-
Notifications
You must be signed in to change notification settings - Fork 26
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
Readme does not work with nvme drives #2
Comments
I think you might be able to use the I also wrote this utility, but it doesn't quite implement the Lenovo algorithm so you'd need to make some changes (in |
Thanks for the reply! :)
I don't understand what it does, so I stop experimenting. :) I will need a backup solution anyway... Working on that... |
I've tried to use the lenovo password algorithm with the nvme program. It didn't work. Either they changed the algorithm or something else doesn't work. |
Hi, I got a new Lenovo T470 laptop in my workplace, which apparently has an nvme SSD (which I did not even know existed). I wondered what the HDD1 password BIOS setting was, so I got to your website and to this project. I wanted to try the first command in the readme, but that gives an error:
My hdparm is from Arch repo, and is the latest version (v9.56).
I wonder if this command could be somehow substituted with the
nvme
command in case of these nvme drives (see https://wiki.archlinux.org/index.php/Solid_State_Drive/NVMe).Now I found a post which seems to support that:
https://forum.manjaro.org/t/hdparm-not-getting-info-for-ssd-samsung-960-evo-m-2/35445/2
"hdparm expects IDE, libata and SCSI-ATA devices. NVMe is not any of those. If you want to get info about your NVMe device, install the nvme-cli tools."
I tried the above hdparm command on a sda device and it spits out some hexadecimal data.
I installed nvme-cli from AUR, but I wonder if there is a command which would produce the same (or similar, but usable) output, and whether this project can work with nvme drives in the first place.
If not, maybe it should be clarified in the readme. Thanks.
The text was updated successfully, but these errors were encountered: