Summat's not right.
 

Got a wee issue that could do with some advice. I've done a forum search under "137GB" and not been able to get an answer. However, if I've duplicated a thread, then apologies in advance.

I'm setting up a system at the moment. The motherboard is a SuperMicro P4DCE+ operating twin Zeon processors and an Intel 860 chipset, which is 48bit compatible.

The primary drive (master of 2.1 GB size) is loaded with Windows 2000 SP4, and has had the registry updated to incorporate "EnableBigLba". The secondary drive (slave) is a 160GB Hitachi Deckstar.

The issue is that the system BIOS recognises the the slave but only reports it as 137GB and windows does likewise. If I try to format the drive (NTFS) then I get the same - 137GB.

I realise that there's limitations regarding very large drives, but I know that the system is 48bit compatible - so there shouldn't be an issue, sigh.............!

Have I missed something obvious?

Cheers and Si thee

Re: Summat's not right.
 

At the risk of the obvious have you checked the jumpers on the drive to make sure they're not restricting the available space for "compatibility"?

Re: Summat's not right.
 

Did someone accidentally disable LBA support in the bios?
Look around the IDE controller options/ drive options should be there somewhere.

Re: Summat's not right.
 

whats the mobos bios date?

run this little test but if the bios does not see the correct size I think a flash maybe in order if you can find a new one that says it fixes this http://www.48bitlba.com/enablebiglbatool.htm this says it could be defined but not correctly set but im guessing this is what you have done already

Re: Summat's not right.
 

Finally got it sorted. To be honest with you, when I originally started this thread, I'd previously been on to SuperMicro technical support about this issue. They'd assured me that the BIOS version of my motherboard was "48bit" compatible and that all I had to do was install windows and update the registry to suit, I.e. there was absolutely no need to update the BIOS version.:erm:

Anyway, after trawling through the FAQ's (on the site) I finally found one that matched my problem - the answer (one liner) "update the BIOS to the latest version". :mad:

Looks like I was given duff gen from the start, sigh.......!

My thanks to all who responded.

Cheers and Si thee