Does not detect hotplugged storage device

Bug #1410012 reported by themusicgod1
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I plug it in, it doesn't automatically mount, is not visible in nautilus. Mounts fine on system start up.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: udev 218-3ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
ApportVersion: 2.15.1-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Jan 12 22:07:54 2015
EcryptfsInUse: Yes
HotplugNewDevices: /dev/sda /dev/sda1
HotplugNewMounts:

InstallationDate: Installed on 2014-07-09 (187 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708)
MachineType: Acer TravelMate P273-MG
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-8-generic root=UUID=885e04f0-bd26-4885-aa1c-f134c674b8ff ro quiet splash vt.handoff=7
SourcePackage: systemd
Symptom: storage
Title: Does not detect hotplugged storage device
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/27/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.11
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: BA70_HC
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd11/27/2013:svnAcer:pnTravelMateP273-MG:pvrV2.11:rvnAcer:rnBA70_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: TravelMate P273-MG
dmi.product.version: V2.11
dmi.sys.vendor: Acer

Revision history for this message
themusicgod1 (themusicgod1) wrote :
Revision history for this message
Friedemann Schorer (friedemann-schorer) wrote :

Similar problem for me - upgraded from Kubuntu 14.04 to 14.10 to 15.04 beta2 yesterday, plugging in HDD, not showing up in device manager.
syslog gets this upon plugging in:

Apr 17 11:11:37 tp220 kernel: [13210.882897] usb 4-1.2: new high-speed USB device number 7 using ehci-pci
Apr 17 11:11:40 tp220 kernel: [13213.174753] usb 4-1.2: New USB device found, idVendor=174c, idProduct=5106
Apr 17 11:11:40 tp220 kernel: [13213.174764] usb 4-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Apr 17 11:11:40 tp220 kernel: [13213.174770] usb 4-1.2: Product: AS2105
Apr 17 11:11:40 tp220 kernel: [13213.174775] usb 4-1.2: Manufacturer: ASMedia
Apr 17 11:11:40 tp220 kernel: [13213.174779] usb 4-1.2: SerialNumber: JD1008CC0PNERW
Apr 17 11:11:40 tp220 mtp-probe: checking bus 4, device 7: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.2"
Apr 17 11:11:40 tp220 mtp-probe: bus: 4, device: 7 was not an MTP device

HDD doesn't show up in /dev/sd*

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in systemd (Ubuntu):
status: New → Confirmed
Revision history for this message
Martin Pitt (pitti) wrote :

Friedemann, your problem is different. If /dev/sd* does not show up, then this is a kernel or hardware bug.

Changed in systemd (Ubuntu):
status: Confirmed → New
Revision history for this message
Martin Pitt (pitti) wrote :

themusicgod1: Can you still reproduce this? If so, can you please do this:

   udevadm monitor -e

then plug in the drive, and wait a few seconds. Please copy&paste the entire output here.

After that, please do

  udevadm info --export-db > /tmp/udevdb.txt

and attach /tmp/udevdb.txt.

Thanks!

Changed in systemd (Ubuntu):
status: New → Incomplete
Revision history for this message
themusicgod1 (themusicgod1) wrote :
Download full text (9.0 KiB)

If anything it's gotten worse: it used to be on restart, if the drive was plugged in, it would be detected whereas if I plugged it in it would not, now even on restart it's not detected. Mounting manually works just fine.

root@Hedy:/home/themusicgod1# udevadm monitor -e
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[1023.973900] add /devices/pci0000:00/0000:00:14.0/usb2/2-1 (usb)
ACTION=add
BUSNUM=002
DEVNAME=/dev/bus/usb/002/003
DEVNUM=003
DEVPATH=/devices/pci0000:00/0000:00:14.0/usb2/2-1
DEVTYPE=usb_device
MAJOR=189
MINOR=130
PRODUCT=bc2/ab31/342
SEQNUM=2849
SUBSYSTEM=usb
TYPE=0/0/0

KERNEL[1023.974517] add /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0 (usb)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0
DEVTYPE=usb_interface
INTERFACE=8/6/80
MODALIAS=usb:v0BC2pAB31d0342dc00dsc00dp00ic08isc06ip50in00
PRODUCT=bc2/ab31/342
SEQNUM=2850
SUBSYSTEM=usb
TYPE=0/0/0

KERNEL[1023.975297] add /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host7 (scsi)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host7
DEVTYPE=scsi_host
SEQNUM=2851
SUBSYSTEM=scsi

KERNEL[1023.975505] add /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host7/scsi_host/host7 (scsi_host)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host7/scsi_host/host7
SEQNUM=2852
SUBSYSTEM=scsi_host

KERNEL[1023.977126] add /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host7/target7:0:0 (scsi)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host7/target7:0:0
DEVTYPE=scsi_target
SEQNUM=2853
SUBSYSTEM=scsi

KERNEL[1023.977258] add /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host7/target7:0:0/7:0:0:0 (scsi)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host7/target7:0:0/7:0:0:0
DEVTYPE=scsi_device
MODALIAS=scsi:t-0x00
SEQNUM=2854
SUBSYSTEM=scsi

