Skip to main content
The 2024 Developer Survey results are live! See the results

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • Thanks, but by 'fix it' do you mean it makes a blank disk that is usable, or that the old data is still readable? Because this disk has a lot of data I want to be able to access.
    – ID-ZERO
    Commented Jun 14, 2015 at 4:35
  • @ID-ZERO - the latter. That partition table is a map: it exists at the head of the disk - it doesn't write anything over when you rewrite it, except the old partition table. Of course, without the right map, the OS doesn't know where to look for fs superblocks, and so doesn't know where the filesystems are on disk, and so can't mount one. But if you can recreate the map exactly, then the OS will find all of the data exactly where it still is.
    – mikeserv
    Commented Jun 14, 2015 at 5:21
  • So if I understand this correctly, I should do gdisk, then o - Create new empty GUID partition table?
    – ID-ZERO
    Commented Jun 14, 2015 at 7:30
  • I have done as above, and now gdisk thinks it's a 746GiB drive with no partitions. Command (? for help): p Disk /dev/sdc: 1565565872 sectors, 746.5 GiB Logical sector size: 512 bytes Disk identifier (GUID): Partition table holds up to 128 entries First usable sector is 34, last usable sector is 1565565838 Partitions will be aligned on 2048-sector boundaries Total free space is 1565565805 sectors (746.5 GiB) Number Start (sector) End (sector) Size Code Name
    – ID-ZERO
    Commented Jun 14, 2015 at 8:18
  • 1
    @ID-ZERO, looks like SystemRescueCD is broken then or you're using a very outdated version. Use the Ubuntu livecd.
    – psusi
    Commented Jun 14, 2015 at 23:12