ollama - 💡(How to fix) Fix 树莓派 4b 8G内存版本安装报错 [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
ollama/ollama#15728Fetched 2026-04-22 07:43:45
View on GitHub
Comments
1
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
commented ×1labeled ×1

Error Message

Error: remove /root/.ollama/models/blobs/sha256-4c27e0f5b5adf02ac956c7322bd2ee7636fe3f45a8512c9aba5385242cb6e09a-partial-0: no such file or directory

RAW_BUFFERClick to expand / collapse

What is the issue?

ollama pull gemma4:e4b pulling manifest pulling 4c27e0f5b5ad: 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏ 1.8 GB
Error: remove /root/.ollama/models/blobs/sha256-4c27e0f5b5adf02ac956c7322bd2ee7636fe3f45a8512c9aba5385242cb6e09a-partial-0: no such file or directory

Relevant log output

OS

No response

GPU

No response

CPU

No response

Ollama version

No response

extent analysis

TL;DR

  • The issue can likely be resolved by manually removing the partially downloaded blob files from the /root/.ollama/models/blobs/ directory.

Guidance

  • Check the /root/.ollama/models/blobs/ directory for any files with the prefix sha256-4c27e0f5b5adf02ac956c7322bd2ee7636fe3f45a8512c9aba5385242cb6e09a-partial- and remove them manually.
  • Verify that the directory is writable and has sufficient disk space before attempting to pull the gemma4:e4b image again.
  • If the issue persists, try cleaning up the ollama cache and retrying the pull operation.

Example

  • No specific code snippet is applicable in this case, but the manual removal of files can be done using the rm command, e.g., rm /root/.ollama/models/blobs/sha256-4c27e0f5b5adf02ac956c7322bd2ee7636fe3f45a8512c9aba5385242cb6e09a-partial-*

Notes

  • The exact cause of the issue is unclear due to the lack of information about the ollama version and system configuration.
  • Manually removing files from the /root/.ollama/models/blobs/ directory may have unintended consequences if not done carefully.

Recommendation

  • Apply workaround: Manually remove the partially downloaded blob files and retry the pull operation, as the root cause of the issue is unclear and no clear upgrade path is available.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

ollama - 💡(How to fix) Fix 树莓派 4b 8G内存版本安装报错 [1 comments, 1 participants]