What can I do to determine why my hdd is not mounting?

▲
0
▼

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.
linux
hard-drive
mount
asked on Super User Oct 29, 2019 by topencrypt • edited Oct 29, 2019 by topencrypt

2 Answers

▲
1
▼

Does /dev/sdX holds some partitions ?

What is the output of fdisk -l /dev/mapper/4tb.gold ?

If /dev/mapper/4tb.gold represents the whole disk (which was partitionned), then you have to mount one of theses partitions.

answered on Super User Oct 29, 2019 by binarym
▲
1
▼

"sdx" has 3 partitions, "dev/mapper" likely had 1

If the source had 3 partitions, after you cloned it, the mapper device also has 3 partitions now. (It doesn't really matter what the destination had – you overwrote everything while cloning.)

So you cannot mount it for the same reason you cannot actually mount sdx as a whole: a disk with a partition table doesn't have anything mountable. The partitions are mountable, not the disk itself.

Device-mapper devices will not automatically recognize a partition table inside them; you'll have to separately create new dm-linear mappings for each partition. This can be most easily done using the kpartx tool from multipath-tools:

kpartx -av /dev/mapper/diskname

mount /dev/mapper/disknamep1 /mnt

(I would recommend re-doing the cloning from scratch, and this time leaving the partition table unencrypted – instead create a separate crypt device for every partition.)

answered on Super User Oct 29, 2019 by user1686

User contributions licensed under CC BY-SA 3.0