Ollama Models Disappeared: Check the Service and Model Path Before Recovery
TL;DR:
If your Ollama models suddenly disappear from your list, verify your service configuration first, because the systemd service and manually launched instances often read from different storage paths rather than the files actually being deleted.
● Check the specific default directories for your operating system (~/.ollama/models on macOS, /usr/share/ollama/.ollama/models on Linux, C:\Users\%username%\.ollama\models on Windows) or the OLLAMA_MODELS environment variable before altering the disk.
● Redownload replaceable models directly from the Ollama registry instead of running data recovery tools if you confirm the local files are genuinely missing.
● Restrict file recovery scans to strictly irreplaceable data, noting that Recoverit does not explicitly guarantee Ollama managed blob recognition and SSD TRIM operations may render deleted blocks permanently unrecoverable.
Ask AI for a summary
ChatGPT
Perplexity
Gemini
Claude
Grok
In this r/ollama case, the user's model list suddenly appeared empty even though the models had not been intentionally uninstalled. The OP later found that the systemd Ollama service and the manually launched Ollama instance were using different model stores. That is the key diagnostic: an empty ollama list does not by itself prove the model files were deleted.
Check Which Ollama Instance and Model Directory You Are Using
Ollama's official FAQ lists different default model locations by operating system: ~/.ollama/models on macOS, /usr/share/ollama/.ollama/models on Linux, and C:\Users\%username%\.ollama\models on Windows. It also supports a custom location through the OLLAMA_MODELS environment variable.
Decision Check
- The model files still exist in another Ollama directory: Fix the service, user, or
OLLAMA_MODELSconfiguration. Do not run data recovery. - The model is replaceable from Ollama's model registry: Pull the model again after confirming the correct instance and path.
- The local model data is actually deleted and cannot be replaced: Protect the storage before attempting file recovery.
Only Scan the Disk After You Confirm Real Deletion
If the relevant Ollama model directory is genuinely missing files, the drive is stable and readable, and there is no downloadable or backup copy, Recoverit File Recovery can scan local storage for deleted data. Ollama stores models as managed files rather than a simple user-named GGUF in every case, and current public Recoverit documentation does not explicitly promise Ollama blob recognition. Recover any candidates to another drive and verify them before changing the source disk. If the source is an SSD, TRIM may make deleted blocks unavailable even when the filenames or directory structure once existed.