Fist step is to figure out which device is our SD Card. Use the 'lsblk' to list all the block devices currently connected to the system:
sudo lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT,LABEL
This should give an output similar to the following, illustrating that the SD card is connected to /dev/sdb:
AME FSTYPE SIZE MOUNTPOINT LABEL sda 232,9G ├─sda1 ntfs 100M System Reserved ├─sda2 ntfs 69,9G WINDOWS 7 ├─sda3 ext4 153,7G / └─sda4 swap 9,2G [SWAP] sdb 29,8G ├─sdb1 ext4 28,9G └─sdb2 swap 948M
GPT stands for Globally Unique Identifier (GUID) Partition Table, which is a standard for the layout of the partition table on a physical hard disk. GPT is gradually replacing the old MBR (Master Boot Record) standard, which has some limitations that only supports hard disk up to 2TB in size, and up to four primary partitions.
Identify Partition Table type using gdisk (or fdisk):
# gdisk -l /dev/sda
Output should show something similar to:
Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT.
Or with fdisk:
# fdisk -l /dev/sda
For MBR partition types, output should show something similar to:
Disk /dev/sda: 953,9 GiB, 1024209543168 bytes, 2000409264 sectors Disk model: Samsung SSD 850 * * * Disklabel type: dos
For GPT partition types, output should show something similar to:
Disk /dev/sda: 953,9 GiB, 1024209543168 bytes, 2000409264 sectors Disk model: Samsung SSD 850 * * * Disklabel type: gpt
sgdisk --backup=filename /dev/sda
sgdisk --load-backup=filename /dev/sdb sgdisk -G /dev/sdb
The option G (–randomize-guids)Randomize the disk's GUID and all partitions' unique GUIDs (but not their partition type code GUIDs). This function may be used after cloning a disk in order to render all GUIDs once again unique.
A master boot record (MBR) is the 512-byte boot sector that is the first sector of a partitioned data storage device of a hard disk. The total size is 512 bytes (446 + 64 + 2 = 512). Where,
446 bytes – Bootstrap. 64 bytes – Partition table. 2 bytes – Signature.
Next command will copy 512 bytes (MBR) from disk sdX to a backup file:
# dd if=/dev/sdX of=mbr.backup.img bs=512 count=1
Use 512 bytes to overwrite or restore your /dev/sdX the full MBR (which contains both boot code and the drive’s partition table) with the contents of mbr.backup.file.
# dd if=/mbr.backup.img of=/dev/sdX bs=512 count=1
Use 446 bytes to overwrite or restore your /dev/sdX MBR boot code only with the contents of mbr.backup.file. This will preserve the partitioning schema.
# dd if=/mbr.backup.img of=/dev/sdX bs=446 count=1