August 15th, 2023, 11:28
August 16th, 2023, 3:34
August 16th, 2023, 3:58
August 16th, 2023, 5:32
August 17th, 2023, 11:36
fzabkar wrote:I don't think it makes any difference, but just FYI, the drive appears to have been installed in an external enclosure with a 4KB sector size.
Could this drive be one of those which had a jumper for offset-by-one mapping??? This was how WD's older AF models enabled Win XP to maintain physical sector alignment when using LBA 63 (shifted to LBA 64) as the boot sector of the first partition. When you stick such a drive in a 4KB enclosure, the offset would be multiplied by 8.
August 17th, 2023, 11:40
pepe wrote:wanted to edit my prev post, but could not, so:
i would check 148 if it has entries that correlate to the shifts you experience. You will need to identify some more shift points i think.
It's been quite some years since i had such issues with diablo drives, so my memories are pretty faint, it was well before it was common knowledge that 148 stores ranges that cause shifts, so i had to research it. What i recall is that my data might not have been shifted but the head map in DE was shifted relative to the real working values.
It is also possible that entries are missing from 148, let's say, it is more probable than not.
as for the offset jumper: if that was an issue, the offset would be consistent and no problems would arise at all. imo.
pepe
August 17th, 2023, 12:10
fzabkar wrote:I don't think it makes any difference, but just FYI, the drive appears to have been installed in an external enclosure with a 4KB sector size.
Could this drive be one of those which had a jumper for offset-by-one mapping??? This was how WD's older AF models enabled Win XP to maintain physical sector alignment when using LBA 63 (shifted to LBA 64) as the boot sector of the first partition. When you stick such a drive in a 4KB enclosure, the offset would be multiplied by 8.
Powered by phpBB © phpBB Group.