[µpod]

Summary
When the Tangara device is mounted, i'm unable to perform any file operations: creating new files / folders; deleting files; renaming files; etc.

Observed Behaviour
Steps to Reproduce

1. Plug the Tangara into my PC via a USB-A to USB-C cable.
   
2. Enable USB Storage in the Tangara settings.
   
3. Mount the Tangara—either via automagic by clicking on the icon that appears on my Debian desktop, or via 
   
   Code:

   $ doas mount -o uid=$MYUSERUID -o gid=$MYGROUPID /dev/sdXX /path/to/mountpoint
4. Attempt any file operations, either in Thunar or in a terminal window.
   

Results
Thunar tends to hang when attempting anything.  I can browse files mostly successfully, but right-clicking virtually anything; or attempting to move or create files always hangs.  Right-clicking on the Tangara's device icon in the sidebar also hangs.

The terminal window is nominally more successful.  Operations take an eternity, but appear to succeed.  They do not, however.  For example, earlier today i attempted to create a new Music directory, and once "finished" the directory was filled with mysterious (non-existent) garbled garbage (fake files and directories with nonsense names), and

Code:

$ du -hd0 /path/to/mountpoint/Music/dirname/

reported that the directory had a size of 26G, and that the fake folders could not be accessed, returning a permissions error.  The folder and all of the falsely-reported garbage within disappeared upon umounting, and were not present upon a remount.

Unmounting is also dirty.  Via a GUI, it is claimed that file operations need to complete before unmounting (even when none were initiated), but no tool performing said operations is listed.  However, when told to unmount anyway, this completes successfully.

No corruption appears to have yet resulted.

Expected Behaviour
File operations should succeed, etc.

System Info
Computer
Debian 13 "Trixie" x86_64 / amd64
Xfce v. 4.20
Thunar 4.20.2
xfce4-terminal 1.1.4
Kernel 6.12.63+deb13-amd64
Attempts were made on multiple ports (USB-A v.2 and 3) and over multiple USB-A to USB-C cables.

Card
Sandisk Extreme PRO [full-size SD card]
SDXC I, V30
128GB
Formatted as FAT-32L [0x0C]

Tangara
ESP32 v. 2.0.0
SAMD21 v. 6.0
Collator Generic

Additional Notes
I've seen in another forum post that SD card operations via the Tangara's internal reader may be unreliable in general; should i just plan on ejecting the card and mounting it separately in the near-term (i have been doing so on a separate laptop running OpenBSD [which has /never/ played nicely with the Tangara] to this point, but i thought it might be worth reporting this—i was unable to find a similar issue on Codeberg, though apologies if this is redundant >_<)?  Or is this the sort of thing i can troubleshoot, work around, and/or remedy?

Any tips or assistance are appreciated, and i'll be happy to provide additional info if it'd help.  Thanks in advance!

[ailurux]

Yeah, unfortunately the USB mass storage functionality is fairly unreliable at the present moment. It's generally less error prone to use the SD card directly if you can. 
I think there's a couple existing issues that might be relevant:
- https://codeberg.org/cool-tech-zone/tang...issues/112
- https://codeberg.org/cool-tech-zone/tang...issues/310

[jfred]

Yeah I've had similar experiences.

After seeing that one of those issues was labeled "SD Card Hell" I ordered a Samsung card to replace the SanDisk one I had been using, and USB storage mode actually works now. (It's incredibly slow, but does seem to work reliably - I just have to make sure that I wait for the OS to finish writing out from cache.)

The new card is exFAT-formatted from the factory which I haven't changed. I don't recall what my original card was formatted as, but I can check later.

Anecdotally my Tangara does seem a little less crashy with this new card too, though I don't have hard data on that and still have had it crash once or twice. Still need to try and catch one of those crashes while plugged in to grab logs.