-
Notifications
You must be signed in to change notification settings - Fork 61
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
Failed to Restore the Max LBA #114
Comments
nick-hayhurst, |
Loos like the command is failing as the drive fails to report native Max LBA. Sending ATA Read Native Max Address Ext CDB:
0x00 85 07 20 00 00 00 00 00 00 00 00 00 00 40 27 00 This command failed and returned command aborted Sending command with send_IO Sense Data Buffer:
0x00 72 0B 00 00 00 00 00 0E 09 0C 01 04 00 00 00 00 Sense Key: Bh = Aborted Command Command Time (us): 74.10 Read Native Max Address Ext returning: ABORTED Failed to restore the max LBA! At this point we don't know what was the original max lba of the drive and thus we can not reset the drives max lba to the original one. The failure of Read Max Address Ext (which is unexpected) is the main reason of the observed issue. |
nick-hayhurst, |
Hi! Thanks for the response! I am connected by a SAS HBA (LSI) - other devices of similar types don't show this issue when tested or when issuing Read Max Address. Let me know if you need more information! |
Interesting! Is there a way to do so within openSeaChest? Thanks so much! |
I doubt you can do it within openSeaChest. You probably need to do it in bios. |
Well, SeaChest_Security has --revert method and --revertSP method. But those will revert the drive back to factory settings, at the same time all data on the device will be lost. Also you will need the PSID/admin password and your device must support those methods. Once all security is disabled, then you should be able to set the max address of the drive. There are other tools out on GitHub that would get you more functionality for the security and would have more options to access user lBA's. |
Adding detection of support and enabled HPA security extension feature. [Seagate/openSeaChest#114] Signed-off-by: Tyler Erickson <[email protected]>
I'm catching up on this issue. |
It seems that the command is failing because the drive is not reporting the native Max LBA (Logical Block Address). The tool attempts to get the max native LBA by issuing the "Read Max Address Ext" command, but this command fails and returns "command aborted." The last command issued is: Sending ATA Read Native Max Address Ext This command fails and returns "command aborted." The sense data indicates an aborted command with no additional sense information. The failure to get the Max LBA is causing the observed issue, and it's mentioned that the drive is connected via a SAS HBA (LSI). Other devices of similar types don't exhibit this issue when tested. In summary, the problem seems to be specific to this drive and its connection via the SAS HBA, as other similar devices connected in the same way do not encounter this problem |
The latest release (v23.12) has had some updates to the If you can try this new build and share the verbose logs, I will take a look and see if this may help determine what is going on. |
Hi All,
I am attempting to work with a HPA on a Samsung (Dell EMC) ATA (SATA) SSD.
I am using openSeaTools on Ubuntu 22.04.
When trying to read the Native Max Address of this drive, it reports "Not Reported", see below Inquiry Log.
This clearly states the devices supports the HPA, however it is not reporting the Native Max Address...
I ran the openSeaChest
--restoreMaxLBA
command which returned the below:With verbosity set to 4:
Looking at the closing command result, which appears to be showing as "ABORTED".
Any ideas? :)
The text was updated successfully, but these errors were encountered: