SG-1000 filesystem corruption on update



  • Last Friday (2017-05-12) I wanted to update our SG-1000 box to the lastest version. The previous update had been done about a week ago. After starting the update with the web interface, I quickly got the message "System update failed". This didn't bother me much, since we I have seen this before and the update proceeds successfully in the background anyway. However, this time I got via mail the following message:

    There were error(s) loading the rules: /tmp/rules.debug:21: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [21]: table <bogonsv6>persist file "/etc/bogonsv6"</bogonsv6>

    Followed two minutes later by the standard notice "Upgrade is complete.  Rebooting in 10 seconds.". The firewall didn't come back though. Investigation with the console port turned up filesystem corruption, with lots of messages like "read-only filesystem, cannot delete x". Unfortunately I can't give you the exact messages, since I'm managing this system remote and the person on the console port didn't save them.

    We have restored the firewall now with the help of an SD-Card and restored the config, so everything seems to be working normally again (one curious note: The assignment of the WAN and LAN ports seems to have switched around when restored the config).

    Is an issue like this known already? Is there any way to prevent this on future upgrades?


  • Rebel Alliance Developer Netgate

    That isn't a general problem with current SG-1000 updates, but it's possible your SG-1000 caught a bad update on Friday. We've recently added some extra protection to the builder and upgrade code to prevent that sort of thing from happening, it's possible your previous update was from before that happened.

    If you were able to reimage the box and get back up and running then it probably is not a hardware issue. It should be safe to try updating it again.



  • Ok, that's good to know that there is some additional protection. I'll probably hold off further updates until the 2.4 final release though, since it's a right pain to restore it when you are 1000 km from the box :)


Log in to reply