Issue with Multiple USB Mount Points on Toradex iMX7D

ToradexAI · October 3, 2024, 1:50pm

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

Based on the context provided, here are some suggestions to address your queries:

Overwriting USB Mount Rules for Sequential Naming:
- The default behavior of mounting USB devices using UUID or LABEL is managed by the udev rules and systemd services. To achieve sequential naming like usb0, usb1, usb2, you would need to create custom udev rules. However, this can be complex due to the dynamic nature of USB device connections and disconnections.
- You can try creating a custom udev rule that triggers a script to mount the devices at your desired mount points. This script can maintain a mapping of connected devices to sequential mount points. However, this approach requires careful handling of device disconnections to avoid stale mount points.
Accessing USB Mount Points from a Container:
- To allow a container to access USB mount points, you need to ensure that the mount points are shared with the container. You mentioned adding /var/rootdirs/media/ to the container volumes, but you might need to ensure that the specific subdirectories (e.g., /media/usb0, /media/usb1) are also accessible.
- You can achieve this by using Docker’s --mount option to bind mount the specific directories into the container. For example:
```
docker run --rm -it --mount type=bind,source=/var/rootdirs/media/usb0,target=/mnt/usb0 my-container
```
- Ensure that the user inside the container has the necessary permissions to read and write to these directories. If using the torizon user, it should have the appropriate group memberships to access the USB devices.

If these suggestions do not fully resolve your issue, you may need to explore more advanced udev scripting or consider alternative approaches to manage USB devices dynamically.

Please, also check if these links can help you solve your problem:

Container access USB device.