Skip to main content ↑ ↓
Topic: USB3 to M.2 NVME adapter ejected (unmounted) while reading / writing large files (Read 538 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

USB3 to M.2 NVME adapter ejected (unmounted) while reading / writing large files

Hello,

Hope I am posting to the right place, because my issue is not just about Artix ...

I just bought a USB3 to M.2 NVME / SATA SSD Enclosure Adapter:
https://www.alxum.com/collections/hard-drive-accessories/products/m-2-nvme-sata-ssd-enclosure-adapter?variant=40139874566297

I transferred more than 500GB of small files (various data and photos) to it.

Regardless of Linux distro or PC (I have experimented), this device is "automatically" unmounted after five minutes, when I read or write large (video) files.  :o


In the attached file I copy the results from dmesg on this.


This device is correctly detected by lsusb
Code: [Select]
lsusb
Bus 001 Device 005: ID 0bda:9210 Realtek Semiconductor Corp. RTL9210 M.2 NVME Adapter


The ext4 partition on this SSD is automatically mounted under / dev / sdg1
Code: [Select]
lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS

sdg           8:96   0 931,5G  0 disk
└─sdg1        8:97   0 931,5G  0 part /run/media/jp/M2-nvme-1T


But if I run inxi -Fc this /dev/sdg (ID-4)drive appears differently (also in the dmesg report):
Code: [Select]
inxi -Fc
Drives:    Local Storage: total: 5.23 TiB used: 2.68 TiB (51.2%)
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB size: 465.76 GiB
           ID-2: /dev/sda vendor: Samsung model: SSD 840 EVO 250GB size: 232.89 GiB
           ID-3: /dev/sdb vendor: Western Digital model: WD40EZRZ-00WN9B0 size: 3.64 TiB
           ID-4: /dev/sdg type: USB vendor: Kingston model: SNVS1000G size: 931.51 GiB


I saw that others had a similar problem and one apparently solved using usb_modeswitch:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch-data/+bug/1878921

Before I jump into usb_modeswitch which I am not familiar with, I thought I would ask you if you see another possibility to work around this problem.

Fortunately, I have an M2-nvme port on the motherboard, so I can manage while waiting for a possible solution.

Thank you in advance for your ideas and suggestions,