[image: 1772026636774-172be5a0-8f03-43bb-80c9-fb6725bf3040-image.png]
[image: 1772026668178-9bb0a9e8-5e48-4ff6-bd18-39c437ae7e09-image.png]
What's interesting is even though it says it failed to mount, I can still see the files in the file manager, however the edit dates appear different than in the desktop file manager and some files don't line up like the cache is remembered:
[image: 1772027081354-1377a6fb-0d14-4e98-b1ca-d5c8916f5f18-filesystem-resized.jpg]
[image: 1772027233394-19ce8f6f-4d8b-4a31-9a3d-91a468bb22d6-image-resized.png]
That's all kinda nice really, and that the apps can actually run, but it's not clear where they actually exist.
I am not able to select SSD as a place to move them to either, which makes sense.
I'm mostly just curious what happens in case like this, and it appears that as I guessed it does just go on the root drive in a mount point with the volume name, which is a nice solution and lucky I have enough space:
[image: 1772027451484-c0b09bf6-c93f-4510-8b1a-95436cbcd5bd-image-resized.png]
In this case it could have been cool to not need to manually move all of them, and instead re-assign the mount point to the same physical drive, though then I might have run into an issue with the files already existing (which is what happens if I try to move them to the ddrive they were previous on on the new mount point). But having it all work despite it missing and moving them to a another spot or deleting the files and moving them is ok, just a bit labor intensive.
2
3
