Bug 1334569 - Smartmontools issue due to UAS on Seagate Expansion Drive
Summary: Smartmontools issue due to UAS on Seagate Expansion Drive
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: smartmontools
Version: 23
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Michal Hlavinka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-10 04:25 UTC by Steven Ellis
Modified: 2016-12-20 20:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 20:25:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Steven Ellis 2016-05-10 04:25:32 UTC
Description of problem:
With UAS disabled it is possible to run smart tests on external USB3 Seagate Expansion Disk with USB IDs 0bc2:3312.

Tools fail if disk is mounted with UAS enabled

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

Kernel - 4.4.8-300.fc23.x86_64
smartmontools - smartmontools-6.4-2.fc23.x86_64

How reproducible:
Consistent

Steps to Reproduce:
1. Insert USB-3 cable and drive appears as /dev/sdb
2. smartctl -d sat -a /dev/sdb
3. smartctl -d scsi -a /dev/sdb

Actual results:

[root@t440s ~]# smartctl -d sat -a /dev/sdb
smartctl 6.4 2015-06-04 r4109 [x86_64-linux-4.4.8-300.fc23.x86_64] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org

Read Device Identity failed: scsi error unsupported field in scsi command

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.


[root@t440s ~]# smartctl -d scsi -a /dev/sdb
smartctl 6.4 2015-06-04 r4109 [x86_64-linux-4.4.8-300.fc23.x86_64] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               Seagate
Product:              Expansion Desk
Revision:             0739
Compliance:           SPC-4
User Capacity:        4,000,787,025,920 bytes [4.00 TB]
Logical block size:   4096 bytes
scsiModePageOffset: response length too short, resp_len=12 offset=12 bd_len=8
scsiModePageOffset: response length too short, resp_len=12 offset=12 bd_len=8
>> Terminate command early due to bad response to IEC mode page
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.


Expected results:

Valid set of smart output from enclosed Seagate HD

Additional info:

Drive was added to smartmontools under https://www.smartmontools.org/ticket/320. In theory shouldn't require "-d sat" or "-d scsi" to work

Comment 1 Steven Ellis 2016-05-10 06:24:37 UTC
Output if I disable UAS for the drive

echo 0bc2:3312:u > /sys/module/usb_storage/parameters/quirks


May 10 18:20:26 t440s.akl.redhat.com kernel: usb 3-2: new SuperSpeed USB device number 4 using xhci_hcd
May 10 18:20:26 t440s.akl.redhat.com kernel: usb 3-2: New USB device found, idVendor=0bc2, idProduct=3312
May 10 18:20:26 t440s.akl.redhat.com kernel: usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 10 18:20:26 t440s.akl.redhat.com kernel: usb 3-2: Product: Expansion Desk
May 10 18:20:26 t440s kernel: usb 3-2: Manufacturer: Seagate 
May 10 18:20:26 t440s kernel: usb 3-2: SerialNumber: XXXXXXXXX
May 10 18:20:26 t440s kernel: usb 3-2: UAS is blacklisted for this device, using usb-storage instead
May 10 18:20:26 t440s kernel: usb-storage 3-2:1.0: USB Mass Storage device detected
May 10 18:20:26 t440s kernel: usb-storage 3-2:1.0: Quirks match for vid 0bc2 pid 3312: 800000
May 10 18:20:26 t440s kernel: scsi host4: usb-storage 3-2:1.0
May 10 18:20:27 t440s kernel: scsi 4:0:0:0: Direct-Access     Seagate  Expansion Desk   0739 PQ: 0 ANSI: 6
May 10 18:20:27 t440s kernel: sd 4:0:0:0: Attached scsi generic sg1 type 0
May 10 18:20:27 t440s kernel: sd 4:0:0:0: [sdc] Spinning up disk...
May 10 18:20:40 t440s kernel: .........ready
May 10 18:20:40 t440s kernel: sd 4:0:0:0: [sdc] 976754645 4096-byte logical blocks: (4.00 TB/3.64 TiB)
May 10 18:20:40 t440s kernel: sd 4:0:0:0: [sdc] Write Protect is off
May 10 18:20:40 t440s kernel: sd 4:0:0:0: [sdc] Mode Sense: 2b 00 10 08
May 10 18:20:40 t440s kernel: sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
May 10 18:20:40 t440s kernel:  sdc: sdc1 sdc2
May 10 18:20:40 t440s kernel: sd 4:0:0:0: [sdc] Attached SCSI disk


[root@t440s ]# smartctl -a  /dev/sdc
smartctl 6.4 2015-06-04 r4109 [x86_64-linux-4.4.8-300.fc23.x86_64] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     ST4000DM001-1FK17N
Serial Number:    XXXXXXXXX
LU WWN Device Id: 5 000c50 078075bf0
Firmware Version: CC44
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5980 rpm
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Tue May 10 18:21:16 2016 NZST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Comment 2 Steven Ellis 2016-05-10 06:25:16 UTC
With UAS off I can run smart tests without issue.

Comment 3 Steven Ellis 2016-05-10 06:32:15 UTC
Confirmed I can reproduce the issue with the latest 6.5 release of smartmontools from source.

Comment 4 Fedora End Of Life 2016-11-25 08:59:17 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2016-12-20 20:25:14 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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