Turris Mox USB (from module A) not working any more (for mass storage) after TOS 6.0 upgrade

I’ve spotted just one difference between 5.4.4 and 6.0.1.
5.4.4 didn’t had ‘kmod-usb-xhci-hcd’ installed. Ignore ‘kmod-usb3’ on 6.0.1, I’ve tried with and without it, no difference. But removing ‘kmod-usb-xhci-hcd’ on 6.0.1 didn’t helped either.

5.4.4:
opkg list-installed kmod-usb*
kmod-usb-core - 4.14.294-1-28a6284edbf84ab22e01f492fbad32dd
kmod-usb-ehci - 4.14.294-1-28a6284edbf84ab22e01f492fbad32dd
kmod-usb-storage - 4.14.294-1-28a6284edbf84ab22e01f492fbad32dd
kmod-usb-storage-extras - 4.14.294-1-28a6284edbf84ab22e01f492fbad32dd
kmod-usb-storage-uas - 4.14.294-1-28a6284edbf84ab22e01f492fbad32dd
kmod-usb2 - 4.14.294-1-28a6284edbf84ab22e01f492fbad32dd

6.0.1:
opkg list-installed kmod-usb*
kmod-usb-core - 5.15.74-1-68d5cb97f389f2b1d7c118599a176f24
kmod-usb-ehci - 5.15.74-1-68d5cb97f389f2b1d7c118599a176f24
kmod-usb-storage - 5.15.74-1-68d5cb97f389f2b1d7c118599a176f24
kmod-usb-storage-extras - 5.15.74-1-68d5cb97f389f2b1d7c118599a176f24
kmod-usb-storage-uas - 5.15.74-1-68d5cb97f389f2b1d7c118599a176f24
kmod-usb-xhci-hcd - 5.15.74-1-68d5cb97f389f2b1d7c118599a176f24
kmod-usb2 - 5.15.74-1-68d5cb97f389f2b1d7c118599a176f24
kmod-usb3 - 5.15.74-1-68d5cb97f389f2b1d7c118599a176f24

Just an info that USB2 devices work fine, the problem seems to be releated to USB3 only.

Unfortunately the issue still exists in 6.0.3

6.0.3:

root@dullsgard:~# cat /etc/os-release 
NAME="TurrisOS"
VERSION="6.0.3"
ID="turrisos"
ID_LIKE="lede openwrt"
PRETTY_NAME="TurrisOS 6.0.3"
VERSION_ID="6.0.3"
HOME_URL="https://www.turris.cz/"
BUG_URL="https://gitlab.nic.cz/groups/turris/-/issues/"
SUPPORT_URL="https://www.turris.cz/support/"
BUILD_ID="r16703+129-079ce0413a"
OPENWRT_BOARD="mvebu/cortexa53"
OPENWRT_ARCH="aarch64_cortex-a53"
OPENWRT_TAINTS="busybox"
OPENWRT_DEVICE_MANUFACTURER="CZ.NIC"
OPENWRT_DEVICE_MANUFACTURER_URL="https://www.turris.cz/"
OPENWRT_DEVICE_PRODUCT="Turris Mox"
OPENWRT_DEVICE_REVISION="v0"
OPENWRT_RELEASE="TurrisOS 6.0.3 079ce0413a1e3c19dd00be1b90de737c2bc09223"

root@dullsgard:~# opkg list-installed | grep kmod-usb-storage
kmod-usb-storage - 5.15.78-1-3b013b2ab0df9cb289aa3c12cd5614e5
kmod-usb-storage-extras - 5.15.78-1-3b013b2ab0df9cb289aa3c12cd5614e5
kmod-usb-storage-uas - 5.15.78-1-3b013b2ab0df9cb289aa3c12cd5614e5

root@dullsgard:~# lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux 5.15.78 xhci-hcd xHCI Host Controller
Bus 001 Device 001: ID 1d6b:0002 Linux 5.15.78 ehci_hcd EHCI Host Controller
Bus 003 Device 001: ID 1d6b:0003 Linux 5.15.78 xhci-hcd xHCI Host Controller

