Unregognized usb device after hibernation

diegomagikal · 08-01-2020, 06:50 PM

Hello all! This is my first post. Thanks in advance for any help!

I bought a Focusrite Scarlet 2i2 (interface usb audio) and it worked very well in my Ubuntu 20.04. The USB connection has been recognized as new device and all worked fine (audio input and audio output).
But since my computer hibernated for a few minutes and woke up, the usb connection is unrecognized (I can't see the Scarlet as an usb device). The usb port still can power the interface, but the audio output doesn't works anymore (although the audio input is ok).
I tested it on another 2 windows pcs and the same occurs.

My hypothesis is that the partition table has been corrupted. But I don't know what to do (I have no experience with that).

With lsusb command, I can see the Focusrite Scarleth:

Code:

Bus 002 Device 012: ID 1235:8210 Focusrite-Novation 
Bus 002 Device 007: ID 1a2c:2d23 China Resource Semico Co., Ltd 
Bus 002 Device 006: ID 1bcf:0005 Sunplus Innovation Technology Inc. Optical Mouse
Bus 002 Device 005: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub
Bus 002 Device 003: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0bda:0138 Realtek Semiconductor Corp. RTS5138 Card Reader Controller
Bus 001 Device 003: ID 0bda:58e8 Realtek Semiconductor Corp. 
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

With lsblk command, I can't see Scarleth data:

Code:

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0    7:0    0  96,5M  1 loop /snap/core/9436
loop1    7:1    0 800,4M  1 loop /snap/android-studio/91
loop2    7:2    0 800,4M  1 loop /snap/android-studio/90
loop3    7:3    0    55M  1 loop /snap/core18/1880
loop4    7:4    0    97M  1 loop /snap/core/9665
loop5    7:5    0 255,6M  1 loop /snap/gnome-3-34-1804/36
loop6    7:6    0   216M  1 loop /snap/natron/120
loop7    7:7    0    55M  1 loop /snap/core18/1754
loop8    7:8    0 255,6M  1 loop /snap/gnome-3-34-1804/33
loop9    7:9    0  62,1M  1 loop /snap/gtk-common-themes/1506
loop10   7:10   0 166,4M  1 loop /snap/postman/119
loop11   7:11   0 166,4M  1 loop /snap/postman/118
loop12   7:12   0  43,2M  1 loop /snap/snap-store/415
loop13   7:13   0 191,1M  1 loop /snap/flutter/21
loop14   7:14   0  49,8M  1 loop /snap/snap-store/467
loop15   7:15   0 161,4M  1 loop /snap/gnome-3-28-1804/128
loop16   7:16   0   2,8M  1 loop /snap/pulseaudio/9
loop17   7:17   0  29,8M  1 loop /snap/snapd/8140
loop18   7:18   0  29,9M  1 loop /snap/snapd/8542
loop19   7:19   0    56K  1 loop /snap/usb-reset/8
sda      8:0    0 465,8G  0 disk 
├─sda1   8:1    0   100G  0 part 
├─sda2   8:2    0     1K  0 part 
├─sda5   8:5    0   500M  0 part 
├─sda6   8:6    0   110G  0 part /media/diegoluiz/Web
└─sda7   8:7    0 255,3G  0 part /media/diegoluiz/Clientes
sdb      8:16   0 447,1G  0 disk 
├─sdb1   8:17   0   512M  0 part /boot/efi
├─sdb2   8:18   0     1K  0 part 
└─sdb5   8:21   0 446,7G  0 part /

By running fdisk -l, I got the red text "Partition 2 does not start at a physical sector boundary" and "Partition table entries are not in disk order". But what is the disk it refers to?

Code:

Disco /dev/sda: 465,78 GiB, 500107862016 bytes, 976773168 setores
Disk model: TOSHIBA MK5059GS
Unidades: setor de 1 * 512 = 512 bytes
Tamanho de setor (lógico/físico): 512 bytes / 4096 bytes
Tamanho E/S (mínimo/ótimo): 4096 bytes / 4096 bytes
Tipo de rótulo do disco: dos
Identificador do disco: 0x52c4a53d

Dispositivo Inicializar    Início       Fim   Setores Tamanho Id Tipo
/dev/sda1   *             1026048 210741247 209715200    100G  7 HPFS/NTFS/exFAT
/dev/sda2                    1985 976769114 976767130  465,8G  f Win95 (LBA) Partição Extendida
/dev/sda5                    2048   1026047   1024000    500M  1 FAT12
/dev/sda6               210741312 441433813 230692502    110G  7 HPFS/NTFS/exFAT
/dev/sda7               441434176 976769114 535334939  255,3G  7 HPFS/NTFS/exFAT

A partição 2 não inicia em um limite de setor físico.
Partições lógicas fora da ordem do disco.


Disco /dev/sdb: 447,14 GiB, 480113590272 bytes, 937721856 setores
Disk model: SanDisk SSD PLUS
Unidades: setor de 1 * 512 = 512 bytes
Tamanho de setor (lógico/físico): 512 bytes / 512 bytes
Tamanho E/S (mínimo/ótimo): 512 bytes / 512 bytes
Tipo de rótulo do disco: dos
Identificador do disco: 0xcdbabb63

Dispositivo Inicializar  Início       Fim   Setores Tamanho Id Tipo
/dev/sdb1   *              2048   1050623   1048576    512M  b FAT32 W95
/dev/sdb2               1052670 937719807 936667138  446,7G  5 Estendida
/dev/sdb5               1052672 937719807 936667136  446,7G 83 Linux

With dmesg command, after disconnect and reconnect the usb cable I get the following code:

Code:

[29595.424917] usb 2-1.3: USB disconnect, device number 12
[29599.238134] usb 2-1.3: new high-speed USB device number 13 using ehci-pci
[29599.347592] usb 2-1.3: New USB device found, idVendor=1235, idProduct=8210, bcdDevice= 6.45
[29599.347597] usb 2-1.3: New USB device strings: Mfr=1, Product=3, SerialNumber=2
[29599.347600] usb 2-1.3: Product: Scarlett 2i2 USB
[29599.347603] usb 2-1.3: Manufacturer: Focusrite
[29599.347605] usb 2-1.3: SerialNumber: Y*******7

I don't know how to interpret this information... Can you help?

Thanks

JZL240I-U · 08-02-2020, 09:13 AM

The partition table and USB are not interconnected the way you seem to assume AFAIK. Probably you should better concentrate on USB -- which I don't know well. For other readers: Is there a demon or some background service which has to be running using USB-devices? If so, the OP could check on his machine...

diegomagikal · 08-02-2020, 01:37 PM

Quote:

Originally Posted by JZL240I-U

The partition table and USB are not interconnected the way you seem to assume AFAIK. Probably you should better concentrate on USB -- which I don't know well. For other readers: Is there a demon or some background service which has to be running using USB-devices? If so, the OP could check on his machine...

Thanks. Just in case, I already reset the usb port with usb-reset tool, but with no effect. The question is that I get the same error in anothers computers, including windows machines.

I thought about partition table because when I plugged the device before, a partition with some files a appeared (like https://pasteboard.co/Jkx4cJT.png). But now, when I plug the device nothing happens.

JZL240I-U · 08-02-2020, 02:29 PM

Sorry, it says "Image not found".

Partition tables errors simply make no sense: They are indices of hard discs layouts. USB is dynamic, i.e. plug in and the device is known. That's why I asked for demons or background services (which I don't know of but might get killed by hibernation).

diegomagikal · 08-02-2020, 03:03 PM

Quote:

Originally Posted by JZL240I-U

Sorry, it says "Image not found".

Partition tables errors simply make no sense: They are indices of hard discs layouts. USB is dynamic, i.e. plug in and the device is known. That's why I asked for demons or background services (which I don't know of but might get killed by hibernation).

