Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Alix 2d13 upgrade 2.2.0 ERROR 19

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    3 Posts 3 Posters 1.7k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      badclstr
      last edited by

      I've been running on 2.1 since a year now and yesterday after the automatic upgrade to 2.2.0 I got error 19. Bios 0.99h.
      Is my CF dead?

      thank you for your help!

      VT: running with driver "vga".
      CPU: Geode(TM) Integrated Processor by AMD PCS (498.06-MHz 586-class CPU)
        Origin = "AuthenticAMD"  Id = 0x5a2  Family = 0x5  Model = 0xa  Stepping = 2
        Features=0x88a93d <fpu,de,pse,tsc,msr,cx8,sep,pge,cmov,clflush,mmx>AMD Features=0xc0400000 <mmx+,3dnow!+,3dnow!>real memory  = 268435456 (256 MB)
      avail memory = 226222080 (215 MB)
      pnpbios: Bad PnP BIOS data checksum
      random device not loaded; using insecure entropy
      ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
      ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
      module_register_init: MOD_LOAD (ipw_bss_fw, 0xc080eb70, 0) error 1
      ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
      ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
      module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc080ec20, 0) error 1
      ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
      ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
      module_register_init: MOD_LOAD (ipw_monitor_fw, 0xc080ecd0, 0) error 1
      iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
      iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
      module_register_init: MOD_LOAD (iwi_bss_fw, 0xc0837300, 0) error 1
      iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
      iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
      module_register_init: MOD_LOAD (iwi_ibss_fw, 0xc08373b0, 0) error 1
      iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
      iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
      module_register_init: MOD_LOAD (iwi_monitor_fw, 0xc0837460, 0) error 1
      wlan: mac acl policy registered
      kbd0 at kbdmux0
      K6-family MTRR support enabled (2 registers)
      random: <software, yarrow="">initialized
      ACPI BIOS Error (bug): A valid RSDP was not found (20130823/tbxfroot-223)
      ACPI: Table initialisation failed: AE_NOT_FOUND
      ACPI: Try disabling either ACPI or apic support.
      cryptosoft0: <software crypto="">on motherboard
      padlock0: No ACE support.
      pcib0 pcibus 0 on motherboard
      pci0: <pci bus="">on pcib0
      Geode LX: PC Engines ALIX.2 v0.99h tinyBIOS V1.4a (C)1997-2007
      pci0: <encrypt decrypt,="" entertainment="" crypto="">at device 1.2 (no driver attached)
      vr0: <via 10="" vt6105m="" rhine="" iii="" 100basetx="">port 0x1000-0x10ff mem 0xe0000000-0xe00000ff irq 10 at device 9.0 on pci0
      vr0: Quirks: 0x2
      vr0: Revision: 0x96
      miibus0: <mii bus="">on vr0
      ukphy0: <generic ieee="" 802.3u="" media="" interface="">PHY 1 on miibus0
      ukphy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
      vr1: <via 10="" vt6105m="" rhine="" iii="" 100basetx="">port 0x1400-0x14ff mem 0xe0040000-0xe00400ff irq 11 at device 10.0 on pci0
      vr1: Quirks: 0x2
      vr1: Revision: 0x96
      miibus1: <mii bus="">on vr1
      ukphy1: <generic ieee="" 802.3u="" media="" interface="">PHY 1 on miibus1
      ukphy1:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
      vr2: <via 10="" vt6105m="" rhine="" iii="" 100basetx="">port 0x1800-0x18ff mem 0xe0080000-0xe00800ff irq 15 at device 11.0 on pci0
      vr2: Quirks: 0x2
      vr2: Revision: 0x96
      miibus2: <mii bus="">on vr2
      ukphy2: <generic ieee="" 802.3u="" media="" interface="">PHY 1 on miibus2
      ukphy2:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
      isab0: <pci-isa bridge="">port 0x6000-0x6007,0x6100-0x61ff,0x6200-0x623f,0x9d00-0x9d7f,0x9c00-0x9c3f at device 15.0 on pci0
      isa0: <isa bus="">on isab0
      atapci0: <amd cs5536="" udma100="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 15.2 on pci0
      ata0: <ata channel="">at channel 0 on atapci0
      ata1: <ata channel="">at channel 1 on atapci0
      ohci0: <ohci (generic)="" usb="" controller="">mem 0xefffe000-0xefffefff irq 12 at device 15.4 on pci0
      usbus0 on ohci0
      ehci0: <amd cs5536="" (geode)="" usb="" 2.0="" controller="">mem 0xefffd000-0xefffdfff irq 12 at device 15.5 on pci0
      usbus1: EHCI version 1.0
      usbus1 on ehci0
      cpu0 on motherboard
      pmtimer0 on isa0
      orm0: <isa option="" rom="">at iomem 0xe0000-0xea7ff pnpid ORM0000 on isa0
      atrtc0: <at realtime="" clock="">at port 0x70 irq 8 on isa0
      Event timer "RTC" frequency 32768 Hz quality 0
      attimer0: <at timer="">at port 0x40 on isa0
      Timecounter "i8254" frequency 1193182 Hz quality 0
      Event timer "i8254" frequency 1193182 Hz quality 100
      ppc0: parallel port not found.
      uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
      uart0: console (115200,n,8,1)
      uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 on isa0
      Timecounters tick every 1.000 msec
      IPsec: Initialized Security Association Processing.
      usbus0: 12Mbps Full Speed USB v1.0
      usbus1: 480Mbps High Speed USB v2.0
      ugen0.1: <amd>at usbus0
      uhub0: <amd 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
      ugen1.1: <amd>at usbus1
      uhub1: <amd 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus1
      ada0 at ata0 bus 0 scbus0 target 0 lun 0
      ada0: <sandisk sdcfh-004g="" hdx="" 6.02="">CFA-0 device
      ada0: Serial Number AIZ061311235105
      ada0: 16.700MB/s transfers (PIO4, PIO 512bytes)
      ada0: 3815MB (7813120 512 byte sectors: 16H 63S/T 7751C)
      ada0: Previously was known as ad0
      GEOM_PART: integrity check failed (ada0, MBR)
      random: unblocking device.
      Timecounter "TSC" frequency 498061278 Hz quality 800
      GEOM_PART: integrity check failed (diskid/DISK-AIZ061311235105, MBR)
      Root mount waiting for: usbus1 usbus0
      uhub0: 4 ports with 4 removable, self powered
      Root mount waiting for: usbus1
      uhub1: 4 ports with 4 removable, self powered
      Trying to mount root from ufs:/dev/ufs/pfsense0 [ro,sync,noatime]…
      mountroot: waiting for device /dev/ufs/pfsense0 ...
      Mounting from ufs:/dev/ufs/pfsense0 failed with error 19.

      Loader variables:
        vfs.root.mountfrom=ufs:/dev/ufs/pfsense0
        vfs.root.mountfrom.options=ro,sync,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</empty></fstype></device></device></fstype></sandisk></amd></amd></amd></amd></at></at></isa></amd></ohci></ata></ata></amd></isa></pci-isa></generic></mii></via></generic></mii></via></generic></mii></via></encrypt></pci></software></software,></mmx+,3dnow!+,3dnow!></fpu,de,pse,tsc,msr,cx8,sep,pge,cmov,clflush,mmx>

      1 Reply Last reply Reply Quote 0
      • G
        gergero
        last edited by

        You can try to go back to your previous pfSense version: You will need a working serial connection when booting, then choose the alternate NanoBSD Boot Slice (it should contain your previous pfSense install) when you see the option.

        I had to troubleshoot a non-working config-xml: deleting the /conf/config.xml from the command prompt (loader prompt) restored the previous working config on the next boot.

        1 Reply Last reply Reply Quote 0
        • D
          doktornotor Banned
          last edited by

          https://doc.pfsense.org/index.php/Upgrade_Guide#Disk_Driver_Changes

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.