home.social

#partitiontable — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #partitiontable, aggregated by home.social.

  1. @bytebro

    Rescuing a primary partition table that has been corrupted, when the partition itself is intact, should be easy. Especially in the case of EFI partitioning. See the #rodsbooks doco.

    Alternatively: The partition table actually being intact and the NTFS flags saying that the partition needs checking are on, or the MFT pointer or BPB data being lost (which latter could well make it not look like an NTFS volume), requires a different solution.

    #PartitionTable #rescue #gdisk

  2. @bytebro

    Rescuing a primary partition table that has been corrupted, when the partition itself is intact, should be easy. Especially in the case of EFI partitioning. See the #rodsbooks doco.

    Alternatively: The partition table actually being intact and the NTFS flags saying that the partition needs checking are on, or the MFT pointer or BPB data being lost (which latter could well make it not look like an NTFS volume), requires a different solution.

    #PartitionTable #rescue #gdisk

  3. @bytebro

    Rescuing a primary partition table that has been corrupted, when the partition itself is intact, should be easy. Especially in the case of EFI partitioning. See the #rodsbooks doco.

    Alternatively: The partition table actually being intact and the NTFS flags saying that the partition needs checking are on, or the MFT pointer or BPB data being lost (which latter could well make it not look like an NTFS volume), requires a different solution.

    #PartitionTable #rescue #gdisk

  4. @bytebro

    It depends whether it has lost your partition table or unformatted (or marked as needing scan and repair) the partition.

    First thing to do is to use gdisk(8) or sfdisk(8) or *something* to determine what of your partition table, if anything, is actually there at the moment.

    Because that tells you what to fix.

    #PartitionTable #rescue #gdisk

  5. @bytebro

    It depends whether it has lost your partition table or unformatted (or marked as needing scan and repair) the partition.

    First thing to do is to use gdisk(8) or sfdisk(8) or *something* to determine what of your partition table, if anything, is actually there at the moment.

    Because that tells you what to fix.

    #PartitionTable #rescue #gdisk

  6. @bytebro

    It depends whether it has lost your partition table or unformatted (or marked as needing scan and repair) the partition.

    First thing to do is to use gdisk(8) or sfdisk(8) or *something* to determine what of your partition table, if anything, is actually there at the moment.

    Because that tells you what to fix.

    #PartitionTable #rescue #gdisk

  7. @bytebro

    It depends whether it has lost your partition table or unformatted (or marked as needing scan and repair) the partition.

    First thing to do is to use gdisk(8) or sfdisk(8) or *something* to determine what of your partition table, if anything, is actually there at the moment.

    Because that tells you what to fix.

    #PartitionTable #rescue #gdisk

  8. @bytebro

    For what it's worth, if you are using the EFI partitioning scheme:

    It should be relatively easy to use something like gdisk(8) or fixparts(8) to restore from the backup copy of the partition table.

    If the primary and backup copies have both been zapped, then the likelihood is that some serious data corruption has happened, since they are at opposite ends of the disc, nominally.

    rodsbooks.com/gdisk/repairing.

    rodsbooks.com/fixparts/

    #PartitionTable #gdisk #rodsbooks

  9. @bytebro

    For what it's worth, if you are using the EFI partitioning scheme:

    It should be relatively easy to use something like gdisk(8) or fixparts(8) to restore from the backup copy of the partition table.

    If the primary and backup copies have both been zapped, then the likelihood is that some serious data corruption has happened, since they are at opposite ends of the disc, nominally.

    rodsbooks.com/gdisk/repairing.

    rodsbooks.com/fixparts/

    #PartitionTable #gdisk #rodsbooks

  10. @bytebro

    For what it's worth, if you are using the EFI partitioning scheme:

    It should be relatively easy to use something like gdisk(8) or fixparts(8) to restore from the backup copy of the partition table.

    If the primary and backup copies have both been zapped, then the likelihood is that some serious data corruption has happened, since they are at opposite ends of the disc, nominally.

    rodsbooks.com/gdisk/repairing.

    rodsbooks.com/fixparts/

    #PartitionTable #gdisk #rodsbooks

  11. @bytebro

    For what it's worth, if you are using the EFI partitioning scheme:

    It should be relatively easy to use something like gdisk(8) or fixparts(8) to restore from the backup copy of the partition table.

    If the primary and backup copies have both been zapped, then the likelihood is that some serious data corruption has happened, since they are at opposite ends of the disc, nominally.

    rodsbooks.com/gdisk/repairing.

    rodsbooks.com/fixparts/

    #PartitionTable #gdisk #rodsbooks