can't initialize a new usb hdd

[skippy-linuxmint]

I have a new 3.5 in WD WD20EARZ 2TB Hard Drive I am using it in a V7 usb 3.0 Dual Bay Docking System I am running linux mint 22.1 I cant get the new drive to initialize the docking station is working because I have a 500gb also inserted and it works fine but the 2tb shows up in disks but I can't format it any help would be appericated.the drive that wont work is listed as sdd.
Distributor ID: Linuxmint
Description: Linux Mint 22.1
Release: 22.1
Codename: xia
-------------------------------------------
lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 004: ID 3938:1191 2.4G Wireless Mouse
Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 006: ID 1038:1122 SteelSeries ApS SteelSeries KLC
Bus 001 Device 007: ID 5986:211b Bison Electronics Inc. HD Webcam
Bus 001 Device 008: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
Bus 001 Device 022: ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 05e3:0626 Genesys Logic, Inc. Hub
Bus 002 Device 005: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-------------------------------------------------------------------------------------
lsblk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 4K 1 loop /snap/bare/5
loop1 7:1 0 55.5M 1 loop /snap/core18/2934
loop2 7:2 0 55.5M 1 loop /snap/core18/2940
loop3 7:3 0 63.8M 1 loop /snap/core20/2599
loop4 7:4 0 73.9M 1 loop /snap/core22/2082
loop5 7:5 0 73.9M 1 loop /snap/core22/2111
loop6 7:6 0 66.8M 1 loop /snap/core24/1055
loop7 7:7 0 164.8M 1 loop /snap/gnome-3-28-1804/198
loop8 7:8 0 516M 1 loop /snap/gnome-42-2204/202
loop9 7:9 0 618.3M 1 loop /snap/gnome-46-2404/125
loop10 7:10 0 107.9M 1 loop /snap/proton-mail/22
loop11 7:11 0 604M 1 loop /snap/gnome-46-2404/121
loop12 7:12 0 290.8M 1 loop /snap/mesa-2404/912
loop13 7:13 0 91.7M 1 loop /snap/gtk-common-themes/1535
loop14 7:14 0 10.8M 1 loop /snap/snap-store/1270
loop15 7:15 0 49.3M 1 loop /snap/snapd/24792
loop16 7:16 0 50.8M 1 loop /snap/snapd/25202
loop17 7:17 0 101.8M 1 loop /snap/tradingview/66
loop18 7:18 0 103.5M 1 loop /snap/tradingview/65
sda 8:0 0 119.2G 0 disk
└─sda1 8:1 0 119.2G 0 part /media/skippy/d723c653-71df-4f52-aa4c-b49061215e9a
sdb 8:16 0 931.5G 0 disk
├─sdb1 8:17 0 465.9G 0 part
├─sdb2 8:18 0 232.8G 0 part
└─sdb3 8:19 0 231.9G 0 part
sdc 8:32 0 465.8G 0 disk
└─sdc1 8:33 0 465.8G 0 part /media/skippy/500GB
sdd 8:48 0 0B 0 disk -------------------------------------------- here is the disk that wont work sdd
mmcblk0 179:0 0 29.5G 0 disk
└─mmcblk0p1 179:1 0 29.5G 0 part /media/skippy/CCC0-31C0
nvme0n1 259:0 0 238.5G 0 disk
├─nvme0n1p1 259:1 0 512M 0 part /boot/efi
├─nvme0n1p2 259:2 0 1.7G 0 part /boot
└─nvme0n1p3 259:3 0 236.3G 0 part
└─nvme0n1p3_crypt 252:0 0 236.3G 0 crypt
├─vgmint-root 252:1 0 234.4G 0 lvm /
└─vgmint-swap_1 252:2 0 1.9G 0 lvm [SWAP]

 

[KGIII]

Something is amiss...

Was this drive exceptionally cheap, like much lower priced than what you'd expect to pay for that drive?

