Networking issue with 26.04 daily and zsync

Development Discussion
1

While I have confirmed that the UM 26.04 development release is rock solid as an installed OS, I need to clarify that the Live ISO itself has a problem in that it refuses to establish/configure networking, at the very start of the install, forcing the entire process, for me, to be offline, with no mechanism to verify availability of updates before the install process gets under way, forcing a separate secondary download step for getting that set of updates, post-install!

I've tried a number of things to try to get that networking established during the Live session, and I am failing at all attempts. Below are some "reports" resulting from attempts to establish that connection, or from "probes" trying to identify how things are and where they failed.

I hope someone can assist with a quick fix that will work from that Live session. (Nov 19 2025 development release build)


report_inxi_Fza.txt :

System:
  Kernel: 6.17.0-5-generic arch: x86_64 bits: 64 compiler: gcc v: 15.2.0
    clocksource: tsc avail: hpet,acpi_pm parameters: BOOT_IMAGE=/casper/vmlinuz
    --- quiet splash
  Desktop: MATE v: 1.28.2 wm: marco v: 1.26.2 with: mate-panel
    tools: mate-screensaver dm: LightDM v: 1.32.0 Distro: Ubuntu 26.04
    (Resolute Raccoon)
Machine:
  Type: Desktop Mobo: ASUSTeK model: M4A78-E v: Rev 1.xx serial: <filter>
    uuid: 00dc001e-8c00-01fc-92e5-0026188ab57a BIOS: American Megatrends v: 2603
    date: 04/13/2011
