Bug 1627602 - device <n> was not an MTP device
Summary: device <n> was not an MTP device
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-11 01:15 UTC by Peter H. Jones
Modified: 2018-11-30 22:55 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-11-30 22:55:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journal file of successful mount, lines of interest are about 1772-1805 (236.11 KB, text/x-vhdl)
2018-09-11 01:23 UTC, Peter H. Jones
no flags Details
journal file of failed mount, lines of interest are about 2274-2284 (297.04 KB, text/x-vhdl)
2018-09-11 01:28 UTC, Peter H. Jones
no flags Details
journal file of successful mount, lines of interest are about 1001-end (241.54 KB, text/plain)
2018-09-18 18:54 UTC, Peter H. Jones
no flags Details
journal file of failed mount, lines of interest are about 2247-end (291.17 KB, text/plain)
2018-09-18 18:57 UTC, Peter H. Jones
no flags Details

Description Peter H. Jones 2018-09-11 01:15:07 UTC
Description of problem:
USB disk drive is not recognized, appears in lsusb, but not lsblk.

Version-Release number of selected component (if applicable):
kernel-4.17.19-100.fc27.x86_64
No mtp-probe package present

How reproducible:
Every time on one computer, never on another. Software is on an SD card with USB adapter.

Steps to Reproduce:
1. Boot
2. Insert Western Digital USB drive
3. journalctl -b

Actual results:
Failing system log contains "device <n> not an MTP device" message.
Failing system is a Dell XPS-15-9560.

Expected results:
Succesful mount

Additional info:
Failure also happens with Fedora 29 Workstation respin

Comment 1 Peter H. Jones 2018-09-11 01:23:44 UTC
Created attachment 1482246 [details]
journal file of successful mount, lines of interest are about 1772-1805

log file from computer where mount works

Comment 2 Peter H. Jones 2018-09-11 01:28:06 UTC
Created attachment 1482247 [details]
journal file of failed mount, lines of interest are about 2274-2284

Comment 3 Peter H. Jones 2018-09-18 18:54:40 UTC
Created attachment 1484473 [details]
journal file of successful mount, lines of interest are about 1001-end

Comment 4 Peter H. Jones 2018-09-18 18:57:26 UTC
Created attachment 1484474 [details]
journal file of failed mount, lines of interest are about 2247-end

Comment 5 Peter H. Jones 2018-09-28 01:42:28 UTC
Mount now works in kernel 4.18.10-100.fc27.x86_64.
Log is below. Are the 5 lines with x's (they show in red in journalctl) of concern? Do they indicate a problem with my disk?

