On 1/3/24 15:48, Rich Shepard wrote:
> [Wed Jan  3 14:13:21 2024] usb 1-11: new high-speed USB device number 2 using 
> xhci_hcd
> [Wed Jan  3 14:13:21 2024] usb 1-11: New USB device found, idVendor=1f75, 
> idProduct=0611, bcdDevice= 0.06
> [Wed Jan  3 14:13:21 2024] usb 1-11: New USB device strings: Mfr=4, 
> Product=5, SerialNumber=6
> [Wed Jan  3 14:13:21 2024] usb 1-11: Product: XT-U33502
> [Wed Jan  3 14:13:21 2024] usb 1-11: Manufacturer: XinTop
> [Wed Jan  3 14:13:21 2024] usb 1-11: SerialNumber: 20230921
> [Wed Jan  3 14:13:21 2024] usb-storage 1-11:1.0: USB Mass Storage device 
> detected
> [Wed Jan  3 14:13:21 2024] scsi host10: usb-storage 1-11:1.0
> [Wed Jan  3 14:13:22 2024] scsi host10: scsi scan: INQUIRY result too short 
> (5), using 36
> [Wed Jan  3 14:13:22 2024] scsi 10:0:0:0: Direct-Access     XinTop   
> XT-U33502             PQ: 0 ANSI: 0
> [Wed Jan  3 14:13:22 2024] sd 10:0:0:0: [sdg] Very big device. Trying to use 
> READ CAPACITY(16).
> [Wed Jan  3 14:13:22 2024] sd 10:0:0:0: [sdg] 7814037168 512-byte logical 
> blocks: (4.00 TB/3.64 TiB)
> [Wed Jan  3 14:13:22 2024] sd 10:0:0:0: [sdg] Write Protect is off
> [Wed Jan  3 14:13:22 2024] sd 10:0:0:0: [sdg] Mode Sense: 3b 00 00 00
> [Wed Jan  3 14:13:22 2024] sd 10:0:0:0: [sdg] No Caching mode page found
> [Wed Jan  3 14:13:22 2024] sd 10:0:0:0: [sdg] Assuming drive cache: write 
> through
> [Wed Jan  3 14:13:22 2024] sd 10:0:0:0: [sdg] Very big device. Trying to use 
> READ CAPACITY(16).
> [Wed Jan  3 14:13:22 2024] sd 10:0:0:0: [sdg] Very big device. Trying to use 
> READ CAPACITY(16).
> [Wed Jan  3 14:13:22 2024] sd 10:0:0:0: [sdg] Attached SCSI disk
> [Wed Jan  3 14:15:17 2024] usb 1-11: USB disconnect, device number 2

As Russell mentioned, your USB adapter is disconnecting, that is why 
/dev/sdg is AWOL.  Are you sure you are plugging into a the correct 
port?  Bad USB adapter?

PRO TIP: Connect *JUST* the USB adapter - no drive - and check dmesg.  
It should not disconnect (just show 'media removed') and the USB adapter 
*MUST* be listed in 'lsusb'.  For example, for my 3.0 USB adapter

# dmesg
[603063.361794] usb 4-4: USB disconnect, device number 2
[603067.792014] usb 4-4: new SuperSpeed USB device number 3 using xhci_hcd
[603067.804645] usb 4-4: New USB device found, idVendor=174c, 
idProduct=5106, bcdDevice= 0.01
[603067.804650] usb 4-4: New USB device strings: Mfr=2, Product=3, 
SerialNumber=1
[603067.804652] usb 4-4: Product: AS2105
[603067.804654] usb 4-4: Manufacturer: ASMedia
[603067.804656] usb 4-4: SerialNumber: 00000000000000000000
[603067.805029] usb-storage 4-4:1.0: USB Mass Storage device detected
[603067.805311] scsi host10: usb-storage 4-4:1.0
[603068.822185] scsi 10:0:0:0: Direct-Access     ASMT 2105             
0    PQ: 0 ANSI: 5
[603068.822690] sd 10:0:0:0: [sdf] Media removed, stopped polling
[603068.823478] sd 10:0:0:0: [sdf] Attached SCSI removable disk

and

$ lsusb

...
Bus 004 Device 002: ID 174c:5106 ASMedia Technology Inc. ASM1051 SATA 
3Gb/s bridge
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
...

If you do not see something similar, then fighting with fdisk is folly.

-Ed.

Reply via email to