TerraMaster Forum

Short answer @tmp is not on either Volume
VMs is installed on Volume 1 and the storage space is on Volume 2
Just the regular /tmp exists
[Filesystem Size Used Avail Use% Mounted on
/dev/md9 7.5G 5.9G 1.2G 84% /
tmpfs 50M 28K 50M 1% /dev/shm
tmpfs 6.3G 22M 6.2G 1% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
efivarfs 192K 89K 99K 48% /sys/firmware/efi/efivars
tmpfs 16G 374M 16G 3% /tmp
/dev/mapper/vg0-lv1 55T 19T 36T 35% /var/subvols/8vEbTxkKvwb
/dev/mapper/vg0-lv1 55T 19T 36T 35% /Volume2
/dev/mapper/vg1-lv0 1.9T 491M 1.9T 1% /var/subvols/8vEbTxkKvwa
/dev/mapper/vg1-lv0 1.9T 491M 1.9T 1% /Volume1
/dev/mapper/vg0-lv1 55T 19T 36T 35% /home
/dev/sde1 13T 7.0T 5.8T 55% /Volume2/@usb/usbshare_sde1

Please try entering this: If @tmp does not exist, you can try creating the @tmp manually. Then check if you can successfully export it.

Well, look at that.
I always use ls -al (don't remember the i option)
I created the @tmp on Volume2
Export is working, although when you select Export, it immediately shows "Operation Successful" then the export actually starts.

So next question, was @tmp always supposed to have been there? Does the install of VMs supposed to create it?
Given my initial install and uninstall weeks ago, who knows what happened to it.
**I did check the 425 and my F6 and they also don't have @tmp as well, so I'm guessing the VMs install should create it.
But wait there is more!
So, after creating the @tmp, the import feature started working, I can upload an ISO. Although I'm not sure what I can from that.

Under normal circumstances, VMs automatically create this directory. The issue has been resolved; please wait for a future VMs update.

TMzethar wrote: ↑20 Apr 2026, 08:55 Under normal circumstances, VMs automatically create this directory. The issue has been resolved; please wait for a future VMs update.

The newly released VMs v1.0.044 has fixed this issue.

Good to know, but I had that running on the F4-424 Pro, which will be offline for a while.