Umbrel always restoring from SSD

Hey,
I have some issue with Umbrel. Something went wrong with the new 0.4.15 update.
So I tried to install 0.4.14 again.
But this will not work. Umbrel always restores the 0.4.15 someway.
I flashed the SD card and in four runs I did

  1. rm -rf /mnt/data/*
  2. mkfs ext4
  3. shred -f -z /dev/sda1
  4. pluged the SSD to Windows, erased the volume and full formatted it to NTFS

After each run the debug log shows

Yes, it contains an Umbrel install

No, SD version is not newer, exiting.

What should I do now? How can this happen? I mean I completely tore it to zero?!

Full log:

=====================
= Umbrel debug info =

Umbrel version

0.4.14

Flashed OS version

v0.4.14

Raspberry Pi Model

Revision : c03111
Serial : 10000000be1e6bd2
Model : Raspberry Pi 4 Model B Rev 1.1

Firmware

Dec 1 2021 15:01:54
Copyright (c) 2012 Broadcom
version 71bd3109023a0c8575585ba87cbb374d2eeb038f (clean) (release) (start)

Temperature

temp=30.6’C

Throttling

throttled=0x0

Memory usage

          total        used        free      shared  buff/cache   available
Mem:           3.8G        153M        3.4G         16M        271M        3.6G
Swap:          4.1G          0B        4.1G

total: 4.1%
system: 4.1%
tor: 0%
lnd: 0%
electrs: 0%
bitcoin: 0%

Memory monitor logs

tail: cannot open ‘/home/umbrel/umbrel/scripts/…/logs/memory-monitor.log’ for reading: No such file or directory

Filesystem information

Filesystem Size Used Avail Use% Mounted on
/dev/root 7.0G 3.2G 3.5G 48% /
/dev/sda1 916G 4.3G 866G 1% /home/umbrel/umbrel

Startup service logs

– Logs begin at Thu 2019-02-14 10:11:59 UTC, end at Wed 2022-03-02 19:15:35 UTC. –
Mar 02 19:15:25 umbrel systemd[1]: Starting Umbrel Startup Service…
Mar 02 19:15:25 umbrel umbrel startup[1176]: ======================================
Mar 02 19:15:25 umbrel umbrel startup[1176]: ============ CONFIGURING =============
Mar 02 19:15:25 umbrel umbrel startup[1176]: ========= UMBREL (mainnet) ===========
Mar 02 19:15:25 umbrel umbrel startup[1176]: ======================================
Mar 02 19:15:25 umbrel umbrel startup[1176]: Generating auth credentials
Mar 02 19:15:25 umbrel umbrel startup[1176]: Generating Tor password
Mar 02 19:15:29 umbrel umbrel startup[1176]: Unable to find image ‘getumbrel/tor:v0.4.1.9’ locally

External storage service logs

– Logs begin at Thu 2019-02-14 10:11:59 UTC, end at Wed 2022-03-02 19:15:35 UTC. –
Mar 02 19:14:18 umbrel systemd[1]: Starting External Storage Mounter…
Mar 02 19:14:18 umbrel external storage mounter[536]: Running external storage mount script…
Mar 02 19:14:26 umbrel external storage mounter[536]: Found device “ASMT 2115”
Mar 02 19:14:26 umbrel external storage mounter[536]: Blacklisting USB device IDs against UAS driver…
Mar 02 19:14:27 umbrel external storage mounter[536]: Rebinding USB drivers…
Mar 02 19:14:27 umbrel external storage mounter[536]: Checking USB devices are back…
Mar 02 19:14:27 umbrel external storage mounter[536]: Waiting for USB devices…
Mar 02 19:14:28 umbrel external storage mounter[536]: Waiting for USB devices…
Mar 02 19:14:29 umbrel external storage mounter[536]: Checking if the device is ext4…
Mar 02 19:14:36 umbrel external storage mounter[536]: Yes, it is ext4
Mar 02 19:14:36 umbrel external storage mounter[536]: Checking if device contains an Umbrel install…
Mar 02 19:14:36 umbrel external storage mounter[536]: Yes, it contains an Umbrel install
Mar 02 19:14:36 umbrel external storage mounter[536]: Bind mounting external storage over local Umbrel installation…
Mar 02 19:14:36 umbrel external storage mounter[536]: Bind mounting external storage over local Docker data dir…
Mar 02 19:14:36 umbrel external storage mounter[536]: Bind mounting external storage to /swap
Mar 02 19:14:36 umbrel external storage mounter[536]: Bind mounting SD card root at /sd-card…
Mar 02 19:14:36 umbrel external storage mounter[536]: Checking Umbrel root is now on external storage…
Mar 02 19:15:15 umbrel external storage mounter[536]: Checking /var/lib/docker is now on external storage…
Mar 02 19:15:15 umbrel external storage mounter[536]: Checking /swap is now on external storage…
Mar 02 19:15:15 umbrel external storage mounter[536]: Setting up swapfile
Mar 02 19:15:15 umbrel external storage mounter[536]: rm: cannot remove ‘/swap/swapfile’: No such file or directory
Mar 02 19:15:15 umbrel external storage mounter[536]: Setting up swapspace version 1, size = 4 GiB (4294963200 bytes)
Mar 02 19:15:15 umbrel external storage mounter[536]: no label, UUID=f9ba0f29-3ab6-42ff-b93a-5cab27f2f33e
Mar 02 19:15:15 umbrel external storage mounter[536]: Checking SD Card root is bind mounted at /sd-root…
Mar 02 19:15:15 umbrel external storage mounter[536]: Starting external drive mount monitor…
Mar 02 19:15:15 umbrel external storage mounter[536]: Mount script completed successfully!
Mar 02 19:15:15 umbrel systemd[1]: Started External Storage Mounter.

External storage SD card update service logs

– Logs begin at Thu 2019-02-14 10:11:59 UTC, end at Wed 2022-03-02 19:15:35 UTC. –
Mar 02 19:15:24 umbrel systemd[1]: Starting External Storage SDcard Updater…
Mar 02 19:15:25 umbrel external storage updater[1098]: Checking if SD card Umbrel is newer than external storage…
Mar 02 19:15:25 umbrel external storage updater[1098]: No, SD version is not newer, exiting.
Mar 02 19:15:25 umbrel systemd[1]: Started External Storage SDcard Updater.

Karen logs

tail: cannot open ‘logs/karen.log’ for reading: No such file or directory

Docker containers

NAMES STATUS

Umbrel logs

ERROR: The Compose file ‘./docker-compose.yml’ is invalid because:
networks.default.ipam.config.subnet is invalid: should use the CIDR format
services.tor_proxy.ports contains an invalid type, it should be a number, or an object
services.bitcoin.ports contains an invalid type, it should be a number, or an object
services.electrs.ports contains an invalid type, it should be a number, or an object
services.lnd.ports contains an invalid type, it should be a number, or an object
services.lnd.ports contains an invalid type, it should be a number, or an object
services.nginx.ports contains an invalid type, it should be a number, or an object
services.lnd.ports value [‘9735:9735’, ‘:’, ‘:’] has non-unique elements

Bitcoin Core logs

ERROR: The Compose file ‘./docker-compose.yml’ is invalid because:
networks.default.ipam.config.subnet is invalid: should use the CIDR format
services.tor_proxy.ports contains an invalid type, it should be a number, or an object
services.bitcoin.ports contains an invalid type, it should be a number, or an object
services.electrs.ports contains an invalid type, it should be a number, or an object
services.lnd.ports contains an invalid type, it should be a number, or an object
services.lnd.ports contains an invalid type, it should be a number, or an object
services.nginx.ports contains an invalid type, it should be a number, or an object
services.lnd.ports value [‘9735:9735’, ‘:’, ‘:’] has non-unique elements

LND logs

ERROR: The Compose file ‘./docker-compose.yml’ is invalid because:
networks.default.ipam.config.subnet is invalid: should use the CIDR format
services.tor_proxy.ports contains an invalid type, it should be a number, or an object
services.bitcoin.ports contains an invalid type, it should be a number, or an object
services.electrs.ports contains an invalid type, it should be a number, or an object
services.lnd.ports contains an invalid type, it should be a number, or an object
services.lnd.ports contains an invalid type, it should be a number, or an object
services.nginx.ports contains an invalid type, it should be a number, or an object
services.lnd.ports value [‘9735:9735’, ‘:’, ‘:’] has non-unique elements

electrs logs

ERROR: The Compose file ‘./docker-compose.yml’ is invalid because:
networks.default.ipam.config.subnet is invalid: should use the CIDR format
services.tor_proxy.ports contains an invalid type, it should be a number, or an object
services.bitcoin.ports contains an invalid type, it should be a number, or an object
services.electrs.ports contains an invalid type, it should be a number, or an object
services.lnd.ports contains an invalid type, it should be a number, or an object
services.lnd.ports contains an invalid type, it should be a number, or an object
services.nginx.ports contains an invalid type, it should be a number, or an object
services.lnd.ports value [‘9735:9735’, ‘:’, ‘:’] has non-unique elements

Tor logs

ERROR: The Compose file ‘./docker-compose.yml’ is invalid because:
networks.default.ipam.config.subnet is invalid: should use the CIDR format
services.tor_proxy.ports contains an invalid type, it should be a number, or an object
services.bitcoin.ports contains an invalid type, it should be a number, or an object
services.electrs.ports contains an invalid type, it should be a number, or an object
services.lnd.ports contains an invalid type, it should be a number, or an object
services.lnd.ports contains an invalid type, it should be a number, or an object
services.nginx.ports contains an invalid type, it should be a number, or an object
services.lnd.ports value [‘9735:9735’, ‘:’, ‘:’] has non-unique elements

==== Result ====

The debug script did not automatically detect any issues with your Umbrel.

To do a new install, you must exclude all partitions on SSD. You can use “disk management” of Windows to do that. Umbrel will create needed partitions and format them.
It is not possible downgrade Umbrel flashing SD.

seems so.
But this saved my :peach:

cd ~/umbrel && sudo ./scripts/update/update --repo getumbrel/umbrel#v0.4.14

Now Umbrel is working again :hot_face: