Partitioning abve the 1024 boundary ???

  compumac 10:54 15 Oct 07
Locked

Windows XP - I am resizing the partitions on one desktop and also a laptop using Partition Magic V8. When the new size for ‘C’ is entered the dialogue comes up “resizing or moving an operating system partition beyond the 1024 cylinder boundary may make the computer unbootable”. I believe that in the past I have ignored this on my other PC’s and everything has worked OK. As one of these machines has valuable data on it I am reluctant to proceed with the resizing without seeking advice. (Albeit the data is backed up anyway).
Any advice welcomed.

  compumac 13:41 15 Oct 07

I have now looked at other forums and found only two references to "resizing or moving an operating system partition beyond the 1024 cylinder boundary may make the computer unbootable” These both appeared to be referring to 70/80Gb capacity hard discs.
Any thoughts out there?

  compumac 16:57 15 Oct 07

There must be someone out there with knowledge of partitioning?

  DieSse 17:04 15 Oct 07

Useful writeup here click here

  compumac 18:12 15 Oct 07

Thanks for that, although I also had just come across it and it might very well be that the inference that resizing might only refer to Dos V6.22 or thereabouts. I really need to be sure as otherwise it could be quite disasterous

  Fruit Bat /\0/\ 18:33 15 Oct 07

You should be able to resize to what ever you wish.

Bios used to be the limiting size as to what it would recognise, but this could be got round with overlay software.

Your limits error may come from:
Physical partition limits

In the design of Logical Volume Manager (LVM), each logical partition maps to one physical partition (PP). And, each physical partition maps to a number of disk sectors. The design of LVM limits the number of physical partitions that LVM can track per disk to 1016. In most cases, not all of the 1016 tracking partitions are used by a disk.
When this limit is exceeded, you might see a message similar to the following:

0516-1162 extendvg: Warning, The Physical Partition Size of PPsize requires the
creation of TotalPPs partitions for PVname. The limitation for volume group
VGname is LIMIT physical partitions per physical volume. Use chvg command
with -t option to attempt to change the maximum Physical Partitions per
Physical volume for this volume group.

Where:

PPsize
Is 1 MB to 1 GB in powers of 2.
Total PPs
Is the total number of physical partitions on this disk, given the PPsize.
PVname
Is the name of the physical volume, for example, hdisk3.
VGname
Is the name of the volume group.
LIMIT
Is 1016 or a multiple of 1016.

This limitation is enforced in the following instances:

1. When creating a volume group using the mkvg command, you specified a number of physical partitions on a disk in the volume group that exceeded 1016. To avoid this limitation, you can select from the physical partition size ranges of 1, 2, 4 (the default), 8, 16, 32, 64, 128, 256, 512 or 1024 MB and use the mkvg -s command to create the volume group. Alternatively, you can use a suitable factor that allows multiples of 1016 partitions per disk, and use the mkvg -t command to create the volume group.
2. When adding a disk to a pre-existing volume group with the extendvg command, the new disk caused the 1016 limitation violation. To resolve this situation, convert the existing volume group to hold multiples of 1016 partitions per disk using the chvg -t command. Alternatively, you can re-create the volume group with a larger partition size that allows the new disk, or you can create a standalone volume group consisting of a larger physical size for the new disk.

Partition limitations and the rootvg
If the installation code detects that the rootvg drive is larger than 4 GB, it changes the mkvg-s value until the entire disk capacity can be mapped to the available 1016 tracks. This installation change also implies that all other disks added to rootvg, regardless of size, are also defined at that physical partition size.
Partition limitations and RAID systems
For systems using a redundant array of identical disks (RAID), the /dev/hdiskX name used by LVM may consist of many non-4 GB disks. In this case, the 1016 requirement still exists. LVM is unaware of the size of the individual disks that really make up /dev/hdiskX. LVM bases the 1016 limitation on the recognized size of /dev/hdiskX, and not the real physical disks that make up /dev/hdiskX.

  compumac 18:43 15 Oct 07

Thanks for reply. Not sure that I understand though. Both the machines referred to have 70/70Gb hard discs and both are running Windows XP SP2. Partition Magic would be started within Windows. Do I therefore understand that the 1024 boundary indication can safely be ignored as I feel sure that quite some time ago I did ignore it and I do not remember any problems arising.

  Fruit Bat /\0/\ 18:57 15 Oct 07

Yes ignore it.

I repartitioned my desktop using PM8 to 20G for op system 6G backup, 2G recovery files for drivers tools and software setup install files, and the rest for data.

  compumac 20:04 15 Oct 07

Sure??

  gardener 20:50 15 Oct 07

If one of your disks has valuable data on it I would suggest you back it up to external media of some sort.

  gardener 20:51 15 Oct 07

Sorry, I see you already have.

This thread is now locked and can not be replied to.

How to get Windows 10 for free | How to install Windows 10: There is still a way to avoid paying…

1995-2015: How technology has changed the world in 20 years

Alex Chinneck’s giant ice cube Christmas tree at Kings Cross

Apple rumours & predictions 2017: The iPhone 8, new iPads, and everything else you should expect fr7…