OPNsense Forum
English Forums => 23.7 Legacy Series => Topic started by: eszett on August 26, 2023, 03:09:11 pm
-
Hello Community,
as already described in the topic I can not update to 23.7.2. Short description what happened.
I have pushed the update of the repo via the GUi. There is always a window with the new features. The message and update I canceled to pull a backup of the config before. This also worked. A short time later the machine was no longer accessible. After a reboot, I can no longer perform updates. It comes the error message "The release type "opnsense" is not available on this repository."
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 23.7.1_3 at Sat Aug 26 12:03:00 CEST 2023
Fetching changelog information, please wait... done
self: No packages available to install matching 'opnsense'
***DONE***
But according to ChangeLog 23.7.2 should be installed. In the shell I can't do anything via pkg update or opnsense-update -f either.
Dear community, I need some support or help.
Thanks!
It is a phy. machine. Currently it is running, but on state 23.7.1
Addendum: Apparently my pkg database is shot. I can't even reinstall nano. A pkg update and upgrade is executed without a message. Also I can't display the installed packages.
-
What's the output for these commands ?
df -hopnsense-update -u
Also need to see the health check, either from the Firmware section or press 12 in the console and answer h to the yes/no prompt
-
Thx for help :)
root@opnsense:/ # df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/gpt/rootfs 454G 2.6G 415G 1% /
devfs 1.0K 1.0K 0B 100% /dev
/dev/gpt/efifs 256M 1.7M 254M 1% /boot/efi
devfs 1.0K 1.0K 0B 100% /var/dhcpd/dev
devfs 1.0K 1.0K 0B 100% /var/unbound/dev
/usr/local/lib/python3.9 454G 2.6G 415G 1% /var/unbound/usr/local/lib/python3.9
root@opnsense:/ # opnsense-update -u
No known packages set to fetch was specified.
root@opnsense:/ #
this is option 12 output
Enter an option: 12
Fetching change log information, please wait... done
This will automatically fetch all available updates and apply them.
Proceed with this action? [y/N]: y
Nothing to do.
Starting web GUI...done.
Generating RRD graphs...done.
*
*
*
-
You need to answer h to the yes/no question
-
more ouput does not come
Fetching change log information, please wait... done
This will automatically fetch all available updates and apply them.
Proceed with this action? [y/N]: y
Nothing to do.
Starting web GUI...done.
Generating RRD graphs...done.
*** opnsense.myhome.lan: OPNsense 23.7.1_3 ***
LAN (re0) -> v4: 10.0.16.254/24
OPT1 (ue0) -> v4: 192.168.2.254/24
WAN (igc0) -> v4/DHCP4: 9x.xx.xx.xx/22
WG1 (wg1) -> v4: 10.11.0.1/24
HTTPS: SHA256 18 55 ................................
SSH: SHA256 Bqk................................ (ECDSA)
SSH: SHA256 aUkUp............................ (ED25519)
SSH: SHA256 qoD3by............................(RSA)
0) Logout 7) Ping host
1) Assign interfaces 8) Shell
2) Set interface IP address 9) pfTop
3) Reset the root password 10) Firewall log
4) Reset to factory defaults 11) Reload all services
5) Power off system 12) Update from console
6) Reboot system 13) Restore a backup
Enter an option:
Proceed with this action? [y/N]: h
>>> Check installed kernel version
Version 23.7.1 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 23.7.1 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense
>>> Check installed plugins
No plugins found.
>>> Check locked packages
No locks found.
>>> Check for missing package dependencies
>>> Check for missing or altered package files
>>> Check for core packages consistency
Core package "opnsense" not known to package database.
Press any key to return to menu.
-
Nevermind
-
Proceed with this action? [y/N]: h
>>> Check installed kernel version
Version 23.7.1 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 23.7.1 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense
>>> Check installed plugins
No plugins found.
>>> Check locked packages
No locks found.
>>> Check for missing package dependencies
>>> Check for missing or altered package files
>>> Check for core packages consistency
Core package "opnsense" not known to package database.
Press any key to return to menu.
Looks clean, try this now and paste the output please:
opnsense-update -fur 23.7.2
-
unfortunately without success
root@opnsense:/ # opnsense-update -fur 23.7.2
Fetching packages-23.7.2-amd64.tar: ..[fetch: https://pkg.opnsense.org/FreeBSD:13:amd64/23.7/sets/packages-23.7.2-amd64.tar.sig: Not Found] failed, no signature found
the same commands with 23.7.1 worked and reboot
-
Try the -fiur switch instead.
-i will not verify the packages as there's something broken there, but if it completes then any missing bits should be repaired including signature verification for 23.7.3+
If you have a way of checking the output as the machine boots see if there's any message reporting the filesystem dirty, and check the smart data as well - should the hdd be dying.
-
Why are we forcing (-f) insecure (-i) major (-u) updates on users? Let's try to stay away from opnsense-update -u here... -r doesn't even work without a release number ;)
If the package database is damaged the only clean solution is to run a full bootstrap:
# opnsense-bootstrap
It will reinstall everything (avoiding a major upgrade wherever it may have taken the user) and keep all settings.
Cheers,
Franco
-
Thanks Franco, forgot about bootstrap (never had to use it either)
-
Why are we forcing (-f) insecure (-i) major (-u) updates on users? Let's try to stay away from opnsense-update -u here... -r doesn't even work without a release number ;)
If the package database is damaged the only clean solution is to run a full bootstrap:
# opnsense-bootstrap
It will reinstall everything (avoiding a major upgrade wherever it may have taken the user) and keep all settings.
Cheers,
Franco
unfortunately does not work
root@opnsense:/ # opnsense-update -fiur 23.7.2
Fetching packages-23.7.2-amd64.tar: ..[fetch: https://pkg.opnsense.org/FreeBSD:13:amd64/23.7/sets/packages-23.7.2-amd64.tar: Not Found] failed, no update found
the file does not exist
https://pkg.opnsense.org/FreeBSD:13:amd64/23.7/sets/
can i run the bootstrap via ssh or do i need vga
-
> unfortunately does not work
Precisely ;)
Cheers,
Franco
-
can i run the bootstrap via ssh or do i need vga
ssh should be fine
-
Brief feedback on my problem. The opnsense-bootstrap command made the firewall unusable and I had to reinstall the system completely. The old installation gave error messages that the filesystem is corrupt.
I see it sportily and could immediately test my backup. Unfortunately, the packages have to be reinstalled. Is there a way to check the package dependency?
Thanks that helped me!
-
After importing the config check or updates, wait for it to finish and reboot. The existing plugins will be reinstalled and after reboot it should all come up as expected.
You still need to check the smart data on the ssd, it's unclear if you only had a corrupted FS or those are signs of the SSD being on its last leg.
-
Thank you for taking up the topic again. I have installed the smartmontools via pkg and briefly checked the SSD. The state is defined as PASSED. To understand the whole output. I can not find any error with the SSD.
I installed the packages manually via the package manager. Everything works again. Even Wireguard worked again right away.
smartctl -t short -a /dev/nvme0
smartctl 7.4 2023-08-01 r5530 [FreeBSD 13.2-RELEASE-p2 amd64] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: Fanxiang S500PRO 512GB
Serial Number: FXS500PRO224690021
Firmware Version: SN09273
PCI Vendor/Subsystem ID: 0x1e4b
IEEE OUI Identifier: 0x000000
Total NVM Capacity: 512,110,190,592 [512 GB]
Unallocated NVM Capacity: 0
Controller ID: 0
NVMe Version: 1.4
Number of Namespaces: 1
Namespace 1 Size/Capacity: 512,110,190,592 [512 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 000000 0000000001
Local Time is: Mon Aug 28 10:15:54 2023 CEST
Firmware Updates (0x14): 2 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Log Page Attributes (0x02): Cmd_Eff_Lg
Maximum Data Transfer Size: 512 Pages
Warning Comp. Temp. Threshold: 90 Celsius
Critical Comp. Temp. Threshold: 95 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 6.50W - - 0 0 0 0 0 0
1 + 5.80W - - 1 1 1 1 0 0
2 + 3.60W - - 2 2 2 2 0 0
3 - 0.7460W - - 3 3 3 3 5000 10000
4 - 0.7260W - - 4 4 4 4 8000 45000
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 41 Celsius
Available Spare: 100%
Available Spare Threshold: 1%
Percentage Used: 1%
Data Units Read: 104,470 [53.4 GB]
Data Units Written: 17,771,382 [9.09 TB]
Host Read Commands: 2,640,907
Host Write Commands: 82,768,711
Controller Busy Time: 381
Power Cycles: 25
Power On Hours: 5,265
Unsafe Shutdowns: 19
Media and Data Integrity Errors: 6
Error Information Log Entries: 116
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 41 Celsius
Temperature Sensor 2: 46 Celsius
Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged
Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
No Self-tests Logged
Self-test has begun
Use smartctl -X to abort test
-
Thank you for taking up the topic again. I have installed the smartmontools via pkg and briefly checked the SSD. The state is defined as PASSED. To understand the whole output. I can not find any error with the SSD.
I installed the packages manually via the package manager. Everything works again. Even Wireguard worked again right away.
smartctl -t short -a /dev/nvme0
smartctl 7.4 2023-08-01 r5530 [FreeBSD 13.2-RELEASE-p2 amd64] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: Fanxiang S500PRO 512GB
Serial Number: FXS500PRO224690021
Firmware Version: SN09273
PCI Vendor/Subsystem ID: 0x1e4b
IEEE OUI Identifier: 0x000000
Total NVM Capacity: 512,110,190,592 [512 GB]
Unallocated NVM Capacity: 0
Controller ID: 0
NVMe Version: 1.4
Number of Namespaces: 1
Namespace 1 Size/Capacity: 512,110,190,592 [512 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 000000 0000000001
Local Time is: Mon Aug 28 10:15:54 2023 CEST
Firmware Updates (0x14): 2 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Log Page Attributes (0x02): Cmd_Eff_Lg
Maximum Data Transfer Size: 512 Pages
Warning Comp. Temp. Threshold: 90 Celsius
Critical Comp. Temp. Threshold: 95 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 6.50W - - 0 0 0 0 0 0
1 + 5.80W - - 1 1 1 1 0 0
2 + 3.60W - - 2 2 2 2 0 0
3 - 0.7460W - - 3 3 3 3 5000 10000
4 - 0.7260W - - 4 4 4 4 8000 45000
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 41 Celsius
Available Spare: 100%
Available Spare Threshold: 1%
Percentage Used: 1%
Data Units Read: 104,470 [53.4 GB]
Data Units Written: 17,771,382 [9.09 TB]
Host Read Commands: 2,640,907
Host Write Commands: 82,768,711
Controller Busy Time: 381
Power Cycles: 25
Power On Hours: 5,265
Unsafe Shutdowns: 19
Media and Data Integrity Errors: 6
Error Information Log Entries: 116
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 41 Celsius
Temperature Sensor 2: 46 Celsius
Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged
Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
No Self-tests Logged
Self-test has begun
Use smartctl -X to abort test
I don't see any tests run, just that SMART hasn't raised any alerts. You should run a long test to double check.