maxtor 200GB only 137.4G in bios. flashin doesn't work

[DavidNL]

Hi, I'm David, I joined this forum just now. I'm certainly not an expert, but I know enough to get by building and installing pc's. However, I've come across the same problem as mentioned before... That is to say - a friend of mine just bought a new k8nf-9 with a Maxtor diamondmax 10 200GB SATA disk. I helped him build and install... but... only 137.4G. I really don't know why, I've flashed the bios to latest version but that doesn't do any good! So help or suggestions will be appreciated! I've read the other thread about this problem, but doesn't seem to have a solution since june?

p.s. the problem wouldn't by any chance be solved if I install XP /sp2 would it? Since the post originally only sees 137.4G?

please help!

 

[mainegeek]

DavidNL,
The 137gig limit is probably caused by the OS being used
ie: Win98,WinME.

 

[Freestone]

See answers to your post in thread751-1069651

 

[firewolfrl]

Does the drive read the correct size in the Bios?

 

[DavidNL]

Thanks for reacting so soon. But it's certainly not an OS problem, since the OS isn't installed yet. What I ment with last sentence of previous post is that the sys. bios doesn't recognise the full 200GB... So Windows will automatically copy this info from bios, right? Anyway... I've done some research in the mean time and I've grown a little wiser - however my problem stays unsolved. The k8nf-9 should certainly support lba48 bit, plus I've flashed bios to latest version as mentioned before. So... Strange huh? Any additional help would surely be appreciated!

 

[DavidNL]

p.s. Thanks Freestone, but that isn't the solution to my problem. I should mention that I formatted the (sata)drive with Maxblast4 (Maxtor program) so It has nothing to do with XP installation. Bios doesn't see it right. Beginning to think the disk may be faulty...

 

[Freestone]

I realized after posting that you described a different problem than your post in the other thread. Any chance you can try the drive in another system? There are no jumpers on the drive than would limit its capacity? I doubt it, but I have to ask.

 

[firewolfrl]

Hmmm????
SATA controllers are set up to see large disk drives at 150 ATA. I think it may be a jumper on the drive. but if not then you should call the MB manufacturer and see if there are any issues with that model drive and the MB.
it doesn't hurt to call maxtor too.

 

[cdogg]

I can guarantee you that with a motherboard that new, the BIOS is not the problem. But here's your predicament:

137.4GB is the exact limit of 28-bit LBA.

The problem, however, is that the SATA interface does not have the 28-bit limitation. This whole conversation about

http://www.48bitlba.com

strictly applies to IDE devices. Therefore, as freestone mentioned, I suspect that there is a jumper on the drive limiting it to 28-bit LBA for compatibility with older motherboards. See this FAQ:

http://www.48bitlba.com/faq.htm#FAQ5

Also be aware that a 200GB drive specification from a hard drive manufacturer is actually 186.26GB.

~cdogg
"Insanity: doing the same thing over and over again and expecting different results." - Albert Einstein
[tab][navy]For general rules and guidelines to get better answers, click here:[/navy] faq219-2884

 

[DavidNL]

Thank you all...

I already thought about the jumper-scenario my self. But too bad, no jumpers. Actually, there are only two pins on the disk -- I doubt if it's wise to put a jumper on them as it might damage the disk? And wouldn't it be strange that if the drives capacity is limited, there's no documentation about that?

And I was one step ahead of you... I already mailed Maxtor and the manufacturer of the mobo. Looks like they're puzzled too...

CDOGG, thanks for enlightening me on the subject of sata and 48bit lba. Is it verified, by the way? If so, that's one option to cross out. thanks again, all of you (for being so helpfull to a newcomer) and any fresh ideas are still welcome...

 

[cdogg]

Well, 48-bit LBA does apply to SATA drives when it comes to the OS. You have to be using Windows 2000 SP3 (or later) or WinXP SP1 (or later).

It does not apply to the BIOS since the first SATA motherboards came out long after the 48-bit LBA issue was addressed. Besides, your motherboard is much, much too recent to be subject to the 28-bit LBA debate.

Call Maxtor and see if the wrong setting in the MaxBlast utility could have caused the issue, or whether you should be looking for a jumper. I realize that you already "mailed" them, but it wouldn't hurt to get a second opinion, especially over the phone so they can ask questions while you explain the issue.

~cdogg
"Insanity: doing the same thing over and over again and expecting different results." - Albert Einstein
[tab][navy]For general rules and guidelines to get better answers, click here:[/navy] faq219-2884

 

[firewolfrl]

I have to agree with cdogg

 

[wolluf]

have you tried removing the partition you created with maxblast and creating a new one with for example XP install's tools? (as long as you have at least a SP1 install CD - you can create one with slipstreaming if needed). Or if necessary, running something like killdisk to completely wipe the drive and start again (as it sounds like something has got set in the partition table which shouldn't have).

 

[DavidNL]

wolluf: yes I have tried that. And an error in the partion table is something I haven't thought of yet. Worth a try wiping it. Thanks!

 

[cdogg]

The size of the hard drive shown on the POST screen does not reflect file allocation table information (it reads sectors, heads, cylinders, etc).

Therefore, I don't think it matters how you do the partitioning. For example, inserting an unformatted, brand new hard drive should show up correctly in the BIOS and on the POST screen.

Are we absolutely sure you're seeing 137.4GB on the POST screen?

The reason why I ask is because the POST screen typically rounds to the nearest GB.

~cdogg
"Insanity: doing the same thing over and over again and expecting different results." - Albert Einstein
[tab][navy]For general rules and guidelines to get better answers, click here:[/navy] faq219-2884

 

[DavidNL]

It is the post which says 137.4GB, it's sort of an built-in sata function in bios.

I've hooked the bad puppy up in my own system and no luck... also 137.4GB in Maxblast and about the same in XP/sp2.

So, we're taking the drive back to the store to get another one of the same make to check that one. I'll let you know what happens next...

 

[DavidNL]

p.s. my system (test case) is a MSI KT6 Delta-FISR

 

[garebo]

Just wondering if you might try to run the "write zero" to the hard drive that comes with maxtor diagnostics. I have found that to solve a few hard drive problems in the past, although, to be honest, i havent used it for this specific problem.
Another way might be to use a win98se boot disk and try to fdisk and format the drive that way. Even though it would be fat32 perhaps your bios might then see if as 185 gigs as it should. Then you could reformat it NTFS using windows wx. This may not work with sata, not sure on this part.
But i do know that the "write zero" program has helped me out a lot and so has the win98 boot disk\fdisk\format. Just not for this exact issue, but worth a try?



Good advice + great people = tek-tips

 

[DavidNL]

My problem is solved. Thank you for all your help but it was a faulty drive! Go figure... But it's working fine now.

Thanks!

David

 

[garebo]

How did it get from faulty to fixed?


Good advice + great people = tek-tips