Mapping UI fails with error 'no space left on device'

  • Updated on Dec 2, 2025
  • 1 minute(s) read
Prev Next

Issue description

The Mapping UI fails with the following error message:

Ooops, an error occured!
We are very sorry, but something unexpected happened. An error occurred and we strongly recommend to restart the application or cold-restart the trolley.
This error has been logged; providing the log files to the NavVis staff will be of great help.
Backend returned error '[Errno 28] No space left on device: '/srv/data/datasets_rec/2021-09-29_19.58.17 

Additionally the following Ubuntu message might appear in a dark window on top of the screen:

Low disk Space on "srv"
The volume "srv" has only 0 bytes disk space remaining.

Scope

This solution applies to NavVis VLX and NavVis M6 System Software incl. 2.13.0.

Troubleshooting procedure

The SSD used on the device is either full or corrupted. When a Dataset was started before this message pops up, it might not be complete or saved by the Safe-Shutdown mode.

  1. Connect the SSD to a PC and copy all data on it to local storage. Use a 3rd party tool for safe copying (eg. https://freefilesync.org/) to prevent any errors during copying.

  2. Deleted the data from the SSD once it has been copied.

  3. Try mapping again

  4. If the error reoccurs, reformat the SSD to exFat as described in our documentation.

FAQ

What error message appears when the Mapping UI fails?

The error message states: 'Ooops, an error occurred! We are very sorry, but something unexpected happened. An error occurred and we strongly recommend to restart the application or cold-restart the trolley.'

What does the Ubuntu message indicate?

The Ubuntu message indicates 'Low disk Space on "srv". The volume "srv" has only 0 bytes disk space remaining.'

What systems does this issue apply to?

This issue applies to NavVis VLX and NavVis M6 System Software including version 2.13.0.

What should I do if the SSD is full or corrupted?

You should connect the SSD to a PC, copy all data to local storage, delete the data from the SSD, and then try mapping again.

What tool can I use for safe copying of data from the SSD?

You can use a third-party tool like FreeFileSync for safe copying.

What should I do if the error reoccurs after trying to map again?

If the error reoccurs, you should reformat the SSD to exFat as described in the documentation.

Related articles