5.4.4

root@dullsgard:~# cat /etc/os-release 
NAME="TurrisOS"
VERSION="5.4.4"
ID="turrisos"
ID_LIKE="lede openwrt"
PRETTY_NAME="TurrisOS 5.4.4"
VERSION_ID="5.4.4"
HOME_URL="https://www.turris.cz/"
BUG_URL="https://gitlab.nic.cz/groups/turris/-/issues/"
SUPPORT_URL="https://www.turris.cz/support/"
BUILD_ID="r11431+100-83b0e20711"
OPENWRT_BOARD="mvebu/cortexa53"
OPENWRT_ARCH="aarch64_cortex-a53"
OPENWRT_TAINTS="busybox"
OPENWRT_DEVICE_MANUFACTURER="CZ.NIC"
OPENWRT_DEVICE_MANUFACTURER_URL="https://www.turris.cz/"
OPENWRT_DEVICE_PRODUCT="Turris Mox"
OPENWRT_DEVICE_REVISION="v0"
OPENWRT_RELEASE="TurrisOS 5.4.4 83b0e20711ee4a927634b3c2a018c93527e84a2b"

root@dullsgard:~# opkg list-installed | grep kmod-usb-storage
kmod-usb-storage - 4.14.294-1-28a6284edbf84ab22e01f492fbad32dd
kmod-usb-storage-extras - 4.14.294-1-28a6284edbf84ab22e01f492fbad32dd
kmod-usb-storage-uas - 4.14.294-1-28a6284edbf84ab22e01f492fbad32dd

root@dullsgard:~# lsusb
Bus 003 Device 002: ID 1234:5678 Brain Actuated Technologies 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Seems my problem is somehow related to this, cause I have the same problems on my MOX with the 6.0.3 Update. Nevertheless on 6.0.2 my USB drive worked well (except the fact that Nextcloud initial setup doesn’t work) - but the update on 6.0.3 always breaks the USB drive access (I didn’t try a USB 2 device and can just speak for USB 3 devices).

MOX classic, HBK branch (i.e. 6.0.4), .5 GB, 2x WiFi, simple config.