journalctl -e gives:
Sep 27 21:33:16 localhost.localdomain kernel: usb 3-7: new high-speed USB device number 5 using xhci_hcd
Sep 27 21:33:17 localhost.localdomain kernel: usb 3-7: New USB device found, idVendor=1058, idProduct=0748, bcdDevice=10.19
Sep 27 21:33:17 localhost.localdomain kernel: usb 3-7: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Sep 27 21:33:17 localhost.localdomain kernel: usb 3-7: Product: My Passport 0748
Sep 27 21:33:17 localhost.localdomain kernel: usb 3-7: Manufacturer: Western Digital
Sep 27 21:33:17 localhost.localdomain kernel: usb 3-7: SerialNumber: 575838314542325846353334
Sep 27 21:33:17 localhost.localdomain kernel: usb-storage 3-7:1.0: USB Mass Storage device detected
Sep 27 21:33:17 localhost.localdomain kernel: scsi host7: usb-storage 3-7:1.0
Sep 27 21:33:17 localhost.localdomain mtp-probe[2972]: checking bus 3, device 5: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-7"
Sep 27 21:33:17 localhost.localdomain mtp-probe[2972]: bus: 3, device: 5 was not an MTP device
Sep 27 21:33:18 localhost.localdomain kernel: scsi 7:0:0:0: Direct-Access     WD       My Passport 0748 1019 PQ: 0 ANSI: 6
Sep 27 21:33:18 localhost.localdomain kernel: scsi 7:0:0:1: Enclosure         WD       SES Device       1019 PQ: 0 ANSI: 6
Sep 27 21:33:18 localhost.localdomain kernel: sd 7:0:0:0: Attached scsi generic sg4 type 0
Sep 27 21:33:18 localhost.localdomain kernel: scsi 7:0:0:1: Attached scsi generic sg5 type 13
Sep 27 21:33:18 localhost.localdomain kernel: sd 7:0:0:0: [sdd] Spinning up disk...
Sep 27 21:33:24 localhost.localdomain kernel: .
Sep 27 21:33:24 localhost.localdomain kernel: scsi 7:0:0:1: Wrong diagnostic page; asked for 1 got 8 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Sep 27 21:33:24 localhost.localdomain kernel: scsi 7:0:0:1: Failed to get diagnostic page 0x1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Sep 27 21:33:24 localhost.localdomain kernel: scsi 7:0:0:1: Failed to bind enclosure -19 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Sep 27 21:33:24 localhost.localdomain kernel: ses 7:0:0:1: Attached Enclosure device
Sep 27 21:33:24 localhost.localdomain kernel: ready
Sep 27 21:33:24 localhost.localdomain kernel: sd 7:0:0:0: [sdd] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB)
Sep 27 21:33:24 localhost.localdomain kernel: sd 7:0:0:0: [sdd] Write Protect is off
Sep 27 21:33:24 localhost.localdomain kernel: sd 7:0:0:0: [sdd] Mode Sense: 47 00 10 08
Sep 27 21:33:24 localhost.localdomain kernel: sd 7:0:0:0: [sdd] No Caching mode page found xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Sep 27 21:33:24 localhost.localdomain kernel: sd 7:0:0:0: [sdd] Assuming drive cache: write through xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Sep 27 21:33:24 localhost.localdomain kernel:  sdd: sdd1 sdd2 sdd3 sdd4
Sep 27 21:33:24 localhost.localdomain kernel: sd 7:0:0:0: [sdd] Attached SCSI disk
Sep 27 21:33:24 localhost.localdomain kernel: EXT4-fs (sdd1): mounted filesystem with ordered data mode. Opts: (null)
Sep 27 21:33:24 localhost.localdomain udisksd[772]: Mounted /dev/sdd1 at /run/media/jones/2tp001data on behalf of uid 3000
Sep 27 21:33:25 localhost.localdomain dbus-daemon[1507]: [session uid=3000 pid=1507] Activating service name='org.gnome.Shell.HotplugSniffer' requested by ':1.21' (uid=3000 pid=1604 comm="/usr/bin/gnome-shell " label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
Sep 27 21:33:25 localhost.localdomain tracker-miner-f[1926]: Could not set mount point in database 'urn:nepomuk:datasource:57669c6e-1453-4fa6-b8c4-d22b1ba2c9f0', GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal: UNIQUE constraint failed: nie:DataObject.nie:url
Sep 27 21:33:25 localhost.localdomain dbus-daemon[1507]: [session uid=3000 pid=1507] Successfully activated service 'org.gnome.Shell.HotplugSniffer'
Sep 27 21:33:26 localhost.localdomain ntfs-3g[3011]: Version 2017.3.23 integrated FUSE 28
Sep 27 21:33:26 localhost.localdomain ntfs-3g[3011]: Mounted /dev/sdd4 (Read-Write, label "2tp001ntfs", NTFS 3.1)
Sep 27 21:33:26 localhost.localdomain ntfs-3g[3011]: Cmdline options: rw,nodev,nosuid,uid=3000,gid=3000,uhelper=udisks2
Sep 27 21:33:26 localhost.localdomain ntfs-3g[3011]: Mount options: rw,nodev,nosuid,uhelper=udisks2,allow_other,nonempty,relatime,default_permissions,fsname=/dev/sdd4,blkdev,blksize=4096
Sep 27 21:33:26 localhost.localdomain ntfs-3g[3011]: Global ownership and permissions enforced, configuration type 7
Sep 27 21:33:26 localhost.localdomain udisksd[772]: Mounted /dev/sdd4 at /run/media/jones/2tp001ntfs on behalf of uid 3000
Sep 27 21:33:26 localhost.localdomain tracker-miner-f[1926]: Could not set mount point in database 'urn:nepomuk:datasource:69460C9C647E820C', GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal: UNIQUE constraint failed: nie:DataObject.nie:url
Sep 27 21:33:28 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Comment 6 Peter H. Jones 2018-09-28 02:27:52 UTC
Oops, my success was on a computer where the mount has always worked. The mount still doesn't work on the Dell XPS.

I'll post update system logs with the new kernel.

Comment 7 Ben Cotton 2018-11-27 14:20:10 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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 8 Ben Cotton 2018-11-30 22:55:26 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.