thunar-volman 0.8.1 (Fedora 25) Plugging in a particular thumb drive, the following gets dumped to syslog: Dec 31 13:04:18 thinkpad kernel: usb 3-2: new high-speed USB device number 3 using xhci_hcd Dec 31 13:04:18 thinkpad kernel: usb 3-2: New USB device found, idVendor=0781, idProduct=5575 Dec 31 13:04:18 thinkpad kernel: usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Dec 31 13:04:18 thinkpad kernel: usb 3-2: Product: Cruzer Glide Dec 31 13:04:18 thinkpad kernel: usb 3-2: Manufacturer: SanDisk Dec 31 13:04:18 thinkpad kernel: usb 3-2: SerialNumber: 2005194263165E0311F4 Dec 31 13:04:18 thinkpad kernel: usb-storage 3-2:1.0: USB Mass Storage device detected Dec 31 13:04:18 thinkpad kernel: scsi host6: usb-storage 3-2:1.0 Dec 31 13:04:18 thinkpad mtp-probe: checking bus 3, device 3: "/sys/devices/pci0000:00/0000:00:1c.6/0000:0e:00.0/usb3/3-2" Dec 31 13:04:18 thinkpad mtp-probe: bus: 3, device: 3 was not an MTP device Dec 31 13:04:18 thinkpad org.xfce.FileManager: thunar-volman: Unsupported USB device type "usb". Dec 31 13:04:18 thinkpad org.xfce.FileManager: thunar-volman: Unsupported USB device type "usb-storage". Dec 31 13:04:19 thinkpad kernel: scsi 6:0:0:0: Direct-Access SanDisk Cruzer Glide 1.00 PQ: 0 ANSI: 6 Dec 31 13:04:19 thinkpad kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0 Dec 31 13:04:19 thinkpad kernel: sd 6:0:0:0: [sdb] 30464000 512-byte logical blocks: (15.6 GB/14.5 GiB) Dec 31 13:04:19 thinkpad kernel: sd 6:0:0:0: [sdb] Write Protect is off Dec 31 13:04:19 thinkpad kernel: sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Dec 31 13:04:19 thinkpad kernel: sdb: sdb1 Dec 31 13:04:19 thinkpad kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk Dec 31 13:04:19 thinkpad org.xfce.FileManager: thunar-volman: Unknown block device type "disk". And the new volume does not appear in Thunar. The kernel itself has no issues reading the thumb drive: [root@thinkpad ~]# fdisk /dev/sdb Welcome to fdisk (util-linux 2.28.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): p Disk /dev/sdb: 14.5 GiB, 15597568000 bytes, 30464000 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x567e68e2 Device Boot Start End Sectors Size Id Type /dev/sdb1 * 2048 30463999 30461952 14.5G c W95 FAT32 (LBA) And I can mount it manually without any apparent issues: [root@thinkpad 0]# pwd /var/run/user/0 [root@thinkpad 0]# mkdir thumbdrive [root@thinkpad 0]# mount /dev/sdb1 thumbdrive [root@thinkpad 0]# ls -al thumbdrive total 1584 drwxr-xr-x. 6 root root 8192 Dec 31 1969 . drwx------. 4 root root 100 Dec 31 13:07 .. drwxr-xr-x. 4 root root 8192 Dec 31 06:24 boot -rwxr-xr-x. 1 root root 389408 Dec 9 04:52 bootmgr -rwxr-xr-x. 1 root root 1178976 Nov 2 02:12 bootmgr.efi drwxr-xr-x. 4 root root 8192 Dec 31 06:24 efi -rwxr-xr-x. 1 root root 1048 Sep 25 12:06 reagent.xml drwxr-xr-x. 2 root root 8192 Dec 31 06:24 sources drwxr-xr-x. 2 root root 8192 Dec 31 06:24 'System Volume Information' [root@thinkpad 0]# umount /dev/sdb1
So, I was having the same exact issue today. Googled it, and this came up -- my own bug report. I completely forgot about it; but this is still an issue as of 0.9.5 (F31).
What output does the following command generate? # blkid -o udev -p /dev/sdb1
[root@thinkpad ~]# blkid -p /dev/sdb /dev/sdb: PTUUID="957945d2" PTTYPE="dos"
That is not the same command.
Ok, let's try again. [root@thinkpad ~]# blkid -o udev -p /dev/sdb ID_PART_TABLE_UUID=957945d2 ID_PART_TABLE_TYPE=dos
The partition is "/dev/sdb1".
[root@thinkpad ~]# blkid -o udev -p /dev/sdb1 ID_FS_LABEL=RECOVERY ID_FS_LABEL_ENC=RECOVERY ID_FS_UUID=ACDE-1F74 ID_FS_UUID_ENC=ACDE-1F74 ID_FS_VERSION=FAT32 ID_FS_TYPE=vfat ID_FS_USAGE=filesystem ID_PART_ENTRY_SCHEME=dos ID_PART_ENTRY_UUID=957945d2-01 ID_PART_ENTRY_TYPE=0xc ID_PART_ENTRY_FLAGS=0x80 ID_PART_ENTRY_NUMBER=1 ID_PART_ENTRY_OFFSET=2048 ID_PART_ENTRY_SIZE=30461952 ID_PART_ENTRY_DISK=8:16
I found this similar looking bug report (old, closed): https://bugzilla.redhat.com/show_bug.cgi?id=1203410 Is the problem hardware or distribution specific? Does the volume appear in a different file manager?
I get the same behavior on two different hardware platforms: a laptop, plugging in the thumb drive directly onto the laptop port, and on a server plugging in the thumb drive into the USB hub. I can't say if it's distribution or file manager specific. All I have is Fedora and XFCE. Don't really use anything else. But I can tell you the following. Plugging in the thumb drive results in the following activity in syslog: Feb 4 19:36:35 monster kernel: sd 5:0:0:0: [sdc] Write Protect is off Feb 4 19:36:35 monster kernel: sd 5:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Feb 4 19:36:35 monster kernel: sdc: sdc1 Feb 4 19:36:35 monster kernel: sd 5:0:0:0: [sdc] Attached SCSI removable disk Feb 4 19:36:35 monster Thunar[3409]: thunar-volman: Unknown block device type "disk". Feb 4 19:36:41 monster Thunar[3409]: thunar-volman: Could not detect the volume corresponding to the device. Feb 4 19:36:42 monster tracker-store[93506]: OK Feb 4 19:36:42 monster systemd[2382]: tracker-store.service: Succeeded. Feb 4 19:37:07 monster kernel: usb 1-2.4.7: USB disconnect, device number 29 Feb 4 19:37:07 monster journal[81276]: Failed to open file '/sys/class/scsi_host/host5/unique_id': No such file or directory Feb 4 19:37:19 monster kernel: usb 1-2.4.6: new high-speed USB device number 30 using ehci-pci Feb 4 19:37:19 monster kernel: usb 1-2.4.6: New USB device found, idVendor=0781, idProduct=5575, bcdDevice= 1.00 Feb 4 19:37:19 monster kernel: usb 1-2.4.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Feb 4 19:37:19 monster kernel: usb 1-2.4.6: Product: Cruzer Glide Feb 4 19:37:19 monster kernel: usb 1-2.4.6: Manufacturer: SanDisk Feb 4 19:37:19 monster kernel: usb 1-2.4.6: SerialNumber: 2005194263165E0311F4 Feb 4 19:37:19 monster kernel: usb-storage 1-2.4.6:1.0: USB Mass Storage device detected Feb 4 19:37:19 monster kernel: scsi host5: usb-storage 1-2.4.6:1.0 Feb 4 19:37:19 monster mtp-probe[93604]: checking bus 1, device 30: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2.4/1-2.4.6" Feb 4 19:37:19 monster mtp-probe[93604]: bus: 1, device: 30 was not an MTP device Feb 4 19:37:19 monster mtp-probe[93611]: checking bus 1, device 30: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2.4/1-2.4.6" Feb 4 19:37:19 monster mtp-probe[93611]: bus: 1, device: 30 was not an MTP device Feb 4 19:37:19 monster Thunar[3409]: thunar-volman: Unsupported USB device type "usb". Feb 4 19:37:19 monster Thunar[3409]: thunar-volman: Unsupported USB device type "usb-storage". Feb 4 19:37:20 monster kernel: scsi 5:0:0:0: Direct-Access SanDisk Cruzer Glide 1.00 PQ: 0 ANSI: 6 Feb 4 19:37:20 monster kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0 Feb 4 19:37:20 monster kernel: sd 5:0:0:0: [sdc] 30464000 512-byte logical blocks: (15.6 GB/14.5 GiB) Feb 4 19:37:20 monster kernel: sd 5:0:0:0: [sdc] Write Protect is off Feb 4 19:37:20 monster kernel: sd 5:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Feb 4 19:37:20 monster kernel: sdc: sdc1 Feb 4 19:37:20 monster kernel: sd 5:0:0:0: [sdc] Attached SCSI removable disk Feb 4 19:37:20 monster Thunar[3409]: thunar-volman: Unknown block device type "disk". The thumb drive does not get automounted and Thunar does not open. But, at this point: [root@monster ~]# mkdir /tmp/flash [root@monster ~]# mount /dev/sdc1 /tmp/flash [root@monster ~]# ls -al /tmp/flash total 464 drwxr-xr-x. 6 root root 8192 Dec 31 1969 . drwxrwxrwt. 24 root root 620 Feb 4 19:41 .. drwxr-xr-x. 41 root root 8192 Feb 1 10:55 Boot -r-xr-xr-x. 1 root root 410988 Jan 23 17:14 bootmgr -rwxr-xr-x. 1 root root 1 Mar 18 2019 BOOTNXT drwxr-xr-x. 4 root root 8192 Feb 1 10:55 EFI -rwxr-xr-x. 1 root root 1119 Aug 10 15:01 reagent.xml drwxr-xr-x. 2 root root 8192 Feb 1 10:55 sources drwxr-xr-x. 2 root root 8192 Feb 1 10:55 'System Volume Information' Nothing out of the ordinary appears to be the case, with this thumb drive. This is maybe hardware specific only because a different thumb drive does get mounted and opened by Thunar. This is a different thumb drive, same hardware: Feb 4 19:43:55 monster kernel: usb 1-2.4.7: new high-speed USB device number 31 using ehci-pci Feb 4 19:43:55 monster kernel: usb 1-2.4.7: New USB device found, idVendor=05dc, idProduct=a838, bcdDevice=11.00 Feb 4 19:43:55 monster kernel: usb 1-2.4.7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Feb 4 19:43:55 monster kernel: usb 1-2.4.7: Product: USB Flash Drive Feb 4 19:43:55 monster kernel: usb 1-2.4.7: Manufacturer: Lexar Feb 4 19:43:55 monster kernel: usb 1-2.4.7: SerialNumber: AALXOGG5HL9TIFZS Feb 4 19:43:55 monster kernel: usb-storage 1-2.4.7:1.0: USB Mass Storage device detected Feb 4 19:43:55 monster kernel: scsi host5: usb-storage 1-2.4.7:1.0 Feb 4 19:43:55 monster mtp-probe[93803]: checking bus 1, device 31: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2.4/1-2.4.7" Feb 4 19:43:55 monster mtp-probe[93803]: bus: 1, device: 31 was not an MTP device Feb 4 19:43:55 monster mtp-probe[93809]: checking bus 1, device 31: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2.4/1-2.4.7" Feb 4 19:43:55 monster mtp-probe[93809]: bus: 1, device: 31 was not an MTP device Feb 4 19:43:55 monster Thunar[3409]: thunar-volman: Unsupported USB device type "usb". Feb 4 19:43:55 monster Thunar[3409]: thunar-volman: Unsupported USB device type "usb-storage". Feb 4 19:43:56 monster kernel: scsi 5:0:0:0: Direct-Access Lexar USB Flash Drive 1100 PQ: 0 ANSI: 6 Feb 4 19:43:56 monster kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0 Feb 4 19:43:56 monster kernel: sd 5:0:0:0: [sdc] 62517248 512-byte logical blocks: (32.0 GB/29.8 GiB) Feb 4 19:43:56 monster kernel: sd 5:0:0:0: [sdc] Write Protect is off Feb 4 19:43:56 monster kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Feb 4 19:43:56 monster kernel: sdc: sdc1 Feb 4 19:43:56 monster kernel: sd 5:0:0:0: [sdc] Attached SCSI removable disk Feb 4 19:43:56 monster Thunar[3409]: thunar-volman: Unknown block device type "disk". Feb 4 19:44:02 monster journal[3125]: Mounted /dev/sdc1 at /run/media/mrsam/Lexar on behalf of uid 1004 Feb 4 19:44:02 monster systemd[2382]: Starting Tracker metadata database store and lookup manager... Feb 4 19:44:02 monster systemd[2382]: Started Tracker metadata database store and lookup manager. Feb 4 19:44:02 monster systemd[2382]: Started dbus-:1.2-org.freedesktop.thumbnails.Thumbnailer1@7.service. Feb 4 19:44:02 monster tumblerd[93859]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o Feb 4 19:44:02 monster tumblerd[93859]: Registered thumbnailer gnome-thumbnail-font --size %s %u %o Feb 4 19:44:02 monster tumblerd[93859]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o Feb 4 19:44:02 monster tumblerd[93859]: Registered thumbnailer gsf-office-thumbnailer -i %i -o %o -s %s Feb 4 19:44:02 monster tumblerd[93859]: Registered thumbnailer evince-thumbnailer -s %s %u %o Feb 4 19:44:02 monster tumblerd[93859]: Registered thumbnailer /usr/bin/totem-video-thumbnailer -s %s %u %o Feb 4 19:44:02 monster journal[3409]: Failed to set property "thunar::/last-details-view-column-widths": Operation was cancelled n I see that this one also logs "thunar-volman: Unknown block device type "disk"." diagnostic here, but this one does get mounted, and opened, with no user action. Something about a particular class of thumb drives is preventing these thumb drives from getting automatically seen and opened in Thunar, but they can be mounted manually, and nothing appears to be out of the ordinary for them.
That is a Windows Recovery USB drive, correct? Maybe I can obtain or create one, and try to reproduce the issue.
Yes, I used "Recovery Media Creator" utility on Windows 10 to create it, without too much fanfare. It works, and I can boot a Qemu guest VM off this USB thumb drive, and get into the Windows 10 recovery tool. The disk itself looks like an ordinary vfat disk. mount autodetects its format normally, without any special options and mounts it as a vfat volume, then lists it as: /dev/sdd1 on /tmp/flash type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
-- GitLab Migration Automatic Message -- This bug has been migrated to xfce.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.xfce.org/xfce/thunar-volman/-/issues/13. Please create an account or use an existing account on one of our supported OAuth providers. If you want to fork to submit patches and merge requests please continue reading here: https://docs.xfce.org/contribute/dev/git/start#gitlab_forks_and_merge_requests Also feel free to reach out to us on the mailing list https://mail.xfce.org/mailman/listinfo/xfce4-dev