Does jumper "capping" the disk size destroy partitions?

[ecto]

Hello,

Quick scennario:
User takes an 80GB disk, changes the jumper setting not realizing it's
the setting that caps the disk size to 32GB.
He then reverts the jumpers and re-installs the disk.
The disk that used to contain an operating system and data now does not
boot.
Disk manager shows two partitions. One is the "capped" 32GB partition,
and the rest shows as unallocated.

Does this mean the partition was permanently rendered unbootable?
Can this be reverted?

Unfortunately I do not have any specs for that particular disk.

Any helpful ideas would be welcome.

thanks,

ecto

 

[CJT]

Hello,

Quick scennario:
User takes an 80GB disk, changes the jumper setting not realizing it's
the setting that caps the disk size to 32GB.
He then reverts the jumpers and re-installs the disk.
The disk that used to contain an operating system and data now does not
boot.
Disk manager shows two partitions. One is the "capped" 32GB partition,
and the rest shows as unallocated.

Does this mean the partition was permanently rendered unbootable?

Define "permanently."

Can this be reverted?

How much are you willing to spend?

 

[Rod Speed]

Quick scennario:
User takes an 80GB disk, changes the jumper setting not
realizing it's the setting that caps the disk size to 32GB.
He then reverts the jumpers and re-installs the disk.
The disk that used to contain an operating system and data now does not boot.
Disk manager shows two partitions. One is the "capped" 32GB partition,
and the rest shows as unallocated.

Does this mean the partition was permanently rendered unbootable?

Nope, you can certainly wipe the drive, partition it again and reinstall everything.

Can this be reverted?

Probably not easily without a reinstall.

 

[Yousuf Khan]

Hello,

Quick scennario:
User takes an 80GB disk, changes the jumper setting not realizing it's
the setting that caps the disk size to 32GB.
He then reverts the jumpers and re-installs the disk.
The disk that used to contain an operating system and data now does not
boot.
Disk manager shows two partitions. One is the "capped" 32GB partition,
and the rest shows as unallocated.

Does this mean the partition was permanently rendered unbootable?
Can this be reverted?

The disk is not unbootable, it certainly still has the 32GB capped
partitition which can still be made bootable. However whatever data you
had in the original 80GB uncapped partition is now probably gone.

Yousuf Khan

 

[Folkert Rienstra]

Quick answer re subject title: No

but ......

Hello,

Quick scennario:
User takes an 80GB disk, changes the jumper setting not realizing it's
the setting that caps the disk size to 32GB.
He then reverts the jumpers and re-installs the disk.

The disk that used to contain an operating system and data

How many and what size partitions?

now does not boot.

Define "does not boot".

Disk manager shows two partitions.
Oh?

One is the "capped" 32GB partition,

It's either a 32 GB partition or it is a capped partition of different size,
what is it.

and the rest shows as unallocated.

So what's the second (partition)?

Does this mean the partition was permanently rendered unbootable?

What/which partition?

Can this be reverted?

Clearly depends on what the problem is, which isn't at all clear.