Messages

1

20.7 Legacy Series / Re: Power fails do corrupt SD Cards and MSATA

« on: November 03, 2020, 04:29:07 pm »

The Nano image.
"dd gzcat OPNsense-20.7-OpenSSL-nano-amd64.img.bz2 | sudo dd of=/dev/disk2 bs=512”

2

20.7 Legacy Series / Re: Power fails do corrupt SD Cards and MSATA

« on: November 03, 2020, 04:20:10 pm »

Thanks to the suggestion of Michael Steinmann from PCengines.
He suggested to download the serial image,  boot it from the USB and install it to the mSATA.
Disconnect power and reconnect it do not create the problem as reported.

3

20.7 Legacy Series / Re: APU power fails do corrupt SD Cards and MSATA as well

« on: November 01, 2020, 02:19:39 pm »

update:
Tried with version 19.1 APU restarts properly after power fail.
Remark 19.1 runs on FreeBSD 11.2 p9
 

4

20.7 Legacy Series / Re: APU power fails do corrupt SD Cards and MSATA as well

« on: October 31, 2020, 01:13:57 pm »

You are right about the error message.
It seems to me this error message is misleading.
- I have tried with with 64GB SD Card and with 16GB mSATA just after the installation of OPNsense i pull the power plug, to simulate the power outage. No additional options installed. 

5

20.7 Legacy Series / Re: APU power fails do corrupt SD Cards and MSATA as well

« on: October 31, 2020, 09:26:54 am »

It looks to me its a FreeBSD issue. How can we inhibit caching? What do you mean with a paperwight OS?

6

20.7 Legacy Series / Re: APU power fails do corrupt SD Cards and MSATA as well

« on: October 30, 2020, 07:54:15 pm »

Problem occurs with APU2 as well

7

20.7 Legacy Series / Power fails do corrupt SD Cards and MSATA

« on: October 30, 2020, 08:51:20 am »

Hi,
I had a power fail with my APU3 running 20.7 Software. The Box did not come up.
The following errors are observed on the serial console.

CYLINDER GROUP 104: BAD MAGIC NUMBER
UNEXPECTED SOFT UPDATE INCONSISTENCY

REBUILD CYLINDER GROUP? yes

CYLINDER GROUP 105: BAD MAGIC NUMBER
UNEXPECTED SOFT UPDATE INCONSISTENCY

REBUILD CYLINDER GROUP? Yes


REBUILD CYLINDER GROUP? yes

** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
UNREF FILE  I=27  OWNER=root MODE=100644
SIZE=785656 MTIME=Oct 29 20:17 2020
RECONNECT? yes

NO lost+found DIRECTORY
CREATE? yes

CYLINDER GROUP 0: BAD MAGIC NUMBER
UNEXPECTED SOFT UPDATE INCONSISTENCY

REBUWARNING:  was not properly dismounted
ILD CYLINDER GROUP? yes

fsck_ufs: bad inode number 0 to ginode
pid 34421 (mktemp), uid 0 inumber 2 on : out of inodes

: create/symlink failed, no inodes free
mkdir: /tmp/.cdrom: No space left on device
mount_unionfs: /tmp/.cdrom: No such file or directory
mkdir: /tmp/.cdrom: No space left on device
mount_unionfs: /tmp/.cdrom: No such file or directory
mkdir: /tmp/.cdrom: No space left on device
mount_unionfs: /tmp/.cdrom: No such file or directory
mkdir: /tmp/.cdrom: No space left on device
mount_unionfs: /tmp/.cdrom: No such file or directory
mkdir: /tmp/.cdrom: No space left on device
mount_unionfs: /tmp/.cdrom: No such file or directory
mkdir: /tmp/.cdrom: No space left on device
mount_unionfs: /tmp/.cdrom: No such file or directory
mkdir: /tmp/.cdrom: No space left on device
mount_unionfs: /tmp/.cdrom: No such file or directory
PHP Warning:  file_put_contents(): Only 0 of 2086 bytes written, possibly out of free disk space in /usr/local/etc/rc.subr.d/recover on line 270
PHP Warning:  file_put_contents(): Only 0 of 820 bytes written, possibly out of free disk space in /usr/local/etc/rc.subr.d/recover on line 274
pwd_mkdb: /etc/pwd.db.tmp: No space left on device
pwd_mkdb: /etc/pwd.db.tmp: No space left on device
Setting hostuuid: e5a54693-1a22-11eb-83e7-000db957347c.
Setting hostid: 0x8878688a.
Configuring vt: blanktime.
pid 26310 (mktemp), uid 0 inumber 2 on : out of inodes

