Trying to update the packet list (opkg update) using Luci results in
The *opkg update* command failed with code 1.,
On the console:
Collected errors:
* opkg_download: Failed to download https://downloads.openwrt.org/releases/24.10.0/targets/mediatek/filogic/packages/Packages.gz, wget returned 4.
* opkg_download: Check your network settings and connectivity.
* opkg_download: Failed to download https://downloads.openwrt.org/releases/24.10.0/packages/aarch64_cortex-a53/base/Packages.gz, wget returned 4.
* opkg_download: Check your network settings and connectivity.
* opkg_download: Failed to download https://downloads.openwrt.org/releases/24.10.0/targets/mediatek/filogic/kmods/6.6.73-1-d649d775435da5a8637f7a955a80d331/Packages.gz, wget returned 4.
* opkg_download: Check your network settings and connectivity.
* opkg_download: Failed to download https://downloads.openwrt.org/releases/24.10.0/packages/aarch64_cortex-a53/luci/Packages.gz, wget returned 4.
* opkg_download: Check your network settings and connectivity.
* opkg_download: Failed to download https://downloads.openwrt.org/releases/24.10.0/packages/aarch64_cortex-a53/packages/Packages.gz, wget returned 4.
* opkg_download: Check your network settings and connectivity.
* opkg_download: Failed to download https://downloads.openwrt.org/releases/24.10.0/packages/aarch64_cortex-a53/routing/Packages.gz, wget returned 4.
* opkg_download: Check your network settings and connectivity.
* opkg_download: Failed to download https://downloads.openwrt.org/releases/24.10.0/packages/aarch64_cortex-a53/telephony/Packages.gz, wget returned 4.
* opkg_download: Check your network settings and connectivity.
downloads.openwrt.org is pingable and the Packages.gz can be downloaded on my PC via browser.
@frollic : I can neither delete nor disable wan6 @Dante : The ping works from the router
After I have found this FAQ, I realized that /tmp is 100% full. Of course, /tmp can be cleared by a reboot but I would like to avoid that. I have deleted system.log.old (131095 bytes) but that was obviously not enough.
The most hungry storage consumer is adguardhome's query log (/tmp/lib/adguardhome/data/querylog.json). I have reduced it's size by temporariy skipping the logging of queries of intranet addresses. But even with the reduced number of log entries the daily growth in my small installation (2 PCs, 3 Proxmox nodes with some small servers and usually 2 mobile devices) is > 90.000 entries / 25 MB.
My next step is the installation of an internal NVME SSD and moving /tmp to it.
unfortunately I tried to move /tmp before I had read your post , the result was a router in coma. Access was possible only via ssh and IP address.
But I found a way to move at least the /tmp/lib/adguardhome directory to the SSD. Here is the solution:
Moving AdGuard Home Data to an NVMe SSD on OpenWRT
I encountered issues when trying to mount an NVMe SSD via /etc/fstab on OpenWRT. The system did not recognize the mount entry, so I had to handle mounting through /etc/rc.local instead. Here’s how I successfully moved the /tmp/lib/adguardhome directory to the SSD:
1. Create a Btrfs Subvolume
First, ensure the SSD is formatted with Btrfs and create a subvolume for temporary data:
mkfs.btrfs -f /dev/nvme0n1
mount /dev/nvme0n1 /mnt/nvme
btrfs subvolume create /mnt/nvme/@temp
2. Modify /etc/rc.local for Persistent Mounting
Since OpenWRT seems to ignore /etc/fstab, I added the following lines to /etc/rc.local before exit 0:
mount /dev/nvme0n1 /mnt/nvme
mount -o subvol=@temp /dev/nvme0n1 /temp
ln -sfn /temp/lib/adguardhome /tmp/lib/adguardhome
3. Prepare the Directory Structure
Before rebooting, make sure the target directory exists:
mkdir -p /temp/lib/adguardhome
4. Reboot and Verify
Restart the router:
reboot
After rebooting, check if the mount and symlink work as expected:
mount | grep temp
ls -lah /tmp/lib/adguardhome
Key Findings:
/etc/fstab did not work for mounting the SSD at boot.
The alternative /etc/config/fstab might work with block-mount, but I didn't test it.
/etc/rc.local successfully mounts the SSD and links the directory.
/tmp/lib/adguardhome is now stored on the SSD, reducing RAM usage.
This solution should work for anyone who wants to move specific /tmp subdirectories to an SSD while keeping the rest of /tmp in RAM.
Let me know if you have improvements or a better approach!
You can configure the AdGuard Home work directory in the config. No need for linking anything in the rc.local. You can also compress the querylog out of the box.
, the result was a router in coma. Access was possible only via ssh and IP address.