Messages

Hello,
during upgrading my opnsense box via serial com1 (soekris, cfcard, nano), I lost internet connection.
System was at point Fetching base-16.7.7-i386.txz and stopped upgrading.
I rebooted the system via console and did upgrade again.
Fetching base-16.7.7-i386.txz.
Fetching base-16.7.7-i386.obsolete.
Fetching kernel-16.7.7-i386.txz.
Installing kernel-16.7.7-i386.txz.
Installing base-16.7.7-i386.txz.
Installing base-16.7.7-i386.obsolete.
System did an automated reboot, but now I get the following error:

Trying to mount root from ufs:/dev/ufs/OPNsense1 [rw,async,noatime]...
mountroot: waiting for device /dev/ufs/OPNsense1 ...
Mounting from ufs:/dev/ufs/OPNsense1 failed with error 19.

Loader variables:
  vfs.root.mountfrom=ufs:/dev/ufs/OPNsense1
  vfs.root.mountfrom.options=rw,async,noatime

Manual root filesystem specification:
  <fstype>:<device> [options]
      Mount <device> using filesystem <fstype>
      and with the specified (optional) option list.

    eg. ufs:/dev/da0s1a
        zfs:tank
        cd9660:/dev/acd0 ro
          (which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /)

  ?               List valid disk boot devices
  .               Yield 1 second (for background tasks)
  <empty line>    Abort manual input

mountroot>

Any hints to solve this issue.

Thank you.
Roro

Franco,
thanks for the support.
The messages are gone now.
Greetings.

and it driving crazy. >:(

Hi Franco,
i'm still getting the messages again.
Is it also possible to turn of:
tunefs: soft updates: (-n)                                 enabled
Greets

Recap:
after a few days of hard try and error.
Soekris net5501-70 serial.
Opnsense i386 cf-card.

Findings:
1. because I could not see much via serial (soekris 9600, opnsense 115200). fixed
2. the nanobsd boot menu. Here you can choose:
   1  OPNsense
   2  OPNsense

   F6 PXE
   Boot:  1

3. then the freebsd/opnsense logo will come, but it doesn't display well on serial output, so you miss the freebsd/opnsense menu with Multiuser, Singleuser etc.

4. then I had issues with VI and /etc/fstab. I choose to use EE to edit this file and I was able to add "# notrim".

5. Finally SUCCES. The trim messages are gone. Thanks to Franco's help.

root@opn01:~ # tunefs -p /dev/ad0s1a
tunefs: POSIX.1e ACLs: (-a)                                disabled
tunefs: NFSv4 ACLs: (-N)                                   disabled
tunefs: MAC multilabel: (-l)                               disabled
tunefs: soft updates: (-n)                                 enabled
tunefs: soft update journaling: (-j)                       disabled
tunefs: gjournal: (-J)                                     disabled
tunefs: trim: (-t)                                         disabled
tunefs: maximum blocks per file in a cylinder group: (-e)  512
tunefs: average file size: (-f)                            16384
tunefs: average number of files in a directory: (-s)       64
tunefs: minimum percentage of free space: (-m)             8%
tunefs: space to hold for metadata blocks: (-k)            1032
tunefs: optimization preference: (-o)                      time
tunefs: volume label: (-L)                                 OPNsense0

root@opn01:~ # tunefs -p /dev/ada0s1a
tunefs: POSIX.1e ACLs: (-a)                                disabled
tunefs: NFSv4 ACLs: (-N)                                   disabled
tunefs: MAC multilabel: (-l)                               disabled
tunefs: soft updates: (-n)                                 enabled
tunefs: soft update journaling: (-j)                       disabled
tunefs: gjournal: (-J)                                     disabled
tunefs: trim: (-t)                                         disabled
tunefs: maximum blocks per file in a cylinder group: (-e)  512
tunefs: average file size: (-f)                            16384
tunefs: average number of files in a directory: (-s)       64
tunefs: minimum percentage of free space: (-m)             8%
tunefs: space to hold for metadata blocks: (-k)            1032
tunefs: optimization preference: (-o)                      time
tunefs: volume label: (-L)                                 OPNsense0
root@opn01:~ #
root@opn01:~ #

The whole evening upgrading the opnsense cf i386 soekris box from version 15.x.x to 16.7.2 OpenSSL.
1  OPNsense
2  OPNsense

F6 PXE
Boot:  2

Took a long time but no errors at all.
As usuall I go from openssl to libressl and then the messages about:

(ada0:ata0:0:0:0): CAM status: ATA Status Error
etc.

appears again. After that I went to sleep.

Now I will go back to OpenSSL and see whats happening.

System is running now OPNsense 16.7.2 (i386/OpenSSL), but:

0) Logout                             7) Ping host
1) Assign Interfaces                  8) Shell
2) Set interface(s) IP address        9) pfTop
3) Reset the root password           10) Filter Logs
4) Reset to factory defaults         11) Restart web interface
5) Power off system                  12) Upgrade from console
6) Reboot system                     13) Restore a configuration

