@padam I agree with you, but the idea is to give us all the chances we can have, and strictly follow:
So I just sent an e-mail to the support team, pointing to your new JIRA ticket.
I had this answer from support team yesterday:
Thank you for reporting your issue with your USB3 SSDs.
We have stopped working on that issue because all the USB3 devices that we have started to work. We are sorry to read that you keep dealing with that issue.
Nevertheless, if you are able to send us one of that devices for debugging as you suggest, we would be grateful for that.
Could you please send it to the following address with a label that it belongs to this ticket number?
(…)
There is a possible workaround to apply in the meantime. If you connect your SSD over a USB2 cable, it should work even with the current Turris OS 6.2.4 version. The speed would not be the same, though.
With kind regards
Stepan Rechner
To be sure I don’t send a USB stick for nothing, I tested again today to upgrade my MOX to latest Turris OS (6.2.4).
As expected, it does not recognize my external hard drive and/or my USB sticks. As usual, lsusb -t and dmesg do not see it.
As usual, reverting to 5.4.4 makes everything work again.
So I’ll send my USB stick (a USB3 128GB Kingston DataTraveler) in Czech Republic, to let Turris test on their side.
3 Likes
Mossroy, thank you very much for providing your hardware for the team to test.
You are not alone with this issue. I own a SanDisk USB 3 Stick (SDCZ430-032G) which is not recognized by 6.2.4 as well.
For info, they have received my USB stick and will test with it:
I want to confirm that we have received your 128GB Kingston flash drive, together with printed instructions on how to reproduce the issue.
Thank you very much for your cooperation. I will pass it on to our kernel-specialized colleges to have a look at it.
1 Like
For info, I’ve asked the support team for news.
They just answered:
unfortunately, we are waiting for the new information yet.
We will inform you, thank you for your patience.
1 Like
They received my USB stick one month ago, so I’ve asked for news and got this answer:
let me apologize for the long response time.
I´ll forward your message to our kernel specialist.
2 Likes
Well, 2 more weeks and still no answer from Turris support. I don’t even know if they tried to reproduce with my USB stick 
I suppose they don’t consider that issue as a priority.
Instead of asking again for news, I suggest that other people affected by this issue open a support ticket, too. See Support - Turris Documentation. Maybe they believe I’m the only one affected, or that I have some unusual USB device. Give your own symptoms and impact, and give detail on your USB device(s): brand/model and USB ID from lsusb -t.
If you have other ideas to make things move forward, don’t hesitate…
I know that would be just a workaround (and I haven’t read the whole thread history), but did you try connecting the device via a (powered) USB hub?
@peci1 : @Hai mentioned in Turris Mox USB (from module A) not working any more (for mass storage) after TOS 6.0 upgrade - #2 by Hai the same issue with an externally powered disk.
I finally have some (good) news.
They managed to reproduce the issue, but only on Mox devices that have an old U-Boot version.
So they asked me which U-Boot version I have on my board. Mine is 2018.11. You can check yours with the following command:
root@turris:~# strings /dev/mtdblock1 | grep "U-Boot 20"
U-Boot 2018.11 (Dec 16 2018 - 12:50:19 +0000)
root@turris:~#
Their conclusion:
Dear Mossroy,
this means that you have old firmware, which is the cause of the issue.
Please install the nor-update package and run it, with commands:
opkg update
opkg install nor-update
nor-updateWe will be sending you back your USB flash drive on monday.
I haven’t tested yet.
Do you have the same U-Boot version as I have?
@jada4p can you check you already have a more recent one? (which would explain why the issue was solved for you since TOS 6.2.2)
3 Likes
Sure:
root@MOXjp:~# strings /dev/mtdblock1 | grep "U-Boot 20"
U-Boot 2021.10-rc3-00050-g7d3fea2c7f (Sep 07 2021 - 18:16:56 +0200)
Thus it is really newer one.
I can’t neither remember nor explain how it happened that there is newer U-boot version installed on my MOX… Sorry.
1 Like
Hello, the nor-update worked on my MOX machine even though the update seemed to fail at first attempt (unrequested run right after package installation). Also I haven’t found nor-update package, but found similar fix-nor-update that I installed.
# strings /dev/mtdblock1 | grep "U-Boot 20"
U-Boot 2018.11 (Dec 16 2018 - 12:50:19 +0000)
# opkg update
Downloading https://repo.turris.cz/hbk/mox/packages/core/Packages.gz
Updated list of available packages in /var/opkg-lists/turrisos_core
Downloading https://repo.turris.cz/hbk/mox/packages/core/Packages.sig
Signature check passed.
Downloading https://repo.turris.cz/hbk/mox/packages/base/Packages.gz
Updated list of available packages in /var/opkg-lists/turrisos_base
Downloading https://repo.turris.cz/hbk/mox/packages/base/Packages.sig
Signature check passed.
Downloading https://repo.turris.cz/hbk/mox/packages/cesnet/Packages.gz
Updated list of available packages in /var/opkg-lists/turrisos_cesnet
Downloading https://repo.turris.cz/hbk/mox/packages/cesnet/Packages.sig
Signature check passed.
Downloading https://repo.turris.cz/hbk/mox/packages/luci/Packages.gz
Updated list of available packages in /var/opkg-lists/turrisos_luci
Downloading https://repo.turris.cz/hbk/mox/packages/luci/Packages.sig
Signature check passed.
Downloading https://repo.turris.cz/hbk/mox/packages/node/Packages.gz
Updated list of available packages in /var/opkg-lists/turrisos_node
Downloading https://repo.turris.cz/hbk/mox/packages/node/Packages.sig
Signature check passed.
Downloading https://repo.turris.cz/hbk/mox/packages/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/turrisos_packages
Downloading https://repo.turris.cz/hbk/mox/packages/packages/Packages.sig
Signature check passed.
Downloading https://repo.turris.cz/hbk/mox/packages/routing/Packages.gz
Updated list of available packages in /var/opkg-lists/turrisos_routing
Downloading https://repo.turris.cz/hbk/mox/packages/routing/Packages.sig
Signature check passed.
Downloading https://repo.turris.cz/hbk/mox/packages/telephony/Packages.gz
Updated list of available packages in /var/opkg-lists/turrisos_telephony
Downloading https://repo.turris.cz/hbk/mox/packages/telephony/Packages.sig
Signature check passed.
Downloading https://repo.turris.cz/hbk/mox/packages/turrispackages/Packages.gz
Updated list of available packages in /var/opkg-lists/turrisos_turrispackages
Downloading https://repo.turris.cz/hbk/mox/packages/turrispackages/Packages.sig
Signature check passed.
# opkg install fix-nor-update
Installing fix-nor-update (1-61) to root...
Downloading https://repo.turris.cz/hbk/mox/packages/turrispackages/fix-nor-update_1-61_aarch64_cortex-a53.ipk
Installing turris-mox-firmware (2.0-3) to root...
Downloading https://repo.turris.cz/hbk/mox/packages/turrispackages/turris-mox-firmware_2.0-3_aarch64_cortex-a53.ipk
Installing turris-nor-update (1.1.0-7) to root...
Downloading https://repo.turris.cz/hbk/mox/packages/turrispackages/turris-nor-update_1.1.0-7_aarch64_cortex-a53.ipk
Configuring turris-mox-firmware.
Configuring turris-nor-update.
Configuring fix-nor-update.
Mount is denied because the NTFS volume is already exclusively opened.
The volume may be already mounted, or another software may use it which
could be identified for example by the help of the 'fuser' command.
Verifying /dev/mtd0 against secure-firmware.bin ...
18a0c1bc58839cbbc7aef70db637d261 - /dev/mtd0
e12a263c63bd9860cff844763e81e56b - secure-firmware.bin
Failed
Unlocking /dev/mtd0 ...
Erasing /dev/mtd0 ...
Writing from secure-firmware.bin to /dev/mtd0 ...
Verifying /dev/mtd1 against uboot ...
437cb920201336f556abd2b448248714 - /dev/mtd1
bd802eb0ec60fd89f983ac3cd4860fba - uboot
Failed
Cannot parse config file '/etc/fw_env.config': No such file or directory
Unlocking /dev/mtd1 ...
Erasing /dev/mtd1 ...
Writing from uboot to /dev/mtd1 ...
Verifying /dev/mtd3 against rescue ...
e9b30ada843663c579829652847c7bb8 - /dev/mtd3
39f02d9fb36b4258bac37924bcdf570c - rescue
Failed
Unlocking /dev/mtd3 ...
Erasing /dev/mtd3 ...
Writing from rescue to /dev/mtd3 ...
Can''t find anything to flash to 'dtb' partition
# reboot
...
Warning: Changes performed using anything other than
official web interface reForis are not covered by
Turris support team unless instructed!
______ _ ____ _____
/_ __/_ ____________(_)____ / __ \/ ___/
/ / / / / / ___/ ___/ / ___/ / / / /\__
/ / / /_/ / / / / / (__ ) / /_/ /___/ /
/_/ \__,_/_/ /_/ /_/____/ \____//____/
-----------------------------------------------------
TurrisOS 6.3.2, Turris Mox
-----------------------------------------------------
$ su
Password:
# nor-update
Mount is denied because the NTFS volume is already exclusively opened.
The volume may be already mounted, or another software may use it which
could be identified for example by the help of the 'fuser' command.
Verifying /dev/mtd0 against secure-firmware.bin ...
e12a263c63bd9860cff844763e81e56b - /dev/mtd0
e12a263c63bd9860cff844763e81e56b - secure-firmware.bin
Success
Verifying /dev/mtd1 against uboot ...
bd802eb0ec60fd89f983ac3cd4860fba - /dev/mtd1
bd802eb0ec60fd89f983ac3cd4860fba - uboot
Success
Verifying /dev/mtd3 against rescue ...
39f02d9fb36b4258bac37924bcdf570c - /dev/mtd3
39f02d9fb36b4258bac37924bcdf570c - rescue
Success
Can''t find anything to flash to 'dtb' partition
# strings /dev/mtdblock1 | grep "U-Boot 20"
U-Boot 2022.07 (Aug 15 2022 - 12:25:08 +0000)
# lsusb
Bus 003 Device 002: ID 0951:1656 Kingston DT Ultimate G2
Bus 002 Device 001: ID 1d6b:0002 Linux 5.15.107 xhci-hcd xHCI Host Controller
Bus 001 Device 001: ID 1d6b:0002 Linux 5.15.107 ehci_hcd EHCI Host Controller
Bus 003 Device 001: ID 1d6b:0003 Linux 5.15.107 xhci-hcd xHCI Host Controller
For me also run right after package installation, second run was not necessary. After it was run strings showed new U-Boot installed:
root@turris:~# opkg install nor-update
Unknown package 'nor-update'.
Collected errors:
* opkg_install_cmd: Cannot install package nor-update.
root@turris:~# opkg install fix-nor-update
Installing fix-nor-update (1-61) to root...
Downloading https://repo.turris.cz/hbs/mox/packages/turrispackages/fix-nor-update_1-61_aarch64_cortex-a53.ipk
Installing turris-mox-firmware (2.0-3) to root...
Downloading https://repo.turris.cz/hbs/mox/packages/turrispackages/turris-mox-firmware_2.0-3_aarch64_cortex-a53.ipk
Installing turris-nor-update (1.1.0-7) to root...
Downloading https://repo.turris.cz/hbs/mox/packages/turrispackages/turris-nor-update_1.1.0-7_aarch64_cortex-a53.ipk
Configuring turris-mox-firmware.
Configuring turris-nor-update.
Configuring fix-nor-update.
Verifying /dev/mtd0 against secure-firmware.bin ...
18a0c1bc58839cbbc7aef70db637d261 - /dev/mtd0
e12a263c63bd9860cff844763e81e56b - secure-firmware.bin
Failed
Unlocking /dev/mtd0 ...
Erasing /dev/mtd0 ...
Writing from secure-firmware.bin to /dev/mtd0 ...
Verifying /dev/mtd1 against uboot ...
437cb920201336f556abd2b448248714 - /dev/mtd1
bd802eb0ec60fd89f983ac3cd4860fba - uboot
Failed
Unlocking /dev/mtd1 ...
Erasing /dev/mtd1 ...
Writing from uboot to /dev/mtd1 ...
Verifying /dev/mtd3 against rescue ...
e9b30ada843663c579829652847c7bb8 - /dev/mtd3
39f02d9fb36b4258bac37924bcdf570c - rescue
Failed
Unlocking /dev/mtd3 ...
Erasing /dev/mtd3 ...
Writing from rescue to /dev/mtd3 ...
Can't find anything to flash to 'dtb' partition
root@turris:~# strings /dev/mtdblock1 | grep "U-Boot 20"
U-Boot 2022.07 (Aug 15 2022 - 12:25:08 +0000)
I’ll upgrade my MOX to 6.x in the evening today.
It’s peculiar - I see from above that there is even more recent version of U-boat… I wonder if I should update to it… Could someone from team/support advice?
I can confirm that my USB3 HDD is working after the upgrade of U-Boot.
BusyBox v1.33.2 (2023-04-26 23:52:34 UTC) built-in shell (ash)
______ _ ____ _____
/_ __/_ ____________(_)____ / __ \/ ___/
/ / / / / / ___/ ___/ / ___/ / / / /\__
/ / / /_/ / / / / / (__ ) / /_/ /___/ /
/_/ \__,_/_/ /_/ /_/____/ \____//____/
-----------------------------------------------------
TurrisOS 6.3.2, Turris Mox
-----------------------------------------------------
root@turris:~# lsusb
Bus 003 Device 002: ID 0bc2:3322 Seagate Expansion Desk
Bus 002 Device 001: ID 1d6b:0002 Linux 5.15.96 xhci-hcd xHCI Host Controller
Bus 001 Device 001: ID 1d6b:0002 Linux 5.15.96 ehci_hcd EHCI Host Controller
Bus 003 Device 001: ID 1d6b:0003 Linux 5.15.96 xhci-hcd xHCI Host Controller
1 Like
I can also confirm that the USB3 SSD now continues to work with my MOX after the TOS 6.0 upgrade. Fix was the u-boot upgrade from U-Boot 2018.11 to U-Boot 2022.07 via
opkg install fix-nor-update
Now I have:
- U-Boot 2022.07 (Aug 15 2022 - 12:25:08 +0000)
- TurrisOS 6.3.2, Turris Mox
USB SSD listed (as it was before with TOS 5)
root@turris:~# lsusb
Bus 003 Device 002: ID 0781:55bb SanDisk Portable SSD
Bus 002 Device 001: ID 1d6b:0002 Linux 5.15.96 xhci-hcd xHCI Host Controller
Bus 001 Device 001: ID 1d6b:0002 Linux 5.15.96 ehci_hcd EHCI Host Controller
Bus 003 Device 001: ID 1d6b:0003 Linux 5.15.96 xhci-hcd xHCI Host Controller
Thanks a lot @Mossroy for taking the time and effort to get this solved via Turris Support and lending your hardware!
1 Like
The Turris guys rock! This is the second super-weird low-level problem solved in the last month 