KERNEL[1023.977324] add /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host7/target7:0:0/7:0:0:0/scsi_disk/7:0:0:0 (scsi_disk)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host7/target7:0:0/7:0:0:0/scsi_disk/7:0:0:0
SEQNUM=2855
SUBSYSTEM=scsi_disk

KERNEL[1023.977440] add /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host7/target7:0:0/7:0:0:0/scsi_device/7:0:0:0 (scsi_device)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host7/target7:0:0/7:0:0:0/scsi_device/7:0:0:0
SEQNUM=2856
SUBSYSTEM=scsi_device

KERNEL[1023.979630] add /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host7/target7:0:0/7:0:0:0/scsi_generic/sg0 (scsi_generic)
ACTION=add
DEVNAME=/dev/sg0
DEVPATH=/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host7/target7:0:0/7:0:0:0/scsi_generic/sg0
MAJOR=21
MINOR=0
SEQNUM=2857
SUBSYSTEM=scsi_generic

KERNEL[1023.979743] add /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host7/target7:0:0/7:0:0:0/bsg/7:0:0:0 (bsg)
ACTION=add
DEVNAME=/dev/bsg/7:0:0:0
DEVPATH=/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host7/target7:0:0/7:0:0:0/bsg/7:0:0:0
MAJOR=252
MINOR=0
SEQNUM=2858
SUBSYSTEM=bsg

UDEV [1023.980608] add /devices/pci00...

Read more...

Revision history for this message
themusicgod1 (themusicgod1) wrote :

attachment /tmp/udevdb.txt

Changed in systemd (Ubuntu):
status: Incomplete → Opinion
status: Opinion → New
Revision history for this message
themusicgod1 (themusicgod1) wrote :

Still issue in 15.10 wily werewolf.

Revision history for this message
TJ (tj) wrote :

Came across this bug looking for another issue. Some observations:

There is no information in this report of the file-system type. It is file-systems not partitions or devices that are mounted, so any problem with an unclean file-system could prevent it being auto-mounted.

The partition looks to use the entire 4GB so any fsck on a file-sytem within it would take a long time before an auto-mount could occur.

Revision history for this message
themusicgod1 (themusicgod1) wrote :

fdisk:
Device Start End Sectors Size Type
/dev/sdb1 63 976751999 976751937 3.7T Microsoft basic data

df -T
/dev/sdb1 ext4 3845699852 3638315492 12017592 100% /mnt/disk

Revision history for this message
TJ (tj) wrote :

What does this report?

$ sudo lsblk /dev/sdb1

Also, is there an entry referring to it already, possibly with noauto option?

$ cat /etc/fstab

I'm wondering if you are effected by the mirror side of the issue I was researching.

In my case systemd is insisting on trying to mount non-existent hot-plug storage devices at boot-time. The external storage is connected via ExpressCard/SATA controller. At some point systemd added entries for the encrypted partitions, LVM VGs, and file-systems into its generator targets, and now at every boot waits for a long time waiting for those devices to appear.

$ ls -l /var/run/systemd/generator/

So far I've not found out how to safely disable those generator targets, or how to prevent them being created in the first place.

I wonder if your system has similar targets configured not to mount the file-system, or no targets at all?

Revision history for this message
themusicgod1 (themusicgod1) wrote :

 lsblk /dev/sdb1
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb1 8:17 0 3.7T 0 part /mnt/disk

fstab:
UUID=885e04f0-bd26-4885-aa1c-f134c674b8ff / ext4 errors=remount-ro 0 1
/swap none swap defaults
(ie only my other hard disk and swap)

ls -l /var/run/systemd/generator/
total 8
drwxr-xr-x 2 root root 60 Oct 16 13:54 local-fs.target.requires
drwxr-xr-x 2 root root 60 Oct 16 13:54 local-fs.target.wants
-rw-r--r-- 1 root root 277 Oct 16 13:54 -.mount
drwxr-xr-x 2 root root 60 Oct 16 13:54 multi-user.target.wants
-rw-r--r-- 1 root root 0 Oct 16 13:54 netplan.stamp
drwxr-xr-x 2 root root 40 Oct 16 13:54 openvpn.service.wants
drwxr-xr-x 2 root root 40 Oct 16 13:54 postfix.service.wants
-rw-r--r-- 1 root root 160 Oct 16 13:54 swap.swap
drwxr-xr-x 2 root root 60 Oct 16 13:54 swap.target.requires
drwxr-xr-x 2 root root 60 Oct 16 13:54 tor.service.wants

tags: added: yakkety
Revision history for this message
themusicgod1 (themusicgod1) wrote :

I've since bought about 4 more 4TiB storage devices that all have the same issue(different manufacturers (?))

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

As far as I understand big hard-drives are not automatically mounted - but should be present as partitions to mount via nautilus. E.g. I would not expect 4TiB drives to automount.
Automatically mounted are only flash-usb sticks.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in systemd (Ubuntu):
status: New → Confirmed
Dan Streetman (ddstreet)
Changed in systemd (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.