Ask Your Question
1

External Hard drive detected but not mounted

asked 2017-08-28 14:18:17 -0600

Chadi gravatar image

When I used to have windows my 1TB verbatim hard drive (after a few months of working perfectly) started malfunctioning, It wasn't always mounted by my windows 10 OS. When I switched to Fedora I had the same problem. So far it hasn't worked on fedora. The external hard drive is less than a year old. I do not understand what prompted the problem since it was sudden.

Lsusb:

Bus 001 Device 005: ID 0a5c:5804 Broadcom Corp. BCM5880 Secure Applications Processor with fingerprint swipe sensor
Bus 001 Device 004: ID 1bcf:2b8d Sunplus Innovation Technology Inc. 
Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
Bus 001 Device 002: ID 8087:8001 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 014: ID 18a5:0408 Verbatim, Ltd 
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Dmesg:

[ 6186.680262] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 6217.547435] usb 3-2: reset SuperSpeed USB device number 12 using xhci_hcd
[ 6541.130248] usb 3-2: reset SuperSpeed USB device number 12 using xhci_hcd
[ 6676.010335] usb 3-2: USB disconnect, device number 12
[ 6676.927706] usb 3-2: new SuperSpeed USB device number 13 using xhci_hcd
[ 6676.942352] usb 3-2: New USB device found, idVendor=18a5, idProduct=0408
[ 6676.942358] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6676.942361] usb 3-2: Product: Portable USB 3.0 Hard Drive
[ 6676.942364] usb 3-2: Manufacturer: Verbatim
[ 6676.942366] usb 3-2: SerialNumber: 2346530428D7
[ 6676.944012] usb-storage 3-2:1.0: USB Mass Storage device detected
[ 6676.944811] scsi host2: usb-storage 3-2:1.0
[ 6681.481000] scsi 2:0:0:0: Direct-Access              VirtualDisk           PQ: 0 ANSI: 6
[ 6681.481402] sd 2:0:0:0: Attached scsi generic sg1 type 0
[ 6681.481804] sd 2:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B)
[ 6681.481806] sd 2:0:0:0: [sdb] 0-byte physical blocks
[ 6681.482151] sd 2:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 6681.482454] sd 2:0:0:0: [sdb] Asking for cache data failed
[ 6681.482458] sd 2:0:0:0: [sdb] Assuming drive cache: write through

fdisk does not show the hard drive either:

 Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: 15BA1A8C-ADC0-497B-B900-A4ABD3759DF9
Device         Start       End   Sectors   Size Type
/dev/sda1       2048   1050623   1048576   512M EFI System
/dev/sda2    1050624 232368127 231317504 110.3G Linux filesystem
/dev/sda3  968644608 976771071   8126464   3.9G Linux swap
/dev/sda4  232368128 841381887 609013760 290.4G Linux filesystem
/dev/sda5  841381888 842610687   1228800   600M Linux filesystem

It does show up in disks though with the tag no media

edit retag flag offensive close merge delete

Comments

Is this drive still under warranty? Does it still (at least sometimes) work under windows? Have you checked its SMART status/report?

ozeszty gravatar imageozeszty ( 2017-08-28 15:42:26 -0600 )edit

It is under warranty but I lost the receipt (stupid I know). I haven't checked it on windows in a long time and since Fedora is now my one and only OS it doesn't seem necessary to test it on windows. how can I check its SMART status?

Chadi gravatar imageChadi ( 2017-08-28 15:44:55 -0600 )edit

AFAIK fdisk needs the device: fdisk /dev/sdb in your case. Also, have you tried mounting it manually? mount /dev/sdb1 /mnt (or whatever partition)

fcomida gravatar imagefcomida ( 2017-08-28 16:24:50 -0600 )edit

fdisk: cannot open /dev/sdb: No such file or directory

I received that error after running fdisk /dev/sdb. I expected this error since as I said fdisk does not detect the hard drive in the first place. Attempting to manually mount yields this error:

mount: /mnt: can't read superblock on /dev/sdb.
Chadi gravatar imageChadi ( 2017-08-28 16:42:26 -0600 )edit
1

@Chadi I incline toward the faulty cable (or faulty usb controller) hypotesis. It seems connection is coming and going, you can see: fdisk: cannot open /dev/sdb: No such file or directory (/dev/sdb isn't there) and mount: /mnt: can't read superblock on /dev/sdb. (now /dev/sdb is detected)

fcomida gravatar imagefcomida ( 2017-08-28 17:39:55 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2017-08-28 15:39:41 -0600

sideburns gravatar image

Welcome to ask.fedora! If your drive suddenly stopped being recognized and mounted by Windows and is doing the same thing with Fedora, it's either a loose cable or a bad drive. And, if it's that young, it's probably under warranty, so it shouldn't cost you anything to replace.

edit flag offensive delete link more

Comments

RMA'ing will most probably mean data loss, so if any files are needed, then connecting drive directly to a computer and maybe testdisk recovery should be advised. In that case, can the drive be removed from it's case without breaking any seals? 'cause... ;)

ozeszty gravatar imageozeszty ( 2017-08-28 16:09:21 -0600 )edit

I don't mind loosing data at all. In fact the last time it worked on windows I attempted a disk format to try and solve the problem. As for warranty issues ... I lost my receipt and the retailer wouldn't acknowledge my purchase.

Chadi gravatar imageChadi ( 2017-08-28 16:43:37 -0600 )edit

Talk to the OEM, then. The drive should have a serial number that will tell when it was made. That should be enough to establish that it's still under warranty, unless it's been sitting on the shelf too long.

sideburns gravatar imagesideburns ( 2017-08-28 17:07:18 -0600 )edit

Question Tools

1 follower

Stats

Asked: 2017-08-28 14:18:17 -0600

Seen: 2,364 times

Last updated: Aug 28 '17