Unable to recover deleted files, invalid paths

Insight & Feedback
1

Title. Unable to recover deleted files back to system due to invalid paths.

Is there any other way to access the deleted files/folder outside of the GUI?

My App data location folders don’t seem to work either, I cant access them. The buttons don’t work either. I also don’t have a .trash folder. Everything doesn’t look right.

Screenshot 2026-05-10 015541
Screenshot 2026-05-10 015541665×776 79.6 KB

Screenshot 2026-05-10 015740
Screenshot 2026-05-10 015740852×426 16.4 KB

2

This definitely does not look right.
Your screenshots suggest the storage paths/database may no longer match the actual mounted locations.

A few things stand out:

  • Zima Storage shows 0 B Available
  • App paths still point to /media/ZimaOS-HD/...
  • The folder shortcut buttons are not responding
  • Trash exists in UI, but the actual .trash path may not exist anymore
  • This is very similar to the path/mount inconsistencies many users started seeing after the 1.6.x storage changes

Before touching anything, I would first verify whether /media/ZimaOS-HD is a real mounted filesystem or just a leftover folder now sitting on the system disk.

Ask them to post these results:

mount | grep ZimaOS-HD

df -h

ls -lah /media

ls -lah /media/ZimaOS-HD

find /media -maxdepth 2 -type d -name "*trash*" 2>/dev/null

Also important:
I would avoid manually creating or deleting .trash folders right now until the actual mount state is confirmed. With the recent storage changes, a wrong cleanup step could make recovery harder if the data is still physically present on the disk.

If /media/ZimaOS-HD is no longer an active mount, the UI may still be referencing stale paths from before the storage migration.