I’m running on a Intel NUC. When I click the Install now from the Settings screen I get an Update Failed message and have to reenter my password.to log back in. The system is still on 1.5 and tells me umbrelOS 1.7.1 is now available to install.
Same thing over here!
Running a small nuc with unknown hardware but also grub boot installed.. @admins
I tried everything to make it work the last 48 hours but nothing works, and im so happy with the external usb support but it needs to work
Is there already 1.7.1 I only see 1.7 ?
Thats the upfollowing release.. its called Semantic Versioning (SemVer).
To explain why a version jumps from 1.5 directly to 1.7.1, it helps to understand the standard Major.Minor.Patch structure:
The Format: X.Y.Z..
X - Major Version: Incremented when you make incompatible API changes.
Y - Minor Version: Incremented when you add functionality in a backward-compatible manner.
Z - Patch Version: Incremented when you make backward-compatible bug fixes.
This seems to happen to all of us Intel NUC owners… I had the same problem trying to update from 1.4.2 to 1.5 on a Intel NUC (Model NUC10i7FNH). I ended up starting over from scratch and loading 1.5. I haven’t tried updating to 1.7.1 yet, but I’m sure I’ll have similar problems with a failed install.
Try stopping your apps before upgrading.
I managed the 1.5 to 1.7.1 upgrade but it resulted in 5 apps refusing to start.
The only way I managed to resolve this, was to restore each app using “rewind” from my backup server .. to the day before the upgrade.
This really sucks for a server OS
(My system is a RPI5)
Hello,
I suggest you check the logs:
cat /var/lib/mender/device_type
mender --version
sudo systemctl is-active mender-client mender 2>/dev/null || true
and check if you have an external disk mounted. If so, unmount it.
sudo umount /home/umbrel/umbrel/external/Untitled
then restart the 1.7.1 installation.
Hi, I do have an external disk with the blockchain data on. Would I then shut down my Pi4, disconnect the external drive and then start and update?
Yes, try doing it like that.
And what if you boot off the external drive?
Starting the Pi4 without the external SSD did not work. I just got to a page where I could set up a new Umbrel or restore. So I assume info about my Umbrel is stored on the SSD, not the SD card? Or is there another way to do it?
Yes, your assumption is correct. On Umbrel OS (especially Raspberry Pi setups), the base OS lives on the microSD card, while all your apps, data, Bitcoin blockchain, files, settings, and configurations are stored on the external SSD. This design allows you to reflash the SD card without losing everything.
When you boot without the SSD, Umbrel detects no external storage and drops you into the fresh setup/restore screen—which is expected behavior.
Recommended Upgrade Path: Clean Flash (Safest for Major Version Jump)
Upgrading from 1.5 to 1.7.1 via the in-UI OTA update has been problematic for many users (especially on Pi 4/5), with failed updates, apps not starting afterward, or other issues.a6989b
Backup first (if not already using Umbrel’s built-in backups):
Use the Backups feature in umbrelOS 1.5 (to USB, NAS, or another Umbrel).
Or manually copy critical data if possible.
Download the latest image:
Get umbrelos-pi4.img.zip from the official releases: Release umbrelOS 1.7.1 · getumbrel/umbrel · GitHub (or the latest).
Flash the new image to your microSD card:
Use Balena Etcher (recommended) or Raspberry Pi Imager.
Flash the .img file to the SD card (not the SSD).
Boot with the SSD attached:
Insert the newly flashed SD card.
Connect your external SSD.
Power on the Pi 4.
It should boot into your existing Umbrel (it detects the data on the SSD and restores/mounts everything). The first boot may take 5–10+ minutes.
Access it:
Go to umbrel.local (or your Pi’s IP) in a browser.
Log in with your existing credentials.
This process is the standard way to “upgrade” the OS on Pi hardware and is more reliable than in-place OTA for bigger jumps.
If OTA Update Still Appeals (Less Recommended Right Now)
In Settings → check for updates and try installing 1.7.1.
Stop all apps first.
Some users report issues with external drives or Mender (the update system)—check logs if it fails (cat /var/lib/mender/device_type, etc.).
Have a backup ready and be prepared to fall back to the flash method.
I’d recommend you not to follow what someone copy-pasting from an AI suggests (and clearly hasn’t tested himself), it’s safer to wait for a smother upgrade version, there’s probably no need to rush, and this version hasn’t been tested enough, it went from beta to final version in just 6 days.
My 2 cents.
My case is a little different. I run Umbrel on a miniPC and I was updating from version 1.5 to 1.7.1. Initially, the installation was completed and after restarting, my browser displayed that initial screen asking me to create an account or restore a backup.
I have my apps and data on a second SSD drive. Since version 1.0 or 1.1, I used to run these steps via SSH so that my Umbrel would recognize my credentials and I could access my data again:
-=-=-=-=-=-=-=-=-=-=-=-=
login umbrel - umbrel
lsblk
sudo mount /dev/sdb1 /home
lsblk
sudo nano /etc/fstab
#comments out old /home
/dev/sdb1 /home ext4 defaults 0 0
ctrl x -Y
sudo reboot now
-=-=-=-=-=-=-=-=-=-=-=-=
I did exactly the same thing this time, however, when accessing umbrel.local it remained on the welcome page, not recognizing that I already had an account. I verified that now the edit I made to the fstab file no longer remains after the restart. Somehow Umbrel is erasing it, so it doesn’t recognize my second drive and can’t find my data.
After much discussion with Gemini trying to solve the problem, which apparently has to do with something called Rugix, I found no alternative but to revert to version 1.5. I flashed it from the USB, ran the commands above, and everything went back to normal.
Now, if possible, I would like suggestions on how to update to version 1.7.1 safely. I’m not in a hurry to update, but I know I’ll have to do it sooner or later, because something has changed in the reboot process and will remain in future versions.
Those of you who have a second SSD to store apps and data, how are you getting Umbrel to automatically identify this other drive? I’m thinking of creating a backup, installing version 1.7.1 again, and trying to restore my account with that backup. Will that work?
Thank you for your attention.
After running for a couple of days my Dockge app now no longer shows any stacks, is it a Docker issue? How do I fix from ssh ..thanks
(The data is all there for the containers that Dockge manages, but the stacks are gone .. how to restore?)
EDIT: Seems the docker.pid was locked, so docker would not run. Deleted it and restarted Dockge and got everything back.
To my opinion umbrel should solve these issues.
It is not a communities task to experiment with workarounds, which may fail or not. Update should be tested extensively before lauch. Hardware mentioned here is common hardware.
I also tried to upgrade from 1.5 to 1.7.1 on my Pi 4B, using both OTA updates and SD card flashing, and every time the SSD was not “mounted” by UmbrelOS.
Sometimes the umbrel services straight up failed to start, no dashboard, nothing and sometimes it was just like a fresh install using the SD card’s storage.
Even tried to upgrade my SSD enclosure to make sure it supports UASP (a suggestion from Gemini).
What I noticed though is that on boot, when I ssh into the pi and run lsblk, I can see my SSD but when I try to read anything on it, the command hangs then it stops showing up on lsblk until a reboot.
I think that the 1.7.1 release is just broken and should be addressed by the maintainers and that additionnal hardware tests should be done before a release.
For now if you have the same problem, just stay on 1.5 untill a new update addresses this.
I agree 100%!
Yep, Umbrel is broke .. maintainers fix please!
Any experience with v1.7.2 yet?