Where did you get the HDD from?

No SMART and a statistically unlikely serial number make me extremely suspicious. HDDs (and SSDs) are often counterfeited. In most counterfeit examples, they at least have some storage - but not the full amount. They just change the firmware to pretend to have more available storage and then delete files after you go about their real storage limit.

 

[theLegionWithin]

just to rule it out, you've tested the 500gb drive in both bays?

 

[skippy-linuxmint]

Something is amiss...

Was this drive exceptionally cheap, like much lower priced than what you'd expect to pay for that drive?

Where did you get the HDD from?

No SMART and a statistically unlikely serial number make me extremely suspicious. HDDs (and SSDs) are often counterfeited. In most counterfeit examples, they at least have some storage - but not the full amount. They just change the firmware to pretend to have more available storage and then delete files after you go about their real storage limit.

no I took the plastic off this drive it was purchased at Wallmart new

 

[skippy-linuxmint]

just to rule it out, you've tested the 500gb drive in both bays?

Yes I have and the 500gb 2.5in drive works perfectly in both bays. From the best I can tell I need to get the partition table GPT or MBR set on it before it can be formated so the system can know the size of the disk but I could be wrong the last new HDD I installed was windows 95 back when you had to set master and slave on old IDE cables.
I now have it on another labtopto see here is the new info
============================================
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0bda:4853 Realtek Semiconductor Corp. Bluetooth Radio
Bus 001 Device 003: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge
Bus 001 Device 004: ID 04f2:b78e Chicony Electronics Co., Ltd Integrated Camera
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

==========================================================
and
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 465.8G 0 disk
\u2514\u2500sda1 8:1 0 465.8G 0 part
sdb 8:16 0 1.8T 0 disk
mmcblk0 179:0 0 116.5G 0 disk
\u251c\u2500mmcblk0p1 179:1 0 512M 0 part /boot/efi
\u2514\u2500mmcblk0p2 179:2 0 116G 0 part /
mmcblk0boot0 179:8 0 4M 1 disk
mmcblk0boot1 179:16 0 4M 1 disk


here is the docking station I am using in the attachment:

 

[KGIII]

I have looked this device up online and can't find much information.

I have a dumb idea... A shot in the dark, if you will...

Some of these devices may have a limit to the disk sizes they'll work with. I've seen this with other devices, but I have no experience with one of these. I looked at the packaging online, but that didn't have any information at all on it. I looked for a user manual online but V7's page has no information about this product that I could find.

An immediate example from my own experience is some new MP3 players that I bought. They weren't kidding about their limitations. I tried a 256 GB card in one and it would not recognize it. It works just fine with a 128 GB card, though I only had one of those on hand.

This is just spitballing. I have no idea if this is actually the case. It seems dumb but they may have gone the 'less expensive' route and used some hardware that only allows disks of a certain size. Given the advertised price, that could be the case.

Did this device come with a manual of any value?

 

[bob466]

I also have a docking bay...haven't used it for years...I also have a new unused 2TB Seagate HDD...well it was more than 14 years ago...still in its anti-static bag.

This 2TB HDD has never been in Linux or UEFI...here it is...

The HDD is unformatted but shows all info and SMART works...I think the HDD you have should be returned as there's clearly something wrong with it...always buy well know brands...hope this helps.

It also shows up in Computer too...

 

[osprey]

@skippy-linuxmint
In post #1 the disk on that machine is: /dev/sdd
In post #5 on a different machine it appears as: /dev/sdb

What happens if you run, as root, fdisk on either of those machines, for example on the first machine:

fdisk -l /dev/sdd

The output of the following command could be of interest as well:

lsblk -o NAME,MAJ:MIN,RM,RO,SIZE,TYPE,FSTYPE,LABEL,MOUNTPOINT,MODE,OWNER,GROUP

