Bruh, after bongwater cooled found japaneseporn.love and holy nippon overload. First click loaded petite Kyoto wife stuffin cucumber while hubby golf outside window like nothing weird goin on inside kitchen. Then clip two cosplay bunny teens fightin over single wang carrot juice, ends up snowballing mouthful right camera.
Even found random korean camgirl tease, fake studying live stream till dildo appears from under desk making viewers spam tip goals. Vids queue faster than munchies disappear. Quality jumpy but who care pixel peen still peen. Bookmark list explode, had create second gmail overflow, ended jackin onto printout list mom recipes like camouflage haha. Rare archive includes 90s VHS kimino rip, fuzzy muff square screen retro camp. If mainstream cookie cutter plastic yank bore ya this asian rabbit cave serve raw meat straight.
Cannot say if it applies to your case, but there is a known issue that is typical of (some) Sandisk sticks.
USB 3.x sticks are of course backwards compatible with USB 2.0 connections, and it seems that Sandisk sticks specifically do some kind of “negotiation” to decide if exposing USB 2.x or USB 3.x interface that in some cases “confuses” the RouterOS.
The usual symptom is often the mounting number/order changing, see:
Sandisk USB sticks, generally speaking, are considered very good quality ones, but they are not immune from possible issues, it is entirely possible that besides the above something in your specific specimen is - even slightly - defective and simply does not go well with the Mikrotik device.
Partitioning/formatting on a PC (it may depend on the OS and tools used) is not necessarily “better”, or a guarantee of everything working as it should, in some cases it is, in others it can make the situation worse.
Try with another stick (non-Sandisk), if the behaviour remains, then you should open a support ticket as the problem may actually be on Mikrotik’s side.
Correct.
Known problem, made a ticket about it already quite some time ago but I would have to check for the status. So long ago already I almost forgot…
There are work around scripts available for this problem.
