• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows XP DiskPart

manly

Lifer
I've had an underutilized hard drive for a long time, so I finally bit the bullet and decided to use diskpart to extend C: by 40GB. Microsoft 's documentation states, "You cannot extend the current system or boot partitions." but of course I know better. 😉

DISKPART> extend size=40000

DiskPart successfully extended the volume.

It seems to have worked properly, but Disk Management did not reduce the unallocated Free space by 40GB as it should have. So according to its math, my drive grew from 160GB to 200GB.

Will this correct itself after reboot, or should I start preparing for the eventual reformat/reinstall?

Actually, looking at Disk Management now, after deleting unused filesystems, I did not delete the enclosing extended partition that is now overreported in size. So I wonder how hosed my partition table is with this "fuzzy math".
 
System was working fine after filesystem extension. I shouldn't have rebooted, but I did. Then discovered GRUB no longer worked; booted into Windows Recovery Console to run fixmbr. It spit out some warning that my partition table was invalid, and that it could hose things. I ran it anyway. 😛

Now, Windows won't boot. Thankfully, the data seems to be intact. More troubleshooting/backup/reinstallation ahead...
 
Originally posted by: manly
System was working fine after filesystem extension. I shouldn't have rebooted, but I did. Then discovered GRUB no longer worked; booted into Windows Recovery Console to run fixmbr. It spit out some warning that my partition table was invalid, and that it could hose things. I ran it anyway. 😛

Now, Windows won't boot. Thankfully, the data seems to be intact. More troubleshooting/backup/reinstallation ahead...

I guess there really is a reason for those pesky little warnings??? :0

pcgeek11
 
Originally posted by: pcgeek11
I guess there really is a reason for those pesky little warnings??? :0

pcgeek11
Not really; on a hunch, I set the Windows partition active. It now boots and is operational.

Although I could manually fix the aforementioned inconsistency in the partition table; apparently, it is safely ignored.
 
Originally posted by: manly
Originally posted by: pcgeek11
I guess there really is a reason for those pesky little warnings??? :0

pcgeek11
Not really; on a hunch, I set the Windows partition active. It now boots and is operational.

Although I could manually fix the aforementioned inconsistency in the partition table; apparently, it is safely ignored.

Glad to hear it worked out for you...

pcgeek11
 
Back
Top