USB port disconnected with NVMe drive enclosure

VIM4
1

This is on Ubuntu 22.04 server – just installed fresh through oowow. I just received a NVMe to USB enclosure today and took the Kingston A2000 NVMe module and installed it… I formatted it as ext4 (as /dev/sda1) and all was good…

now it’s hours later… and I tried writing a file on it and get the following:

khadas@Khadas:/media$ ls -la
ls: reading directory ‘.’: Input/output error
total 0
khadas@Khadas:/media$

In checking the logs I find the following:

[ 5690.017727] usb 2-1: USB disconnect, device number 2
[ 5691.250331] usb 2-1: new SuperSpeed Gen 1x2 USB device number 3 using xhci-hcd
[ 5691.281402] usb 2-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=20.01
[ 5691.281408] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5691.281411] usb 2-1: Product: Ugreen Storage Device
[ 5691.281414] usb 2-1: Manufacturer: Ugreen
[ 5691.281417] usb 2-1: SerialNumber: 012938000171
[ 5691.314286] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 5691.314633] scsi host1: usb-storage 2-1:1.0
[ 5692.753485] scsi 1:0:0:0: Direct-Access KINGSTON SA2000M8/500G 1.00 PQ: 0 ANSI: 6
[ 5692.756273] sd 1:0:0:0: [sdb] 1000215216 512-byte logical blocks: (512 GB/477 GiB)
[ 5692.756786] sd 1:0:0:0: [sdb] Write Protect is off
[ 5692.756791] sd 1:0:0:0: [sdb] Mode Sense: 37 00 00 08
[ 5692.757400] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA
[ 5692.778366] sdb: sdb1 sdb2
[ 5692.782109] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 5874.144286] EXT4-fs error (device sda1): __ext4_get_inode_loc:4813: inode #15335431: block 61341728: comm vi: unable to read itable block
[ 5874.145192] Aborting journal on device sda1-8.
[ 5874.145766] Buffer I/O error on dev sda1, logical block 59277312, lost sync page write
[ 5874.146776] JBD2: Error -5 detected when updating journal superblock for sda1-8.
[ 5874.147729] EXT4-fs (sda1): Remounting filesystem read-only
[ 5874.148517] EXT4-fs error (device sda1) in ext4_reserve_inode_write:6060: IO failure
[ 5874.149470] EXT4-fs error (device sda1) in ext4_dirty_inode:6259: IO failure
[ 6179.286715] EXT4-fs error (device sda1): __ext4_find_entry:1605: inode #15335425: comm vi: reading directory lblock 0
[ 6179.287415] EXT4-fs error (device sda1): __ext4_find_entry:1605: inode #15335425: comm vi: reading directory lblock 0
[ 6179.288931] EXT4-fs error (device sda1): __ext4_find_entry:1605: inode #15335425: comm vi: reading directory lblock 0
[ 6179.290186] EXT4-fs error (device sda1): __ext4_find_entry:1605: inode #15335425: comm vi: reading directory lblock 0
[ 6179.291469] EXT4-fs error (device sda1): __ext4_find_entry:1605: inode #15335425: comm vi: reading directory lblock 0
[ 6185.821412] EXT4-fs warning (device sda1): htree_dirblock_to_tree:1014: inode #15335425: lblock 0: comm ls: error -5 reading directory block
[ 6187.889881] EXT4-fs warning (device sda1): htree_dirblock_to_tree:1014: inode #15335425: lblock 0: comm ls: error -5 reading directory block
[ 6192.708237] EXT4-fs warning (device sda1): htree_dirblock_to_tree:1014: inode #15335425: lblock 0: comm ls: error -5 reading directory block
[ 6195.133859] EXT4-fs warning (device sda1): htree_dirblock_to_tree:1014: inode #15335425: lblock 0: comm ls: error -5 reading directory block
[ 6200.820998] EXT4-fs error (device sda1): __ext4_find_entry:1605: inode #15335425: comm vi: reading directory lblock 0
[ 6200.821707] EXT4-fs error (device sda1): __ext4_find_entry:1605: inode #15335425: comm vi: reading directory lblock 0
[ 6238.310391] EXT4-fs error (device sda1): __ext4_find_entry:1605: inode #15335425: comm vi: reading directory lblock 0
[ 6238.311083] EXT4-fs error (device sda1): __ext4_find_entry:1605: inode #15335425: comm vi: reading directory lblock 0
[ 6240.728331] EXT4-fs error (device sda1): __ext4_find_entry:1605: inode #15335425: comm vi: reading directory lblock 0
[ 6240.729026] EXT4-fs error (device sda1): __ext4_find_entry:1605: inode #15335425: comm vi: reading directory lblock 0
[ 6240.730430] EXT4-fs error (device sda1): __ext4_find_entry:1605: inode #15335425: comm vi: reading directory lblock 0
[ 6242.825012] EXT4-fs warning (device sda1): htree_dirblock_to_tree:1014: inode #15335425: lblock 0: comm ls: error -5 reading directory block
[ 6246.323914] EXT4-fs warning (device sda1): htree_dirblock_to_tree:1014: inode #2: lblock 0: comm ls: error -5 reading directory block
[ 6306.855885] EXT4-fs warning (device sda1): htree_dirblock_to_tree:1014: inode #2: lblock 0: comm ls: error -5 reading directory block
[ 6309.235781] EXT4-fs error (device sda1): __ext4_find_entry:1605: inode #15335425: comm bash: reading directory lblock 0
[ 6309.236514] EXT4-fs error (device sda1): __ext4_find_entry:1605: inode #15335425: comm bash: reading directory lblock 0
[ 6309.237876] EXT4-fs error (device sda1): __ext4_find_entry:1605: inode #15335425: comm bash: reading directory lblock 0
[ 6309.239296] EXT4-fs error (device sda1): __ext4_find_entry:1605: inode #15335425: comm bash: reading directory lblock 0
[ 6309.240632] EXT4-fs error (device sda1): __ext4_find_entry:1605: inode #15335425: comm bash: reading directory lblock 0
[ 6323.064247] EXT4-fs warning (device sda1): htree_dirblock_to_tree:1014: inode #2: lblock 0: comm ls: error -5 reading directory block

