1

Topic: The Story Behind My Handle

Hey guys, I'm in somewhat of a stumped state of mind right now.

I was really excited about the pre-rc1 release of vista, so much so that I was willing to resize my C: partition for some extra unallocated space for a new partition.  So anyways, I have a crappy refurb 250 sata150 Maxtor, with some bad sectors.

Ive made a mistake that i confess to all you.  I ran NTFSresize -b -s200G -v.

Anyways, I tried to create a new partition, and wouldn't you know, only 12 mb of unallocated space.   Hmmm i thought to myself.  I went into my Windows Explorer to find 126G used and 57G free... capacity 199,999,995,904bytes.  Ok, where did the missing 50G disappear to?  How do I recover?  So far 3 Partition programs see a total capacity of 250G but are unable to successfully resize the partition to its maximum capacity..

Duhh uhmm? What should I do?  Practically is welcome.

Your Friend,
Missing50G

2

Re: The Story Behind My Handle

sounds .... unclear..
Did you use gparted or just ntfsresize? If you just used ntfsresize you need to resize the partition as well. I advice you to do all this using gparted and well the gparted livecd (latest release).
Please start it and tell us what you see. Also provide us with the output of fdisk -lu <device>

3

Re: The Story Behind My Handle

Sorry for being unclear.

I used the GParted LiveCD.  Since GParted does not allow you to resize partitions with bad sectors, I became bold and stupid and using the terminal, manually tried using NTFSresize.

Here is the FDisk data:

fdisk -lu /dev/sda
Disk /dev/sda: 250.9 GB, 250999111168 bytes
255 heads, 63 sectors/track, 30515 cylinders, total 490232639 sectors
Units = sectors of 1 * 512 = 512 bytes

Device      Boot Start          End            Block          ID  System
/dev/sda1   *    63             490207409  24510367+  7   HPFS/NTFS
/dev/sda2         490207410 490223474  8032+         5   Extended
/dev/sda5         490207473 490223474  8001           7   HPFS/NTFS

_________________

fdisk -lu /dev/sda1
Disk /dev/sda1: 250.9GB, 250986161664 bytes
255 heads, 63 sectors/track, 30513 cylinders, total 490207347 sectors
Units = sectors of 1 * 512 = 512 bytes

Device        Boot    Start           End               Block         ID     System
/dev/sdap1  ?      6579571      1924427647  958924038+  70  DiskSecure Multi-boot
Partition 1 does not end on cylinder boundary
/dev/sdap2  ?      1953251627 3771827541  909287957+  43  Unknown
Partition 2 does not end on cylinder boundary
/dev/sdap3  ?      225735265   225735274    5                  72  Unknown
Partition 3 does not end on cylinder boundary
/dev/sdap4          2642411520 2642463409  25945           0    Empty
Partition 4 does not end on cylinder boundary

This doesnt look like a partition table
Probably you selected the wrong device

Partition table entries are not in disk order

____________________

Well thats what I got, any help would be honored

4

Re: The Story Behind My Handle

OK now that I reread my first post, I think the haziness is what device I used the NTFSresize with.  I used it on /dev/sda1,

5

Re: The Story Behind My Handle

OMG IM A NOOB!!!

I'm so sorry to all of you that have read my story.

I forgot to FDisk.


And I thank the moderator who replied to my post in giving me subtle hints into figuring out my problem instead of just going out and telling me.

I envy your expertise, and hopefully may one day come that I gain the knowledge of using all of linux's finest tools.  Thanks!

-NotMissing50Ganymore:)

6

Re: The Story Behind My Handle

i still don't get why you use the gparted livecd and then do all this by hand?

anyway, i'm glad your problem is solved smile