new uploads (the same image):

https://paste.pics/31d4b84cb1920309dfb319975aea495f
https://snipboard.io/ezYVCH.jpg
https://pasteboard.co/Jkx4cJT.png

JZL240I-U · 08-03-2020, 07:57 AM

Ahh, now I see what you mean. What happens is that with end of hibernation your system "perceives" the device as an USB-hard disc. No idea how to correct that. Google?

kilgoretrout · 08-03-2020, 12:09 PM

Quote:

I tested it on another 2 windows pcs and the same occurs.

It's not entirely clear from your post, but I assume this device was working in both windows and Ubuntu before. Then after hibernation in Ubuntu, the device no longer works in either. Please confirm. Also, by hibernation, did you suspend to ram or disk?

Your output demonstrates that two storage devices have been detected, a 500GB Toshiba hard drive and a 500 GB Sandisk SSD where your operating system is installed. The red error message from fdisk is a common one and can be ignored; it is of no significance. To illustrate here's the same error message in my fdisk output:

Code:

# fdisk -l
 Disk /dev/sdb: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD1003FZEX-0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x000916a1

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sdb1  *            63  212019199  212019137 101.1G  7 HPFS/NTFS/exFAT
/dev/sdb2        212019200 1953525167 1741505968 830.4G  f W95 Ext'd (LBA)
/dev/sdb5        212021248 1949329407 1737308160 828.4G 83 Linux
/dev/sdb6       1949333504 1953523711    4190208     2G 82 Linux swap / Solaris

Partition 1 does not start on physical sector boundary.

Your dmesg output shows that on reconnecting the device, your system is loading the ehci-pci driver for the device which is the driver for usb storage devices. I am curious as to whether lsblk then shows another storage device, sdc.

I assume this is the device we're talking about:
https://www.amazon.com/Focusrite-Sca.../dp/B07QR73T66

This is a device for recording audio and since it is not clear whether the device has its own internal storage , I'm guessing that the device is designed to place its recordings on the attached computers internal hard drive. If it does have internal storage, that would explain the loading of the ehci-pci driver and F: drive letter in windows; it's for accessing the devices internal storage. Also, on the Amazon website reviews, there's some question as to whether the device is supported by Windows 10.

If you are connecting via a USB3 port, I would suggest trying the device on a USB2 port if one is available. The specs for the device show it is designed for USB2. USB3 is supposed to be backward compatible but I've had issues with some USB devices acting flakey on USB3 but working fine on USB2.

Other than that, I would contact the manufacturer and try to get a replacement under their 3 year warranty.