LBA problem on Maxtor Fireball drive

[lostinspace]

Hi,
I recently imaged a Maxtor drive. The LBA on the label is 80293248 but the LBA reported in bios was more like 7929320. The file system (NTFS) cannot be seen under normal conditions however after scanning in R-Studio and getdataback etc I can see all the relevant files and folders.
My problem is that I cannot open the vast majority of files and the ones that do are missing data (confirmed with hex editor). This problem disappears if I extract RAW data but of course I lose all the file names and folders etc.
Is the drive now effectively looking in the wrong place for information due to the reduced LBA size?
Bear in mind that the drive was originally formatted with a single and full NTFS partition back in the days when it was healthy and so I’m assuming all the MFT records reflect this and not the current LBA size.

I was wondering if the file structure be restored by editing the MFT to reflect these changes or am I on completely the wrong track with this?

[Starling]

Try HDD Capacity Restore 1.1 to reset HPA.

[BGman]

Try HDD Capacity Restore 1.1 to reset HPA.

Why not MHDD / NHPA command?

[Starling]

They guy is already lost-in-space. Do you want him also to get lost-in-dos?

[lostinspace]

Hardly, I use MHDD all the time

The drive genuinely believes that 78165359 is the full LBA. Any attempt to uncut the drive makes no difference.

The whole issue was not helped by it visiting another data recovery company first. They were unable to get anything off it. They did however succeed in losing a couple of screws of the PCB.

[pcimage]

Do you have PC3000, to check the transalator?

[N.C.]

Hardly, I use MHDD all the time

The drive genuinely believes that 78165359 is the full LBA. Any attempt to uncut the drive makes no difference.

The whole issue was not helped by it visiting another data recovery company first. They were unable to get anything off it. They did however succeed in losing a couple of screws of the PCB.

If the drive was at one dr company, maybe they have messed up the SA and this is why the NHPA not works...
If i have no right, and the drive is in HPA mode, you can image it under linux, because the kernel detect the HPA setting, and bypass this to reach the total capacity.

I am not sure it works form wich kernel version....

Janos

[Starling]

78165359 is better than 7929320. Were you able to restore it to 78165359?