`lsblk` not displaying USB Mass Storage Device But Shows Up On `lsusb` about usbipd-win HOT 6 CLOSED

What's in the WSL syslog when you attach?

from usbipd-win.

/var/log/syslog does not exist as a file or directory.

from usbipd-win.

If you are not running a syslog daemon (syslogd or journald), you can get live logging if you leave dmesg running.

This is really a Linux administration issue, judging from:

Bus 001 Device 002: ID 05ac:12a8 Apple, Inc. iPhone 5/5C/5S/6/SE

usbipd-win is working fine.

from usbipd-win.

usbipd-win just forwards the device, it does not care about the device type. The fact that the attach worked means that usbipd-win is working. It is now up to the client to load a driver for it and send URBs to the device.

I don't know that device type it is, maybe a block device requiring a special driver, maybe some other device type. But as far as usbipd-win is concerned, it doesn't matter. You really need to check the client (WSL) side logs/device tree to see what device drivers are required. A normal starting point would be syslog, or dmesg, or lsusb -v.

from usbipd-win.

There is no storage class amongst the interface listed. Maybe you need to enable that in the device (either before you plug it in, or approve file access after you plug it in). All seems working correctly otherwise.

from usbipd-win.

The device (in its current configuration) simply does not expose a mass storage interface; the mass storage driver simply isn't activated because the device does not support it (in its current configuration). That has nothing to do with the kernel. You probably need to configure the device itself somehow; maybe proprietary software is needed to configure the device (it has several "Vender Specific" interfaces after all).

In the end, this has nothing to do with usbipd-win, which itself is entirely device type agnostic. usbipd-win just passes through all USB traffic irrespective of the device type.

from usbipd-win.