Partition Not Showing up in /dev

I recently unmounted a 4TB hard drive from one computer in order to access the files directly from another computer. It seemed like there were no problems with the unmounting process. When connecting the hard drive to the other computer, the hard drive is recognized in "/dev" as sdb, but the partition "sdb1" is not appearing, therefore I cannot mount it. If I run

fdisk -l /dev/sdb


WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdb: 4000.8 GB, 4000787030016 bytes
255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 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
Disk identifier: 0x00000000

Device Boot          Start     End      Blocks      Id  System
/dev/sdb1               1  4294967295  2147483647+  ee  GPT

The sdb1 partition shows up. Since this is a 4TB partition, I also ran the command

parted /dev/sdb

GNU Parted 2.3
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print                                                            
Model: ASMT 2105 (scsi)
Disk /dev/sdb: 4001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start  End  Size  File system  Name  Flags

Then typed "print". In this case, the sdb1 partition does NOT show up.

Why is there a mismatch of information here? Does this mean that the partition has been deleted? Is there any way to possibly recover this partition and mount it?

Thank you very much in advance

Solution 1:

Run the command partprobe to make the computer rescan the disk for partitions.

Solution 2:

I don't know if this is still an up to date problem, but I had the same issue with one of my harddrives. I used testdisk and told it to analyze the disk. It found the missing partition and updated the disks partition table. Then I ran the command partprobe and the partition showed up in /dev/ fully functional.

Solution 3:

This is likely not your issue, but I had an issue with similar symptoms that was caused by there being a RAID superblock on the drive.

Now, granted, I wanted to wipe everything on my drive anyway, so this is not recommended if that is not the case for you. Butmdadm --zero-superblock /dev/sdb did the trick for me in my case.