Bug 1364769 - Hardware Error on USB Drive since Fedora Core 24
Summary: Hardware Error on USB Drive since Fedora Core 24
Keywords:
Status: CLOSED DUPLICATE of bug 1351305
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 24
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-07 09:14 UTC by Maarten van Leunen
Modified: 2016-08-10 07:38 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-08-10 07:38:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Maarten van Leunen 2016-08-07 09:14:07 UTC
Description of problem:
dmesg shows error when plugging usb drive into Fedora Core 24. Recently upgraded from Fedora Core 22 which did not have this problem.

I can mount the diskdrive just fine and all data is on it.

Version-Release number of selected component (if applicable):
Fedora Core 24

How reproducible:
Plug in USB drive.

Steps to Reproduce:
1. plugin usb drive
2. check dmesg

Actual results:
[  666.722960] usb 1-1.6: new high-speed USB device number 3 using ehci-pci
[  666.809652] usb 1-1.6: New USB device found, idVendor=1058, idProduct=1021
[  666.809658] usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  666.809662] usb 1-1.6: Product: Ext HDD 1021
[  666.809666] usb 1-1.6: Manufacturer: Western Digital
[  666.809669] usb 1-1.6: SerialNumber: 574D43315432313138383334
[  666.879403] usb-storage 1-1.6:1.0: USB Mass Storage device detected
[  666.879567] scsi host10: usb-storage 1-1.6:1.0
[  666.879732] usbcore: registered new interface driver usb-storage
[  666.887991] usbcore: registered new interface driver uas
[  667.884708] scsi 10:0:0:0: Direct-Access     WD       Ext HDD 1021     2021 PQ: 0 ANSI: 4
[  667.885571] sd 10:0:0:0: Attached scsi generic sg2 type 0
[  667.886205] sd 10:0:0:0: [sdc] 3907024896 512-byte logical blocks: (2.00 TB/1.82 TiB)
[  667.888224] sd 10:0:0:0: [sdc] Write Protect is off
[  667.888234] sd 10:0:0:0: [sdc] Mode Sense: 17 00 10 08
[  667.890218] sd 10:0:0:0: [sdc] No Caching mode page found
[  667.890228] sd 10:0:0:0: [sdc] Assuming drive cache: write through
[  667.917280]  sdc: sdc1
[  667.922716] sd 10:0:0:0: [sdc] Attached SCSI disk
[  668.099563] sd 10:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[  668.099575] sd 10:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] [descriptor] 
[  668.099582] sd 10:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
[  668.099590] sd 10:0:0:0: [sdc] tag#0 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
[  668.207723] sd 10:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[  668.207728] sd 10:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] [descriptor] 
[  668.207730] sd 10:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
[  668.207733] sd 10:0:0:0: [sdc] tag#0 CDB: ATA command pass through(12)/Blank a1 06 20 da 00 00 4f c2 00 b0 00 00
[  668.229296] md: bind<sdc1>
[  668.925847] usb 1-1.5: new high-speed USB device number 4 using ehci-pci
[  669.012551] usb 1-1.5: New USB device found, idVendor=1058, idProduct=1021
[  669.012557] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  669.012561] usb 1-1.5: Product: Ext HDD 1021
[  669.012565] usb 1-1.5: Manufacturer: Western Digital
[  669.012568] usb 1-1.5: SerialNumber: 574D43315431373033343231
[  669.014816] usb-storage 1-1.5:1.0: USB Mass Storage device detected
[  669.015010] scsi host11: usb-storage 1-1.5:1.0
[  670.020481] scsi 11:0:0:0: Direct-Access     WD       Ext HDD 1021     2021 PQ: 0 ANSI: 4
[  670.021425] sd 11:0:0:0: Attached scsi generic sg3 type 0
[  670.023802] sd 11:0:0:0: [sdd] 3907024896 512-byte logical blocks: (2.00 TB/1.82 TiB)
[  670.025793] sd 11:0:0:0: [sdd] Write Protect is off
[  670.025801] sd 11:0:0:0: [sdd] Mode Sense: 17 00 10 08
[  670.027774] sd 11:0:0:0: [sdd] No Caching mode page found
[  670.027781] sd 11:0:0:0: [sdd] Assuming drive cache: write through
[  670.059454]  sdd: sdd1
[  670.064823] sd 11:0:0:0: [sdd] Attached SCSI disk
[  670.263123] sd 11:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[  670.263129] sd 11:0:0:0: [sdd] tag#0 Sense Key : Hardware Error [current] [descriptor] 
[  670.263132] sd 11:0:0:0: [sdd] tag#0 Add. Sense: No additional sense information
[  670.263136] sd 11:0:0:0: [sdd] tag#0 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
[  670.354942] sd 11:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[  670.354951] sd 11:0:0:0: [sdd] tag#0 Sense Key : Hardware Error [current] [descriptor] 
[  670.354956] sd 11:0:0:0: [sdd] tag#0 Add. Sense: No additional sense information
[  670.354961] sd 11:0:0:0: [sdd] tag#0 CDB: ATA command pass through(12)/Blank a1 06 20 da 00 00 4f c2 00 b0 00 00
[  670.446699] md: bind<sdd1>
[  670.490276] md: raid1 personality registered for level 1
[  670.490646] md/raid1:md0: active with 2 out of 2 mirrors
[  670.490671] md0: detected capacity change from 0 to 2000261283840
[  837.150302] perf: interrupt took too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
[  892.107055] EXT4-fs (md0): mounting ext3 file system using the ext4 subsystem
[  893.368252] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)


Expected results:
Same but without the tag#0 errors.

Additional info:
- As I said, the drive mounts just fine, but I get a little spooked with messages like this.
- Fedora core 22 did not have this problem
- Not that it matters, but the two drives are a software raid1 configuration with md (but should not matter here)

Comment 2 Maarten van Leunen 2016-08-10 07:37:49 UTC
Running kernel:

bash-4.3$ uname -a
Linux micemouse 4.6.4-301.fc24.i686 #1 SMP Tue Jul 12 12:25:36 UTC 2016 i686 i686 i386 GNU/Linux

Comment 3 Maarten van Leunen 2016-08-10 07:38:15 UTC

*** This bug has been marked as a duplicate of bug 1351305 ***


Note You need to log in before you can comment on or make changes to this bug.