New 2tb external hard drive not recognized(RESOLVED)

[AZgl1800]

I have a 6TB Seagate drive like you talk about, it is now about 3 or 4 years old.
It came with its' own Power Supply for the USB drive.

I think you are having power problems....

for myself, Mint 18.3 Cinnamon was able to see the drive, and I divided it into two separate partitions.
NTSF for allowing files to be moved from/to Windows from/to Linux

ext4 for just Linux Mint backups, etc.

[kato181]

The OP's seagate is only USB3.0 it does not come with it's own psu. I'm just waiting on him to reply to my message. It's unusual that it doesn't show under the command lsusb. Just wondering if he has pushed the usb cable in firmly enough in the drive.

[AZgl1800]

The OP's seagate is only USB3.0 it does not come with it's own psu. I'm just waiting on him to reply to my message. It's unusual that it doesn't show under the command lsusb. Just wondering if he has pushed the usb cable in firmly enough in the drive.

sorry about that, missed that feature.

I won't buy drives that do not come with a power supply.

[kato181]

I was the same until one psu died and I couldn't get a replacement. So I pulled it apart and used the drive as a sata drive. The drive he has is a 5400rpm drive..Ooooh...the pain of having a slow drive these days. I always ensure if i have to get an external drive that it's always 7200rpm.

[digger44]

I have run lsusb on all three usb ports. The results are:

Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 0489:e042 Foxconn / Hon Hai Broadcom BCM20702 Bluetooth
Bus 001 Device 004: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Bus 001 Device 003: ID 0000:3825
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 1f75:0621 Innostor Technology Corporation
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 04f2:b2e1 Chicony Electronics Co., Ltd
Bus 003 Device 004: ID 1a2c:2c27 China Resource Semico Co., Ltd
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


foobar@foobar-Lenovo-Z580:~$ lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 0489:e042 Foxconn / Hon Hai Broadcom BCM20702 Bluetooth
Bus 001 Device 004: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Bus 001 Device 003: ID 0000:3825
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 1f75:0621 Innostor Technology Corporation
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 04f2:b2e1 Chicony Electronics Co., Ltd
Bus 003 Device 007: ID 1a2c:2c27 China Resource Semico Co., Ltd
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub



foobar@foobar-Lenovo-Z580:~$ lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 0489:e042 Foxconn / Hon Hai Broadcom BCM20702 Bluetooth
Bus 001 Device 004: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Bus 001 Device 009: ID 1f75:0621 Innostor Technology Corporation
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 04f2:b2e1 Chicony Electronics Co., Ltd
Bus 003 Device 010: ID 1a2c:2c27 China Resource Semico Co., Ltd
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
foobar@foobar-Lenovo-Z580:~$


I took this to a Windows 10 machine. It recognized it on that machine. So I reformated it as NTSC. The Windows machine could no longer recognize the hard drive. Nor could my Linux machine.

I checked the bios in my Linux machine. There was no item for USB 3.0 only for USB legacy or UEFI, Legacy was enabled.

At this point I appear to be at a dead end. If anyone can think of anything else I can try I'll happily comply. If not I may try removing it from it's case and trying to see if it will work in an enclosure. Thanks for your help.

[Dark Owl]

So I reformated it as NTSC

I don't think so! If you did somehow manage to do that, it would explain much.

Presuming you mean NTFS, I think the only conclusion is there's something wrong with the drive. There's nothing unusual in Win10 corrupting a drive (just by plugging it in) so that other OSes can't see it, but not so that Win10 can't see it.

[kato181]

Try changing the external drive to another usb port and start windows. If it doesn't show, then pull the drive out and plug it in again. It should make a beep saying that windows has detected a usb device inserted. If it then detects the drive, then format it as fat32 and not ntfs.

[digger44]

Thank you Kato 181. We tried starting up Windows 10 with the HD attached. It did detect it however when we tried formatting with NTFS and then exFat it said that Windows could not format the drive. We downloaded Rufus and Then MiniTool but neither of these were able to format the drive in Fat32. So at this point I am concluding this request and will try to remove the drive from the case and put it into a usb case to see if it can be recognized and reformatted with this. I want to thank everyone who helped me with this problem.

[kato181]

Exfat was developed mainly for usb and sd cards only.
Format the drive as fat32 only, winwoes & LM will still recognise the drive.

[karlchen]

<mod>
last_fix's post has been turned into a new thread: viewtopic.php?f=49&t=351315
In case it really were the same issue, then the confirmed solution should work for last_fix as well.
So the issue may not be quite the same.
</mod>