Page 1 of 1
[AHCI] identification data has no Model and Size on real hw
Posted: Sun Jan 22, 2023 9:35 am
by nifanfa
Tested on real hardware. BIOS ahci version is set to ahci 2.0
As you can see. the second last value is 0xA5 that means the identify data is correct.
But the Model name is filled with 0x20 and both offset 120(ATA_IDENT_MAX_LBA) and 200(ATA_IDENT_MAX_LBA_EXT) are zero
Even the identify data doesn't looks right. but it reads the disk correctly
and the identication look working on VMware
Re: [AHCI] identification data has no Model and Size on real
Posted: Sun Jan 22, 2023 9:43 am
by nifanfa
Is there any way except identify the disk to get the size of disk? and Model?
Re: [AHCI] identification data has no Model and Size on real
Posted: Sun Jan 22, 2023 7:04 pm
by Octocontrabass
nifanfa wrote:But the Model name is filled with 0x20
Your photo has too much information cut off to be certain, but it looks like the model name is "Hoodisk SSD" (6F 48 64 6F 73 69 20 6B 53 53 20 44).
nifanfa wrote:and both offset 120(ATA_IDENT_MAX_LBA) and 200(ATA_IDENT_MAX_LBA_EXT) are zero
Your photo has too much information cut off to tell what values are in these words.
Re: [AHCI] identification data has no Model and Size on real
Posted: Sun Jan 22, 2023 11:46 pm
by nifanfa
Octocontrabass wrote:nifanfa wrote:But the Model name is filled with 0x20
Your photo has too much information cut off to be certain, but it looks like the model name is "Hoodisk SSD" (6F 48 64 6F 73 69 20 6B 53 53 20 44).
nifanfa wrote:and both offset 120(ATA_IDENT_MAX_LBA) and 200(ATA_IDENT_MAX_LBA_EXT) are zero
Your photo has too much information cut off to tell what values are in these words.
thank you. i think my struct was wrong.
Re: [AHCI] identification data has no Model and Size on real
Posted: Mon Jan 23, 2023 12:31 am
by nifanfa
i found that sometimes the Signature (offset 510) is not 0xA5 so on that time the Model name and maxlba will be invalid value
Re: [AHCI] identification data has no Model and Size on real
Posted: Mon Jan 23, 2023 12:43 am
by Octocontrabass
You should still be able to read the model name and maximum LBA even when the Checksum Validity Indicator is not 0xA5. It sounds like there's a problem somewhere in your driver.