CPU:
  Info: model: AMD Phenom II X4 810 socket: AM2 bits: 64 type: MCP arch: K10
    level: v1 built: 2009-13 process: AMD 45nm family: 0x10 (16) model-id: 4
    stepping: 2 microcode: 0x10000DB
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 4 smt: <unsupported> cache:
    L1: 512 KiB desc: d-4x64 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB L3: 4 MiB
    desc: 1x4 MiB
  Speed (MHz): avg: 800 min/max: 800/2600 boost: disabled
    base/boost: 2600/2600 scaling: driver: acpi-cpufreq governor: schedutil
    volts: 1.5 V ext-clock: 200 MHz cores: 1: 800 2: 800 3: 800 4: 800
    bogomips: 20869
  Flags-basic: ht lm nx pae sse sse2 sse3 sse4a svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass status: Not affected
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; STIBP: disabled; RSB filling;
    PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape status: Not affected
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] RS780D [Radeon HD 3300]
    vendor: ASUSTeK driver: radeon v: kernel alternate: amdgpu arch: TeraScale
    code: R6xx/RV6xx/RV7xx process: TSMC 55-65nm built: 2005-13 ports:
    active: VGA-1 empty: DVI-D-1 bus-ID: 01:05.0 chip-ID: 1002:9614
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.18 compositor: marco v: 1.26.2 driver:
    X: loaded: radeon unloaded: fbdev,modesetting,vesa dri: r600 gpu: radeon
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1440x900 s-dpi: 96 s-size: 381x238mm (15.00x9.37")
    s-diag: 449mm (17.69")
  Monitor-1: VGA-1 mapped: VGA-0 model: HP w1707 serial: <filter>
    built: 2009 res: mode: 1440x900 hz: 60 scale: 100% (1) dpi: 99 gamma: 1.2
    size: 370x230mm (14.57x9.06") diag: 436mm (17.2") ratio: 16:10 modes:
    max: 1440x900 min: 720x400
  API: EGL v: 1.5 hw: drv: amd r600 platforms: device: 0 drv: r600 device: 1
    drv: swrast gbm: drv: r600 surfaceless: drv: r600 x11: drv: r600
    inactive: wayland
  API: OpenGL v: 4.5 compat-v: 3.3 vendor: mesa v: 25.2.6-1ubuntu1
    glx-v: 1.4 direct-render: yes renderer: AMD RS780 (DRM 2.51.0 /
    6.17.0-5-generic LLVM 20.1.8) device-ID: 1002:9614 memory: 312.5 MiB
    unified: no
  Info: Tools: api: eglinfo,glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] SBx00 Azalia
    driver: snd_hda_intel v: kernel bus-ID: 00:14.2 chip-ID: 1002:4383
    class-ID: 0403
  Device-2: Advanced Micro Devices [AMD/ATI] RS780 HDMI Audio [Radeon
    3000/3100 / HD 3200/3300] driver: snd_hda_intel v: kernel bus-ID: 01:05.1
    chip-ID: 1002:960f class-ID: 0403
  API: ALSA v: k6.17.0-5-generic status: kernel-api
    tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.4.9 status: n/a (root, process) with:
    1: pipewire-pulse status: active 2: wireplumber status: active
    tools: pw-cat,pw-cli,wpctl
Network:
  Device-1: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet
    vendor: ASUSTeK driver: ATL1E v: N/A modules: atl1e pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: dc00 bus-ID: 02:00.0 chip-ID: 1969:1026
    class-ID: 0200
  IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Info: services: NetworkManager,wpa_supplicant
Drives:
  Local Storage: total: 2.29 TiB used: 206.9 MiB (0.0%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
    model: WD5000AAKS-00V1A0 size: 465.76 GiB block-size: physical: 512 B
    logical: 512 B speed: 1.5 Gb/s tech: N/A serial: <filter> fw-rev: 1D05
    scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WD20EZRX-00DC0B0 size: 1.82 TiB block-size: physical: 4096 B
    logical: 512 B speed: 3.0 Gb/s tech: N/A serial: <filter> fw-rev: 0A80
    scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 model: USB DISK 2.0 size: 14.46 GiB
    block-size: physical: 512 B logical: 512 B type: USB rev: 2.0 spd: 480 Mb/s
    lanes: 1 mode: 2.0 speed: <unknown> tech: N/A serial: <filter>
    fw-rev: PMAP scheme: GPT
Partition:
  ID-1: / raw-size: N/A size: 1.76 GiB used: 28.1 MiB (1.6%) fs: overlay
    source: ERR-102
  ID-2: /var/log raw-size: 10.86 GiB size: 10.59 GiB (97.49%)
    used: 202.2 MiB (1.9%) fs: ext4 block-size: 4096 B dev: /dev/sdc4
    maj-min: 8:36
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 2 GiB used: 4.7 MiB (0.2%) priority: -2
    dev: /dev/sda2 maj-min: 8:2
  ID-2: swap-2 type: partition size: 996.2 MiB used: 0 KiB (0.0%)
    priority: -3 dev: /dev/sdb10 maj-min: 8:26
  ID-3: swap-3 type: partition size: 996.2 MiB used: 0 KiB (0.0%)
    priority: -4 dev: /dev/sdb11 maj-min: 8:27
  ID-4: swap-4 type: partition size: 1024 MiB used: 0 KiB (0.0%)
    priority: -5 dev: /dev/sdb2 maj-min: 8:18
  ID-5: swap-5 type: partition size: 6 GiB used: 0 KiB (0.0%) priority: -6
    dev: /dev/sdb5 maj-min: 8:21
Sensors:
  System Temperatures: cpu: 59.0 C mobo: 40.0 C
  Fan Speeds (rpm): cpu: 2454 case-1: 0 case-2: 0
  Power: 12v: 12.42 5v: N/A 3.3v: 3.47 vbat: N/A
Info:
  Memory: total: 4 GiB note: est. available: 3.51 GiB used: 1.15 GiB (32.7%)
  Processes: 250 Power: uptime: 8m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 1.36 GiB services: mate-power-manager,upowerd
    Init: systemd v: 257 default: graphical tool: systemctl
  Packages: 2194 pm: dpkg pkgs: 2182 libs: 1156 tools: apt,apt-get pm: snap
    pkgs: 12 Compilers: gcc: 15.2.0 Shell: Bash (sudo) v: 5.3.3
    running-in: mate-terminal inxi: 3.3.39

report_ip_link_show.txt :

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 00:26:18:8a:b5:7a brd ff:ff:ff:ff:ff:ff
    altname enx0026188ab57a

report_lshw_network.txt :

  *-network
       description: Ethernet interface
       product: AR8121/AR8113/AR8114 Gigabit or Fast Ethernet
       vendor: Qualcomm Atheros
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: enp2s0
       version: b0
       serial: 00:26:18:8a:b5:7a
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=ATL1E driverversion=6.17.0-5-generic duplex=full firmware=L1e ip=192.168.0.10 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:18 memory:fbec0000-fbefffff ioport:dc00(size=128)

report_lspci_v.txt :

02:00.0 Ethernet controller: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet (rev b0)
	Subsystem: ASUSTeK Computer Inc. Device 831c
	Flags: bus master, fast devsel, latency 0, IRQ 18, NUMA node 0
	Memory at fbec0000 (64-bit, non-prefetchable) [size=256K]
	I/O ports at dc00 [size=128]
	Capabilities: [40] Power Management version 2
	Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [58] Express Endpoint, IntMsgNum 0
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [180] Device Serial Number ff-8a-b5-7a-00-26-18-ff
	Kernel driver in use: ATL1E
	Kernel modules: atl1e

report_jounalctl_NetworkManager.txt :

root@ubuntu-mate:/home/ubuntu-mate#  journalctl --no-pager --no-hostname -b -u NetworkManager

Dec 28 18:35:11 systemd[1]: Starting NetworkManager.service - Network Manager...
Dec 28 18:35:12 NetworkManager[2336]: <info>  [1766946912.8060] NetworkManager (version 1.52.0) is starting... (boot:fb3abd51-3e63-40ac-bbb2-0856ce545023)
Dec 28 18:35:12 NetworkManager[2336]: <info>  [1766946912.8060] Read config: /etc/NetworkManager/NetworkManager.conf, /usr/lib/NetworkManager/conf.d/{10-dns-resolved.conf,no-mac-addr-change.conf}, /run/NetworkManager/conf.d/10-globally-managed-devices.conf, /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
Dec 28 18:35:12 NetworkManager[2336]: <info>  [1766946912.8123] manager[0x5b3dd3d3a3e0]: monitoring kernel firmware directory '/lib/firmware'.
Dec 28 18:35:12 NetworkManager[2336]: <info>  [1766946912.8124] monitoring ifupdown state file '/run/network/ifstate'.
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.0049] hostname: hostname: using hostnamed
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.0049] hostname: static hostname changed from (none) to "ubuntu-mate"
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.0056] dns-mgr: init: dns=systemd-resolved rc-manager=unmanaged (auto), plugin=systemd-resolved
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.0059] manager[0x5b3dd3d3a3e0]: rfkill: Wi-Fi hardware radio set enabled
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.0059] manager[0x5b3dd3d3a3e0]: rfkill: WWAN hardware radio set enabled
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.0788] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.52.0/libnm-device-plugin-adsl.so)
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.1267] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.52.0/libnm-device-plugin-bluetooth.so)
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.1404] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.52.0/libnm-device-plugin-team.so)
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.1674] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.52.0/libnm-device-plugin-wifi.so)
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.1678] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.52.0/libnm-device-plugin-wwan.so)
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.1683] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.1683] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.1684] manager: Networking is enabled by state file
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.1773] settings: Loaded settings plugin: ifupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.52.0/libnm-settings-plugin-ifupdown.so")
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.1776] settings: Loaded settings plugin: keyfile (internal)
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.1778] ifupdown: management mode: unmanaged
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.1781] ifupdown:       interface-parser: parsing file /etc/network/interfaces
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.1782] ifupdown:       interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d/*
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.1782] ifupdown:       interface-parser: parsing file /etc/network/interfaces.d/50-cloud-init.cfg
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.1783] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces.d/50-cloud-init.cfg
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.1783] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.1785] ifupdown: guessed connection type (enp2s0) = 802-3-ethernet
Dec 28 18:35:13 NetworkManager[2336]: <info>  [1766946913.1789] ifupdown: guessed connection type (enp2s0) = 802-3-ethernet
Dec 28 18:35:16 NetworkManager[2336]: <info>  [1766946916.0374] dhcp: init: Using DHCP client 'internal'
Dec 28 18:35:16 NetworkManager[2336]: <info>  [1766946916.0385] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
Dec 28 18:35:16 NetworkManager[2336]: <info>  [1766946916.0407] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')
Dec 28 18:35:16 NetworkManager[2336]: <info>  [1766946916.0427] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')
Dec 28 18:35:16 NetworkManager[2336]: <info>  [1766946916.0445] device (lo): Activation: starting connection 'lo' (7ddaa5f4-b4fe-43e3-8169-3bcb32bf01f7)
Dec 28 18:35:16 NetworkManager[2336]: <info>  [1766946916.0457] device (enp2s0): carrier: link connected
Dec 28 18:35:16 NetworkManager[2336]: <info>  [1766946916.0465] manager: (enp2s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Dec 28 18:35:16 NetworkManager[2336]: <info>  [1766946916.0599] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Dec 28 18:35:16 systemd[1]: Started NetworkManager.service - Network Manager.
Dec 28 18:35:16 NetworkManager[2336]: <info>  [1766946916.0631] device (lo): state change: disconnected -> prepare (reason 'none', managed-type: 'external')
Dec 28 18:35:16 NetworkManager[2336]: <info>  [1766946916.0640] device (lo): state change: prepare -> config (reason 'none', managed-type: 'external')
Dec 28 18:35:16 NetworkManager[2336]: <info>  [1766946916.0646] device (lo): state change: config -> ip-config (reason 'none', managed-type: 'external')
Dec 28 18:35:16 NetworkManager[2336]: <info>  [1766946916.0653] device (lo): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')
Dec 28 18:35:16 NetworkManager[2336]: <info>  [1766946916.0702] device (lo): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
Dec 28 18:35:16 NetworkManager[2336]: <info>  [1766946916.0705] device (lo): state change: secondaries -> activated (reason 'none', managed-type: 'external')
Dec 28 18:35:16 NetworkManager[2336]: <info>  [1766946916.0714] device (lo): Activation: successful, device activated.
Dec 28 18:35:16 NetworkManager[2336]: <info>  [1766946916.0719] manager: startup complete
Dec 28 18:35:16 NetworkManager[2336]: <info>  [1766946916.0729] modem-manager: ModemManager available
Dec 28 18:35:35 NetworkManager[2336]: <info>  [1766946935.5066] agent-manager: agent[5714fefabd8cc8b3,:1.58/org.freedesktop.nm-applet/1000]: agent registered
Dec 28 18:56:21 NetworkManager[2336]: <info>  [1766948181.8722] caught SIGTERM, shutting down normally.
Dec 28 18:56:21 systemd[1]: Stopping NetworkManager.service - Network Manager...
Dec 28 18:56:21 NetworkManager[2336]: <info>  [1766948181.8755] exiting (success)
Dec 28 18:56:21 systemd[1]: NetworkManager.service: Deactivated successfully.
Dec 28 18:56:21 systemd[1]: Stopped NetworkManager.service - Network Manager.
Dec 28 18:56:21 systemd[1]: NetworkManager.service: Consumed 1.796s CPU time, 29.9M memory peak.
Dec 28 18:56:21 systemd[1]: Starting NetworkManager.service - Network Manager...
Dec 28 18:56:21 NetworkManager[6855]: <info>  [1766948181.9601] NetworkManager (version 1.52.0) is starting... (after a restart, boot:fb3abd51-3e63-40ac-bbb2-0856ce545023)
Dec 28 18:56:21 NetworkManager[6855]: <info>  [1766948181.9602] Read config: /etc/NetworkManager/NetworkManager.conf, /usr/lib/NetworkManager/conf.d/{10-dns-resolved.conf,no-mac-addr-change.conf}, /run/NetworkManager/conf.d/10-globally-managed-devices.conf, /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
Dec 28 18:56:21 NetworkManager[6855]: <info>  [1766948181.9654] manager[0x5fa878d0b2f0]: monitoring kernel firmware directory '/lib/firmware'.
Dec 28 18:56:21 NetworkManager[6855]: <info>  [1766948181.9655] monitoring ifupdown state file '/run/network/ifstate'.
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.0941] hostname: hostname: using hostnamed
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.0942] hostname: static hostname changed from (none) to "ubuntu-mate"
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.0952] dns-mgr: init: dns=systemd-resolved rc-manager=unmanaged (auto), plugin=systemd-resolved
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.0962] manager[0x5fa878d0b2f0]: rfkill: Wi-Fi hardware radio set enabled
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.0963] manager[0x5fa878d0b2f0]: rfkill: WWAN hardware radio set enabled
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.1373] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.52.0/libnm-device-plugin-adsl.so)
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.1847] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.52.0/libnm-device-plugin-bluetooth.so)
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.1988] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.52.0/libnm-device-plugin-team.so)
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.1992] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.52.0/libnm-device-plugin-wifi.so)
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.1995] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.52.0/libnm-device-plugin-wwan.so)
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.1998] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.1999] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.2000] manager: Networking is enabled by state file
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.2021] settings: Loaded settings plugin: ifupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.52.0/libnm-settings-plugin-ifupdown.so")
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.2022] settings: Loaded settings plugin: keyfile (internal)
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.2022] ifupdown: management mode: unmanaged
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.2022] ifupdown:       interface-parser: parsing file /etc/network/interfaces
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.2190] ifupdown:       interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d/*
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.2191] ifupdown:       interface-parser: parsing file /etc/network/interfaces.d/50-cloud-init.cfg
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.2192] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces.d/50-cloud-init.cfg
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.2192] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.2194] ifupdown: guessed connection type (enp2s0) = 802-3-ethernet
Dec 28 18:56:22 NetworkManager[6855]: <info>  [1766948182.2198] ifupdown: guessed connection type (enp2s0) = 802-3-ethernet
Dec 28 18:56:24 NetworkManager[6855]: <info>  [1766948184.3243] dhcp: init: Using DHCP client 'internal'
Dec 28 18:56:24 NetworkManager[6855]: <info>  [1766948184.3246] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
Dec 28 18:56:24 NetworkManager[6855]: <info>  [1766948184.3251] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')
Dec 28 18:56:24 NetworkManager[6855]: <info>  [1766948184.3255] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')
Dec 28 18:56:24 NetworkManager[6855]: <info>  [1766948184.3265] device (lo): Activation: starting connection 'lo' (7ddaa5f4-b4fe-43e3-8169-3bcb32bf01f7)
Dec 28 18:56:24 NetworkManager[6855]: <info>  [1766948184.3270] device (enp2s0): carrier: link connected
Dec 28 18:56:24 NetworkManager[6855]: <info>  [1766948184.3275] manager: (enp2s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Dec 28 18:56:24 NetworkManager[6855]: <info>  [1766948184.3439] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Dec 28 18:56:24 systemd[1]: Started NetworkManager.service - Network Manager.
Dec 28 18:56:24 NetworkManager[6855]: <info>  [1766948184.3462] device (lo): state change: disconnected -> prepare (reason 'none', managed-type: 'external')
Dec 28 18:56:24 NetworkManager[6855]: <info>  [1766948184.3467] device (lo): state change: prepare -> config (reason 'none', managed-type: 'external')
Dec 28 18:56:24 NetworkManager[6855]: <info>  [1766948184.3482] device (lo): state change: config -> ip-config (reason 'none', managed-type: 'external')
Dec 28 18:56:24 NetworkManager[6855]: <info>  [1766948184.3494] device (lo): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')
Dec 28 18:56:24 NetworkManager[6855]: <info>  [1766948184.3577] modem-manager: ModemManager available
Dec 28 18:56:24 NetworkManager[6855]: <info>  [1766948184.3579] device (lo): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
Dec 28 18:56:24 NetworkManager[6855]: <info>  [1766948184.3581] device (lo): state change: secondaries -> activated (reason 'none', managed-type: 'external')
Dec 28 18:56:24 NetworkManager[6855]: <info>  [1766948184.3586] device (lo): Activation: successful, device activated.
Dec 28 18:56:24 NetworkManager[6855]: <info>  [1766948184.3592] manager: startup complete
Dec 28 18:56:24 NetworkManager[6855]: <info>  [1766948184.4257] agent-manager: agent[1c05f8105e0ec09a,:1.58/org.freedesktop.nm-applet/1000]: agent registered
Dec 28 19:01:41 NetworkManager[6855]: <info>  [1766948501.3804] caught SIGTERM, shutting down normally.
Dec 28 19:01:41 systemd[1]: Stopping NetworkManager.service - Network Manager...
Dec 28 19:01:41 NetworkManager[6855]: <info>  [1766948501.3834] exiting (success)
Dec 28 19:01:41 systemd[1]: NetworkManager.service: Deactivated successfully.
Dec 28 19:01:41 systemd[1]: Stopped NetworkManager.service - Network Manager.
Dec 28 19:01:41 systemd[1]: NetworkManager.service: Consumed 1.024s CPU time, 28.4M memory peak.
Dec 28 19:01:41 systemd[1]: Starting NetworkManager.service - Network Manager...
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.5308] NetworkManager (version 1.52.0) is starting... (after a restart, boot:fb3abd51-3e63-40ac-bbb2-0856ce545023)
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.5309] Read config: /etc/NetworkManager/NetworkManager.conf, /usr/lib/NetworkManager/conf.d/{10-dns-resolved.conf,no-mac-addr-change.conf}, /run/NetworkManager/conf.d/10-globally-managed-devices.conf, /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.5377] manager[0x5de693495570]: monitoring kernel firmware directory '/lib/firmware'.
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.5377] monitoring ifupdown state file '/run/network/ifstate'.
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.6665] hostname: hostname: using hostnamed
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.6666] hostname: static hostname changed from (none) to "ubuntu-mate"
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.6676] dns-mgr: init: dns=systemd-resolved rc-manager=unmanaged (auto), plugin=systemd-resolved
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.6686] manager[0x5de693495570]: rfkill: Wi-Fi hardware radio set enabled
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.6686] manager[0x5de693495570]: rfkill: WWAN hardware radio set enabled
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.6842] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.52.0/libnm-device-plugin-adsl.so)
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.6999] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.52.0/libnm-device-plugin-bluetooth.so)
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.7059] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.52.0/libnm-device-plugin-team.so)
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.7281] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.52.0/libnm-device-plugin-wifi.so)
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.7284] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.52.0/libnm-device-plugin-wwan.so)
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.7287] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.7288] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.7288] manager: Networking is enabled by state file
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.7311] settings: Loaded settings plugin: ifupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.52.0/libnm-settings-plugin-ifupdown.so")
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.7312] settings: Loaded settings plugin: keyfile (internal)
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.7312] ifupdown: management mode: unmanaged
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.7312] ifupdown:       interface-parser: parsing file /etc/network/interfaces
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.7369] ifupdown:       interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d/*
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.7371] ifupdown:       interface-parser: parsing file /etc/network/interfaces.d/50-cloud-init.cfg
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.7371] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces.d/50-cloud-init.cfg
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.7371] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.7373] ifupdown: guessed connection type (enp2s0) = 802-3-ethernet
Dec 28 19:01:41 NetworkManager[7794]: <info>  [1766948501.7377] ifupdown: guessed connection type (enp2s0) = 802-3-ethernet
Dec 28 19:01:43 NetworkManager[7794]: <info>  [1766948503.7787] dhcp: init: Using DHCP client 'internal'
Dec 28 19:01:43 NetworkManager[7794]: <info>  [1766948503.7790] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
Dec 28 19:01:43 NetworkManager[7794]: <info>  [1766948503.7795] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')
Dec 28 19:01:43 NetworkManager[7794]: <info>  [1766948503.7800] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')
Dec 28 19:01:43 NetworkManager[7794]: <info>  [1766948503.7807] device (lo): Activation: starting connection 'lo' (7ddaa5f4-b4fe-43e3-8169-3bcb32bf01f7)
Dec 28 19:01:43 NetworkManager[7794]: <info>  [1766948503.7815] device (enp2s0): carrier: link connected
Dec 28 19:01:43 NetworkManager[7794]: <info>  [1766948503.7821] manager: (enp2s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Dec 28 19:01:43 systemd[1]: Started NetworkManager.service - Network Manager.
Dec 28 19:01:43 NetworkManager[7794]: <info>  [1766948503.7862] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Dec 28 19:01:43 NetworkManager[7794]: <info>  [1766948503.8047] modem-manager: ModemManager available
Dec 28 19:01:43 NetworkManager[7794]: <info>  [1766948503.8049] device (lo): state change: disconnected -> prepare (reason 'none', managed-type: 'external')
Dec 28 19:01:43 NetworkManager[7794]: <info>  [1766948503.8052] device (lo): state change: prepare -> config (reason 'none', managed-type: 'external')
Dec 28 19:01:43 NetworkManager[7794]: <info>  [1766948503.8053] device (lo): state change: config -> ip-config (reason 'none', managed-type: 'external')
Dec 28 19:01:43 NetworkManager[7794]: <info>  [1766948503.8055] device (lo): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')
Dec 28 19:01:43 NetworkManager[7794]: <info>  [1766948503.8138] device (lo): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
Dec 28 19:01:43 NetworkManager[7794]: <info>  [1766948503.8142] device (lo): state change: secondaries -> activated (reason 'none', managed-type: 'external')
Dec 28 19:01:43 NetworkManager[7794]: <info>  [1766948503.8151] device (lo): Activation: successful, device activated.
Dec 28 19:01:43 NetworkManager[7794]: <info>  [1766948503.8157] manager: startup complete
Dec 28 19:01:43 NetworkManager[7794]: <info>  [1766948503.8755] agent-manager: agent[d1d40de98b44b8f4,:1.58/org.freedesktop.nm-applet/1000]: agent registered
2

(one last report; size overrun for the previous post)

report_nmcli_device_status.txt :

root@ubuntu-mate:/home/ubuntu-mate# nmcli device status

DEVICE  TYPE      STATE                   CONNECTION 
lo      loopback  connected (externally)  lo         
enp2s0  ethernet  unmanaged               --         


root@ubuntu-mate:/home/ubuntu-mate# nmcli connection show

NAME  UUID                                  TYPE      DEVICE 
lo    7ddaa5f4-b4fe-43e3-8169-3bcb32bf01f7  loopback  lo     


root@ubuntu-mate:/home/ubuntu-mate# nmcli device enp2s0 status

GENERAL.DEVICE:                         enp2s0
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         00:26:18:8A:B5:7A
GENERAL.MTU:                            1500
GENERAL.STATE:                          10 (unmanaged)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
WIRED-PROPERTIES.CARRIER:               on
IP4.ADDRESS[1]:                         192.168.0.10/24
IP4.GATEWAY:                            192.168.0.1
IP4.ROUTE[1]:                           dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000
IP4.ROUTE[2]:                           dst = 0.0.0.0/0, nh = 192.168.0.1, mt = 1002
IP4.ROUTE[3]:                           dst = 192.168.0.0/24, nh = 0.0.0.0, mt = 1002
IP6.ADDRESS[1]:                         fd00:8494:8c30:fac2:da0d:eec4:2535:2431/64
IP6.ADDRESS[2]:                         fe80::9c6f:a53b:b4a3:d015/64
IP6.GATEWAY:                            --
IP6.ROUTE[1]:                           dst = fe80::/64, nh = ::, mt = 256
IP6.ROUTE[2]:                           dst = fd00:8494:8c30:fac2::/64, nh = ::, mt = 1002
IP6.ROUTE[3]:                           dst = fc00::/7, nh = fe80::8694:8cff:fe30:fac2, mt = 1002
IP6.ROUTE[4]:                           dst = fd00:8494:8c30:fac2::/64, nh = ::, mt = 256
3

Your pasted details contain a 6.17 kernel? where the current dailies have had 6.18 awhile now, eg. http://cdimage.ubuntu.com/ubuntu-mate/daily-live/20251228/ (2025-12-28) is much newer than your mentioned ISO from more than a month ago.

Please try a recent build, don't keep re-trying ancient dailies.

2 Likes
4

I don't have unlimited downloads.

I am trying to do maximum coverage with what I have before I make another jump for a more recent daily.

Given that, is there any advice available from anyone?

5

You're aware and take advantage of the zsync too I hope...

eg. I run a script to update my ISO, it'll include the commands

wget http://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/resolute-desktop-amd64.iso.zsync
zsync -u http://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/resolute-desktop-amd64.iso  resolute-desktop-amd64.iso.zsync

ie. it'll download the .zsync file fully (~8.2MB currently) and then use that to update my current ISO by downloading the changed sections of it.

I actually also wget the manifest as well; and for the first download of the cycle I start with the questing (or a prior ISO) too that I've copied and change the name to the reflect new codename, so I'm not even downloading the whole file even that first ISO download for a development cycle.

I just did a check; if you start with a 25.10 ISO you'll start the download with 35.4% complete; with only CPU & local disk used in that calculation (and small zsync file I mentioned earlier)... but if you start with your newer 20251119 ISO you'll have far less to download than the 20251007 ISO used in my 35.4% [starting point] comparison I'd bet.

Later addition: A zsync tutorial was added to this site; refer Ubuntu MATE daily iso painless update script

3 Likes
6

Thank you, Chris! That's amazing! I did NOT know what zsync was all about. I will definitely look at that today.

That tip is very much appreciated!

7

Well, Chris, I was hoping that would work for me, but it seems zsync didn't want to work with me! :frowning:

Here is the session log. Maybe you could help clarify what happened and, if anything, what I did wrong.


root@OasisMega1:/DB001_F3/Distros__Local # wget http://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/resolute-desktop-amd64.iso.zsync

--2025-12-29 13:17:35--  http://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/resolute-desktop-amd64.iso.zsync
Resolving cdimage.ubuntu.com (cdimage.ubuntu.com)... 91.189.91.124, 185.125.190.37, 2620:2d:4000:1::17, ...
Connecting to cdimage.ubuntu.com (cdimage.ubuntu.com)|91.189.91.124|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8599849 (8.2M) [application/x-iso9660-image]
Saving to: ‘resolute-desktop-amd64.iso.zsync.1’

resolute-desktop-amd64.iso.zsync.1  100%[================================================================>]   8.20M  2.84MB/s    in 2.9s    

2025-12-29 13:17:38 (2.84 MB/s) - ‘resolute-desktop-amd64.iso.zsync.1’ saved [8599849/8599849]

root@OasisMega1:/DB001_F3/Distros__Local # sync

root@OasisMega1:/DB001_F3/Distros__Local # zsync -u http://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/resolute-desktop-amd64.iso  resolute-desktop-amd64.iso.zsync
reading seed file resolute-desktop-amd64.iso: *****************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************
Read resolute-desktop-amd64.iso. Target 44.8% complete.      ***************************************
downloading from http://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/resolute-desktop-amd64.iso:
########------------ 44.8%cdimage.ubuntu.com: No such file or directory
########------------ 44.8% 0.0 kBps aborted    

failed to retrieve from resolute-desktop-amd64.iso
Aborting, download available in resolute-desktop-amd64.iso.part
verifying download...root@OasisMega1:/DB001_F3/Distros__Local # ls -ltr *.iso*
-rw-rw-r-- 1 ericthered ericthered 4196413440 May 10  2024 ubuntu-mate-24.04-desktop-amd64.iso
-rw-rw-r-- 1 ericthered ericthered 3733731328 Jun 15  2024 ubuntu-mate-22.04.4-desktop-amd64.iso
-rw-rw-r-- 2 ericthered ericthered 3861516288 Nov 23 12:25 UbuntuMATE__26.04_LTS__2025-11-19__resolute-desktop-amd64.iso
-rw-rw-r-- 2 ericthered ericthered 3861516288 Nov 23 12:25 resolute-desktop-amd64.iso
-rw-rw-r-- 1 ericthered ericthered 6465673216 Dec 13 20:28 UbuntuDesktop__26.04_LTS__2025-12-11__resolute-desktop-amd64.iso
-rw-rw-r-- 1 ericthered ericthered 5338458112 Dec 26 15:51 UbuntuXubuntu__26.04_LTS__2025-12-25__resolute-desktop-amd64.iso
-rw------- 1 root       root       4402958336 Dec 29 14:16 resolute-desktop-amd64.iso.part
root@OasisMega1:/DB001_F3/Distros__Local #
8

I'll suggest trying that command again, Canonical infrastructure does timeout now & again giving errors that can annoy us.

A copy/paste of your command worked perfectly here

guiverc@d7050-next:/de2900/ubuntu_mate_64$   zsync -u http://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/resolute-desktop-amd64.iso  resolute-desktop-amd64.iso.zsync
reading seed file resolute-desktop-amd64.iso: *************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************Read resolute-desktop-amd64.iso. Target 100.0% complete.      ********
verifying download...checksum matches OK
used 4403007488 local, fetched 0
2 Likes
9

Well, Chris, I've tried again. What I find strange is that it failed again but, more importantly, it failed again at *exactly 44.8%, just like the last time! I don't think it is a memory issue, because I have plenty of SWAP available:

root@OasisMega1:/DB001_F3/Distros__Local # swapon
NAME       TYPE        SIZE   USED PRIO
/dev/sda2  partition     2G 276.7M   99
/dev/sdb11 partition 996.2M   268M   99
/dev/sdb10 partition 996.2M 270.1M   99
/dev/sdb2  partition  1024M     0B   50
/dev/sdb5  partition     6G     0B    1
root@OasisMega1:/DB001_F3/Distros__Local #

My November ISO was just under 4 Gigs:

-rw-rw-r-- 2 ericthered ericthered 3861516288 Nov 23 12:25 UbuntuMATE__26.04_LTS__2025-11-19__resolute-desktop-amd64.iso

The remnants from the failed process reached about 4.3 Gigs:

-rw------- 1 root       root       4402958336 Dec 29 22:32 resolute-desktop-amd64.iso.part

I reviewed the command options for zsync, but I didn't see anything that would allow resume from last point of failure (HINT: enhancement request)!

My physical location is Ottawa, Canada. Is there an alternate server where I could get that download to minimize any possible network glitches that could be causing the failure?

As you can see, for critical tasks, I use root, so there is not reason to suspect privilege issues.

How long is the process supposed to run for? It seemed to run for about 45 to 50 minutes before "crash".

Any ideas on how to circumvent the problem?

Tomorrow, I will try again while running top to monitor the RAM and SWAP usage live. I'll see whether that reveals any condition that it is hitting on.

10

Your file-system is one without limit isn't it??

eg. fat32 has a limit of around 4GB, and thus its impossible to grow a file larger, which can cause unclear error messages such as lack of disk space etc (even though disk space may still exist; no further extents being possible for that file being the problem).

I'm not a great person to say how long a zsync should take, I'm an aussie with slow internet (by world standards) & I just start a script in a small window & tend to ignore it until much later, so 2 mins or 22 mins would feel the same to me.

(FYI: the terminal I'd run a zsync on is visible underneath this window, but only 3 bottom lines show... I'd just check now & again to see if it's back at $PS1 or prompt waiting command, then scroll up & view the output when I next changed task).

When it fails, only the last downloaded block will be lost, it'll detect all prior downloaded sections will pre-exist & thus won't be downloaded, so you'll usually only lose 2-10MB of download on a fail (ie. block size). ie. when you next try I'd expect it to start at 44.8% (or very close; eg. 44.7%). If it isn't doing that, you've another clue probably that it's local storage.

1 Like
11

Well, I've been working on the drive where I intended to keep the file, which is /DB001_F3, as seen below, but it has more space than the expected "final" image size. I can't imagine why it would need too much more space than that, but it is possible. AND ... the *.part file is still there, so releasing that would give me another 4 Gigs at least. :slight_smile:

So ... no "restart at last fail" point option. Correct?

Tomorrow, I will swap to a location on my ROOT partition, and see how that pans out.

	Filesystem      Size  Used Avail Use% Mounted on
	/dev/sdb3       192G   78G  104G  43% /
	/dev/sdb7       289G  266G  7.7G  98% /DB001_F2
	/dev/sdb8       289G  266G  7.7G  98% /DB001_F3
	/dev/sdb9       289G  249G   25G  91% /DB001_F4
	/dev/sdb12      192G  163G   19G  90% /DB001_F5
	/dev/sdb13      192G  166G   17G  92% /DB001_F6
	/dev/sdb14      288G  259G   15G  95% /DB001_F7
	/dev/sdb4        92G   22G   66G  25% /DB001_F8
12

There is no need, it scans any .part files and calculates from them what you already have, and then downloads what is required, ie. the delta or difference, so a complete file can be created/written to your actual file-system.

From such a tiny amount of free space, I'd suspect your issue is lack of disk space... if its not file-system, as you didn't give fs details that I saw (eg. ext4, btrfs etc)...

It has no limit of .part files you can have, ie. prior re-tries, but I forget what it does once it has a good download, and if it uses the existing .part that it calculated had the most OR creates a new file copying data from that (ie. .part will be untouched; until complete then its erased; more space required during operation with clean on completion); or overwrites that file changing/completing it. I do know I've ended up with many part files which may mean it needs sufficient space for full download, even if only a small % is actually downloaded; but the many .part files I recall may have been the result of something I did; sorry I forget specifics.

I've used zsync for so long, I've forgotten whatever I learnt when I explored it when I first discovered it, and no mostly recognize what problems I can have (lack of disk space - I correct that as I always want double-digit GB free on my LAN storage I download to) or network issues.

2 Likes
13

Well, I tried using my system disk as the workspace (over 100Gigs free) and that didn't work either.

I guess I won't be wasting my time with zsync until I have more time to figure it out.

This is the log of my latest attempt:

root@OasisMega1:~/00__HandOff/zsync__Workspace # wget http://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/resolute-desktop-amd64.iso.zsync
--2025-12-30 16:47:53--  http://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/resolute-desktop-amd64.iso.zsync
Resolving cdimage.ubuntu.com (cdimage.ubuntu.com)... 91.189.91.124, 185.125.190.37, 2620:2d:4000:1::17, ...
Connecting to cdimage.ubuntu.com (cdimage.ubuntu.com)|91.189.91.124|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8599881 (8.2M) [application/x-iso9660-image]
Saving to: ‘resolute-desktop-amd64.iso.zsync’

resolute-desktop-amd64.iso.zsync    100%[=================================================================>]   8.20M  1.87MB/s    in 4.4s    

2025-12-30 16:47:58 (1.87 MB/s) - ‘resolute-desktop-amd64.iso.zsync’ saved [8599881/8599881]

root@OasisMega1:~/00__HandOff/zsync__Workspace # sync
root@OasisMega1:~/00__HandOff/zsync__Workspace # ls -l
total 5712068
drwxr-xr-x 2 root       root             4096 Dec 30 16:17 HOLD
-rw-r--r-- 1 root       root          8599881 Dec 29 22:14 k
-rw-rw-r-- 1 ericthered ericthered 3861516288 Nov 23 12:25 resolute-desktop-amd64.iso
-rw------- 1 root       root       4403023872 Dec 30 15:33 resolute-desktop-amd64.iso.part
-rw-r--r-- 1 root       root          8599881 Dec 29 22:14 resolute-desktop-amd64.iso.zsync
-rwxr-x--- 1 root       root             3654 Dec 29 15:27 USER__ISO__BurnImageOnStick.sh
-rw-r--r-- 1 root       root              858 Dec 30 16:26 USER__ISO__Daily__Zsync.sh

root@OasisMega1:~/00__HandOff/zsync__Workspace # rm -f resolute-desktop-amd64.iso.zsync

root@OasisMega1:~/00__HandOff/zsync__Workspace # wget http://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/resolute-desktop-amd64.iso.zsync
--2025-12-30 17:00:22--  http://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/resolute-desktop-amd64.iso.zsync
Resolving cdimage.ubuntu.com (cdimage.ubuntu.com)... 185.125.190.37, 91.189.91.124, 2620:2d:4000:1::17, ...
Connecting to cdimage.ubuntu.com (cdimage.ubuntu.com)|185.125.190.37|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8599881 (8.2M) [application/x-iso9660-image]
Saving to: ‘resolute-desktop-amd64.iso.zsync’

resolute-desktop-amd64.iso.zsync    100%[=================================================================>]   8.20M  1.98MB/s    in 4.3s    

2025-12-30 17:00:27 (1.90 MB/s) - ‘resolute-desktop-amd64.iso.zsync’ saved [8599881/8599881]

root@OasisMega1:~/00__HandOff/zsync__Workspace # zsync -i resolute-desktop-amd64.iso -u http://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/resolute-desktop-amd64.iso resolute-desktop-amd64.iso.zsync
reading seed file resolute-desktop-amd64.iso: ********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************Read resolute-desktop-amd64.iso. Target 44.7% complete.      ************
reading seed file resolute-desktop-amd64.iso.part: *******************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************Read resolute-desktop-amd64.iso.part. Target 44.8% complete.      
downloading from http://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/resolute-desktop-amd64.iso:
########------------ 44.8%cdimage.ubuntu.com: No such file or directory
########------------ 44.8% 0.0 kBps aborted    

failed to retrieve from resolute-desktop-amd64.iso
Aborting, download available in resolute-desktop-amd64.iso.part
verifying download...root@OasisMega1:~/00__HandOff/zsync__Workspace #
14

My thinking has returned to what I said before, but you didn't provide file-system details.

If it's always at the same point; I'd firstly look at fs maximums, and that you're not trying to download a larger file than it can actually store; be it fs limit; extents limits etc...

  • Is the fs capable of storing files that large?
  • Do you have sufficient extents/innodes available; df -hi

If you have a file of the size you're trying to get on the partition already; I'd try and just cp that there and see if it works, or it aborts/abends and the error message hopefully provides a clue as to problem.

Always stopping at the same point implies something file-system related to me, if not something network (something between you & server that is not liking a specific bit pattern & thus doing something to cause problems).

1 Like
15

Both the original /DB001_F3, and the root (/) partitions, are ext4.

/dev/sdb3    ext4     DB001_F1   /                192G   46%   block:scsi:pci
/dev/sdb7    ext4     DB001_F2   /DB001_F2        289G   98%   block:scsi:pci
/dev/sdb8    ext4     DB001_F3   /DB001_F3        289G   98%   block:scsi:pci
/dev/sdb9    ext4     DB001_F4   /DB001_F4        289G   98%   block:scsi:pci
/dev/sdb12   ext4     DB001_F5   /DB001_F5        192G   90%   block:scsi:pci
/dev/sdb13   ext4     DB001_F6   /DB001_F6        192G   92%   block:scsi:pci
/dev/sdb14   ext4     DB001_F7   /DB001_F7        288G   95%   block:scsi:pci
/dev/sdb4    ext4     DB001_F8   /DB001_F8         92G   25%   block:scsi:pci
/dev/sdb2    swap     DB001_S1   [SWAP]             1G         block:scsi:pci
/dev/sdb10   swap     DB001_S2   [SWAP]             1G         block:scsi:pci
/dev/sdb11   swap     DB001_S3   [SWAP]             1G         block:scsi:pci
/dev/sdb5    swap     DB001_S4   [SWAP]             6G         block:scsi:pci
/dev/sda1    ext4     DB003_F1   /site/DB003_F1   456G    4%   block:scsi:pci
/dev/sda2    swap     DB003_S1   [SWAP]             2G         block:scsi:pci

As for the extents (df -hi), long way to go before I use those up:

Filesystem     Inodes IUsed IFree IUse% Mounted on
/dev/sdb3         13M  969K   12M    8% /
/dev/sdb7         19M  188K   19M    1% /DB001_F2
/dev/sdb8         19M  1.4K   19M    1% /DB001_F3
/dev/sdb9         19M  318K   19M    2% /DB001_F4
/dev/sdb12        13M  295K   12M    3% /DB001_F5
/dev/sdb13        13M   40K   13M    1% /DB001_F6
/dev/sdb14        19M   38K   19M    1% /DB001_F7
/dev/sdb4        5.9M   828  5.9M    1% /DB001_F8
/dev/sda1         29M  274K   29M    1% /site/DB003_F1
tmpfs            458K  1.5K  457K    1% /run
tmpfs            458K     1  458K    1% /dev/shm
tmpfs            458K     4  458K    1% /run/lock
tmpfs             92K   121   92K    1% /run/user/1000

As to whether the partition can handle a file of the expected size, I have a file in another directory on the original /DB001_F3 partition, which is almost 8 Gigs:

root@OasisMega1:/DB001_F3/ISO__BackupRepository_DVD # ls -l
total 7640424
-rw-r--r-- 1 root       root       7823783936 Jun 17  2019 BladeRunner2049.iso
drwxrwxr-x 2 ericthered ericthered       4096 Jun 17  2019 testMount
root@OasisMega1:/DB001_F3/ISO__BackupRepository_DVD #

The only other thing is whether the system has some "quota" mechanism which is not allowing even root from exceeding a given usage threshold. Is that possible?

I would try to fill the disk to see how far I could go, as root, but I'm afraid that could end up corrupting the filesystem. Do you think it is safe to try that?

Anyhow, it doesn't explain why it still crashed while doing it on on the ROOT partition, with almost 90Gigs free!!!

:frowning:

1 Like
16

The only line that 'grabs' me is

failed to retrieve from resolute-desktop-amd64.iso

whilst I don't have any failed zsync messages around to see what is normal (it's what I'd like), I'd probably look for clues in system logs (dmesg, journalctl) and hope for a clue; check in /var/crash/ too... but I've not seen that.

A quick search online and a cause for the message is using an older zsync app, but I have no idea about that, as that doesn't feel right with me, but what release are you using??

I also found Bug #2107337 “zsync 0.6.2-7: “failed to retrieve” if input file ...” : Bugs : zsync package : Ubuntu but whilst I do recall mention of that on IRC (or matrix) long ago, I remember none of the specifics about it; I've never experienced it.

My thoughts anyway (not sure they're worth 2c even)

Later edit: strikeout used as I do recall not using zsync awhile, and just using wget.. so maybe I have experienced it, but either way my memory is too vague with specifics...

2 Likes
17

I've downloaded the source for zsync from the development repository.

I am trying to understand why some forms of the command seem to be failing with error reporting a condition(s) which is not, per my perception, a true condition (see at bottom). :frowning:

When I run autoconf, I get the following errors:

root@OasisMega1:~/00__HandOff/Workspace__Zsync/zsync-master/c # autoconf
configure.ac:11: error: possibly undefined macro: AM_INIT_AUTOMAKE
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:12: error: possibly undefined macro: AM_MAINTAINER_MODE
configure.ac:52: error: possibly undefined macro: AM_WITH_DMALLOC
configure.ac:64: error: possibly undefined macro: AM_CONDITIONAL
root@OasisMega1:~/00__HandOff/Workspace__Zsync/zsync-master/c # ls -ltr

Do you know if those significant? or can I ignore those, since a configure script was generated? It seems they are, because the configure script itself fails:

root@OasisMega1:~/00__HandOff/Workspace__Zsync/zsync-master/c # ./configure
configure: error: cannot find required auxiliary files: config.guess config.sub
root@OasisMega1:~/00__HandOff/Workspace__Zsync/zsync-master/c # 


root@OasisMega1:~/00__HandOff/Workspace__Zsync # zsync -i /root/00__HandOff/Workspace__Zsync/resolute-desktop-amd64__OLDER.iso -u http://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/resolute-desktop-amd64.iso resolute-desktop-amd64.iso.zsync
open: No such file or directory
not using seed file /root/00__HandOff/Workspace__Zsync/resolute-desktop-amd64__OLDER.iso
Read /root/00__HandOff/Workspace__Zsync/resolute-desktop-amd64__OLDER.iso. Target 0.0% complete.      
reading seed file resolute-desktop-amd64.iso.part: ********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************^C
root@OasisMega1:~/00__HandOff/Workspace__Zsync #
18

FYI: I've got family local (normally interstate) so not spending that much time on my PC or at home, so I've not explored anything...

I've never tried to compile code, but I just re-run my zsync script in elevated mode here on my resolute install and didn't have issue

guiverc@d7050-next:/de2900/ubuntu_mate_64$   sudo su
[sudo: authenticate] Password: 
root@d7050-next:/de2900/ubuntu_mate_64#   bash zsync_resolute 
-rw------- 1 guiverc guiverc 4.2G Dec 29 04:15 resolute-desktop-amd64.iso.zs-old
-rw------- 1 guiverc guiverc 4.2G Dec 29 04:15 resolute-desktop-amd64.iso.old
-rw-rw-r-- 1 guiverc guiverc  68K Dec 29 14:07 resolute-desktop-amd64.manifest.old
-rw-rw-r-- 1 guiverc guiverc 8.3M Dec 29 14:15 resolute-desktop-amd64.zsync.old
-rw------- 1 guiverc guiverc 4.2G Dec 31 04:15 resolute-desktop-amd64.iso
-rw-rw-r-- 1 guiverc guiverc  68K Dec 31 14:08 resolute-desktop-amd64.manifest
-rw-rw-r-- 1 guiverc guiverc 8.3M Dec 31 14:15 resolute-desktop-amd64.iso.zsync
'resolute-desktop-amd64.iso' -> 'resolute-desktop-amd64.iso.old'
...
Read resolute-desktop-amd64.iso. Target 97.5% complete.      *********
downloading from http://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/resolute-desktop-amd64.iso:
#################### 100.0% 1888.6 kBps DONE      

verifying download...checksum matches OK
used 4253622272 local, fetched 107275418
-rw------- 1 guiverc guiverc 4.2G Dec 31 04:15 resolute-desktop-amd64.iso.zs-old
-rw------- 1 guiverc guiverc 4.2G Dec 31 04:15 resolute-desktop-amd64.iso.old
-rw-rw-r-- 1 guiverc guiverc  68K Dec 31 14:08 resolute-desktop-amd64.manifest.old
-rw-rw-r-- 1 guiverc guiverc 8.3M Dec 31 14:15 resolute-desktop-amd64.zsync.old
-rw------- 1 root    root    4.1G Jan  2 04:13 resolute-desktop-amd64.iso
-rw-r--r-- 1 root    root     68K Jan  2 14:07 resolute-desktop-amd64.manifest
-rw-r--r-- 1 root    root    8.2M Jan  2 14:14 resolute-desktop-amd64.iso.zsync

so I'm not having issues here, using my own $UID/$USER or as root. I don't currently have time for more, at least for now.

3 Likes
19

I really did not expect to hear back until Monday or later, Chris, so thank you for looking at that. Really much appreciated!

:slight_smile:

2 Likes