Description of problem: No appropriate driver for this device is found when it is plugged into a USB port. Not sure whether this is a udev problem or kernel. No doubt somebody will say ;) Sorry I don't have enough knowledge to be more accurate. This may just be a feature request. Version-Release number of selected component (if applicable): kernel-modules-5.4.19-200.fc31.x86_64 libgudev-232-6.fc31.x86_64 systemd-udev-243.7-1.fc31.x86_64 How reproducible: 100% Steps to Reproduce: 1. tail -f /var/log/messages 2. Plug in USB device (with mSATA SSD installed). 3. Wait for kernel to say: kernel: sd 6:0:0:0: [sde] Attached SCSI removable disk 4. fdisk -l /dev/sde Actual results: fdisk: cannot open /dev/sde: No medium found Expected results: Disk /dev/sde: 60 GiB, etc. Additional info: Bug 1408603 seems related but is closed EOL. Here is the device itself: https://smile.amazon.co.uk/dp/B07B7LCYXR?ref_=pe_3187911_248764861_302_E_DDE_dt_1
Further info: hw-probe produces this output: USB 174c:55aa » / 08-06-50 ASMedia Technology Inc. Name: ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge disk usb_storage, uas detected Then it adds,'This device model is known to have problems' in a mouseover message.
This bug was filed against udev package, but that page is logn gone (and nobody looks at the bugs here). Reassigning to systemd.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-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 '31'. 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 31 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.
Missing drivers is a kernel issue. I don't think this is related to systemd/udevd in any way. As first step, please check if the newest kernels also don't support the device. See https://fedoraproject.org/wiki/RawhideKernelNodebug.
The kernel contains support for these ASMedia devices but they are known to be difficult. As an example please see the hoops the uas module jumps through to try to identify ASMedia hardware correctly: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/usb/storage/uas-detect.h#n74 If this is still a problem with rawhide kernel then please provide the same data as requested in BZ1230336#c3. You might also try to have the hardware use the older usb-storage method instead of uas with something like: $ echo options usb-storage quirks=174c:55aa:u | sudo tee /etc/modprobe.d/blacklist_asmedia-55aa.conf $ sudo dracut -f reboot To undo that remove the /etc/modprobe.d/blacklist_asmedia-55aa.conf file and rerun dracut.
Thanks for this. I no longer have the device, so perhaps this bug should be closed.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.