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

Same here. After TOS6 upgrade turris does not detect USD drive. ReForis Storage shows:

Current State

Your setup is currently broken and you are probably loosing data, set a new storage device as soon as you can!
No drives connected. Please connect a drive and refresh the page.

Did you have TOS 5.4.4 before the upgrade to 6? There’s another bug MOX - HBS@5.4.4 s SDIO se chce updatovat na TOS 6.0 i když by neměl, where they say that the MOX with 5.4.4 by mistake upgraded to 6. Ideally the MOX should have first upgraded to 5.4.5, which is supposed to block the upgrade to 6.

Based on the history of my snapshots, the pre-update snapshot yesterday has been done on version 5.4.4. I have no snapshot on 5.4.5.
So I suppose I never got the 5.4.5.

Is there a manual way to switch to 5.4.5?
I probably can restore my 5.4.4 snapshot, but there’s a risk it will upgrade again to 6.0, I suppose?

switch-branch --version 5.4.4 (its not a mistake, though. I will need to check, why 5.4.5 is not in archive… ):frowning: Use this, only if you want to have working SDIO Wi-Fi card.

I have the same issue - USB on A module not working afer upgrade to 6.0.
Should we expect a fix to 6 that will remedy the issue, is it such that that cannot happen?

Not keen to revert to 5.4.4 with switch-branch (mostly because the docs say “unsupported” to switch ‘down’ a release).
What would you recommend?
Thanks

Thanks.
My WiFi seems OK.

But it would be welcome to have an official advice about this issue and Mox reboots randomly after TOS 6.0 upgrade.
These regressions are real blockers for a daily use, at least for me.

Should we keep TOS 6.0, because fixes will come very quickly? Are there workarounds we could apply to wait a bit more? Or should we “officially” switch back to 5.4.x?

1 Like

You have already 3 threads created and many posts are cross referenced to each other, please stick to one thread otherwise it will be a lot of confusing to me or to someone else.

Same problem, USB on A module is not working. I have MOX start with E module, no wifi. The difference is, that I did not upgrade at all, I re-flashed MOX to TOS 6.0 with the USB drive. At first the USB seemed to work, but after some update and restart USB was gone.

1 Like

Having restored 5.4.4 and got everything working again I though to have another go at the update - I now have 6.0.1.
USB on moudle A still not working - so I removed the WiFi module from module A. I also removed Module B which has an LTE modem in the mPCIe slot. This made no difference, the USB port still does not work.
Reverting again to 5.4.4 because I cannot tolerate the lack of secondary storage .
I do have this error message in reForis Notofication:

“Your MOX HW configuration changed! You added moxtet-peridot.0 module(s). You removed moxtet-pci-bridge.0 moxtet-peridot.1 module(s). Make sure that your setup is correct or try factory reset for new setup.”

I saw no related messages in dmesg.

Again any suggestions gratefully received.

The same problem here as well.
After upgrade to 6.0.1 is USB port on module A not working.
My HW: Turris MOX: Wired Set (included modules: A+C) 512 MB RAM
Upgraded from 5.4.4 to 6.0.1
314 | pre | 104.20MiB | 2022-10-24 20:58:45 +0200 | Automatic pre-update snapshot (TurrisOS 5.4.4)
315 | pre | 11.44MiB | 2022-10-28 01:31:35 +0200 | Automatic pre-update snapshot (TurrisOS 6.0.1)
316 | post | 10.92MiB | 2022-10-28 01:31:42 +0200 | Automatic post-update snapshot (TurrisOS 6.0.1)

lsusb -t
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=orion-ehci/1p, 480M

Please advise on further troubleshooting. I’ll be happy to provide whatever logs/traces needed to investigate this issue.
I need my NAS/Backup drive working again.

I don’t have a MOX, so I can only guess here. You could check whether you have the relevant kernel modules installed LuCI → System → Software. A package like kmod-usb-storage-extras should pull in all the relevant packages as dependencies.

Thanks for the idea.
However, I have already listed the packages I had with v6.0.0 in a previous comment: Turris Mox USB (from module A) not working any more (for mass storage) after TOS 6.0 upgrade - #6 by Mossroy and kmod-usb-storage-extras is in the list

The same here, all relevant packages are installed:
opkg list-installed | grep kmod-usb-storage
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

I’ve reverted to 5.4.4 and USB3 HDD works fine again. I didn’t even touched physically anything, just 'schnapps rollback ’ to pre-upgrade snapshot and then ‘reboot’

On 5.4.4:
lsusb -vt
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
|__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=orion-ehci/1p, 480M

Logs from 5.4.4 - ZeroBin

Logs from 6.0.1 - ZeroBin

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…