: create/symlink failed, no inodes free
mkdir: /var/etc: No space left on device
mkdir: /var/lib: No space left on device
chown: /var/lib/php/sessions: No such file or directory
chmod: /var/lib/php/sessions: No such file or directory
eval: cannot create /var/run/dmesg.boot: No space left on device
/usr/local/etc/rc.subr.d/crashdump: cannot create /tmp/ddb.conf: No space left on device
Configuring crash dump device: /dev/null
usage: ddb capture [-M core] [-N system] print
       ddb capture [-M core] [-N system] status
       ddb script scriptname
       ddb script scriptname=script
       ddb scripts
       ddb unscript scriptname
       ddb pathname
.ldconfig: mkstemp(/var/run/ld-elf.so.hints.227C1m): No space left on device
ELF ldconfig path: /lib /usr/lib /usr/local/lib /usr/local/lib/ipsec /usr/local/lib/perl5/5.30/mach/CORE
32-bit compatibility ldconfig path:


First I upgraded the APU3 to the latest BIOS. Still the same.
Booting from MSATA or SD Card -> same symptoms

This just happens with Power Loss. Its reproduceable.
Thanks for your hints
Jakob

8

General Discussion / Re: Wake On Lan from GUI

« on: August 14, 2020, 08:44:26 am »

Hi, thanks for your posting. In My case Servers do not wake up by the CRON entry. Manually clicking in the dashboard to wake it up is working. Any tips how i can debug it? Below my action_wol file

cat actions_wol.conf
[wake]
command:/usr/local/bin/wol -i
parameters: %s %s
type:script
description:Wake on LAN


root@OPNs:~ # service configd restart
Stopping configd...done
Starting configd.

9

Development and Code Review / CRON entry for WOL

« on: August 10, 2020, 12:03:21 pm »

Hi, would somebody help me to create a entry which sends a WOL packet via Cron to a device on my LAN.
Probably I just need to know where the WOL???.php ist located. Then I could call it trough Cron, would this work?
Thank you Jakob

10

20.7 Legacy Series / Re: Zerotier stops intermittend (unstable) (20.1.7)

« on: June 07, 2020, 05:29:57 pm »

Thank you. I have tried this no change. Zerotier still dies after some hours. Trying to bring it up trough the Web Interface is not possible.

11

20.7 Legacy Series / Re: Zerotier stops intermitend working (20.1.7)

« on: June 02, 2020, 08:55:35 am »

If I go to System:Diagnostics:Activity I see WCPU 100%

12

20.7 Legacy Series / Zerotier stops intermittend (unstable) (20.1.7)

« on: June 02, 2020, 08:52:56 am »

Hi,
Zerotier seems to stop after a while (30min - 2h) In the Dashbord the Icon indcates red. Under VPN Zerotier the green "arrow flag" is on.  under Networks I get unable to retrieve network info.  Sometime I can restart zerotier via the shell "zerotier-one". Sometime "zerotier-one" just hangs. Checking via myzerotier shows that the OPNsense is not connectet to zerotier.
What can I do helping to get better info to find the root cause?
Jakob 

13

20.1 Legacy Series / Re: Update to 20.1.7 killed zerotier interface

« on: June 01, 2020, 11:32:39 pm »

I do also have stability issues with ZT. I did not use it before on OPNsense

14

German - Deutsch / Re: Kriege Portforwarding /NAT nicht hin

« on: May 30, 2020, 04:06:35 pm »

Wie erstelle ich automatisch eine Regel? Im Menue finde ich nichts, habe ich etwas übersehen. Auf jeden Fall vielen Dank für deine Tips. Jakob

15

German - Deutsch / Re: Kriege Portforwarding /NAT nicht hin

« on: May 30, 2020, 10:53:23 am »

Das mit dem Quellenport und TCP hatte ich umgehend nach deiner Empfehlung geändert. (Entschuldige, dass ich es nicht erwähnt hatte.) Leider hat es nichts gebracht. Danke Jakob