After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 640956 - enlarge an partition on an gpt disk with to small disklabel.
enlarge an partition on an gpt disk with to small disklabel.
Status: RESOLVED DUPLICATE of bug 566935
Product: gparted
Classification: Other
Component: application
0.5.1
Other Linux
: Normal normal
: ---
Assigned To: gparted maintainers alias
gparted maintainers alias
Depends on:
Blocks:
 
 
Reported: 2011-01-30 17:27 UTC by treaki
Modified: 2011-02-10 17:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
screenshot and details log (167.53 KB, application/x-xz)
2011-01-30 17:27 UTC, treaki
Details

Description treaki 2011-01-30 17:27:21 UTC
Created attachment 179640 [details]
screenshot and details log

hi,

I tried to enlarge an partition on an gpt partitioned disk. the contens was copied with dd from a smaller disk. but its gave an error:

Not all of the space available to /dev/sdc appears to be used, you can fix the GPT to use all of the space (an extra 586051200 blocks) or continue with the current setting?

treaki
Comment 1 Curtis Gedak 2011-01-30 17:46:38 UTC
From the description of the problem, it would appear that the GPT partition table does not represent all of the space available.

If you are using RAID, did you increase the size of the RAID?

If you are using a normal disk device, did you copy a disk image from a smaller disk to a large disk?

If either of the above is the case, then this problem has been reported previously in the following report:
Bug #566935 - Unable to expand Areca RAID partition from 2.6TB to 3.4TB


Although this problem cannot currently be solved within gparted, you can resolve the problem in parted.

To fix the problem, open a terminal window and start parted with root privilege on the device.

E.g.,
     sudo parted /dev/sdc

When parted starts, it should indicate that the GPT does not use all of the available space and then provide you with a prompt to correct the situation.  When parted has adjusted the GPT to use all of the space, you can then quit from parted.

Next you can then use GParted to grow your partition.  :-)
Comment 2 Curtis Gedak 2011-02-03 20:09:26 UTC
treaki@gmail.com, does the description in comment #1 sound like the problem you experienced?

If so then you can follow the work-around to fix the problem, and I will mark this bug as a duplicate of bug #566935.
Comment 3 treaki 2011-02-05 00:50:45 UTC
hi,

i dont use any RAID-System (software or hardware). I just copied on 200GB hdd to an 500HDD.

> From the description of the problem, it would appear that the GPT partition
> table does not represent all of the space available.

Yes correct,

> If you are using a normal disk device, did you copy a disk image from a smaller
> disk to a large disk?

yes and i mean i said it:

> I tried to enlarge an partition on an gpt partitioned disk. the contens was
> copied with dd from a smaller disk. but its gave an error:


> To fix the problem, open a terminal window and start parted with root privilege
> on the device.

That is exact the thing i did.

ok if there is still a bug with the same problem i am sorry about peeving you. Thanks for the help
Comment 4 Curtis Gedak 2011-02-10 17:45:30 UTC

*** This bug has been marked as a duplicate of bug 566935 ***