Unfortunately, only couple of minutes ago I noticed that external USB 3 does not work :-((( I took its work for granted and didn’t checked.

There are no errors in system log. It is even recognized as USB 3 (“Dec 5 14:35:54 MOXjp kernel: [ 1.322502] xhci-hcd d0058000.usb: Host supports USB 3.0 SuperSpeed”).

Flash disk itself is OK - checked in Ubuntu NB, saw its content OK.

Unfortunately I can’t tell when this happened, most probably sometimes after some 6.0.x update.

If needed, can send logs and/or diagnostics to support - @pepe ?

Edit: last entry in syslog was :
Nov 29 20:27:36 MOXjp crond[3704]: (cron) INFO (Shutting down)
when syslog was linked to /srv/log/messages on this USB3.

Wild idea, might this be related to some power saving feature? I ran into issues when I enabled luci-app-hd-idle, the disk spun-down just fine, but somehow failed to spin-up again and the loging directed to /srv was unhappy pretty quickly. I simply stopped using luci-app-hd-idle for now…

I don’t think so, especially in my case - AFAIK there is no power saving at my MOX classic :wink: Moreover my USB, used in MOX, is flash device (Kingston Data Traveller).

Edit: and this last message was caused by MOX shutdown…

1 Like

Question: (support, @Pepe )

What difference is between USB drivers for MOX and Omnia? I use USB flashes in my Omnia, one is v2, second is v3, and both work well :wink: - see

Text copy of part of Storage section of reForis on my Omnia:

Device Description Filesystem UUID
sda Kingston DataTraveler 2.0 (14.4 GiB) sda1 KontejnerUb (14.4 GiB) ext4 7301662b-48cd-4396-8767-371bd10c682a
sdb Kingston DataTraveler 3.0 (7.2 GiB) sdb1 TOjpLogs8G (7.2 GiB) ext4 90da6f93-5978-442d-9933-c1e564d56345

and part of mount command

Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 14710336 4438712 9499444 32% /usbKont
/dev/sdb1 7287628 654028 6239520 9% /usbLogRB

(sorry for bad formating ;-))

According to Turris OS 6.1.0 is now released for Turris Omnia and Turris MOX - #5 by jada4p , this issue is still there with TOS 6.1.0.

Please do not forget us: we’re stuck on TOS 5.x as we need to use USB3 mass storage on our Mox.

1 Like

An Issue exists for this topic: USB 3 devices not recognized in MOX (#391) · Issues · Turris / Turris OS / Turris Build · GitLab

2 Likes

It looks like HBK branch has some bugfix for this, changelog says “Fixed USB 3 port on Turris MOX module A”, but after I updated my Mox to Turris OS 6.2.2, unfortunately USB 3.0 devices are still not visible in the system. I tried my ICY BOX IB-RD3640SU3 (disks spin up, but that’s all) and also Kingston DT Ultimate 32GB flash drive with no success.

1 Like

Based on Turris OS 6.2.2 is out! - #6 by jada4p, it seems to be fixed with Turris OS 6.2.2?

Yes, at least for me :wink: it is really working

(df:)
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda              15138816      6408  14594488   0% /srv

(fdisk -l /dev/sda:)
Disk /dev/sda: 14.44 GiB, 15502147584 bytes, 30277632 sectors
Disk model: DataTraveler 3.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

(ls /srv:)
log    spool

Thanks @jada4p : could you also provide the output of a lsusb -vt on your MOX?

No problem.

(lsusb -vt:)
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    ID 1d6b:0003
    |__ Port 1: Dev 2, If 0, Class=, Driver=usb-storage, 5000M
        ID 0951:1666
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
    ID 1d6b:0002
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=orion-ehci/1p, 480M
    ID 1d6b:0002

Edit:
One thing more: trying to check whether there are another variants of fdisk (i.e. cfdisk, sfdisk, parted) I issued find command with result bellow

find / -name \\*disk
/sys/class/scsi_disk
/sys/devices/platform/soc/soc:internal-regs@d0000000/d0058000.usb/usb3/3-1/3-1:1.0/host0/target0:0:0/0:0:0:0/scsi_disk
/usr/sbin/fdisk

showing first that there is only fdisk command present (which should be included manually, as shown by AreYouLoco
(Fdisk is missing on newly installed Turris OS?) using opkg update and
opkg install fdisk), and, second, that - if I understand it well - there is USB3 driver used.

Edit2:
Parted could be installed in simillar way.

2 Likes

I just upgraded my Mox to Turris OS 6.2.2, but it still does not see my USB3 mass-storage devices (that work well with Turris OS 5.4.4).

root@turris:~# uname -a
Linux turris 5.15.88 #0 SMP Wed Jan 18 07:04:32 2023 aarch64 GNU/Linux
root@turris:~# cat /etc/os-release 
NAME="TurrisOS"
VERSION="6.2.2"
ID="turrisos"
ID_LIKE="lede openwrt"
PRETTY_NAME="TurrisOS 6.2.2"
VERSION_ID="6.2.2"
HOME_URL="https://www.turris.cz/"
BUG_URL="https://gitlab.nic.cz/groups/turris/-/issues/"
SUPPORT_URL="https://www.turris.cz/support/"
BUILD_ID="r16820+125-8b46a263ab"
OPENWRT_BOARD="mvebu/cortexa53"
OPENWRT_ARCH="aarch64_cortex-a53"
OPENWRT_TAINTS="busybox"
OPENWRT_DEVICE_MANUFACTURER="CZ.NIC"
OPENWRT_DEVICE_MANUFACTURER_URL="https://www.turris.cz/"
OPENWRT_DEVICE_PRODUCT="Turris Mox"
OPENWRT_DEVICE_REVISION="v0"
OPENWRT_RELEASE="TurrisOS 6.2.2 8b46a263ab4afaf9857f0d29d369c2eefbf8a4f4"
root@turris:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mmcblk0p1        15558140   9826476   4544516  68% /
devtmpfs                   512         0       512   0% /dev
tmpfs                   506320     23596    482724   5% /tmp
tmpfs                      512         0       512   0% /dev
none                     51200        52     51148   0% /srv
root@turris:~# lsusb -vt
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    ID 1d6b:0003  
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
    ID 1d6b:0002  
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=orion-ehci/1p, 480M
    ID 1d6b:0002
root@turris:~# opkg list-installed kmod-usb*
kmod-usb-core - 5.15.88-2-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-ehci - 5.15.88-2-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-storage - 5.15.88-2-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-storage-extras - 5.15.88-2-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-storage-uas - 5.15.88-2-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-xhci-hcd - 5.15.88-2-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb2 - 5.15.88-2-64722ee4b91fa2779e55bbf4f1bbe4a6

I’ve tried to install package kmod-usb3 (and restart), but it was not better.
I’ve tried with different USB3 devices with not more luck. When I plug or unplug any USB3 mass-storage device, nothing happens in dmesg. If I plug or unplug an USB2 mass-storage device, it’s properly detected and shows up in dmesg.

I’ve generated a diagnostic report (with dmesg etc), if it can help.

But I have to revert to 5.4.4 again (the USB3 device is the storage of my k3s cluster so it’s a blocker).

1 Like

According to listing of installed modules, you had version 5.15.88 of them, while I have installed version 5.15.89, ie. newer

root@MOXjp:~# opkg list-installed kmod-usb*
kmod-usb-core - 5.15.89-1-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-ehci - 5.15.89-1-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-storage - 5.15.89-1-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-storage-extras - 5.15.89-1-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb-storage-uas - 5.15.89-1-64722ee4b91fa2779e55bbf4f1bbe4a6
kmod-usb2 - 5.15.89-1-64722ee4b91fa2779e55bbf4f1bbe4a6

I suppose that you didn’t made update properly :frowning:

Edit:
As mentioned in another thread:

“Search the forum, probably you have to do fresh (clean) installation of last version. Suggest to follow documentation”

Another mention regarding manual update using SSH was to issue command opkg update first, only than opkg install *module-name* .

1 Like

Interesting, many thanks for this feedback!

I had simply accepted the upgrade that the Mox suggested to me on January 19th (with, indeed, kernel 5.15.88).

I just did the upgrade again, and it also gave me a kernel 5.15.88.
I ran an “opkg update”, then asked again to check for updates in the UI: no update (except the removal of fix-* packages, version 1-59, that I applied)

Can’t imagine what the problem could be… As suggested elsewhere, possible solution may be to create fresh snapshot (schnapps), export it (to USB or SSD) for later extracting of your configurations, do fresh installation of last medkit, import snapshot created in previous step and extract your configurations and implement them…

Have a good luck!

I also tried to run pkgupdate from the command-line, but it does not help either:

root@turris:~# pkgupdate
INFO:Target Turris OS: 6.2.2
WARN:Requested package reforis-snapshots-plugin-l10n-fr that is missing, ignoring as requested.
WARN:Requested package reforis-openvpn-plugin-l10n-fr that is missing, ignoring as requested.
WARN:Requested package reforis-data-collection-plugin-l10n-fr that is missing, ignoring as requested.
WARN:Requested package reforis-diagnostics-plugin-l10n-fr that is missing, ignoring as requested.
WARN:Requested package reforis-haas-plugin-l10n-fr that is missing, ignoring as requested.

As the upgrade to kernel 5.15.88 has been suggested to me on January 19th, I’ll try to revert to a snapshot before this date: I have one on January 15th. Hopefully it might let it find the kernel 5.15.89?