Hi,
i just want to share my experience after my OPNsense failed the second time and i could not restore my xml backup file.
Restoring the xml backup file, result always in a reboot loop caused by a disk failure, but disk is/was 100% good.
Several gray hairs later ;) and spending several hours investigating this issue:
Workaround found: I had to remove these line from the backup xml file. After that, restore was successful. Anyone any idea why this result in a disk failure?
<IDS version="1.0.5">
<rules/>
<userDefinedRules/>
<files>
<file uuid="5bdd53f6-0552-4a45-a981-78a674e70657">
<filename>opnsense.uncategorized.rules</filename>
<filter/>
<enabled>1</enabled>
</file>
<file uuid="837a812c-2eaa-491c-ab91-7f5240ddc4a6">
<filename>opnsense.test.rules</filename>
<filter/>
<enabled>1</enabled>
</file>
... 8< ....
<file uuid="f76ddd41-0d1c-4171-896b-e1c0ddd4a333">
<filename>abuse.ch.sslblacklist.rules</filename>
<filter/>
<enabled>1</enabled>
</file>
<file uuid="578e0b99-0a57-4c0f-865e-5d436a691c8c">
<filename>abuse.ch.feodotracker.rules</filename>
<filter/>
<enabled>1</enabled>
</file>
</files>
<fileTags/>
<general>
<enabled>1</enabled>
<ips>1</ips>
<promisc>0</promisc>
<interfaces>opt2,wan,opt3,opt4,lan,opt1</interfaces>
<homenet>192.168.0.0/16,10.0.0.0/8,172.16.0.0/12</homenet>
<defaultPacketSize/>
<UpdateCron>139165dc-593b-49c4-a468-03c9e8975c0e</UpdateCron>
<AlertLogrotate>D0</AlertLogrotate>
<AlertSaveLogs>4</AlertSaveLogs>
<MPMAlgo>ac</MPMAlgo>
<detect>
<Profile>medium</Profile>
<toclient_groups/>
<toserver_groups/>
</detect>
<syslog>0</syslog>
<syslog_eve>0</syslog_eve>
<LogPayload>0</LogPayload>
</general>
</IDS>
Another workaround was, restore ALL from original xml backup file and restore only section "opnsense additions" from a clean machine xml backup file. But some important sections were missing, so this is a bad workaround.
Hope this helps anyone else running into the same issue.
BR schtebo