Evening all
I've had a couple of machines do this. Particular machine giving me jip today is a Centos 6.5 minimal install running on Vshpere 5.1 on a Thick provisioned, lazy zeroed disk.
Normal process is to delete partition (/dev/sda2) create new primary, accept default start and end of partition, set type to 8e, go to expert mode, set new beginning (again accept default) and then write changes and reboot.
Once rebooted run pvresize and lvextend etc. However... the actual recreation of the primary partition fails to increase the size.
Example of this step where it worked before....
Command (m for help): p
Disk /dev/sda: 45.1 GB, 45097156608 bytes 255 heads, 63 sectors/track, 5482 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00009407
Device Boot Start End Blocks Id System /dev/sda1 * 1 64 512000 83 Linux Partition 1 does not end on cylinder boundary. /dev/sda2 64 4178 33041408 8e Linux LVM
Command (m for help): d Partition number (1-4): 2
Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 2 First cylinder (64-5482, default 64): Using default value 64 Last cylinder, +cylinders or +size{K,M,G} (64-5482, default 5482): Using default value 5482
However in this instance on recreating the partition the end sector is same as the one I originally deleted.
Has anyone else come across this? Is it a VM thing or a Centos thing? I've followed this step on other Centos machines and Ubuntu machines a few times now and most of the rest worked straight off so wondering if I'm missing something obvious....
At least its not kernel panicking on me like another machine but I'll raise a separate post about that.....
cheers, Kiweegie.
[link][3 comments]