|
Home > Archive > Cheap Linux Hardware > July 2006 > Hard drive limit?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| ***** charles 2006-07-14, 1:14 pm |
| Hi all,
I have a new ASROCK K7VM3 motherboard and a
Maxtor DiamonMax Plus 8 40G ATA/133 HDD
6E040L0 which passes all the diag tests.
When I go to the Maxtor knowledge base they say
to get a new controller card or use their overlay soft
ware. No other solutions are listed.
Problem is that the hd only shows up as a 33G
drive from the bios. The limitation jumper is not set
so it should show 40G. I have
used the "wipe drive" feature in the Maxtor diag soft
ware and it still didn't fix this. I know that the drive
should show up as 40G but I can't get it to do this.
I did have the drive in an older motherboard that had
the 33G limitation and ever since then I haven't been
able to get the drive back up to the 40G limit. How
do I fix this since I have done it with others just not
Maxtor?
thanks,
charles....
| |
| Larry Gagnon 2006-07-14, 1:14 pm |
| On Fri, 14 Jul 2006 14:31:15 +0000, ***** charles wrote:
> Hi all,
>
> I have a new ASROCK K7VM3 motherboard and a
> Maxtor DiamonMax Plus 8 40G ATA/133 HDD
> 6E040L0 which passes all the diag tests.
> When I go to the Maxtor knowledge base they say
> to get a new controller card or use their overlay soft
> ware. No other solutions are listed.
> Problem is that the hd only shows up as a 33G
> drive from the bios.
Did you actually go into the BIOS and set the drive to "Auto"? and then
save and reboot?
| |
| ***** charles 2006-07-14, 1:14 pm |
| "Larry Gagnon" <lggagnon@fakeuniserve.com> wrote in message
> news:pan.2006.07.14.14.50.07.300991@fakeuniserve.com...
> On Fri, 14 Jul 2006 14:31:15 +0000, ***** charles wrote:
>
>
> Did you actually go into the BIOS and set the drive to "Auto"? and then
> save and reboot?
Yes. Drive still comes up with 33G limit.
charles.....
| |
| ***** charles 2006-07-14, 1:14 pm |
| "***** charles" <shultzjrX@sbcglobal.net> wrote in message
> news:VzOtg.48643$VE1.33962@newssvr14.news.prodigy.com...
> "Larry Gagnon" <lggagnon@fakeuniserve.com> wrote in message
>
> Yes. Drive still comes up with 33G limit.
Called Maxtor tech support, downloaded MaxBlast and this fixes it.
later.........
| |
| Vilmos Soti 2006-07-14, 1:14 pm |
| "***** charles" <shultzjrX@sbcglobal.net> writes:
> "Larry Gagnon" <lggagnon@fakeuniserve.com> wrote in message
>
> Yes. Drive still comes up with 33G limit.
>
> charles.....
What about ignoring it? Linux doesn't use the BIOS to access your
disk except at the very beginning at booting. Once I had an old
P133 computer, and the BIOS hanged at POST if the drive settings
were bigger than 8GB. Linux did recognize, partition, and use
the whole drive. Finally I just let the BIOS think it is only
8GB, so everyone was happy. One thing you might want to ensure
though. Ensure that the sector/track and the head count are
correct, and decrease the cylinder count in the BIOS to make it
happy.
Vilmos
| |
| ***** charles 2006-07-15, 1:14 pm |
| "Vilmos Soti" <vilmos@soti.ca> wrote in message
> news:lqirm0yyl4.fsf@vilmos.msmri.medicine.ubc.ca...
> "***** charles" <shultzjrX@sbcglobal.net> writes:
>
>
> What about ignoring it? Linux doesn't use the BIOS to access your
> disk except at the very beginning at booting. Once I had an old
> P133 computer, and the BIOS hanged at POST if the drive settings
> were bigger than 8GB. Linux did recognize, partition, and use
> the whole drive. Finally I just let the BIOS think it is only
> 8GB, so everyone was happy. One thing you might want to ensure
> though. Ensure that the sector/track and the head count are
> correct, and decrease the cylinder count in the BIOS to make it
> happy.
>
> Vilmos
Thanks for the response. I usually check out my hardware in a
DOS/Windows environment since I am much more familiar in that
arena. When the hardware list came up and said 33G when it should
have said 41G I wanted to correct it. M$ fdisk would only "see"
33G of the whole thing so when I MaxBlasted it, that fixed the problem.
MaxBlast has a utility built in that is called "set max size" that cured it.
Funny, the drive seemed to run a lot hotter before I reset it. Now it is
cooler. There seem to be a lot more utilities for stuff like this in the
DOS/Windows world.
Now that I am sure the drive is working properly, it passed all
the diags and when I put Ubuntu on it, if there are any problems, I
will know that they aren't caused by hardware.
thanks,
charles....
| |
| iforone 2006-07-15, 1:14 pm |
|
***** charles wrote:
> "Vilmos Soti" <vilmos@soti.ca> wrote in message
> Thanks for the response. I usually check out my hardware in a
> DOS/Windows environment since I am much more familiar in that
> arena. When the hardware list came up and said 33G when it should
> have said 41G I wanted to correct it. M$ fdisk would only "see"
> 33G of the whole thing so when I MaxBlasted it, that fixed the problem.
> MaxBlast has a utility built in that is called "set max size" that cured it.
> Funny, the drive seemed to run a lot hotter before I reset it. Now it is
> cooler. There seem to be a lot more utilities for stuff like this in the
> DOS/Windows world.
>
> Now that I am sure the drive is working properly, it passed all
> the diags and when I put Ubuntu on it, if there are any problems, I
> will know that they aren't caused by hardware.
>
> thanks,
> charles....
FWIW - my older Intel, PII mobo (circa 2000) only recognizes 65Gigs(?)
of my 80GB drive -- the 'updated' win98/me FDisk utility (d/l from
Microshaft's site) can recognize the full size of the 80GB, but my BIOS
still sees only 60 some-odd GBs (yes, the BIOS is the latest available
- circa 2000).
No bother to me, as long as the OSes (Debian Sid + Win98 dual boot)
can/does utilize the whole drive. My Debian install (as of now) happens
to be on the Orig WD drive that was new (9.1GB only) when the system
was made -- but I previously had Debian installed on the 80GB too.
I suspect different translation parameters (LBA) between HDD Manu and
their utilities -- on any drives newer, than say oh, ~1999, one
shouldn't need to enter the CHS in the BIOS, as these newer drives use
ZonedBit recording and LBA to address the locations/regions/tracks.
Therefore the AUTO setting (in the BIOS) should suffice for most every
drive (as long as the drive's *jumpers* are set correctly), as it's
onboard Controller will communicate that info to the BIOS.
Just my .02 ;-)
Regards
| |
| chuckcar 2006-07-15, 7:13 pm |
| "iforone" <floydstestemail@yahoo.com> wrote in
news:1152980625.559163.178380@35g2000cwc.googlegroups.com:
>
> ***** charles wrote:
> I suspect different translation parameters (LBA) between HDD Manu and
> their utilities -- on any drives newer, than say oh, ~1999, one
> shouldn't need to enter the CHS in the BIOS, as these newer drives use
> ZonedBit recording and LBA to address the locations/regions/tracks.
> Therefore the AUTO setting (in the BIOS) should suffice for most every
> drive (as long as the drive's *jumpers* are set correctly), as it's
> onboard Controller will communicate that info to the BIOS.
>
> Just my .02 ;-)
>
The *only* downside to that is a bit longer on boot while the bios ID's
the drive - can be quite a few seconds as opposed to immediate if the
CHS are entered.
> Regards
>
>
--
(setq (chuck nil) car(chuck) )
|
|
|
|
|