GPT PMBR size mismatch 解决方法
https://blog.csdn.net/agave7/article/details/83177858
root@debian:/home/liyezhen/src/sbk_debian_32bit/build/product_tools# fdisk -l /dev/sdb
GPT PMBR size mismatch (60062499 != 60995327) will be corrected by w(rite).
The backup GPT table is corrupt, but the primary appears OK, so that will be used.
Disk /dev/sdb: 29.1 GiB, 31229607936 bytes, 60995328 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: BE4B4A96-2EDA-4A01-886E-97A3523426A3
Device Start End Sectors Size Type
/dev/sdb1 2048 104447 102400 50M EFI System
/dev/sdb2 104448 299007 194560 95M Linux filesystem
/dev/sdb3 299008 2252799 1953792 954M Linux filesystem
/dev/sdb4 2252800 10854399 8601600 4.1G Linux filesystem
root@debian:/home/liyezhen/src/sbk_debian_32bit/build/product_tools# parted -l
Model: ATA ST3500413AS (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 496GB 496GB primary ext4 boot
2 496GB 500GB 4218MB extended
5 496GB 500GB 4218MB logical linux-swap(v1)
Error: The backup GPT table is corrupt, but the primary appears OK, so that will
be used.
OK/Cancel? ok
Warning: Not all of the space available to /dev/sdb appears to be used, you can fix the GPT to use all of the space (an extra 932828 blocks) or continue with the current setting?
Fix/Ignore? fix
Model: Kingston DataTraveler 3.0 (scsi)
Disk /dev/sdb: 31.2GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 53.5MB 52.4MB fat16 Linux filesystem boot, esp
2 53.5MB 153MB 99.6MB ext4
3 153MB 1153MB 1000MB ext4
4 1153MB 5557MB 4404MB ext4
Error: The backup GPT table is corrupt, but the primary appears OK, so that will be used.
OK/Cancel? ok
Model: SanDisk Ultra USB 3.0 (scsi)
Disk /dev/sdc: 30.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 53.5MB 52.4MB fat16 Linux filesystem boot, esp
2 53.5MB 153MB 99.6MB ext4
3 153MB 1153MB 1000MB ext4
4 1153MB 5557MB 4404MB ext4
root@debian:/home/liyezhen/src/sbk_debian_32bit/build/product_tools#
root@debian:/home/liyezhen/src/sbk_debian_32bit/build/product_tools#
root@debian:/home/liyezhen/src/sbk_debian_32bit/build/product_tools#
root@debian:/home/liyezhen/src/sbk_debian_32bit/build/product_tools# fdisk -l /dev/sdb
Disk /dev/sdb: 29.1 GiB, 31229607936 bytes, 60995328 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: BE4B4A96-2EDA-4A01-886E-97A3523426A3
Device Start End Sectors Size Type
/dev/sdb1 2048 104447 102400 50M EFI System
/dev/sdb2 104448 299007 194560 95M Linux filesystem
/dev/sdb3 299008 2252799 1953792 954M Linux filesystem
/dev/sdb4 2252800 10854399 8601600 4.1G Linux filesystem
root@debian:/home/liyezhen/src/sbk_debian_32bit/build/product_tools# mount /dev/sdb4 /mnt/usb
mount: wrong fs type, bad option, bad superblock on /dev/sdb4,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
root@debian:/home/liyezhen/src/sbk_debian_32bit/build/product_tools#
root@debian:/home/liyezhen/src/sbk_debian_32bit/build/product_tools#
root@debian:/home/liyezhen/src/sbk_debian_32bit/build/product_tools# fsck.ext4 /dev/sdb4
e2fsck 1.42.12 (29-Aug-2014)
Superblock has an invalid journal (inode 8).
Clear
*** ext3 journal has been deleted - filesystem is now ext2 only ***