Enter an option: (ada0:ata0:0:0:0): DSM TRIM. ACB: 06 01 00 00 00 40 00 00 00 00
01 00
(ada0:ata0:0:0:0): CAM status: ATA Status Error
(ada0:ata0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
(ada0:ata0:0:0:0): RES: 51 04 20 3c 2f 74 74 00 00 01 00
(ada0:ata0:0:0:0): Retrying command

So I think the switch from OpenSSL to LibreSSL causes these messages in the system log.
Is this solvable in the installation or otherwise?

Greets.

Well I booted system with OPNsense1, I will update this slice and see whats happening next.
Fetching the update files now. Upgrade in progress:
Fetching libevent2-2.0.22_1.txz: 100%  254 KiB 260.0kB/s    00:01
Fetching libedit-3.1.20150325_1.txz: 100%  119 KiB 121.8kB/s    00:01
Fetching ldns-1.6.17_5.txz: 100%  379 KiB 388.3kB/s    00:01
Fetching jansson-2.7_1.txz: 100%   39 KiB  40.4kB/s    00:01
Fetching idnkit-1.0_5.txz: 100%  184 KiB 188.5kB/s    00:01
Fetching gmp-5.1.3_2.txz: 100%  474 KiB 484.9kB/s    00:01
Fetching gettext-runtime-0.19.6.txz: 100%  144 KiB 147.7kB/s    00:01
Fetching freetype2-2.6.2.txz: 100%  535 KiB 547.4kB/s    00:01
Fetching easy-rsa-3.0.1.txz: 100%   31 KiB  32.1kB/s    00:01
Fetching dnsmasq-2.75_1,1.txz: 100%  257 KiB 262.7kB/s    00:01
Fetching dhcp6-20080615_5.txz: 100%  104 KiB 106.2kB/s    00:01
Fetching curl-7.46.0_2.txz: 100%    1 MiB   1.5MB/s    00:01
Fetching choparp-20150613.txz: 100%    7 KiB   7.2kB/s    00:01
Fetching ca_root_nss-3.21.txz: 100%  330 KiB 337.7kB/s    00:01
Fetching bind910-9.10.3P2.txz: 100%    6 MiB   5.9MB/s    00:01
Fetching apinger-0.6.1_4.txz: 100%   32 KiB  33.0kB/s    00:01
Fetching libucl-0.7.3_1.txz: 100%   79 KiB  80.7kB/s    00:01
Checking integrity... done (0 conflicting)
[1/74] Upgrading openssl from 1.0.2_4 to 1.0.2_6...
[1/74] Extracting openssl-1.0.2_6:  62%

Franco,
don't know what happened but system is back to OPNsense 15.7.18_1-i386 and i had to assing nics and ips again.
I was trying with serial connection and I reset the soekris system with reset button.
I will build the system up again and see what happens.
Keep you informed.
Roro

Hi Franco,
i'm still strugling with this one.
What I do:
First reboot and start Opnsense with option 2.
I do:
# cat /etc/fstab
/dev/ufs/OPNsense0 / ufs rw,async,noatime 1 1
# vi /etc/fstab
ex/vi: Error: /var/tmp/vi.recover/: Read-only file system
ex/vi: Modifications not recoverable if the session fails
ex/vi: Error: /etc/fstab: Read-only file system
ex/vi: Error: Unable to create temporary file: Read-only file system
#
Sorry, but I still don't know how to get this partition read write.
I'm missing knowledge to get this slice read write.
What is the trick?

Hi Franco,
thanks for the reply.
I have done research as well and found tunefs and fsck.
As I have a CF there are 2 slices.
ad0s1a has trim enabled and ad0s2a has trim disabled.
When I try to disabled it on ad0s1a i'm not able due to the fact that this slice is still readonly.
I thought by booting in second slice i could disable it, but still no success.
Can you tell me how to enable writing to the first slice.
Greetings,
Rosie

Hi Everyone,
I have 2 Soekris devices installed with CF-card running Opnsense 16.7.2-i386.

On both I get the following messages in the System Log File:
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): Error 5, Retries exhausted
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): RES: 51 04 6f 63 6b 45 45 00 00 01 00
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): CAM status: ATA Status Error
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): DSM TRIM. ACB: 06 01 00 00 00 40 00 00 00 00 01 00
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): Retrying command
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): RES: 51 04 6f 63 6b 45 45 00 00 01 00
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): CAM status: ATA Status Error
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): DSM TRIM. ACB: 06 01 00 00 00 40 00 00 00 00 01 00
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): Retrying command
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): RES: 51 04 6f 63 6b 45 45 00 00 01 00
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): CAM status: ATA Status Error
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): DSM TRIM. ACB: 06 01 00 00 00 40 00 00 00 00 01 00
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): Retrying command
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): RES: 51 04 6f 63 6b 45 45 00 00 01 00
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): CAM status: ATA Status Error
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): DSM TRIM. ACB: 06 01 00 00 00 40 00 00 00 00 01 00
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): Retrying command
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): RES: 51 04 6f 63 6b 45 45 00 00 01 00
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): CAM status: ATA Status Error
Aug 26 12:16:51    kernel: (ada0:ata0:0:0:0): DSM TRIM. ACB: 06 01 00 00 00 40 00 00 00 00 01 00

It has to do with the disk, anyone seen this before and is there a solution for this?

Greets,
Rosie

Hi when I look in firewall normal view I get this.

Jul 7 20:04:56    2_VR2_OPT1 xxx.xxx.xxx.17:<span title="Service 445/tcp: microsoft-ds">445</span>    xxx.xxx.xxx.100:12775    TCP:PA
Jul 7 20:04:27    2_VR2_OPT1 0.0.0.0:<span title="Service 68/udp: bootpc">68</span>    
255.255.255.255:<span title="Service 67/udp: bootps">67</span>    UDP

Never saw the </span> words.

Hi,
I have Block bogon networks enabled on my 10.x.x.x network.
After upgrade to 16.1.15-i386 this network will be handled as a BOGON network and then will be blocked.

Any clues?
Greetz
Roro.

point of attention:

First I had pfsense running on this machine with WAN on vr0 and LAN on vr1 (optX on vrX).

When I used the opnsense cf-card LAN is on vr0 and WAN is on vr1.

I didn't had time to test it over again with a 8gb cf-card.
I burnt the image to 4gb cf-card and it works now on soekris net5501.
Update also to latest OPNsense 15.7.20-i386 version.