If you could use code tags, it would be easier for readers to read. If unsure about using them, see here: https://linux.org/threads/the-code-tag-and-why-it-matters.57746/#post-276419

Presumably if fdisk sees the disk, one can try and format it and then put a filesystem on it, it unless I'm missing something.

 

[skippy-linuxmint]

I have looked this device up online and can't find much information.

I have a dumb idea... A shot in the dark, if you will...

Some of these devices may have a limit to the disk sizes they'll work with. I've seen this with other devices, but I have no experience with one of these. I looked at the packaging online, but that didn't have any information at all on it. I looked for a user manual online but V7's page has no information about this product that I could find.

An immediate example from my own experience is some new MP3 players that I bought. They weren't kidding about their limitations. I tried a 256 GB card in one and it would not recognize it. It works just fine with a 128 GB card, though I only had one of those on hand.

This is just spitballing. I have no idea if this is actually the case. It seems dumb but they may have gone the 'less expensive' route and used some hardware that only allows disks of a certain size. Given the advertised price, that could be the case.

Did this device come with a manual of any value?

I have a pamplet that came with it it works with up to 16 TB or that's what it says
Mine came from walmart but here is a link to mine https://www.ebay.com/itm/157040598335

 

[skippy-linuxmint]

I also have a docking bay...haven't used it for years...I also have a new unused 2TB Seagate HDD...well it was more than 14 years ago...still in its anti-static bag.

This 2TB HDD has never been in Linux or UEFI...here it is...
View attachment 27742

The HDD is unformatted but shows all info and SMART works...I think the HDD you have should be returned as there's clearly something wrong with it...always buy well know brands...hope this helps.

It also shows up in Computer too...
View attachment 27744
View attachment 27743

Here is what I get when I try to format and it don't matter what filing system I try to format it to with the disks gui on mint

 

[skippy-linuxmint]

@skippy-linuxmint
In post #1 the disk on that machine is: /dev/sdd
In post #5 on a different machine it appears as: /dev/sdb

What happens if you run, as root, fdisk on either of those machines, for example on the first machine:

fdisk -l /dev/sdd

The output of the following command could be of interest as well:

lsblk -o NAME,MAJ:MIN,RM,RO,SIZE,TYPE,FSTYPE,LABEL,MOUNTPOINT,MODE,OWNER,GROUP

If you could use code tags, it would be easier for readers to read. If unsure about using them, see here: https://linux.org/threads/the-code-tag-and-why-it-matters.57746/#post-276419

Presumably if fdisk sees the disk, one can try and format it and then put a filesystem on it, it unless I'm missing something.

with fdisk:
skippy@lenovo-01:~$ sudo fdisk -l /dev/sdc
[sudo] password for skippy:
fdisk: cannot open /dev/sdc: Input/output error
========================================
skippy@lenovo-01:~$ lsblk -o NAME,MAJ:MIN,RM,RO,SIZE,TYPE,FSTYPE,LABEL,MOUNTPOINT,MODE,OWNER,GROUP
NAME MAJ:MIN RM RO SIZE TYPE FSTYPE LABEL MOUNTPOINT MODE OWNER GROUP
sdb 8:16 0 0 465.8G disk brw-rw---- root disk
sdc 8:32 0 0 1.8T disk brw-rw---- root disk
mmcblk1 179:0 0 0 116.5G disk brw-rw---- root disk
├─mmcblk1p1
│ 179:1 0 0 512M part vfat /boot/efi brw-rw---- root disk
└─mmcblk1p2
179:2 0 0 116G part ext4 / brw-rw---- root disk
mmcblk1boot0
179:8 0 1 4M disk brw-rw---- root disk
mmcblk1boot1
179:16 0 1 4M disk brw-rw---- root disk
=====================================================================================
it is on sdc now where I am tring diferent things.
both devices came from walmart it works good with 500GB in either bay but the 2TB can't get it to work on either bay not linux or windows the drive has never been used and I don't have a pc that I can put the 2TB in because it is a 3.5 in and everything I have is 2.5in or M.2

 

