Samsung <32Gb BIOS problem 1

[stormbind]

Hi,

I just moved a Samsung SV401 (40Gb) from one machine to another. I know nothing of the former computer, and it's now gone.

There is a utility on

http://www.samsunghdd.com

for setting up the drive for use on older motherboards with maximum disk size of 32Gb. I read this but it shouldn't apply.

Unexpectedly, the HDD jumpers were set for <32Gb BIOS fix. Looks like someone already used the above utility! I changed the jumper to regular slave, stuck it in my computer and booted (Forgot to check the CMOS setup at this time).

WinXP displayed a single FAT partition. I wanted 3x 13.3Gb NTFS partitions so deleted the large one. Then it dawned on me that it said 32Gb - meaning 8Gb was missing!

This motherboard supports Hard Drives upto 64Gb. I rebooted and went into the CMOS where auto-detection finds only 32Gb!

How do I get it back to 40Gb?

----------
Memoria mihi benigna erit qui eam perscribam

 

[micker377]

Pull the 32m limiting jumper. You'll have to use Fdisk to remove the old partitions/setup and re-partition the drive. You may find a "Non-DOS" partition, this was to hold "restore info" (if so, use the "remove the "Non-DOS" partition". The easiest way is to use a Win 98 emergency boot disk. Boot from the A: drive and choose "No CD".

 

[stormbind]

As explained in the opening post, pulling the 32Gb limiting jumper was the first thing I did - before the HDD was inserted into this PC.

The BIOS is still detects only 32Gb. WinXP "Disk Management" currently says there is 31.49Gb unallocated space. I would make partitions, but I want the full 40Gb.

The computer doesn't seem able to see the full capacity of the drive. It's as though the 32Gb limit has somehow been made permanent

----------
Memoria mihi benigna erit qui eam perscribam

 

[micker377]

It HAS been made permanant by Fdisk when it was first created. It can only be "fixed" by re-partitioning it with Fdisk.

 

[stormbind]

Sorry, but I don't follow. I am familiar with Microsoft FDISK for DOS, but have not seen it in years - nor can I find it anywhere in WinXP. It is not included when creating a DOS boot disk.

The only (similar) utility I currently have is Microsoft Disk Management, built into WinXP (right click 'My Computer' and select 'Manage'). It supports partitions and dynamic drives.

From that GUI: There are currently no partitions on the drive. There is 32Gb of unalocated space.

From the BIOS: 32Gb storage capacity detected. This ignores partitions.

Your assumption goes no way to explaining why the BIOS, which ignores partitions, auto-detects only 32Gb.

Where in WinXP can I find a copy of fdisk?

----------
Memoria mihi benigna erit qui eam perscribam

 

[micker377]

Re-read my first post. I said you would have to use a Win 98 Emergency Boot Disk to get the full use of Fdisk. Win XP only works with a "bare" disk, you have to repair the partitions already created on the drive.

 

[wolluf]

try

http://www.killdisk.com/features.htm

to really wipe the disk & then start again.

 

[Freestone]

http://www.samsung.com/Products/HardDiskDrive/utilities/index.htm

It looks as if you may want to create the Ontrack Disk Manager diskette and run it with the 32GB Limiting jumper removed. This should refresh the overlay software that was placed on the drive and reassert the full 40GB partitioning information.

An alternative looks to be a low-level format with Samsung's tool in order to get rid of the overlay software.

 

[stormbind]

Thanks,

I did as you suggested. It actually installed the overlay software, which puts up a blue banner with the DMI pool message after POST. This wasn't there before so it seems the previous setup had the 32Gb limiting jumper + no overlay.

It's now giving me 40Gb.

My motherboard is still detecting only 32Gb. This makes no sense given that Gigabyte clearly state that the board supports more than this.

Anyway, it's working, which is good!

If anyone has an idea for why my BIOS isn't behaving as expected, I would be grateful for your input.

----------
Memoria mihi benigna erit qui eam perscribam

 

[wolluf]

So did you try killdisk?