Has anyone seen this before? I believe what happened is that when I initially booted up my Kingston A2000 was /dev/sda and then this disconnect & reconnect and the device came back as /dev/sdb for some reason… I rebooted and it came up as /dev/sdb too… What would cause it to “move” from one device number to another?

Thoughts?

2

Ok… I let things run for a while … and see these disconnects regularly… once the disconnect hits then the drive is unavailable.

khadas@Khadas:~$ dmesg -T | grep “USB disconnect”
[Sun Oct 2 19:36:02 2022] usb 2-1: USB disconnect, device number 2
[Sun Oct 2 19:45:26 2022] usb 2-1: USB disconnect, device number 3
[Sun Oct 2 19:54:02 2022] usb 2-1: USB disconnect, device number 4
[Sun Oct 2 20:26:12 2022] usb 2-1: USB disconnect, device number 5
[Sun Oct 2 20:57:23 2022] usb 2-1: USB disconnect, device number 6
[Sun Oct 2 21:27:05 2022] usb 2-1: USB disconnect, device number 7

I think I’ll try the same test with a regular (non-NVMe) USB drive — just a cheapie thumb drive and see if that behaves differently.

3

This all sounds very familiar to me. My NVMe drives were sometimes detected in my USB3 caddy on previous releases of Ubuntu-Gnome. But they had really bad R/W errors and would disappear after a while. Only a reboot would bring it back.

Overall, I would say it was about the same as having them plugged into the socket on the board.

The latest release doesn’t see them at all in the caddy.

One thing I noticed this morning was fatal errors from modprobe about nvme-fibre not being found.

