Wrong names for blobs in linux

[rrebollo]

After following the new tutorial for installation and usage ollama list output was empty.
After a little back and forth I noticed that the name of the blobs was like these:

sha256::somehash
sha256::anotherhash

With (2):: instead of only a (1):. I manually renamed to just one :. Still empty output for local models. Then I restarted ollama systemd service. I finally got the local model recognized. When looking into the blobs folder the name now looks like:

sha256-somehash
sha256-anotherhash

I'm guessing there is still something to tweak a little more about the new feature for hash names.

[amirrezaDev1378]

Hi there,
I'll look into this matter;
maybe Ollama changed their API,
but I did successfully install a model with no trouble on Fedora about a month ago.

Here is how we rename the models:
file

This was the case for Windows; maybe they changed it for Linux too.

I'll look into this matter and, if required, release a new version.

[rrebollo]

Hi there, I'll look into this matter; maybe Ollama changed their API, but I did successfully install a model with no trouble on Fedora about a month ago.

Here is how we rename the models: file

This was the case for Windows; maybe they changed it for Linux too.

I'll look into this matter and, if required, release a new version.

This definitively would explain the bizarre sha256:: observed by me.

ollama-model-direct-download/app/model-install.go

Line 102 in 7527339

newPath = strings.Replace(newPath, "sha256", "sha256:", 1)

In order to make it "right" I could do something like:

newPath = strings.Replace(newPath, "sha256:", "sha256-", 1)

[amirrezaDev1378]

Yes, this is true, but I'm not sure if this is the case with old versions of Ollama.
It'll need to be tested on Linux and Windows using both the latest and some old versions of Ollama.

I'm planning to work on it tomorrow.
Let me know if you are interested in doing it sooner; if not, I'll gladly fix it tomorrow.

[rrebollo]

@amirrezaDev1378 sadly I don't known anything about golang. I also didn't consider what You are saying about previous ollama versions. I just wanna gave You as much context as I could. At the end I'm very grateful for You making public this tool. It has been really helpful to me. Mainly I did raise the issue expecting the next Linux guy could find some hint.

[amirrezaDev1378]

Thank you,
There will be a fix in tomorrow.

[SaKiEQ]

I am having same issue with both latest Ollama and latest Linux.

Ironically when downloaded manually the files get the 'sha256:' format, in case they are not present or formatted that way, the install 'sudo omdd install --model=deepseek-r1:7b --blobsPath=' will throw an error that files are not present.
Yet when present, it begins to download them again with the 'sha256::***' format, eating up a lot of space and time...

[amirrezaDev1378]

Hi @SaKiEQ .
I'm working on this and will release a fix soon.

[amirrezaDev1378]

This may be our issue:
ollama/ollama@703684a

I won't release a fix for the older versions; they can use the current version.

Also, I'm planning on creating a GUI for this tool.

[amirrezaDev1378]

Released the fix just now, check it out:
https://github.com/amirrezaDev1378/ollama-model-direct-download/releases/tag/V2.1.0

[amirrezaDev1378]

I did test this on a few platforms, but I would really appreciate if you test it on your Linux devices to see every things work for you too.

I'll close this issue, but if you face any issues feel free to open another issue 🙂

[SaKiEQ]

Ok will test in a bit ! Thanks so far.

For anybody stuck like I was, I found this small workaround to at least have ollama download the files. Which seemed impossible for the past few days.

#!/bin/sh

# Set the speed threshold in KB/s
THRESHOLD=500

# Variable to track consecutive slow speed occurrences
slow_count=0

while true; do
  # Measure connection speed (downloading a small file)
  speed=$(curl -s -w '%{speed_download}' -o /dev/null https://speed.hetzner.de/100MB.bin)
  
  # Check if speed is empty or invalid
  if [ -z "$speed" ] || ! echo "$speed" | grep -Eq '^[0-9]+(\.[0-9]+)?$'; then
    echo "Failed to measure speed. Retrying..."
    sleep 10
    continue
  fi

  # Convert speed from bytes/s to KB/s
  speed_kbps=$(echo "$speed / 1024" | awk '{printf "%.0f", $1}')  # Using `awk` for precision

  echo "Current speed: ${speed_kbps} KB/s"

  if [ "$speed_kbps" -lt "$THRESHOLD" ]; then
    slow_count=$((slow_count + 1))
    echo "Speed below threshold ($THRESHOLD KB/s). Slow count: $slow_count"
  else
    slow_count=0  # Reset the counter if speed is above threshold
  fi

  # Retry the pull if slow speed is detected twice in a row
  if [ "$slow_count" -ge 2 ]; then
    echo "Connection speed is slow twice in a row. Retrying pull..."
    timeout 10s ollama pull deepseek-r1:7b
    slow_count=0  # Reset the counter after a pull attempt
  fi

  # Wait for a few seconds before checking again
  sleep 7
done