Re: Samsung hdd problem
- From: Patty <patty1515NOSPAM@xxxxxxxxx>
- Date: Tue, 21 Mar 2006 12:51:44 -0500
On Tue, 21 Mar 2006 11:39:57 -0500, hdrdtd wrote:
"Patty" <patty1515NOSPAM@xxxxxxxxx> wrote in message
news:1jb83kmz70wf$.1qsrumlxse0h3.dlg@xxxxxxxxxxxxx
On Tue, 21 Mar 2006 05:23:44 GMT, Paul wrote:
In article <d_GTf.73575$fe6.71917@xxxxxxxxxxxxxxxxxxxxxx>,
no@xxxxxxxxxxxx
(andrei.husar) wrote:
i got a samsung SV0411N hdd, and the problem is that it only sees 5 gb
from 40. I've tryed everything I know and any of my friends know. do
not know what to do with it. could use some help, cause i do not want
to throw it away. the last thing that i can do is to find out the
exact number of cylinders, numbers of heads, and everything else, to
fix it from BIOS. help please
I've had a Maxtor drive failure, where the controller claimed the
disk was 10GB, when it was actually 40GB. It was a symptom that
the controller could no longer get critical information from the
platters, implying a serious problem.
There are certain "magic" size limits, that have occurred as drive
capacities have grown over the years. The 5GB number does not
ring any bells, and this sound more like the controller cannot
tell how many platters it has any more. This article lists
some of the "magic" sizes:
http://www.win.tue.nl/~aeb/linux/Large-Disk-4.html
Paul
I just put a new WD 80GB hard drive in an older system. The BIOS reported
the size as 14GB. The hard drive is fine and with the WD DataLifeguard
Overlay, the drive is reported correctly in the OS as 80GB. Why did the
BIOS choose 14GB? Since there is no 14GB "magic" size limit, it may be
picking up some kind of cylinder/head reading from the hard drive, and
being confused is reporting what it thinks it should be with those
readings. That's all I can figure. We've determined that the BIOS more
than likely has a limitation of 32GB, but I don't think that it means that
it will report every hard drive over 32GB as that amount. You can use an
alternate jumper setting on most drives to force it to read 32GB, which is
why I think that have that jumper setting available.
Patty
Patty, you don't mention what OS you were using with the 80gig, but be aware
that older versions of the Fdisk utility had a 64gig bug where if the drive
was larger than 64gig, the system would report the size as the difference
between the size and 64gig. 80gig - 64gig = 78gig
Newer versions of Fdisk don't have that problem anymore.
I'm using Windows XP Pro SP2. I'm wondering about your math though...
80-64=16 in my book. ;) There is a discrepency about how hard drive size
is reported in any case. The manufacturer reports the size in decimal
numbers and calls it an "80GB" HD, but when you format it, it's less,
because 1 kilobyte is not really 1,000 bytes, it is actually 1,024 bytes
because it's binary. As hard drives get larger, the difference shows up
even more. In my case, XP Pro reports the size to be a little less than
80GB but it's because of the conversion from decimal to binary that makes
the difference. My other system with a "120GB" hard drive, XP Pro reports
approx. 111.78GB of available space on the full drive.
Patty
.
- Follow-Ups:
- Re: Samsung hdd problem
- From: hdrdtd
- Re: Samsung hdd problem
- References:
- Samsung hdd problem
- From: andrei.husar
- Re: Samsung hdd problem
- From: Paul
- Re: Samsung hdd problem
- From: Patty
- Re: Samsung hdd problem
- From: hdrdtd
- Samsung hdd problem
- Prev by Date: Re: Samsung hdd problem
- Next by Date: Re: Setting up SATA HD and CD ROM - How to connect ide cable for CD-ROM
- Previous by thread: Re: Samsung hdd problem
- Next by thread: Re: Samsung hdd problem
- Index(es):
Relevant Pages
|