I don’t think it is related at all but maybe someone would know,

4

@ps23Rick, is your NVME drive working properly in the USB3 caddy you got?

My drive is working when plugged into the board, but it is still not being recognised in the caddy I have :frowning:

5

I haven’t tried since I wrote the above message… I ended up just switching the caddy over to the RPI4b that I’ve got and using it for the time being … but hopefully I can try again in the next day or two. I ran across the issue while doing a ton of file writes as I think I mentioned above. Not sure if I can just plug the thing in leaving it to just sit there w/o being used — and whether that will show the problem or not. I’ve not tried yet.

6

Thanks.

Mine was seen and seemed to work on previous releases of Ubuntu Gnome until I actually wrote anything serious to it when it would disconnect as you described.

But it is not even seen on the current release so I’m wondering about getting a different brand or maybe even a respected big brand external SSD (from someone like WD or Seagate).

7

My VIM4 is running WD 570 and everything is fine. Ubuntu server

8

What make/model enclosure is it in?

9

The NVMe has a pretty healthy heatsink with a modified mount.
As far as the cabinet, we use stock off the shelf cabinets and machine end panels out of aluminum and drill holes for stand-offs in the removable bottoms.

10

I just plugged my USB enclosure back into the VIM4’s fast USB port… For now I’m just going to let it sit there. I did mount two partitions off the NVMe contained within the USB enclosure but have nothing accessing it at the moment. I’ll probably just let it sit there for 12 hours or so to see if it behaves in little to no accesses. I’m believing it’ll behave but time will tell…

11

Well … that didn’t take long… apparently it does not like my particular enclosure… Without any use (or almost none), this is what transpires:


