Re: Samsung hdd problem


"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.


.

Relevant Pages

  • Re: Loss of SCSI boot after CMOS battery replacement
    ... result of my old motherboard BIOS after all. ... controller takes priority over the SCSI ... IDE first to SCSI first. ... SCSI drives and Win98. ...
    (comp.periphs.scsi)
  • Re: What on earth is happening - long
    ... Report Back. ... I had all the latest bios updates and driver files ... >> drives, which XP would recognise. ... >> board on bootup and when he tried to install XP, ...
    (microsoft.public.windowsxp.general)
  • Re: What on earth is happening - long
    ... Report Back. ... I had all the latest bios updates and driver files ... >> drives, which XP would recognise. ... >> board on bootup and when he tried to install XP, ...
    (microsoft.public.windowsxp.basics)
  • Re: Drives missing at boot
    ... All the drives are always reported by BIOS at boot time. ... RAID1 on the 4 port controller and the RAID0, ... 82801JI 4 port SATA IDE Controller ...
    (Linux-Kernel)
  • Re: install problems for freeBSD 6 on tyan i7520
    ... > and a CD connected through a separate controller channel. ... > I have tried many scenarios for connecting a single hard drive, ... The BIOS sees it. ... > drives seem to be there named just as the boot loader and BIOS see them. ...
    (freebsd-current)