Arch Linux

replabrobin

Member

Registered: 2010-05-06

Posts: 237

[SOLVED] external nvme device no longer works with front panel usb

I have an intel NUC6i5SYB running updated (today) archlinux. I always used to be able to plug in my backup nvme on the front panel usb's.
The power LED comes on, but there is no change in the journal output.

Today I noticed that the front panel USB did not seem to make the nvme recognisable.

I was able to access the device using a powered usb extension plugged into one of the usb's on the back of the nuc and it ends up as /dev/sda (1/2/3).

May 05 15:21:30 minikat kernel: usb 2-4.2: new SuperSpeed USB device number 7 using xhci_hcd
May 05 15:21:30 minikat kernel: usb 2-4.2: New USB device found, idVendor=174c, idProduct=2362, bcdDevice= 1.00
May 05 15:21:30 minikat kernel: usb 2-4.2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
May 05 15:21:30 minikat kernel: usb 2-4.2: Product: M.2 NVMe SSD
May 05 15:21:30 minikat kernel: usb 2-4.2: Manufacturer: ASMedia
May 05 15:21:30 minikat kernel: usb 2-4.2: SerialNumber: 000000000A10
May 05 15:21:30 minikat kernel: scsi host1: uas
.......
May 05 15:21:44 minikat kernel: sd 1:0:0:0: [sda] Optimal transfer size 33553920 bytes
May 05 15:21:44 minikat kernel:  sda: sda1 sda2 sda3
May 05 15:21:44 minikat kernel: sd 1:0:0:0: [sda] Attached SCSI disk
May 05 15:22:00 minikat kernel: EXT4-fs (sda1): mounted filesystem a1386f9b-4016-4510-a4a3-6f8a0d09ae47 with ordered data mode. Quota mode: none.
May 05 15:22:00 minikat udisksd[1878]: Mounted /dev/sda1 at /run/media/robin/a1386f9b-4016-4510-a4a3-6f8a0d09ae47 on behalf of uid 1000

If I plug other usb devices into the front usb's they are seen.

I haven't changed anything on the hardware side. Could the NUC be failing (eg not enough power now from the front). Or has some udev rule stepped in. The fact that I see nothing with journalctl would seem to indicate that the device is just not seen at all. I have checked in the BIOS and nothing there seems to be in the way.

Edit: turns out this was a cable error. After 5 years of use the USB A --> usb C cable to the enclosure has become unreliable. A newer cable seems to work fine.

Last edited by replabrobin (2023-05-14 07:48:39)