[Mon Oct 17 16:57:15 2022] usb 2-1: USB disconnect, device number 2
[Mon Oct 17 16:57:16 2022] usb 2-1: new SuperSpeed Gen 1x2 USB device number 3 using xhci-hcd
[Mon Oct 17 16:57:16 2022] usb 2-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=20.01
[Mon Oct 17 16:57:16 2022] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Mon Oct 17 16:57:16 2022] usb 2-1: Product: Ugreen Storage Device
[Mon Oct 17 16:57:16 2022] usb 2-1: Manufacturer: Ugreen
[Mon Oct 17 16:57:16 2022] usb 2-1: SerialNumber: 012938000171
[Mon Oct 17 16:57:16 2022] usb-storage 2-1:1.0: USB Mass Storage device detected
[Mon Oct 17 16:57:16 2022] scsi host0: usb-storage 2-1:1.0
[Mon Oct 17 16:57:18 2022] scsi 0:0:0:0: Direct-Access     KINGSTON  SA2000M8/500G   1.00 PQ: 0 ANSI: 6
[Mon Oct 17 16:57:18 2022] sd 0:0:0:0: [sda] 1000215216 512-byte logical blocks: (512 GB/477 GiB)
[Mon Oct 17 16:57:18 2022] sd 0:0:0:0: [sda] Write Protect is off
[Mon Oct 17 16:57:18 2022] sd 0:0:0:0: [sda] Mode Sense: 37 00 00 08
[Mon Oct 17 16:57:18 2022] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[Mon Oct 17 16:57:18 2022]  sda: sda1 sda2
[Mon Oct 17 16:57:18 2022] sd 0:0:0:0: [sda] Attached SCSI disk
[Mon Oct 17 16:58:00 2022] EXT4-fs (sda1): recovery complete
[Mon Oct 17 16:58:00 2022] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: errors=remount-ro
[Mon Oct 17 16:58:19 2022] usb 2-1: USB disconnect, device number 3
[Mon Oct 17 16:58:20 2022] usb 2-1: new SuperSpeed Gen 1x2 USB device number 4 using xhci-hcd
[Mon Oct 17 16:58:20 2022] usb 2-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=20.01
[Mon Oct 17 16:58:20 2022] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Mon Oct 17 16:58:20 2022] usb 2-1: Product: Ugreen Storage Device
[Mon Oct 17 16:58:20 2022] usb 2-1: Manufacturer: Ugreen
[Mon Oct 17 16:58:20 2022] usb 2-1: SerialNumber: 012938000171
[Mon Oct 17 16:58:20 2022] usb-storage 2-1:1.0: USB Mass Storage device detected
[Mon Oct 17 16:58:20 2022] scsi host0: usb-storage 2-1:1.0
[Mon Oct 17 16:58:21 2022] scsi 0:0:0:0: Direct-Access     KINGSTON  SA2000M8/500G   1.00 PQ: 0 ANSI: 6
[Mon Oct 17 16:58:21 2022] sd 0:0:0:0: [sda] 1000215216 512-byte logical blocks: (512 GB/477 GiB)
[Mon Oct 17 16:58:21 2022] sd 0:0:0:0: [sda] Write Protect is off
[Mon Oct 17 16:58:21 2022] sd 0:0:0:0: [sda] Mode Sense: 37 00 00 08
[Mon Oct 17 16:58:21 2022] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[Mon Oct 17 16:58:21 2022]  sda: sda1 sda2
[Mon Oct 17 16:58:21 2022] sd 0:0:0:0: [sda] Attached SCSI disk
[Mon Oct 17 17:08:55 2022] usb 2-1: USB disconnect, device number 4
[Mon Oct 17 17:08:56 2022] usb 2-1: new SuperSpeed Gen 1x2 USB device number 5 using xhci-hcd
[Mon Oct 17 17:08:57 2022] usb 2-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=20.01
[Mon Oct 17 17:08:57 2022] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Mon Oct 17 17:08:57 2022] usb 2-1: Product: Ugreen Storage Device
[Mon Oct 17 17:08:57 2022] usb 2-1: Manufacturer: Ugreen
[Mon Oct 17 17:08:57 2022] usb 2-1: SerialNumber: 012938000171
[Mon Oct 17 17:08:57 2022] usb-storage 2-1:1.0: USB Mass Storage device detected
[Mon Oct 17 17:08:57 2022] scsi host0: usb-storage 2-1:1.0
[Mon Oct 17 17:08:58 2022] scsi 0:0:0:0: Direct-Access     KINGSTON  SA2000M8/500G   1.00 PQ: 0 ANSI: 6
[Mon Oct 17 17:08:58 2022] sd 0:0:0:0: [sda] 1000215216 512-byte logical blocks: (512 GB/477 GiB)
[Mon Oct 17 17:08:58 2022] sd 0:0:0:0: [sda] Write Protect is off
[Mon Oct 17 17:08:58 2022] sd 0:0:0:0: [sda] Mode Sense: 37 00 00 08
[Mon Oct 17 17:08:58 2022] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[Mon Oct 17 17:08:58 2022]  sda: sda1 sda2
[Mon Oct 17 17:08:58 2022] sd 0:0:0:0: [sda] Attached SCSI disk
[Mon Oct 17 17:10:15 2022] usb 2-1: USB disconnect, device number 5
[Mon Oct 17 17:10:17 2022] usb 2-1: new SuperSpeed Gen 1x2 USB device number 6 using xhci-hcd
[Mon Oct 17 17:10:17 2022] usb 2-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=20.01
[Mon Oct 17 17:10:17 2022] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Mon Oct 17 17:10:17 2022] usb 2-1: Product: Ugreen Storage Device
[Mon Oct 17 17:10:17 2022] usb 2-1: Manufacturer: Ugreen
[Mon Oct 17 17:10:17 2022] usb 2-1: SerialNumber: 012938000171
[Mon Oct 17 17:10:17 2022] usb-storage 2-1:1.0: USB Mass Storage device detected
[Mon Oct 17 17:10:17 2022] scsi host0: usb-storage 2-1:1.0
[Mon Oct 17 17:10:18 2022] scsi 0:0:0:0: Direct-Access     KINGSTON  SA2000M8/500G   1.00 PQ: 0 ANSI: 6
[Mon Oct 17 17:10:18 2022] sd 0:0:0:0: [sda] 1000215216 512-byte logical blocks: (512 GB/477 GiB)
[Mon Oct 17 17:10:18 2022] sd 0:0:0:0: [sda] Write Protect is off
[Mon Oct 17 17:10:18 2022] sd 0:0:0:0: [sda] Mode Sense: 37 00 00 08
[Mon Oct 17 17:10:18 2022] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[Mon Oct 17 17:10:18 2022]  sda: sda1 sda2
[Mon Oct 17 17:10:18 2022] sd 0:0:0:0: [sda] Attached SCSI disk
[Mon Oct 17 17:18:12 2022] usb 2-1: USB disconnect, device number 6
[Mon Oct 17 17:18:13 2022] usb 2-1: new SuperSpeed Gen 1x2 USB device number 7 using xhci-hcd
[Mon Oct 17 17:18:13 2022] usb 2-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=20.01
[Mon Oct 17 17:18:13 2022] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Mon Oct 17 17:18:13 2022] usb 2-1: Product: Ugreen Storage Device
[Mon Oct 17 17:18:13 2022] usb 2-1: Manufacturer: Ugreen
[Mon Oct 17 17:18:13 2022] usb 2-1: SerialNumber: 012938000171
[Mon Oct 17 17:18:13 2022] usb-storage 2-1:1.0: USB Mass Storage device detected
[Mon Oct 17 17:18:13 2022] scsi host0: usb-storage 2-1:1.0
[Mon Oct 17 17:18:15 2022] scsi 0:0:0:0: Direct-Access     KINGSTON  SA2000M8/500G   1.00 PQ: 0 ANSI: 6
[Mon Oct 17 17:18:15 2022] sd 0:0:0:0: [sda] 1000215216 512-byte logical blocks: (512 GB/477 GiB)
[Mon Oct 17 17:18:15 2022] sd 0:0:0:0: [sda] Write Protect is off
[Mon Oct 17 17:18:15 2022] sd 0:0:0:0: [sda] Mode Sense: 37 00 00 08
[Mon Oct 17 17:18:15 2022] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[Mon Oct 17 17:18:15 2022]  sda: sda1 sda2
[Mon Oct 17 17:18:15 2022] sd 0:0:0:0: [sda] Attached SCSI disk
[Mon Oct 17 17:19:51 2022] usb 2-1: USB disconnect, device number 7
[Mon Oct 17 17:19:53 2022] usb 2-1: new SuperSpeed Gen 1x2 USB device number 8 using xhci-hcd
[Mon Oct 17 17:19:53 2022] usb 2-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=20.01
[Mon Oct 17 17:19:53 2022] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Mon Oct 17 17:19:53 2022] usb 2-1: Product: Ugreen Storage Device
[Mon Oct 17 17:19:53 2022] usb 2-1: Manufacturer: Ugreen
[Mon Oct 17 17:19:53 2022] usb 2-1: SerialNumber: 012938000171
[Mon Oct 17 17:19:53 2022] usb-storage 2-1:1.0: USB Mass Storage device detected
[Mon Oct 17 17:19:53 2022] scsi host0: usb-storage 2-1:1.0
[Mon Oct 17 17:19:54 2022] scsi 0:0:0:0: Direct-Access     KINGSTON  SA2000M8/500G   1.00 PQ: 0 ANSI: 6
[Mon Oct 17 17:19:54 2022] sd 0:0:0:0: [sda] 1000215216 512-byte logical blocks: (512 GB/477 GiB)
[Mon Oct 17 17:19:54 2022] sd 0:0:0:0: [sda] Write Protect is off
[Mon Oct 17 17:19:54 2022] sd 0:0:0:0: [sda] Mode Sense: 37 00 00 08
[Mon Oct 17 17:19:54 2022] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[Mon Oct 17 17:19:54 2022]  sda: sda1 sda2
[Mon Oct 17 17:19:54 2022] sd 0:0:0:0: [sda] Attached SCSI disk
[Mon Oct 17 17:20:50 2022] usb 2-1: USB disconnect, device number 8
[Mon Oct 17 17:20:52 2022] usb 2-1: new SuperSpeed Gen 1x2 USB device number 9 using xhci-hcd
[Mon Oct 17 17:20:52 2022] usb 2-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=20.01
[Mon Oct 17 17:20:52 2022] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Mon Oct 17 17:20:52 2022] usb 2-1: Product: Ugreen Storage Device
[Mon Oct 17 17:20:52 2022] usb 2-1: Manufacturer: Ugreen
[Mon Oct 17 17:20:52 2022] usb 2-1: SerialNumber: 012938000171
[Mon Oct 17 17:20:52 2022] usb-storage 2-1:1.0: USB Mass Storage device detected
[Mon Oct 17 17:20:52 2022] scsi host0: usb-storage 2-1:1.0
[Mon Oct 17 17:20:53 2022] scsi 0:0:0:0: Direct-Access     KINGSTON  SA2000M8/500G   1.00 PQ: 0 ANSI: 6
[Mon Oct 17 17:20:53 2022] sd 0:0:0:0: [sda] 1000215216 512-byte logical blocks: (512 GB/477 GiB)
[Mon Oct 17 17:20:53 2022] sd 0:0:0:0: [sda] Write Protect is off
[Mon Oct 17 17:20:53 2022] sd 0:0:0:0: [sda] Mode Sense: 37 00 00 08
[Mon Oct 17 17:20:53 2022] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[Mon Oct 17 17:20:53 2022]  sda: sda1 sda2
[Mon Oct 17 17:20:53 2022] sd 0:0:0:0: [sda] Attached SCSI disk
12

