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

[GH-ISSUE #15547] Issue when installing gemma4 with Ollama 0.20.6 on Linux ubuntu 13.4.2026 #35693

New Issue
Open
opened 2026-04-22 20:22:45 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-22 20:22:45 -05:00
Owner
Copy Link

Originally created by @arnami on GitHub (Apr 13, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/15547

What is the issue?

ubuntu@django2:~$ ollama

pulling manifest
pulling 4c27e0f5b5ad: 92% ▕█████████████████████████████████████████████████████████████████████████████████████████████████ ▏ 8.9 GB/9.6 GB 14 MB/s 50s
Error: selecting model: failed to pull gemma4: write /usr/share/ollama/.ollama/models/blobs/sha256-4c27e0f5b5adf02ac956c7322bd2ee7636fe3f45a8512c9aba5385242cb6e09a-partial: no space left on device
Ollama 0.20.6

▸ Chat with a model
Start an interactive chat with a model

Relevant log output

OS

Linux

GPU

AMD

CPU

AMD

Ollama version

0.20.6

Originally created by @arnami on GitHub (Apr 13, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/15547 ### What is the issue? ubuntu@django2:~$ ollama pulling manifest pulling 4c27e0f5b5ad: 92% ▕█████████████████████████████████████████████████████████████████████████████████████████████████ ▏ 8.9 GB/9.6 GB 14 MB/s 50s **Error: selecting model: failed to pull gemma4: write /usr/share/ollama/.ollama/models/blobs/sha256-4c27e0f5b5adf02ac956c7322bd2ee7636fe3f45a8512c9aba5385242cb6e09a-partial: no space left on device** Ollama 0.20.6 ▸ Chat with a model Start an interactive chat with a model ### Relevant log output ```shell ``` ### OS Linux ### GPU AMD ### CPU AMD ### Ollama version 0.20.6
GiteaMirror added the bug label 2026-04-22 20:22:45 -05:00
GiteaMirror commented 2026-04-22 20:22:45 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Apr 13, 2026):

no space left on device

Make space on the device, or use OLLAMA_MODELS to store the models on a device with space.

<!-- gh-comment-id:4237835399 --> @rick-github commented on GitHub (Apr 13, 2026): ``` no space left on device ``` Make space on the device, or use [`OLLAMA_MODELS`](https://github.com/ollama/ollama/blob/main/docs/faq.mdx#how-do-i-set-them-to-a-different-location) to store the models on a device with space.
GiteaMirror commented 2026-04-22 20:22:46 -05:00
Author
Owner
Copy Link

@fcorneli commented on GitHub (Apr 13, 2026):

Maybe the Linux installer could use /home/ollama instead of the "root" virtual volume which saturates on all Linux distributions anyway?
Wild guess is that almost everybody has to create /etc/systemd/system/ollama.service.d/override.conf with:

[Service]
Environment="OLLAMA_MODELS=/home/ollama/"
Environment="OLLAMA_NO_CLOUD=1"
Environment="OLLAMA_FLASH_ATTENTION=1"
Environment="OLLAMA_KV_CACHE_TYPE=q8_0"
Environment="OLLAMA_KEEP_ALIVE=10m"
SyslogIdentifier=ollama
<!-- gh-comment-id:4238643509 --> @fcorneli commented on GitHub (Apr 13, 2026): Maybe the Linux installer could use `/home/ollama` instead of the "root" virtual volume which saturates on all Linux distributions anyway? Wild guess is that almost everybody has to create `/etc/systemd/system/ollama.service.d/override.conf` with: ``` [Service] Environment="OLLAMA_MODELS=/home/ollama/" Environment="OLLAMA_NO_CLOUD=1" Environment="OLLAMA_FLASH_ATTENTION=1" Environment="OLLAMA_KV_CACHE_TYPE=q8_0" Environment="OLLAMA_KEEP_ALIVE=10m" SyslogIdentifier=ollama ```
GiteaMirror commented 2026-04-22 20:22:46 -05:00
Author
Owner
Copy Link

@PureBlissAK commented on GitHub (Apr 18, 2026):

🤖 Automated Triage & Analysis Report

Issue: #15547
Analyzed: 2026-04-18T18:20:44.461009

Analysis

  • Type: unknown
  • Severity: medium
  • Components: unknown

Implementation Plan

  • Effort: medium
  • Steps:

This issue has been triaged and marked for implementation.

<!-- gh-comment-id:4274307094 --> @PureBlissAK commented on GitHub (Apr 18, 2026): <!-- ollama-issue-orchestrator:v1 issue:15547 --> ## 🤖 Automated Triage & Analysis Report **Issue**: #15547 **Analyzed**: 2026-04-18T18:20:44.461009 ### Analysis - **Type**: unknown - **Severity**: medium - **Components**: unknown ### Implementation Plan - **Effort**: medium - **Steps**: *This issue has been triaged and marked for implementation.*
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#35693
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?