Openwrt 23.05.4 attendedupgrade error on x86-64 system

I think it is a disk size related error. My system is using 1 GB USB flashdisk. Rootfs image backup file usually has a size of 988166208 bytes. I guess around 988000000 bytes is fine. Or maybe there's something else, i don't know.

{ "url": "https://sysupgrade.openwrt.org", "revision": "r24012-d8dd03c46f", "advanced_mode": "0", "sha256_unsigned": "", "branch": "23.05", "efi": null, "target": "x86/64", "version": "23.05.5", "packages": [ "adguardhome", "arp-scan", "arp-scan-database", "base-files", "bash", "bmon", "busybox", "ca-bundle", "collectd-mod-cpufreq", "collectd-mod-dhcpleases", "collectd-mod-sensors", "coreutils-dd", "coreutils-sort", "curl", "dnsmasq", "dropbear", "e2fsprogs", "firewall4", "fstools", "git", "git-gitweb", "git-http", "grep", "grub2-bios-setup", "htop", "iftop", "kernel", "kmod-8139too", "kmod-amazon-ena", "kmod-amd-xgbe", "kmod-bnx2", "kmod-button-hotplug", "kmod-crypto-rng", "kmod-e1000", "kmod-e1000e", "kmod-forcedeth", "kmod-fs-nfs", "kmod-fs-nfs-v3", "kmod-fs-nfs-v4", "kmod-fs-vfat", "kmod-igb", "kmod-igc", "kmod-ixgbe", "kmod-nft-offload", "kmod-r8169", "kmod-tcp-bbr", "kmod-tg3", "libc", "libgcc", "libustream-mbedtls", "lm-sensors", "lm-sensors-detect", "logd", "logger", "lsblk", "lscpu", "luci", "luci-app-attendedsysupgrade", "luci-app-firewall", "luci-app-opkg", "luci-app-statistics", "luci-base", "luci-light", "luci-mod-admin-full", "luci-mod-network", "luci-mod-status", "luci-mod-system", "luci-proto-ipv6", "luci-proto-ppp", "luci-theme-bootstrap", "mkf2fs", "mtd", "nano-full", "netifd", "nfs-utils", "nfs-utils-libs", "nftables-json", "node", "node-npm", "odhcp6c", "odhcpd-ipv6only", "openssh-keygen", "openssh-sftp-client", "openssh-sftp-server", "opkg", "partx-utils", "ppp", "ppp-mod-pppoe", "procd", "procd-seccomp", "procd-ujail", "resolveip", "rng-tools", "sshfs", "uci", "uclient-fetch", "urandom-seed", "urngd" ], "diff_packages": true, "filesystem": "ext4", "client": "luci/git-24.340.62040-d52505e" }

No source files or tests are named. Start by reproducing the attended upgrade request using the supplied x86/64, ext4, package list, and 1 GB disk details, then inspect the server response and logs; done means the failure's cause is identified and a verified fix or actionable diagnosis is available.