I was trying to understand if this is a power issue, data issue or driver issue and have transferred lots of data to/from various other USB devices without any problem.

I’ve tried various USB3 thumb drives, SATA HDDs, SSDs and Blu Ray Drives in USB powered caddies as well as big (10TB) HDDs in mains powered ones and never had any problem but the VIM4 really hates my USB3 NVMe caddy and keeps telling it might be a faulty cable.

13

The one I’m using is this one… https://a.co/d/0TzpdnS

The thought had come to mind about whether the power brick I’m using is good enough but :man_shrugging:. The power brick I’m using is this one: Amazon.com

14

this is the enclosure I have: https://www.amazon.co.uk/gp/product/B07TSBR114/ref=ppx_yo_dt_b_asin_title_o08_s00?ie=UTF8&psc=1

this is the PSU I’m using: https://www.khadas.com/product-page/usb-c-24w-adapter

but I’ve also got one of these: https://www.letstalktps.com/product/monarch-pd-45w-usb-c-charger/

I have tried different PD compatible USB C cables as well.

doesn’t matter what combination I use, everything except the USB 3 NVMe enclosure works perfectly.

15

I’m hoping, perhaps over time, that Khadas can figure out why only select USB NVMe enclosures work aside from the other NVMe issues as time progresses…

I don’t know if it’s a USB stack issue but that would be my guess — that more work needs to be done on it to tighten things up (or loosen them perhaps) to be more compatible with perhaps odd USB chipsets that can be found in some hardware.

