Update from 6.4.1 to 6.4.2 won't work

This is the first time that my Turris Omnia has a problem updating. I have a first generation Turris Omina. It is currently running v6.4.1.

Also, a factory reset only seems to restart the route without changing anything.

The error message when attempting to update:

Updater execution failed:
INFO:Target Turris OS: 6.4.2
INFO:Queue upgrade of kernel/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ledtrig-oneshot/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-i2c-core/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-regmap-core/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-regmap-i2c/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-eeprom-at24/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-leds-turris-omnia/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ledtrig-gpio/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ledtrig-transient/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-i2c-mux/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-i2c-mux-pca954x/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-nls-base/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-usb-core/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-usb-serial/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-usb-serial-wwan/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-usb-serial-qualcomm/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-gpio-pca953x/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-scsi-core/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-usb-storage/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-usb-storage-extras/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ikconfig/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of omnia-generic-support/turrispackages/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of base-files/core/1463-6.4.2-r16862+127-170d9e447d[1463-6.4.1-r16862+126-170d9e447d]
INFO:Queue upgrade of kmod-nf-conntrack/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-nf-nat/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-nf-log/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-nf-ipt/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-nf-reject/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ipt-core/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ipt-nat/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-nf-conntrack6/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ipt-conntrack/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of knot-resolver/turrispackages/5.7.0-1[5.6.0-3]
INFO:Queue upgrade of kmod-usb-ehci/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-usb2/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-usb-storage-uas/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-br-netfilter/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-crypto-acompress/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-lib-zstd/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-lib-xor/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-lib-raid6/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-lib-zlib-deflate/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-lib-zlib-inflate/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-lib-lzo/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-crypto-hash/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-crypto-crc32c/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-lib-crc32c/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-fs-btrfs/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-crypto-null/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-crypto-gf128/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-crypto-ghash/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-crypto-sha256/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-crypto-aead/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-crypto-manager/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-crypto-hmac/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-crypto-rng/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-crypto-seqiv/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-crypto-ctr/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-crypto-gcm/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-crypto-ccm/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-crypto-cmac/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-cfg80211/core/5.15.127+5.15.81-1-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120+5.15.81-1-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-mac80211/core/5.15.127+5.15.81-1-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120+5.15.81-1-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ath/core/5.15.127+5.15.81-1-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120+5.15.81-1-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ath10k/core/5.15.127+5.15.81-1-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120+5.15.81-1-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ath9k-common/core/5.15.127+5.15.81-1-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120+5.15.81-1-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ath9k/core/5.15.127+5.15.81-1-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120+5.15.81-1-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-nf-flow/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-hwmon-core/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-thermal/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-mt76-core/core/5.15.127+2022-10-01-72b87836-4-59c7aae3065e1430c1f2c7c63d04911e[5.15.120+2022-10-01-72b87836-4-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-mt76-connac/core/5.15.127+2022-10-01-72b87836-4-59c7aae3065e1430c1f2c7c63d04911e[5.15.120+2022-10-01-72b87836-4-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-mt7615-common/core/5.15.127+2022-10-01-72b87836-4-59c7aae3065e1430c1f2c7c63d04911e[5.15.120+2022-10-01-72b87836-4-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-mt7915e/core/5.15.127+2022-10-01-72b87836-4-59c7aae3065e1430c1f2c7c63d04911e[5.15.120+2022-10-01-72b87836-4-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ipt-offload/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-nf-nathelper/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of schnapps/turrispackages/2.12.1-1[2.11.0-1]
INFO:Queue upgrade of kmod-sched-core/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-sched-cake/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ipt-raw/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ipt-conntrack-extra/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ipt-ipopt/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ifb/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-lib-crc-ccitt/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-slhc/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ppp/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-pppox/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-pppoe/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-iptunnel4/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-iptunnel/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-sit/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-iptunnel6/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ip6-tunnel/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of php8/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-bcmath/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-gmp/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-phar/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-filter/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-intl/packages/8.0.30-1[8.0.29-1]
INFO:Queue install of php8-pecl-sodium/packages/2.0.23-1
INFO:Queue upgrade of php8-mod-dom/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-zip/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-curl/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-iconv/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-simplexml/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-session/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-opcache/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-pcntl/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-mbstring/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-xmlwriter/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-xml/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-gd/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-openssl/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-xmlreader/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-fileinfo/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-ctype/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-cli/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-fpm/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of nextcloud/turrispackages/24.0.9-4[24.0.9-2]
INFO:Queue upgrade of kmod-nfnetlink/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ipt-ipset/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-nfnetlink-log/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ipt-nflog/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of php8-mod-mysqlnd/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-pdo/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of php8-mod-pdo-mysql/packages/8.0.30-1[8.0.29-1]
INFO:Queue upgrade of nextcloud-install/turrispackages/24.0.9-4[24.0.9-2]
INFO:Queue upgrade of kmod-nf-conntrack-netlink/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ebtables/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-nf-log6/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-nf-ipt6/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-nf-reject6/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-ip6tables/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-netlink-diag/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of kmod-crypto-md5/core/5.15.127-1-59c7aae3065e1430c1f2c7c63d04911e[5.15.120-1-59c7aae3065e1430c1f2c7c63d04911e]
INFO:Queue upgrade of turris-version/base/6.4.2[6.4.1]
INFO:Downloading packages
line not found
line not found
line not found
DIE:
[string "utils"]:175: [string "utils"]:169: mkdir '/usr/share/updater/download/' failed: Read-only file system


Exit code: -6

Sorry to say that, but it sees your router’s eMMC memory chip just died. I guess you’re still running the OS from this internal drive and haven’t switched over to an mSATA drive. The eMMC chip’s lifespan is very short regarding the number of writes. I actually wonder yours survived for this long. Mine died after about 20 months.

You should rather start ordering: Interní SSD disky | TSBOHEMIA.CZ (but wait, let’s first confirm it indeed is because of dead eMMC).

1 Like

Try following:

" eMMC on its own does not track write cycles like standard drives and does not have mechanism like smart. You can use mmc extcsd read /dev/mmcblk0 from package mmc-utils to take a peak in to amount of used reserved blocks. That is field EXT_CSD_DEVICE_LIFE_TIME_EST. Value is in range of percents so 0x01 is from 0%-10% blocks used, 0x02 is from 10%-20% and so on. When amount of reserved block used is close to 100% then NAND is pretty much EOL."

For example from my omnia:

root@turris:~#  mmc extcsd read /dev/mmcblk0 | grep EXT_CSD_DEVICE_LIFE_TIME_EST_TYP
eMMC Life Time Estimation A [EXT_CSD_DEVICE_LIFE_TIME_EST_TYP_A]: 0x01
eMMC Life Time Estimation B [EXT_CSD_DEVICE_LIFE_TIME_EST_TYP_B]: 0x01
root@turris:~# 

I use a USB harddisk and configured persistent logfiles. I do run pakon, but IIUC in my configuration it uses the external disk…

In retrospect the Omnia should IMHO have opted for a replaceable SD card over eMMC, but I admit that at the time eMMC looked pretty attractive (and who knew back then how much life was actually in the omnia’s design).

P.S.: Things like EXT_CSD_DEVICE_LIFE_TIME_EST tend to not degrade nicely linearly, but initially very slowly, but once it starts things can avalanche into full failure rather rapidly.

3 Likes

Turris Omnia bought 05/2016, mSATA drive Kingston SSDNow UV500 120GB bought 08/2019.
eMMC survived 3 years. I always use Storage, after experience I buy industrial types

TO from campaign, eMMC still alive!

eMMC Life Time Estimation A [EXT_CSD_DEVICE_LIFE_TIME_EST_TYP_A]: 0x01
eMMC Life Time Estimation B [EXT_CSD_DEVICE_LIFE_TIME_EST_TYP_B]: 0x02

i.e. up to 10% and 10-20% reserved blocks used (don’t understand difference between A and B estimations).

I used USB flash for data (logs etc) early - from about autumn 2017. Added SSD for data later, in march 2023.

First of all thanks to all :slight_smile:

@moeller0, I was just about to apply mmc-utils. Of course I had to install that first. But… Same problem. Error because read-only file system. Crazy. It’s obvious that the eMMC is broken.

So I can’t install mmc-utils and therefore I can’t run the test.

But I should be able to flash. And I can choose a different storage, right? :thinking:

It could buy a small mSATA SSD and ask Turris support to do the operation.

1 Like

Many thanks for this info!!! I can now check for eMMC health… I added check to cron :wink:

@miska & team turris, could you maybe include mmc-utils into the basic set of installed software, to avoid catch22 type situations, like this one?

1 Like

Hi Peci,
Is there any good complete guide to migrate the system to the mSATA? I only have /srv so far.

The guides from JardaB above should guide you through it.

1 Like

Does exist similar possibility to display/check how much are USB and/or SSD devices worn out?

For harddisks/SSDs smartctl (out of the smartmontools package) might be usable, but for USB flash drives I really do not know…

Thanks, it works!

root@TOjp:~# smartctl -H /dev/sda
smartctl 7.2 2020-12-30 r5155 [armv7l-linux-5.15.127] (localbuild)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

I used an SSD from the very beginning (ordered it along with the Omnia), so /srv was always on the SSD. Is it still recommended to move everything to the SSD and boot from it? Or will I be fine with that setup?

root@omnia:~# mmc extcsd read /dev/mmcblk0 | grep EXT_CSD_DEVICE_LIFE_TIME_EST_TYP
eMMC Life Time Estimation A [EXT_CSD_DEVICE_LIFE_TIME_EST_TYP_A]: 0x01
eMMC Life Time Estimation B [EXT_CSD_DEVICE_LIFE_TIME_EST_TYP_B]: 0x00

The SSD:

sda            8:0    1 119.2G  0 disk /srv
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%     10685         -

That depends on what usage you have on other parts of the filesystem. If you’re sure nothing does periodic writes to the internal memory, it should last pretty long. But as soon as your ssd will fail and unmount (and it will happen), the router will happily provide the /srv folder on the internal memory and then the decay can be pretty fast.

My suggestion is: make sure you won’t lose anything irreplaceable when the internal memory dies, have a serial cable ready, and use the internal memory as long as it lives. By moving your system to SSD, you’ll lose the physical-button rollback feature, and that was something I really miss now.

If you want to be on a bit safer side, I suggest adding a script to cron that would periodically check if srv is on the mounted drive, and if not, remount it readonly and shout loudly on you.

2 Likes

@miska that sounds like a decent option to include in reforis? Maybe even have it send a notification email if these are configured?

2 Likes

I checked my internal memory just because I read this topic.
My Omnia is from 2017 and I never gave attention to this. I don’t use applications that need storage. The only data that is written regularly are schnapps snapshots.

My eMMC status is this:

mmc extcsd read /dev/mmcblk0 | egrep 'LIFE|EOL'
eMMC Life Time Estimation A [EXT_CSD_DEVICE_LIFE_TIME_EST_TYP_A]: 0x01
eMMC Life Time Estimation B [EXT_CSD_DEVICE_LIFE_TIME_EST_TYP_B]: 0x07
eMMC Pre EOL information [EXT_CSD_PRE_EOL_INFO]: 0x01

Found this command here: https://netmodule-linux.readthedocs.io/en/latest/howto/mmc.html#health-status

Means my internal MMC will be done quit soon and my Omni is broken then? Why is type A and B so different?
I do not have a serial cable and spare mSATA at the moment. Should I oder this soon?

So, your eMMC has used SLC blocks for 10% of their lifetime and MLC blocks for 70% of their lifetime. The EOL info says Normal (under 80% usage).

Higher usage of MLC blocks makes sense, as they are the Multi-level cells, i.e. 2 or 3 bits stored in one “physical bit”. So there’s 2-3 times higher probability each cell will be touched when writing the same amount of data than with SLC cells.

My suggestion would be to start looking for a serial cable and mSATA drive when the EOL status goes to Warning. However, there’s nothing preventing you ordering these two right now. It might be easier now than later (at least regarding the mSATA drive). You will very probably need them in a few months or years.

2 Likes