[SOLVED-ISH] External USB hard drive issue

k.king · 12-05-2020, 05:36 AM

When I plug a WS external USB drive used many times before aok now does not mount.
The following from dmesg.
Does this mean the drive (or electronics of it) are broken?

Code:

[ 1678.529099] usb 1-6: new high-speed USB device number 5 using xhci_hcd
[ 1678.678033] usb 1-6: New USB device found, idVendor=1058, idProduct=0748, bcdDevice=10.22
[ 1678.678037] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[ 1678.678040] usb 1-6: Product: My Passport 0748
[ 1678.678043] usb 1-6: Manufacturer: Western Digital
[ 1678.678045] usb 1-6: SerialNumber: ************************
[ 1678.701182] usb-storage 1-6:1.0: USB Mass Storage device detected
[ 1678.701236] scsi host6: usb-storage 1-6:1.0
[ 1678.701287] usbcore: registered new interface driver usb-storage
[ 1678.703074] usbcore: registered new interface driver uas
[ 1679.709955] scsi 6:0:0:0: Direct-Access     WD       My Passport 0748 1022 PQ: 0 ANSI: 6
[ 1679.710344] scsi 6:0:0:1: Enclosure         WD       SES Device       1022 PQ: 0 ANSI: 6
[ 1679.711794] sd 6:0:0:0: Attached scsi generic sg4 type 0
[ 1679.712195] scsi 6:0:0:1: Attached scsi generic sg5 type 13
[ 1679.712783] sd 6:0:0:0: [sdd] Spinning up disk...
[ 1680.733128] .
[ 1687.041177] scsi 6:0:0:1: Wrong diagnostic page; asked for 1 got 8
[ 1687.041187] scsi 6:0:0:1: Failed to get diagnostic page 0x1
[ 1687.041192] scsi 6:0:0:1: Failed to bind enclosure -19
[ 1687.041554] ready
[ 1687.041768] sd 6:0:0:0: [sdd] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB)
[ 1687.042037] sd 6:0:0:0: [sdd] Write Protect is off
[ 1687.042041] sd 6:0:0:0: [sdd] Mode Sense: 47 00 10 08
[ 1687.042306] sd 6:0:0:0: [sdd] No Caching mode page found
[ 1687.042313] sd 6:0:0:0: [sdd] Assuming drive cache: write through
[ 1687.079397]  sdd: sdd1
[ 1687.081236] sd 6:0:0:0: [sdd] Attached SCSI disk
[ 1687.081363] ses 6:0:0:1: Attached Enclosure device

business_kid · 12-05-2020, 06:27 AM

Not to me.

It indicated the drive was slow to speed up, and the software initally read it wrong and posted errors. It often happens with platter disks.

k.king · 12-05-2020, 07:57 AM

so anything can do to make it re-attempt load or mount?

business_kid · 12-05-2020, 11:55 AM

About half way down your log, it gives you a line 'spinning up disk …", that is, spinning up from zero speed.
Then follow a few errors when it attempts to read the disk while it is underspeed, I guess.

Then it announces 'ready' and does the usual stuff. You don't appear to have it in fstab. In X, you should just retry to mount it, or in a terminal, type

Quote:

sudo mount /dev/sdd1 /somewhere

sgosnell · 12-05-2020, 11:59 AM

There are multiple ways of automounting external drives. You apparently disabled whatever was in use by whatever distro and desktop environment you're using. If you don't want it automounted, you can use the standard mount command. If you do want it automounted, you can put it in /etc/fstab or you can enable automounting hwever that works in whatever DE you're running.

k.king · 12-06-2020, 03:14 AM

Code:

You don't appear to have it in fstab

I can try that, but as it's a portable external drive and not always in use, I don't want it in fstab.

Code:

In X, you should just retry to mount it, or in a terminal, type
Quote:
sudo mount /dev/sdd1 /somewhere

no dice, it is not seen to mount nor be able to act on e.g. gparted /dev/sdd fails

Code:

There are multiple ways of automounting external drives. You apparently disabled whatever was in use

nope, all other usb (pen) drives are still automounting fine

syg00 · 12-06-2020, 03:29 AM

Sounds like a dodgy interface or power maybe. Try the simple things - ues a different cable, and a different plug. Keep an eye on later messages. Plug it in and post "lsblk -f".

k.king · 12-06-2020, 04:03 AM

I swapped to a known working USB cable from another drive
Same results (in dmesg too)
I tried an entry in fstab (that just screwed up the boot process had to revert)
running lsblk -f yields

Code:

NAME   FSTYPE LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sdd                                                                           
└─sdd1 ntfs   My Passport F474B7AA74B76DCC

syg00 · 12-06-2020, 04:09 AM

So it's seen ok. Try mounting it and post all messasges. Also what do you mean by "gparted /dev/sdd fails" ?. Let's see any and all messages - post a photo in need.

k.king · 12-06-2020, 05:39 AM

Code:

what do you mean by "gparted /dev/sdd fails"

Meaning it takes a very long time before showing an ntfs partition with the triangle warning symbol asking for more info yields

Code:

Failed to read lock '/dev/sdd1': Resource temporarily unavailable
Error opening '/dev/sdd1': Resource temporarily unavailable
Failed to mount '/dev/sdd1': Resource temporarily unavailable

Unable to read the contents of this file system!
Because of this some operations may be unavailable.
The cause might be a missing software package.
The following list of software packages is required for ntfs file system support:  ntfs-3g / ntfsprogs.

with regards

Code:

 Try mounting it and post all messages

again takes a very long time before finally responding

Code:

$ sudo mount -t ntfs-3g /dev/sdd1 /mnt/TST099
Error reading bootsector: Input/output error
Failed to mount '/dev/sdd1': Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details.

btw syslog contains

Code:

Dec  6 11:24:16 Unit200320 systemd-udevd[373]: sdd1: Worker [4464] failed
Dec  6 11:24:32 Unit200320 kernel: [ 5350.475501] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=181s
Dec  6 11:24:32 Unit200320 kernel: [ 5350.475507] sd 6:0:0:0: [sdd] tag#0 Sense Key : Not Ready [current]
Dec  6 11:24:32 Unit200320 kernel: [ 5350.475511] sd 6:0:0:0: [sdd] tag#0 Add. Sense: Logical unit is in process of becoming ready
Dec  6 11:24:32 Unit200320 kernel: [ 5350.475516] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 08 00 00 00 20 00
Dec  6 11:24:32 Unit200320 kernel: [ 5350.475522] blk_update_request: I/O error, dev sdd, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
Dec  6 11:27:34 Unit200320 kernel: [ 5532.273046] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=181s
Dec  6 11:27:34 Unit200320 kernel: [ 5532.273052] sd 6:0:0:0: [sdd] tag#0 Sense Key : Not Ready [current]
Dec  6 11:27:34 Unit200320 kernel: [ 5532.273057] sd 6:0:0:0: [sdd] tag#0 Add. Sense: Logical unit is in process of becoming ready
Dec  6 11:27:34 Unit200320 kernel: [ 5532.273061] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 e8 df 87 80 00 00 08 00
Dec  6 11:27:34 Unit200320 kernel: [ 5532.273067] blk_update_request: I/O error, dev sdd, sector 3906963328 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Dec  6 11:30:01 Unit200320 CRON[4675]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Dec  6 11:30:42 Unit200320 kernel: [ 5720.129860] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=187s
Dec  6 11:30:42 Unit200320 kernel: [ 5720.129866] sd 6:0:0:0: [sdd] tag#0 Sense Key : Not Ready [current]
Dec  6 11:30:42 Unit200320 kernel: [ 5720.129871] sd 6:0:0:0: [sdd] tag#0 Add. Sense: Logical unit is in process of becoming ready
Dec  6 11:30:42 Unit200320 kernel: [ 5720.129876] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 08 00 00 00 08 00
Dec  6 11:30:42 Unit200320 kernel: [ 5720.129881] blk_update_request: I/O error, dev sdd, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Dec  6 11:30:42 Unit200320 kernel: [ 5720.129890] Buffer I/O error on dev sdd1, logical block 0, async page read

business_kid · 12-06-2020, 05:42 AM

Code:

NAME   FSTYPE LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sdd                                                                           
└─sdd1 ntfs   My Passport F474B7AA74B76DCC

+1 on syg00's comment. I think I posted that a few posts ago. You have to be root to mount stuff or run gparted, you know that? IME, when these issues go over 8 posts, I begin to question if the OP is acting on advice.

k.king · 12-06-2020, 05:50 AM

really ... all are run with sudo

syg00 · 12-06-2020, 05:55 AM

I'll cut a little more slack - is ntfs-3g installed. If not, why not ?. The in-kernel NTFS driver is as old as dirt. Worst case, the I/O errors may be real (physical) errors, but let's assume they are just logical errors because ntfs-3g isn't there.
As always, more data is always beneficial.

k.king · 12-06-2020, 06:08 AM

Code:

is ntfs-3g installed

yes that is why this drive always used to work
and
as mentioned, all other usb drives still continue to work.... it is only this drive that no longer co-operates.

wpeckham · 12-06-2020, 06:33 AM

Quote:

Originally Posted by k.king

Code:

is ntfs-3g installed

yes that is why this drive always used to work
and
as mentioned, all other usb drives still continue to work.... it is only this drive that no longer co-operates.

Are the other devices, the ones that work, formatted NTFS?