16

btw… I found that if I just plug my enclosure into the VIM4 and mount nothing… that in the logs I just see every few minutes the USB will be disconnected and then reconnect… over and over…

I’d suggest if someone is trying out a USB drive enclosure to plug it in and let it sit for perhaps an hour and see if you see anything in the logs similar to what is shown above… Hopefully it’ll all be quiet and that should be an indication that all is well… but if you’ve got disconnects then you’re with some of us with issues.

17

@technodevotee in your logs are there references to the USB3 control driver – xhci-hcd? just curious as that’s the driver that’s I’m seeing on mine… just wondering if it’s the same for you?

I swapped the NVMe drive from the Kingston A2000 to an older Crucial and of course the behavior is the same.

18

ok… maybe this is a key… not sure… someone with more experience than I can chime in…

All this time I’ve been using the USB3 port (the one farther away from the USB-C power port)… But on a whim I tried the other one at the other end of the board near the USB-C power port… and it’s been idling for almost 15 minutes without issue…

When I use the USB-3 port it disconnects & reconnects every 3-4 minutes on average for me.

So this seems to be something specific to USB-3 only… If USB-2 works solidly that might be a backup option for the time being until this USB3 thing is figured out.

Thoughts?

ps. Here are a few things for you:

root@Khadas:/var/log# lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 10000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 2: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 480M

