Bug 1374866 - Seagate Backup Plus 4T not accessible on USB 3.0 ports
Summary: Seagate Backup Plus 4T not accessible on USB 3.0 ports
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 24
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-09 21:57 UTC by Neal Zimmermann
Modified: 2017-08-08 17:14 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 17:14:00 UTC
Type: Bug


Attachments (Terms of Use)
related information (1.28 KB, text/plain)
2016-09-09 21:57 UTC, Neal Zimmermann
no flags Details

Description Neal Zimmermann 2016-09-09 21:57:18 UTC
Created attachment 1199665 [details]
related information

Description of problem:
When the backup plus is plugged into a USB 3.0 port, it will make a "sing sing sing" (interval between is 2 to 3 seconds) sounds.  The drive fails scrub erase, formatting.  It can be portioned.

A second drive seems to work fine if connected to USB 2.0 ports.

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

4.7.2-201.fc24.x86_64

How reproducible:
Everytime


Steps to Reproduce:
1.Plug the drive into a USB port.
2.Same issues on two different drives (same make and model)
3.

Actual results:
Makes a periodic sound (see above).
Is inaccessible.


Expected results:
Mount and access as any other drive


Additional info:
May have destroyed drive.

Comment 1 Neal Zimmermann 2016-09-11 01:53:08 UTC
For attachment 1199665 [details]: Problem occurs on the Beta and Delta computers when using the USB 3.0 ports, untested on the Gamma computer.

Comment 2 Justin M. Forbes 2017-04-11 15:01:45 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-100.fc24.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.

Comment 3 Neal Zimmermann 2017-04-16 14:38:21 UTC
Post Kernel 4.10.9-100.fc24 upgrade:

Drive no longer makes noise, but is still not recognized on a USB3.0 port.

Comment 4 Fedora End Of Life 2017-07-25 22:56:51 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 2017-08-08 17:14:00 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.