There’s too much going on.
From what I can gather, your disk layout looks something like this:
/dev/sda1 ---> EFI
/dev/sda2 ---> System / OS
- Yet it includes /home/basementmedia/ without the custom “daten” folder, which means you have 12GB of “personal home user” files, such as Documents, Pictures, Downloads, Videos, etc, that are outside of /home/basementmedia/daten/ (Hence why there’s an extra 12GB being used up on sda2 that I’m assuming you would prefer to be on sda3; your large partition.)
/dev/sda3 ---> "daten"
- This dedicated large partition (/dev/sda3) is mounted to a folder named “daten”, which is nested underneath /home/basementmedia/, and thus it appears in the file tree as /home/basementmedia/daten/
Furthermore, I’m not sure when it was configured as such (and perhaps behind the scenes), Timeshift’s backups are mounted under sda3, instead of sda2.
Ideally, /dev/sda3 (your large partition) should have been mounted as /home/ during installation. Going forwards, everything would have been cleanly laid in place, like so:
/dev/sda1 ---> EFI
/dev/sda2 ---> System / OS
/dev/sda3 ---> /home/
As for your personal home folder, you would see the usual things like Documents, Downloads, Pictures, Videos, etc, and also you would create your “daten” folder and dump your 100+ GB of stuff in there.
I believe you went astray from the defaults during installation / post-installation setup. I’m not sure this might be the best distro for a Linux beginner, yet the installer is fairly straight forward. I’m trying to think of a user-friendly way to reclaim those 12GB without putting yourself at risk of accidentally losing data.
EDIT: The live system’s “file-system tree” always starts at “/” and everything nested underneath it are directories and sub-directories.
When you “mount” something, you choose a directory where the partition will branch out its own file-system. From the file browser’s perspective, however, it appears like any other folder.
So for example, let’s say you only have one partition (sda2), and it is the system/OS partition. On the live system, the top-most directory will be “/”.
You’ll see a bunch of directories and sub-directories nested underneath it, such as:
Directories
/etc/
/usr/
/home/
/mnt/
Sub-directories
/etc/alsa/
/usr/share/
/home/winnie/
/mnt/netshare/
You can even start using /home/winnie/ as your user’s home folder and save a bunch of stuff in there. But let’s say you have a brand new empty partition (/dev/sda3)? You decide to mount this brand new empty partition as /home/.
Now when you browse to /home/, you’ll see an empty folder! Where’d your files go? Well, they still exist on sda2, but since you mounted sda3 over /home/, it “replaces it” in the file-system tree, so that starting from /home/ and further down is actually the sda3 file-system (currently empty.)
The moment you unmount sda3 from /home/? You’ll see your existing files once again.
A common partition layout is to use the entire large partition (such as sda2) for everything: Root system (aka “/”) and home. Everything will live under one file-system, one partition.
Another common layout is to reserve /home/ for a separate partition (such as sda3). Which means if sda3 is not mounted or unavailable, your /home/ folder will appear empty (as it should).
What you have going on right now is some stuff lives on sda2, sitting inside /home/basementmedia/, while other stuff lives on sda3, sitting specifically inside /home/basementmedia/daten/
/dev/sda3 mounts to /home/basementmedia/daten/
Theoretically, if you were to unmount /dev/sda3, and then attempt to browse /home/basementmedia/daten/, you would find an empty folder.
EDIT 2: Where did “daten” and all the files within come from? Did it exist before you installed Manjaro, or did you populate it after you installed Manjaro?