[Wed Oct 19 20:28:09 2022] usb 1-1.2: new high-speed USB device number 3 using xhci-hcd
[Wed Oct 19 20:28:09 2022] usb 1-1.2: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=20.01
[Wed Oct 19 20:28:09 2022] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Wed Oct 19 20:28:09 2022] usb 1-1.2: Product: Ugreen Storage Device
[Wed Oct 19 20:28:09 2022] usb 1-1.2: Manufacturer: Ugreen
[Wed Oct 19 20:28:09 2022] usb 1-1.2: SerialNumber: 012938000171
[Wed Oct 19 20:28:09 2022] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[Wed Oct 19 20:28:09 2022] scsi host1: usb-storage 1-1.2:1.0
[Wed Oct 19 20:28:11 2022] scsi 1:0:0:0: Direct-Access     CT250P5S SD8              1.00 PQ: 0 ANSI: 6
[Wed Oct 19 20:28:11 2022] sd 1:0:0:0: [sdb] 488397168 512-byte logical blocks: (250 GB/233 GiB)
[Wed Oct 19 20:28:11 2022] sd 1:0:0:0: [sdb] Write Protect is off
[Wed Oct 19 20:28:11 2022] sd 1:0:0:0: [sdb] Mode Sense: 37 00 00 08
[Wed Oct 19 20:28:11 2022] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[Wed Oct 19 20:28:11 2022]  sdb: sdb1 sdb2
[Wed Oct 19 20:28:11 2022] sd 1:0:0:0: [sdb] Attached SCSI disk

As of the last edit for this message, this is still running w/o issue, albeit I’m not accessing the drive but it isn’t disconnecting repeatedly like it does on the USB3 port. So far it’s been running for almost two hours w/o issues and I’ve got my ext4 filesystem mounted without issue.

19

Well, this is weird.

Normally, I have a wireless keyboard/mouse dongle in the USB2 socket and a monitor connected.

However, the last time I plugged in the VIM4. I only connected the LAN cable and power supply and have been doing everything using SSH.

This morning, I plugged the FIDECO enclosure with the Netac drive installed into the USB3 socket and not only was it seen, it mounted and seems to be reading and writing OK.

So, is it because it is the only device connected to the USB ports?

Unfortunately, I don’t have a USB hub I can try.

Update: things just got even more weird. I connected the HDMI monitor and plugged the keyboard/mouse dongle into the USB2 socket with the FIDECO adapter containing the Netac NVMe drive connected to the USB3 socket and it is working - even after a reboot.

20

O-Kay. odd… mine is easy to reproduce … if I plug it back into the USB3 port on the VIM4 within a few minutes it’ll start it’s cycle of disconnects/reconnects every 3-4 minutes give or take. So far with the enclosure plugged into the USB2 port, zero issues… It’s been mounted for well over 12 hours and not a peep from any drivers or complaints showing up in dmesg output.

I’m getting ready to enable WebDAV on this and will throw some large files on it to see how it behaves with Gb of data being transferred…