I had this problem after I enabled the '4092-cylinder limit' jumper on my
Maxtor drive, because my BIOS (at that point) hung with a drive over 4092
cylinders. I flashed the BIOS afterwards, but forgot about the jumper,
because windows/linux both (somehow) saw the full geometry of the drive.
On Thu, 31 May 2001, Darian Lanx wrote:
I had this problem after I enabled the '4092-cylinder limit' jumper on my
Maxtor drive, because my BIOS (at that point) hung with a drive over 4092
cylinders. I flashed the BIOS afterwards, but forgot about the jumper,
because windows/linux both
This should be 60034905 = 3737*255*63
No, that value is correct, has to do with internals how sysctl calculates the
offsets, but that is an linux issue I am aware off
This should be 59554/16/63 and you do not get all drive space.
As I mentioned, I am aware, that I do not get all drive