Since the last upgrade (i think friday) my external hard drives aren't accessible (mostly)!
SAMBA still works but not via the console (or rather by their mount point)
I cd into where they should be mounted and ls but nothing is listed! and other services like minidlna and transmission dont see them
It appears you are using firmware that is not from the official OpenWrt project.
When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.
Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).
If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.
As stated by @elder_tinkerer , you are currently using the gl-inet vendor firmware. This is not from the official openwrt project.
Your device is well supported by official openwrt - if you switch to firmware from here, we can help. But if you are using the gl-inet firmware, you need to ask them for help.
GL.iNet always is two-fold. They keep their hardware open, they build their firmware upon OpenWrt. But they also do funny things regarding extending, backporting and picking stuff. I generally like their hardware and the user friendliness of their travel routers, but even there ran into so many weird things that I moved to vanilla OpenWrt and always keep a few config tarballs.
Here, the firmware is based on an OpenWrt branch that is very outdated, latest maintained old stable is 23.05. So it is very likely they messed up something when backporting patches. That they do not move to a supported branch of OpenWrt is a sure sign that they will drop updates for that device soon, so it might be best to move to OpenWrt 24.10 now instead of trying to troubleshoot a firmware that will be EOL'ed in a few months.
Remember: You can try to keep the config that is present on the device, but I recommend to swallow that toad and start over with a fresh config (of course, C&P of config piece by piece is legitimate).
No, this will cause major problems. You need to reset to defaults and configure from scratch when you switch to/from official openwrt. The configs from gl-inet firmware is not compatible with official openwrt and vice versa.
