I must preface this with the important note that I am not a Western Digital specialist. I am moderately familiar with GNU/Linux, but not a specialist there either. By all means read along with what I type below, but strongly recommend that you double check my observations before deciding what to do next.
You’re running fdisk 2.33.1; I’ve just checked my Linux Mint 19.2 build and I’m running 2.31.1… not sufficiently different for us to be hugely concerned.
The first message that you paste here begins with a warning: “GPT PMBR size mismatch”
Now, the “MBR” is the “Master Boot Record” - it’s a location on the disk that an operating system will attempt to read when the OS boots. On my Linux system, I open a terminal window and type,
to access the manual pages. The very first paragraph reads as follows: "fdisk is a dialog-driven program for creation and manipulation of partition tables. It understands GPT, MBR, Sun, SGI and BSD partition tables.
I note that the above descriptor does not include “PMBR” master boot records.
So I go to Google Search and enter “PMBR”. Wikipedia,
tells me this: “protective master boot record, a boot sector on a hard disk with an MS-DOS-compatible format partition table embedded in it which also has a GUD partition table (GPT). Its purpose is to protect the disk context from accidential damage by programs which properly interpret the MS-DOS format partition table but do not interpret the GPT – for example the fdisk program of both MS-DOS and Linux”…
This strongly suggests to me that the issue you are experiencing is because the tool you are trying to use, the GNU/Linux fdisk command, cannot handle the provided Master Boot Record configuration/syntax/setup.
This would have been my guess when I see the “size mismatch” error message… That’s because a discrepancy that causes the program you are using to, say, misunderstand the number of bytes used to store a numeric value, can sometime have the effect of leaving you seeing a weird value because the program trying to read the field is not interpreting the field correctly.
My suggestion to you in this instance is that you need to find another utility program, preferably on a different OS, to set up your new drive.
If you don’t have a technically confident friend willing to take the drive and set it up for you (say in a Windows 10 desktop machine), then I’m afraid the best suggestion I have would be to go and find a retail shop with a PC support service in it, or a specialist local computer center.
Sorry - I guess this isn’t quite what you wanted to get for a reply. But I hope it helps.