On Wednesday, 31 July 2024 10:36:20 BST Jacques Montier wrote: > Hello all, > > For a few days, my two usb external disks do not automatically mount on > /run/media/<user>
Have you changed your PC, USB port/hub, kernel or your udisks version, before you noticed this? If you observed this on a laptop, does it happen when mains power is on? > Those disks are successfully detected. > - dmesg : > 20.711135] usb 10-2: New USB device found, idVendor=1058, > idProduct=2621, bcdDevice=10.34 > [ 20.711144] usb 10-2: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [ 20.711147] usb 10-2: Product: Elements 2621 > [ 20.711150] usb 10-2: Manufacturer: Western Digital > [ 20.711152] usb 10-2: SerialNumber: 575837324139315041324831 > [ 20.712935] usb-storage 10-2:1.0: USB Mass Storage device detected > [ 20.713081] scsi host14: usb-storage 10-2:1.0 > [ 21.740964] scsi 14:0:0:0: Direct-Access WD Elements 2621 > 1034 PQ: 0 ANSI: 6 > [ 21.741163] sd 14:0:0:0: Attached scsi generic sg6 type 0 > [ 21.743671] sd 14:0:0:0: [sde] Spinning up disk... > [ 22.764230] ....ready > [ 25.936769] sd 14:0:0:0: [sde] 3906963456 512-byte logical blocks: (2.00 > TB/1.82 TiB) > [ 25.937331] sd 14:0:0:0: [sde] Write Protect is off > [ 25.937337] sd 14:0:0:0: [sde] Mode Sense: 47 00 10 08 > [ 25.937831] sd 14:0:0:0: [sde] No Caching mode page found > [ 25.937836] sd 14:0:0:0: [sde] Assuming drive cache: write through > [ 25.939868] sde: sde1 > > - Some errors by journalctl (attached file) > > juil. 31 11:21:00 GentooLinux udisksd[1178]: Error probing device: Error > sending ATA command IDENTIFY DEVICE to '/dev/sde': Unexpected> > 0000: f0 00 01 00 00 00 00 0a > 00 00 00 00 00 1d 00 00 ................ > 0010: 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 ................ > (g-io-error-quark, 0) > > - I can manually mount them without any issue. > > - USB sticks successfully mount. > > - No problem with Linux Mint OS 23.1 > > Any idea ? > > Thanks in advance, > > Cheers, > > -- > Jacques It often happens external USB drives need enough power to start up fully, before their onboard controller responds to probes from udisksd. If something (from PSU, to battery power, to kernel/desktop power management options) has changed, to the point where the power on the USB port becomes marginal, then such symptoms are possible. Things you could try: 1. Try a different USB port, ideally USB 3.0 or later version e.g. USB 3.2 Gen2, which can provide more power. 2. Use a powered USB Hub between the PC and the drive, or a Y-shaped USB cable to feed the drive from two ports. 3. If on a laptop, use mains power (esp. in the summer when the cooling fan may be demanding more from the battery). 4. Remove other consumables from USB ports sharing the same bus. 5. Do not set your desktop to auto-mount USBs when you plug in, but only when you manually click on it in your GUI. Anecdotal observation: I have a WD Elements drive which I connect through an external powered hub on a USB 2.0 port on the PC. Even though the hub is powered, I have to power it up first, wait a few seconds for the drive to come up to speed (the LED flashing slows down), before I boot the PC. Otherwise it's a hit or miss affair for the PC to detect it. This got worse after some months/years, although the drive itself has seen relatively little use.
signature.asc
Description: This is a digitally signed message part.
