Usb mass storage device — что это?
USB Mass Storage Device — устройство, которое чаще всего является флешкой. Быстрый запуск диспетчера устройств: зажмите Win R, введите команду devmgmt.msc, нажмите ОК.
Разбор названия:
- USB — собственно и так понятно, это порт ЮСБ, в который можно подключить флешку.. разные устройства.. мышку, клавиатуру, телефон..
- Mass — переводится как массовое, то есть что-то популярное, массовое, не особо понятно. Возможно имеется ввиду массовая флеш-память?
- Storage — переводится как хранилище. Имеется ввиду хранилище данных, которым выступает флеш-память.
- Device — означает устройство, чем собственно и является флешка.
Данное устройство вы можете увидеть в диспетчере задач, может быть например в разделе Universal Serial Bus controllers:
Если напротив нет восклицательного знака, значит винда флешку нормально увидела и проблем нет. Однако бывает что проблем нет, винда определила.. но неправильно.. в таком случае нужно шаманить с драйверами..
Хм, есть мысль, что если устройство неправильно обнаружено или если оно с воскликом — тогда может попробовать прогу по автоматической установки драйверов? Нет, я не рекламирую и не предлагаю какую-то ерундовину. Я лично пользовался DevID Agent, мне понравилось — вроде нет рекламы, все понятно, прога небольшая. Если будете ставить, то смотрите чтобы вместе с ней и Яндекс-софт не установился..
Нашел скриншот — получается USB Mass Storage Device может представлять из себя меню, раскрыв которое, вы увидите модель флешки:
РЕКЛАМА
Возможно что как раз в случае, когда такого меню нет и модели флешки не видно — тогда возможно проблемы с дровами. Правда можно попробовать их вручную установить.. Похожий пример:
РЕКЛАМА
Надеюсь кому-то инфа помогла. Удачи и добра, до новых встреч господа!
На главную!01.09.2022
Симптомы.
Само устройство РАБОТАЕТ. Это Вы проверили на другой машине.
- При подключении же именно к Вашему компьютеру, оно либо не определяется вообще, либо определяется неправильно, либо даже правильно определяется, но не работает как нужно.
- Вы уверены, что установлены все необходимые драйверы всех устройств подключенных к системе.
- Вы уверены, что переустановка и обновление драйверов USB контроллеров и устройств USB сделаны корректно.
- В «Управлении устройствами» (Device manager) — показывает, что все устройства работают нормально и конфликтов нет.
- Устройство все равно не работает, ничего не помогает и Вы готовы переустанавливать систему.
Причина.
Как правило такая ситуация может возникнуть если USB 2.0 Enhanced Host Controller использует одно прерывание вместе с каким-либо другим устройством (IRQ Sharing), например звуковым или видео. В этом случае нарушается правильная передача параметров (FDO, PDO)
How to mount an android 4.4.4 in usb mass storage device mode?
I’m trying to mount Android phone (Lenovo P70-A) to recover deleted files. Phone is detected in lsusb and dmesg. Last command prints
usb-storage 1-3:1-0: USB mass storage device detected ...
sd 2:0:0:0: [sdb] Attached SCSI removable disk/dev/sdb has appeared, however the device isn’t shown in lsblk.
Just mount returned error:
> sudo mount /dev/sdb /media/lenovo
> mount: no medium found on /dev/sdbI managed to mount it with specific filesystem types (mount ... ... -t <fs-type>) as bpf, cgroup2, cpuset, devpts, devtmpfs, fuse, fusectl, hugetlbfs, mqueue, pstore, proc, securityfs, sysfs, tmpfs but they contain system files or just nothing. Btw device still wasn’t in ‘lsblk’. Such types as ext2, ext3, ext4 and vfat gave the same errmsg «no medium…».
My aim is to recover deleted photos and videos so what should I do?
List of driver files that match with the above device in our database.
Your driver is up to date — if you have a problem with your driver, you can try to re-install the old version as below .
Sandisk usb not detected by ubuntu 14.04 but detected by windows 7
I think there is a problem with the ehci / high speed USB 3.0 modules in the kernel. I’ve read about this problem with multiple distributions and kernels, and on occasion I read that it had been patched. Early logs of the problem indicated that the kernel would not allocate enough power to deal with the new demands of the high speed USB, which might explain why it works in host mode (because the kernel didn’t get a chance to limit the amount of power allocated), as well as on Windows, but not in Ubuntu.
I have also read that, despite the insufficient power allocation, if you leave the USB stick plugged in for anywhere from 5-15 minutes, it will eventually get prioritized enough to be recognized and mounted.
I’ll follow up later with some links, very curious to see how this turns out.
edit: Alternatively it could be a problem with FUSE. Have you tried mounting it from the command line directly, rather than letting FUSE try and fail repeatedly to automount?
edit 2: Here is a compilation of other instances of the same problem on varying kernels at varying times. It seems to be a regression which keeps appearing in the later kernels just as it is resolved in the originally problematic ones. In each case this was a blkid/udev failure/timeout, and in each case the culprit was a USB 3.0 device being handled by ehci/some variant thereof, and in each case the device is ultimately recognized after a long string of timeouts. In all of the reported instances, forcefully mounting the device with sudo mount was successful, though this may be a fluke.
Worth noting, by the way, is that a kernel downgrade will resolve the issue. The latest release I saw mentioned as working smoothly was 3.10.7, and before that most people were only successful at <3.10.
So, without further adieu, your evidence:
Ubuntu 13.04 Does not recognize USB Drives
Can’t mount specific usb device after kernel upgrade
USB device constantly being reset
Current Kernel causes blkid USB error
Selective Blindness to Certain USB Devices
Unable to connect to the internet on a ubuntu 14.0.4 laptop using zte(reliance cdma) ac2739 usb modem
Many Linux/Ubuntu users face this problem —>(connect to internet using modem zte/etc…..) because modern dongles have USB storage modem CD ROM,
usb_modes switch blablabla…………………..
what is my problem?
—> I am not able**(sometimes able to)** to connect internet using ZTE(Reliance cdma) AC2739 .
How Ubuntu Detect my USB dongle?
Ans : in 3 Ways :
1) do not detect USB device but lsusb show the device.
2) detect the device (1 in 10 case after inserting USB) but network manager does not detect it as broadband connection.
3) detect the device(1 in 15 case after inserting USB) and also network manager detect it as broadband connection——> this is case when I am able to connect to internet.
System logs for all 3 cases:
Common logs (this is what system logs shows every time when I insert USB dongle)
'May 20 20:51:19 pcp kernel: [ 2724.187204] usb 3-3: new full-speed USB device number 10 using xhci_hcd<br/>
May 20 20:51:19 pcp kernel: [ 2724.205404] usb 3-3: New USB device found, idVendor=19d2, idProduct=fff1<br/>
May 20 20:51:19 pcp kernel: [ 2724.205415] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3<br/>
May 20 20:51:19 pcp kernel: [ 2724.205420] usb 3-3: Product: ZTE CDMA Tech<br/>
May 20 20:51:19 pcp kernel: [ 2724.205425] usb 3-3: Manufacturer: ZTE, Incorporated
May 20 20:51:19 pcp kernel: [ 2724.205430] usb 3-3: SerialNumber: 000000000002
May 20 20:51:19 pcp kernel: [ 2724.208710] usb-storage 3-3:1.5: USB Mass Storage device detected
May 20 20:51:19 pcp kernel: [ 2724.208930] scsi14 : usb-storage 3-3:1.5
May 20 20:51:19 pcp mtp-probe: checking bus 3, device 10: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-3"
May 20 20:51:19 pcp mtp-probe: bus: 3, device: 10 was not an MTP device'case 1: (not sowing common logs —>above one)
May 20 18:52:15 pcp usb_modeswitch: switch device 19d2:fff5 on 003/003
May 20 18:52:42 pcp kernel: [ 3082.599319] scsi 7:0:0:0: CD-ROM ZTE USB Storage FFF1 2.31 PQ: 0 ANSI: 2
May 20 18:52:42 pcp kernel: [ 3082.601400] scsi 7:0:0:1: Direct-Access ZTE USB Storage FFF1 2.31 PQ: 0 ANSI: 2
May 20 18:52:43 pcp kernel: [ 3083.337421] sr1: scsi3-mmc drive: 0x/0x caddy
May 20 18:52:43 pcp kernel: [ 3083.337618] sr 7:0:0:0: Attached scsi CD-ROM sr1
May 20 18:52:43 pcp kernel: [ 3083.337689] sr 7:0:0:0: Attached scsi generic sg2 type 5
May 20 18:52:43 pcp kernel: [ 3083.338257] sd 7:0:0:1: Attached scsi generic sg3 type 0
May 20 18:52:43 pcp kernel: [ 3083.346309] sd 7:0:0:1: [sdb] Attached SCSI removable disk
May 20 18:52:43 pcp kernel: [ 3083.386955] systemd-udevd[5293]: Failed to apply ACL on /dev/sr1: No such file or directory
May 20 18:52:43 pcp kernel: [ 3083.386971] systemd-udevd[5293]: Failed to apply ACL on /dev/sr1: No such file or directory
May 20 18:52:43 pcp kernel: [ 3083.391821] systemd-udevd[5293]: Failed to apply ACL on /dev/sr1: No such file or directory
May 20 18:52:43 pcp kernel: [ 3083.391832] systemd-udevd[5293]: Failed to apply ACL on /dev/sr1: No such file or directorycase 2 (not sowing common logs —>provided at top)
May 20 19:35:52 pcp kernel: [ 910.651091] usb 3-3: reset full-speed USB device number 8 using xhci_hcd
May 20 19:35:52 pcp kernel: [ 910.667601] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800777e6180
May 20 19:35:52 pcp kernel: [ 910.667613] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800777e61c0
May 20 19:35:52 pcp kernel: [ 910.672647] scsi 12:0:0:0: CD-ROM ZTE USB Storage FFF1 2.31 PQ: 0 ANSI: 2
May 20 19:35:52 pcp kernel: [ 910.674693] scsi 12:0:0:1: Direct-Access ZTE USB Storage FFF1 2.31 PQ: 0 ANSI: 2
May 20 19:35:52 pcp kernel: [ 910.679319] sr1: scsi3-mmc drive: 372x/372x writer dvd-ram cd/rw xa/form2 cdda
May 20 19:35:52 pcp kernel: [ 910.679996] sr 12:0:0:0: Attached scsi CD-ROM sr1
May 20 19:35:52 pcp kernel: [ 910.681364] sr 12:0:0:0: Attached scsi generic sg2 type 5
May 20 19:35:52 pcp kernel: [ 910.682692] sd 12:0:0:1: Attached scsi generic sg3 type 0
May 20 19:35:52 pcp kernel: [ 910.689527] sd 12:0:0:1: [sdb] Attached SCSI removable disk
May 20 19:35:52 pcp kernel: [ 910.789754] sr1: CDROM (ioctl) error, command: Xdread, Read track info 52 01 00 00 00 01 00 00 08 00
May 20 19:35:52 pcp kernel: [ 910.789777] sr: Sense Key : Hardware Error [current]
May 20 19:35:52 pcp kernel: [ 910.789783] sr: Add. Sense: No additional sense information
May 20 19:35:52 pcp kernel: [ 911.234442] ISO 9660 Extensions: Microsoft Joliet Level 1
May 20 19:35:52 pcp kernel: [ 911.247345] ISOFS: changing to secondary root
May 20 19:35:52 pcp udisksd[2223]: Mounted /dev/sr1 at /media/prakash/Reliance on behalf of uid 1000case 3: (not sowing common logs —>provided at top)
May 20 20:51:19 pcp kernel: [ 2724.248971] usbcore: registered new interface driver usbserial May 20 20:51:19 pcp kernel: [ 2724.248989] usbcore: registered new interface driver usbserial_generic May 20 20:51:19 pcp kernel: [ 2724.249002] usbserial: USB Serial support registered for generic May 20 20:51:19 pcp kernel: [ 2724.264994] usbcore: registered new interface driver option May 20 20:51:19 pcp kernel: [ 2724.265650] usbserial: USB Serial support registered for GSM modem (1-port) May 20 20:51:19 pcp kernel: [ 2724.265826] option 3-3:1.0: GSM modem (1-port) converter detected May 20 20:51:19 pcp kernel: [ 2724.265979] usb 3-3: GSM modem (1-port) converter now attached to ttyUSB0 May 20 20:51:19 pcp kernel: [ 2724.266042] option 3-3:1.1: GSM modem (1-port) converter detected May 20 20:51:19 pcp kernel: [ 2724.266161] usb 3-3: GSM modem (1-port) converter now attached to ttyUSB1 May 20 20:51:19 pcp kernel: [ 2724.266218] option 3-3:1.2: GSM modem (1-port) converter detected May 20 20:51:19 pcp kernel: [ 2724.266334] usb 3-3: GSM modem (1-port) converter now attached to ttyUSB2 May 20 20:51:19 pcp kernel: [ 2724.266390] option 3-3:1.3: GSM modem (1-port) converter detected May 20 20:51:19 pcp kernel: [ 2724.266505] usb 3-3: GSM modem (1-port) converter now attached to ttyUSB3 May 20 20:51:19 pcp kernel: [ 2724.266562] option 3-3:1.4: GSM modem (1-port) converter detected May 20 20:51:19 pcp kernel: [ 2724.266687] usb 3-3: GSM modem (1-port) converter now attached to ttyUSB4 May 20 20:51:19 pcp kernel: [ 2724.266757] option 3-3:1.6: GSM modem (1-port) converter detected May 20 20:51:19 pcp kernel: [ 2724.266885] usb 3-3: GSM modem (1-port) converter now attached to ttyUSB5 May 20 20:51:20 pcp ModemManager[720]: <warn> (ttyUSB5): port attributes not fully set May 20 20:51:20 pcp ModemManager[720]: <warn> (ttyUSB2): port attributes not fully set May 20 20:51:20 pcp ModemManager[720]: <warn> (ttyUSB3): port attributes not fully set May 20 20:51:20 pcp ModemManager[720]: <warn> (ttyUSB1): port attributes not fully set May 20 20:51:20 pcp ModemManager[720]: <warn> (ttyUSB0): port attributes not fully set May 20 20:51:20 pcp ModemManager[720]: <warn> (ttyUSB4): port attributes not fully set May 20 20:51:20 pcp usb_modeswitch: switched to 19d2:ffffffff on 003/009 May 20 20:51:20 pcp kernel: [ 2725.207972] scsi 14:0:0:0: CD-ROM ZTE USB Storage FFF1 2.31 PQ: 0 ANSI: 2 May 20 20:51:20 pcp kernel: [ 2725.210011] scsi 14:0:0:1: Direct-Access ZTE USB Storage FFF1 2.31 PQ: 0 ANSI: 2 May 20 20:51:21 pcp usb_modeswitch[4855]: usb_modeswitch: switched to 19d2:fff1 on 3/10 May 20 20:51:21 pcp kernel: [ 2725.888378] sr1: scsi3-mmc drive: 372x/372x writer dvd-ram cd/rw xa/form2 cdda May 20 20:51:21 pcp kernel: [ 2725.888912] sr 14:0:0:0: Attached scsi CD-ROM sr1 May 20 20:51:21 pcp kernel: [ 2725.889419] sr 14:0:0:0: Attached scsi generic sg2 type 5 May 20 20:51:21 pcp kernel: [ 2725.893403] sd 14:0:0:1: Attached scsi generic sg3 type 0 <br/>May 20 20:51:21 pcp kernel: [ 2725.910131] sd 14:0:0:1: [sdb] Attached SCSI removable disk May 20 20:51:21 pcp kernel: [ 2726.006326] sr1: CDROM (ioctl) error, command: Xdread, Read track info 52 01 00 00 00 01 00 00 08 00 May 20 20:51:21 pcp kernel: [ 2726.006351] sr: Sense Key : Hardware Error [current] May 20 20:51:21 pcp kernel: [ 2726.006357] sr: Add. Sense: No additional sense information May 20 20:51:22 pcp usb_modeswitch[4855]: usb_modeswitch: add device ID 19d2:fff1 to driver option May 20 20:51:22 pcp usb_modeswitch[4855]: usb_modeswitch: please report the device ID to the Linux USB developers! May 20 20:51:22 pcp kernel: [ 2726.597676] ISO 9660 Extensions: Microsoft Joliet Level 1 May 20 20:51:22 pcp kernel: [ 2726.608596] ISOFS: changing to secondary root May 20 20:51:22 pcp udisksd[2228]: Mounted /dev/sr1 at /media/prakash/Reliance on behalf of uid 1000 May 20 20:51:38 pcp ModemManager[720]: <info> Creating modem with plugin 'ZTE' and '6' ports May 20 20:51:38 pcp ModemManager[720]: <warn> Could not grab port (tty/ttyUSB4): 'Cannot add port 'tty/ttyUSB4', unhandled serial type' May 20 20:51:38 pcp ModemManager[720]: <warn> Could not grab port (tty/ttyUSB2): 'Cannot add port 'tty/ttyUSB2', unhandled serial type' May 20 20:51:38 pcp ModemManager[720]: <warn> Could not grab port (tty/ttyUSB5): 'Cannot add port 'tty/ttyUSB5', unhandled serial type' <br/>May 20 20:51:38 pcp ModemManager[720]: <warn> (ttyUSB0): port attributes not fully set May 20 20:51:38 pcp ModemManager[720]: <info> Modem for device at '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-3' successfully created May 20 20:51:39 pcp ModemManager[720]: <warn> Couldn't load unlock retries: 'Unknown error' May 20 20:51:39 pcp ModemManager[720]: <warn> couldn't load list of Own Numbers: 'Failed to parse NV MDN command result: -17' May 20 20:51:39 pcp ModemManager[720]: <warn> couldn't load current allowed/preferred modes: 'Unknown error' <br/>May 20 20:51:39 pcp ModemManager[720]: <info> Modem: state changed (unknown -> disabled) May 20 20:51:39 pcp NetworkManager[784]: <warn> (ttyUSB0): failed to look up interface index May 20 20:51:39 pcp NetworkManager[784]: <info> (ttyUSB0): new Broadband device (driver: 'option1' ifindex: 0) May 20 20:51:39 pcp NetworkManager[784]: <info> (ttyUSB0): exported as /org/freedesktop/NetworkManager/Devices/2 May 20 20:51:39 pcp NetworkManager[784]: <info> (ttyUSB0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] May 20 20:51:39 pcp NetworkManager[784]: <info> (ttyUSB0): deactivating device (reason 'managed') [2] May 20 20:51:39 pcp NetworkManager[784]: <info> (ttyUSB0): device state change: unavailable -> disconnected (reason 'none') [20 30 0]If anyone want text file of whole log please let me know. This problem is in many USB dongles. If any one can provide any solution to this problem please do it. I am trying from 3 days hope I will get solution now.
Usb 3.0 flash drive not being detected
I’ve looked around at numerous other questions about this topic, but none of them seems to help for me.
I have just bought a new 64Gb SanDisk USB 3.0 flash drive. The device works perfectly on Windows but will not work on my Ubuntu 18.04.3 system.
Other older USB flash drives (non 3.0) work perfectly. This is the dmesg output from a working flash drive:
[ 3294.711026] usb 3-3: new high-speed USB device number 12 using xhci_hcd
[ 3294.862173] usb 3-3: New USB device found, idVendor=090c, idProduct=1000
[ 3294.862176] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3294.862178] usb 3-3: Product: USB DISK
[ 3294.862179] usb 3-3: Manufacturer: SMI Corporation
[ 3294.862180] usb 3-3: SerialNumber: AA04012700057951
[ 3294.862718] usb-storage 3-3:1.0: USB Mass Storage device detected
[ 3294.862854] scsi host6: usb-storage 3-3:1.0
[ 3295.892365] scsi 6:0:0:0: Direct-Access S31B0711 USB DISK 1100 PQ: 0 ANSI: 0 CCS
[ 3295.893023] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 3295.894369] sd 6:0:0:0: [sdb] 506880 512-byte logical blocks: (260 MB/248 MiB)
[ 3295.895065] sd 6:0:0:0: [sdb] Write Protect is off
[ 3295.895070] sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 3295.895637] sd 6:0:0:0: [sdb] No Caching mode page found
[ 3295.895646] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 3295.949633] sdb: sdb1
[ 3295.951686] sd 6:0:0:0: [sdb] Attached SCSI removable diskAnd this is what I get with the non-working drive:
[ 4767.506296] usb 4-3: new SuperSpeed USB device number 5 using xhci_hcd
[ 4767.527455] usb 4-3: New USB device found, idVendor=0781, idProduct=5581
[ 4767.527458] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4767.527459] usb 4-3: Product: Ultra
[ 4767.527460] usb 4-3: Manufacturer: SanDisk
[ 4767.527461] usb 4-3: SerialNumber: 01012f36747c0129815ea130fa9a0aace2c965df046c8184e88d20ee76887fdaed1600000000000000000000d1dc4ec9ff1628008155810794a6f969
[ 4767.528394] usb-storage 4-3:1.0: USB Mass Storage device detected
[ 4767.528611] scsi host6: usb-storage 4-3:1.0
[ 4768.670675] usb 4-3: reset SuperSpeed USB device number 5 using xhci_hcd
[ 4768.834621] usb 4-3: reset SuperSpeed USB device number 5 using xhci_hcd
[ 4768.998668] usb 4-3: reset SuperSpeed USB device number 5 using xhci_hcd
[ 4769.162620] usb 4-3: reset SuperSpeed USB device number 5 using xhci_hcdlsusb correctly shows the device as present (see the «SanDisk Corp. Ultra» line):
$ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 0781:5581 SanDisk Corp. Ultra
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 04f2:b35a Chicony Electronics Co., Ltd
Bus 003 Device 003: ID 8087:07dc Intel Corp.
Bus 003 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBut running fdisk -l does not show the drive.
Googling the error «reset SuperSpeed USB device number 5 using xhci_hcd» seems to suggest some low-level communication with the USB device has failed. But I have yet to find a workable solution.
I’m now out of ideas so I’m looking for possible suggestions!
Edit:
I am plugging the drive into a Blue USB socket.
Requested information:
$ cat /proc/cpuinfo | grep "model name" && sudo lshw | grep -A5 "Moth"
model name : Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
model name : Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
model name : Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
model name : Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
model name : Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
model name : Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
model name : Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
model name : Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz description: Motherboard product: W65_67SZ vendor: Notebook physical id: 0 version: Not Applicable serial: Not ApplicableВосстановление работы usb устройств
Все нижеизложенное относится ко всем устройствам USB, которые перестали работать из-за сбоев в операционной системе Windows XP.
Определить vid и pid для восстановления флешки
Воткните флешку в компьютер и запустите Диспетчер устройств. Пуск – Выполнить — mmc devmgmt.msc.
Затем зайдите в раздел Контроллеры универсальной последовательной шины USB.
Находим в списке свою флешку. Обычно, все флешки имеют название Запоминающее устройство для USB.
Жмем на устройстве правую клавишу и открываем Свойства.
Переходим на вкладку Сведения.
В выпадающем списке выбираем пункт Код экземпляра устройства или Коды (ID) оборудования.
В этом окне мы видим PID и VID.