The Chipset of the NVME USB3 Enclosure (Ugreen M.2 SSD Case) is ASM2362.
Now on OpenWRT i tried the Standard Build for RPI 4 and the community build.
opkg says "Package kmod-usb-storage (5.4.113-1) installed in root is up to date."
Output of lsusb is:
Bus 002 Device 002: ID 0b95:1790 ASIX Elec. Corp. AX88179
Bus 002 Device 001: ID 1d6b:0003 Linux 5.4.113 xhci-hcd xHCI Host Controller
Bus 001 Device 002: ID 2109:3431 USB2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux 5.4.113 xhci-hcd xHCI Host Controller
ASIX is my USB to GBit Lan Adapter used for WAN Port.
then attempt to install some kmods and see if it shows up in 'dmesg' or 'lsusb -t'
i'm not really sure what it would be off the top of my head... this command helps to look through the kmods (there are lots and it can be hard to find something if you are not sure what you are looking for);
opkg list | grep '^kmod' | grep -i SOMEWORD
maybe something like 'uasp' ... or 'ata' or 'xhci' or 'usb-*' or something... someone else might have suggestions...
could also be something to do with 'quirks' in cmdline.txt or related upstream patches filtering down... (likely)
so doing a websearch for that chipset and 'quirks' may turn something relevant up...
and the power is also a possibility as bobafett suggested... we have not confirmed yet this is working for you in raspbi(ian|OS)
Perhaps if you still have a Raspberry PI OS card where the drive worked, boot it up and post lsusb -t from there. if you can get a lsusb -v from that device on PI OS it would probably give a bit more info too.
at this point... you would be best to create a thread on the general forum in probably the Hardware category called something like;
"UGREEEN 174c:2362 ASM2362 rpi4 [help]" or similar...
the reasons are;
alot of talented people have likely 'ignored' this thread (too much irrelevant traffic) so don't see your posts
it's looking like a general / 'official' support query from here... which is likely to benefit the whole community if/when resolved
Please link the most relavent post/s of yours within that thread... so people have easy access to the relevent info...
as requested... you may also wish to gather and post the (usb|block|scsi) results from dmesg on boot of OpenWrt...
once the fix is known/created... yes... i'm more than happy to do what I can to facilitate as many disk types within the build by default...
(if I did not say so already... removing usb-modeswitch is another long shot thing to try)
lvm/raid etc. are exceptions as they add alot more bulk and typically will only be used by people who have the skills or need further custom settings... ( and they may be difficult to 'conditionally' turn off once installed )... however like most things... if there is a really cool use... that is reliable/transparent-ish/wanted by many... i'm always willing to reconsider on these grounds...
as stated before... while you can expand openwrt to fill the whole (single OS) drive... a better option is to use the extra drive via 'block-mount' to something like /storage... I can help with this.... or as @mk24 recommended in another thread... to create an additional partition beyond partion2(rootfs) which should persist after sysupgrade (have not physically tested this myself but have seen the sysupgrade code and should work fine I think). extroot-overlay is not supported in this build and even if it was... sysupgrade creates all sorts of requirements to transparently recreate on upgrade...
ouch... in the case of v2ray... just testing an install...
it's big... probably too big to install by default... although... there is a possibility to 'set it up/download' during firstboot... ( which would obviously happen over the normal connection )
-rw-r--r-- 1 root root 5.3M Jun 25 15:54 geoip.dat
-rwxr-xr-x 1 root root 16.5M Jun 25 15:54 v2ctl*
-rwxr-xr-x 1 root root 16.6M Jun 25 15:54 v2ray*
there is no init.d start script... which in a way is good... because it is 'inert'... but may also be restrictive / ambigous / labourious / inconsistent for individuals to setup on their own... and I honestly couldn't provide 'support' for that...