PURPOSE: Determine why the hdd will not mount after creating a duplicate hdd out of it.
Host hdd: 4tb.gold
Destination hdd: boo.boo
Originally mount the hdd = When I 1st connected the 2 hdd's to the computer before doing any other steps afterwards; the number 1 thing I did after starting the computer.
I used the following command to make the duplicate
"sudo dd if=/dev/sdx bs=16M of=/dev/mapper/boo.boo"
whereby the destination hdd ("of...") was mounted before running that command.
I used the following command to originally mount the hdd b/f duplication, and then again when trying to mount the hdd after duplication:
"sudo mount /dev/mapper/boo.boo /mnt"
... The duplicating finished, but now the hdd shows up in lsblk, opens with cryptsetup, but will not mount.
Common error message: "bad superblock, wrong fs type, bad..."
UPDATE: "sudo fsck /dev/sdx" = fsck from util-linux 2.33.1
$ sudo fdisk -l /dev/mapper/boo.boo (destination hdd which was only hdd mounted)
GPT PMBR size mismatch (3907029167 != 3906996399) will be corrected by write.
Disk /dev/mapper/4tb.gold: 1.8 TiB, 2000382156800 bytes, 3906996400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/mapper/4tb.gold-part1 1 3906996399 3906996399 1.8T ee GPT
Partition 1 does not start on physical sector boundary.