Unable to update from 23.1.11_2 to 23.7 (duckdb.IOException: IO Error)

[Elude4282]

Hello everyone,

I have a pretty much vanilla opnsense setup. Basic configuration, no plugins, a few dhch static lease. I try to update diligently.

I'm trying to install the last major release from 23.1.11_2 to 23.7, but I get an error. It also kind of broke Unbound DNS, I deactivated it and activated DNSmask for now.

But it looks like the Unbound database is blocking the update. Anything I can do instead of reinstalling everything?

I tried to updated through the GUI, ssh and the console, but I get the same error.

Thanks,

The error while updating:

Code Select Expand

***GOT REQUEST TO UPGRADE***
Currently running OPNsense 23.1.11_2 at Mon Nov 20 09:16:24 EST 2023
Fetching packages-23.7-amd64.tar: ......................................... done
Fetching base-23.7-amd64.txz: ......... done
Fetching kernel-23.7-amd64.txz: ...... done
Extracting packages-23.7-amd64.tar... done
Extracting base-23.7-amd64.txz... done
Extracting kernel-23.7-amd64.txz... done
Please reboot.
>>> Invoking upgrade script 'unbound-duckdb.py'
Traceback (most recent call last):
  File "/usr/local/etc/rc.syshook.d/upgrade/20-unbound-duckdb.py", line 39, in <module>
    db.connection.execute("EXPORT DATABASE '/var/cache/unbound.duckdb';")
duckdb.IOException: IO Error: Could not read from file "/var/unbound/data/unbound.duckdb": Input/output error
>>> Error in upgrade script '20-unbound-duckdb.py'
***DONE***

[cookiemonster]

IO error normally indicates a hardware problem. Disk dying?

[newsense]

Check free space first, you may have to delete a few logs first

[Elude4282]

Check free space first, you may have to delete a few logs first

I'm only at 36%, so I should have enough space(see attached picture)

[Elude4282]

IO error normally indicates a hardware problem. Disk dying?

There is always this possibility, but everything looks healthy.

[Elude4282]

Well, I fixed the issue.

In console mode, instead of selecting the option to upgrade, I went into the shell and did:

#opnsense-update -up
#opnsense-shell reboot

And the update worked. Not sure what was the issue, but everything works now.