github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-07 00:22:43 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #7183] Failed to update all the models downloaded locally #30323

New Issue
Closed
opened 2026-04-22 09:53:46 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-22 09:53:46 -05:00
Owner
Copy Link

Originally created by @qzc438 on GitHub (Oct 12, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/7183

What is the issue?

When I use this code in the latest version of ollama: ollama list | cut -f 1 | tail -n +2 | xargs -n 1 ollama pull
There is an error message:
pulling manifest
Error: pull model manifest: file does not exist

OS

No response

GPU

No response

CPU

No response

Ollama version

No response

Originally created by @qzc438 on GitHub (Oct 12, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/7183 ### What is the issue? When I use this code in the latest version of ollama: `ollama list | cut -f 1 | tail -n +2 | xargs -n 1 ollama pull` There is an error message: pulling manifest Error: pull model manifest: file does not exist ### OS _No response_ ### GPU _No response_ ### CPU _No response_ ### Ollama version _No response_
GiteaMirror added the bug label 2026-04-22 09:53:46 -05:00
GiteaMirror commented 2026-04-22 09:53:48 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Oct 12, 2024):

ollama list | cut -f 1 | tail -n +2 | xargs -i@ bash -c 'ollama pull @ 2>&- || echo failed: @'
<!-- gh-comment-id:2408535325 --> @rick-github commented on GitHub (Oct 12, 2024): ``` ollama list | cut -f 1 | tail -n +2 | xargs -i@ bash -c 'ollama pull @ 2>&- || echo failed: @' ```
GiteaMirror commented 2026-04-22 09:53:48 -05:00
Author
Owner
Copy Link

@qzc438 commented on GitHub (Oct 12, 2024):

ollama list | cut -f 1 | tail -n +2 | xargs -i@ bash -c 'ollama pull @ 2>&- || echo failed: @'

How do I use this code? It looks like only print logs.

<!-- gh-comment-id:2408541118 --> @qzc438 commented on GitHub (Oct 12, 2024): > ``` > ollama list | cut -f 1 | tail -n +2 | xargs -i@ bash -c 'ollama pull @ 2>&- || echo failed: @' > ``` How do I use this code? It looks like only print logs.
GiteaMirror commented 2026-04-22 09:53:48 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Oct 12, 2024):

Run it from the command line. It will update all the models, and print the names of the models that fail. Then you can determine why the failed models weren't updated: old model, not from the ollama library, etc.

<!-- gh-comment-id:2408544020 --> @rick-github commented on GitHub (Oct 12, 2024): Run it from the command line. It will update all the models, and print the names of the models that fail. Then you can determine why the failed models weren't updated: old model, not from the ollama library, etc.
GiteaMirror commented 2026-04-22 09:53:49 -05:00
Author
Owner
Copy Link

@qzc438 commented on GitHub (Oct 12, 2024):

Run it from the command line. It will update all the models, and print the names of the models that fail. Then you can determine why the failed models weren't updated: old model, not from the ollama library, etc.

Tested. It shows all model updates have failed.

<!-- gh-comment-id:2408545010 --> @qzc438 commented on GitHub (Oct 12, 2024): > Run it from the command line. It will update all the models, and print the names of the models that fail. Then you can determine why the failed models weren't updated: old model, not from the ollama library, etc. Tested. It shows all model updates have failed.
GiteaMirror commented 2026-04-22 09:53:50 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Oct 12, 2024):

Pick a model and run ollama pull $MODEL, post the result. Add the server logs.

<!-- gh-comment-id:2408550778 --> @rick-github commented on GitHub (Oct 12, 2024): Pick a model and run `ollama pull $MODEL`, post the result. Add the [server logs](https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md#how-to-troubleshoot-issues).
GiteaMirror commented 2026-04-22 09:53:50 -05:00
Author
Owner
Copy Link

@qzc438 commented on GitHub (Oct 13, 2024):

Error: pull model manifest: file does not exist

This is the server log: Error: pull model manifest: file does not exist

<!-- gh-comment-id:2408816159 --> @qzc438 commented on GitHub (Oct 13, 2024): > Error: pull model manifest: file does not exist This is the server log: Error: pull model manifest: file does not exist
GiteaMirror commented 2026-04-22 09:53:50 -05:00
Author
Owner
Copy Link

@jmorganca commented on GitHub (Oct 13, 2024):

Hi @qzc438 sorry this isn't easier today will merge with https://github.com/ollama/ollama/issues/2633 or try @rick-github's script

<!-- gh-comment-id:2408824027 --> @jmorganca commented on GitHub (Oct 13, 2024): Hi @qzc438 sorry this isn't easier today will merge with https://github.com/ollama/ollama/issues/2633 or try @rick-github's script
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#30323
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?