[skippy-linuxmint]

@skippy-linuxmint
In post #1 the disk on that machine is: /dev/sdd
In post #5 on a different machine it appears as: /dev/sdb

What happens if you run, as root, fdisk on either of those machines, for example on the first machine:

fdisk -l /dev/sdd

The output of the following command could be of interest as well:

lsblk -o NAME,MAJ:MIN,RM,RO,SIZE,TYPE,FSTYPE,LABEL,MOUNTPOINT,MODE,OWNER,GROUP

If you could use code tags, it would be easier for readers to read. If unsure about using them, see here: https://linux.org/threads/the-code-tag-and-why-it-matters.57746/#post-276419

Presumably if fdisk sees the disk, one can try and format it and then put a filesystem on it, it unless I'm missing something.

I'll check on the code tags I have never used one of these fourms before thanks for the advice

 

[skippy-linuxmint]

sudo fdisk -l /dev/sdc
                            
    fdisk: cannot open /dev/sdc: Input/output error

 skippy@lenovo-01:~$ lsblk -o NAME,MAJ:MIN,RM,RO,SIZE,TYPE,FSTYPE,LABEL,MOUNTPOINT,MODE,OWNER,GROUP

    NAME    MAJ:MIN RM RO   SIZE TYPE FSTYPE LABEL MOUNTPOINT MODE       OWNER GROUP

    sdb       8:16   0  0 465.8G disk                         brw-rw---- root  disk

    sdc       8:32   0  0   1.8T disk                         brw-rw---- root  disk

    mmcblk1 179:0    0  0 116.5G disk                         brw-rw---- root  disk

    ├─mmcblk1p1

    │       179:1    0  0   512M part vfat         /boot/efi  brw-rw---- root  disk

    └─mmcblk1p2

            179:2    0  0   116G part ext4         /          brw-rw---- root  disk

    mmcblk1boot0

            179:8    0  1     4M disk                         brw-rw---- root  disk

    mmcblk1boot1

            179:16   0  1     4M disk                         brw-rw---- root  disk

 

[skippy-linuxmint]

I am still learning how to use the forums thanks for the help and sorry for any inconvenience
I have been beating my head against the wall over this

 

[osprey]

@skippy-linuxmint wrote:

sudo fdisk -l /dev/sdc<br>                            <br>    fdisk: cannot open /dev/sdc: Input/output error

Thanks for the output. Unfortunately, it's not good news. Input/output errors can be caused by a number of things, many of which are a problem without much hope for recovery. Causes for this error can include:
Loose or faulty connections.
Failing drive with bad sectors.
Mechanical issues.
Insufficient power.
More ...

First, check the connections. I expect there are no power issues because other disks work.

The fdisk facility accesses the disk at a low level, meaning that other software is largely irrelevant.
It interacts directly with raw device blocks (e.g. the device /dev/sdc), partition tables (e.g., MBR, GPT), disk sectors, not files or folders. It bypasses the filesystem (like ext4) and doesn't care what files or operating system is on the drive. It's just looking at disk structures in raw binary form. So, that's the level of the problem as it appears at this point.

There is a test you could run to try and read from the drive to confirm the failure which is to run the following command as root:

dd if=/dev/sdc of=/dev/null bs=1M count=1

If this fails with an input/output, it more or less confirms a low-level read failure. It means that one probably couldn't even clean or wipe the disk with the dd tool to start all over. I could be mistaken, but the evidence so far leads me to think of the above.

 

[KGIII]

I have a pamplet that came with it it works with up to 16 TB or that's what it says
Mine came from walmart but here is a link to mine https://www.ebay.com/itm/157040598335

That's exhausted everything I can think of that might rule out mechanical failure at some point in the path. My guess would be the drive itself, which should be easy enough to return for a refund or exchange.