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

    Pfsense not booting on USB and SD on Alix APU.1c

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    24 Posts 7 Posters 14.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.
    • O
      ozlecz
      last edited by

      re: install pfSense-memstick-2.1-RELEASE-amd64.img on a cruzer fit and SD (adata)

      things done:
      =install the memstick image to USB using physdiskwrite successful
      =install the same on SD
      =install SD and USB stick one at a time but failed
      =at one point on the startup press F12 and select the proper drive but still failing to boot

      Pls help as we know we have an issue on the supplied mSATA ssd

      Thanks

      1 Reply Last reply Reply Quote 0
      • GruensFroeschliG
        GruensFroeschli
        last edited by

        If you see the message about pressing F12 then your serial speed is on 115200.
        You won't see any pfSense output since it is at 9600.
        Switch your serial speed to 9600 after selecting your boot medium and you will see the pfSense output.

        We do what we must, because we can.

        Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

        1 Reply Last reply Reply Quote 0
        • O
          ozlecz
          last edited by

          am aware of that and have done so…but it realy didnt boot...otherwise it would have buzz as well

          1 Reply Last reply Reply Quote 0
          • O
            ozlecz
            last edited by

            hello,

            things done;
            =install pfSense-memstick-2.1-RELEASE-i386.img on SD using physdiskwrite
            =doesnt boot
            =also tried with pfSense-memstick-2.1-RELEASE-amd64.img and still the same issue
            =tried writing the image thru gzip but still the problem persist

            pls help….see the output below...thx

            ===================================================================

            coreboot-unknown Tue Dec 24 11:13:00 MST 2013 booting...
            PCI: Left over static devices:
            PCI: 00:15.1
            PCI: 00:15.2
            PCI: 00:15.3
            PCI: Check your devicetree.cb.
            APIC: 00 missing read_resources
            APIC: 01 missing read_resources
            Start bios (version ?-20131224_111227-ubuntubuilderx64)
            CPU Mhz=1000
            Found 28 PCI devices (max PCI bus is 04)
            Found 2 cpu(s) max supported 2 cpu(s)
            Copying PIR from 0x7e16f000 to 0x000fdb40
            Copying MPTABLE from 0x7e170000/7e170010 to 0x000fda10
            Copying ACPI RSDP from 0x7e171000 to 0x000fd9f0
            Copying SMBIOS entry point from 0x7e17c400 to 0x000fd9d0
            Scan for VGA option rom
            EHCI init on dev 00:12.2 (regs=0xfeb08420)
            EHCI init on dev 00:13.2 (regs=0xfeb08520)
            OHCI init on dev 00:14.5 (regs=0xfeb06000)
            EHCI init on dev 00:16.2 (regs=0xfeb08620)
            Found 1 lpt ports
            Found 2 serial ports
            ATA controller 1 at 1f0/3f4/4010 (irq 14 dev a1)
            ATA controller 2 at 170/374/4018 (irq 15 dev a1)
            AHCI controller at 11.0, iobase feb08000, irq 0
            Searching bootorder for: /rom@img/sortbootorder
            Searching bootorder for: /rom@img/memtest
            Searching bootorder for: /pci@i0cf8/usb@16,2/storage@1/@0/@0,0
            Searching bootorder for: /pci@i0cf8/usb@16,2/usb-@1
            USB MSC vendor='Multiple' product='Card  Reader' rev='1.00' type=0 removable=1
            Searching bootorder for: /pci@i0cf8/usb@12,2/hub@1/storage@2/            @0/@0,0
            Searching bootorder for: /pci@i0cf8/usb@12,2/hub@1/usb-            @2
            USB MSC vendor='Generic' product='USB SD Reader' rev='1.00' type=0 removable=1
            Device reports MEDIUM NOT PRESENT
            scsi_is_ready returned -1
            Unable to configure USB MSC drive.
            Searching bootorder for: /pci@i0cf8/usb@12,2/hub@1/storage@2/@0/@0,1
            Searching bootorder for: /pci@i0cf8/usb@12,2/hub@1/usb-*@2
            USB MSC vendor='Generic' product='USB MS Reader' rev='1.03' type=0 removable=1
            Device reports MEDIUM NOT PRESENT
            scsi_is_ready returned -1
            Unable to configure USB MSC drive.
            Unable to configure USB MSC device.
            Initialized USB HUB (0 ports used)
            USB MSC blksize=512 sectors=7744512
            All threads complete.
            Scan for option roms
            Running option rom at c000:0003

            iPXE (http://ipxe.org) 00:00.0 C000 PCI2.10 PnP PMMpmm call arg1=1
            pmm call arg1=0
            +7E13F330pmm call arg1=1
            pmm call arg1=0
            +7E09B470 C000

            Searching bootorder for: /rom@genroms/pxeboot.rom
            Press F12 for boot menu.

            drive 0x000fd960: PCHS=0/0/0 translation=lba LCHS=960/128/63 s=7744512
            Space available for UMB: 000c1000-000ee800
            Returned 49152 bytes of ZoneHigh
            e820 map has 6 items:
              0: 0000000000000000 - 000000000009fc00 = 1 RAM
              1: 000000000009fc00 - 00000000000a0000 = 2 RESERVED
              2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
              3: 0000000000100000 - 000000007e16ac00 = 1 RAM
              4: 000000007e16ac00 - 000000007efffc00 = 2 RESERVED
              5: 00000000f8000000 - 00000000f9000000 = 2 RESERVED
            enter handle_19:
              NULL
            Booting from Hard Disk...
            Booting from 0000:7c00
            /

            1 Reply Last reply Reply Quote 0
            • jimpJ
              jimp Rebel Alliance Developer Netgate
              last edited by

              Make sure to use the serial memstick and choose the embedded kernel during the install.

              Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

              Need help fast? Netgate Global Support!

              Do not Chat/PM for help!

              1 Reply Last reply Reply Quote 0
              • dotdashD
                dotdash
                last edited by

                Sigh. If you're going to write an image to the SD card, use a nano image. If you are going to install to the m-Sata, write the memstick to a USB key and install from the USB to the m-Sata.

                1 Reply Last reply Reply Quote 0
                • O
                  ozlecz
                  last edited by

                  Make sure to use the serial memstick

                  TRIED BOTH pfSense-memstick-2.1-RELEASE-amd64.img/pfSense-memstick-2.1-RELEASE-i386.img/pfSense-memstick-serial-2.1-RELEASE-amd64.img BUT STILL BEHAVES THE SAME

                  and choose the embedded kernel during the install.
                  SIR I DONT KNOW AT WHICH POINT WILL I CHOOSE THIS…NOTE THAT I HAVENT SEEN ANY PFSENSE INITIALIZATION YET. EITHER PHYSDISKWRITE OR GZIP DOEST PASS THROUGH THIS OPTION

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

                    Maybe you need to fix your Caps Lock first? Plus you have already been told that you are doing it completely wrong, so why are you creating duplicate threads?!

                    https://forum.pfsense.org/index.php?topic=74382.0

                    ::)

                    1 Reply Last reply Reply Quote 0
                    • O
                      ozlecz
                      last edited by

                      this topic was created 3 days back and i didnt get any replies. thats why i created another one just and hour back,,sorry for that violation

                      1 Reply Last reply Reply Quote 0
                      • O
                        ozlecz
                        last edited by

                        it boots now with the 386nano image..but it has root mount error issue and goes to mountroot> prompt

                        sorry but am totally new on this..thx

                        note that ive written the image thru physdiskwrte

                        1 Reply Last reply Reply Quote 0
                        • H
                          hugo
                          last edited by

                          Hallo,

                          i have the same problems with my apu, but instead of pfsense i use ipcop.

                          things done:
                          = install to USB-Stick => work
                          = install the same to harddisk => work
                          = install the same to SD => installation worked => booting failed

                          enter handle_19:
                            NULL
                          Booting from Hard Disk…
                          Booting from 0000:7c00

                          PROBLEM SOLVED:
                          –----------------------
                          My problem was a bad formated SD-Card/USB stick.

                          I used "HP USB Disk Storage Format Tool" for formating and Win32DiskImage to write the image to USB and then i had no probles with install on SD.

                          1 Reply Last reply Reply Quote 0
                          • dotdashD
                            dotdash
                            last edited by

                            @ozlecz:

                            it boots now with the 386nano image..but it has root mount error issue and goes to mountroot> prompt

                            sorry but am totally new on this..thx

                            note that ive written the image thru physdiskwrte

                            Did you go through the procedure (documented here https://forum.pfsense.org/index.php?topic=59555.msg406438#msg406438) to set the boot delay?

                            1 Reply Last reply Reply Quote 0
                            • O
                              ozlecz
                              last edited by

                              i did that…in fact it was working now with USB stick but not on an SD.

                              1 Reply Last reply Reply Quote 0
                              • jimpJ
                                jimp Rebel Alliance Developer Netgate
                                last edited by

                                NanoBSD, 2g, amd64, 2.1.1 on a class 4 SD card worked fine for me on the APU I have. Nothing special aside from kern.cam.boot_delay.

                                (If you thought CF was slow, wait til you use an SD below a class 10… :-) )

                                Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                                Need help fast? Netgate Global Support!

                                Do not Chat/PM for help!

                                1 Reply Last reply Reply Quote 0
                                • O
                                  ozlecz
                                  last edited by

                                  am getting this on the physdiskwrite..same for ADATA and transcend 4Gb SD

                                  3965190144 bytes writtenWrite error after 3965190144 bytes (8192).

                                  1 Reply Last reply Reply Quote 0
                                  • jimpJ
                                    jimp Rebel Alliance Developer Netgate
                                    last edited by

                                    Use a smaller image. Try the 2GB NanoBSD on the 4GB card. The card is probably too small to contain the full image. See many other topics for more info on how card makers do that and why.

                                    Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                                    Need help fast? Netgate Global Support!

                                    Do not Chat/PM for help!

                                    1 Reply Last reply Reply Quote 0
                                    • O
                                      ozlecz
                                      last edited by

                                      still it goes to mountroot>

                                      1 Reply Last reply Reply Quote 0
                                      • jimpJ
                                        jimp Rebel Alliance Developer Netgate
                                        last edited by

                                        It will do that until/unless you do the kern.cam.boot_delay change as mentioned in many similar threads for the APU.

                                        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                                        Need help fast? Netgate Global Support!

                                        Do not Chat/PM for help!

                                        1 Reply Last reply Reply Quote 0
                                        • O
                                          ozlecz
                                          last edited by

                                          please find below running config; see the command as per advised…thx

                                          ▒▒▒▒▒▒▒▒▒▒▒P▒▒▒▒▒▒8▒▒▒▒▒▒▒▒▒▒\X▒▒▒▒▒▒▒▒▒▒▒▒▒▒/boot/config: -h
                                          Consoles: serial port
                                          BIOS drive C: is disk0
                                          BIOS 639kB/2064811kB available memory

                                          FreeBSD/x86 bootstrap loader, Revision 1.1
                                          (root@snapshots-8_3-amd64.builders.pfsense.org, Wed Sep 11 19:11:30 EDT 2013)
                                          Loading /boot/defaults/loader.conf
                                          /boot/kernel/kernel data=0x8cc0f8 data=0x5553c8+0xc24e0 syms=[0x8+0xe3700+0x8+0xd15e4]
                                          /
                                          Hit [Enter] to boot immediately, or any other key for command prompt.
                                          Booting [/boot/kernel/kernel] in 3 seconds…

                                          Type '?' for a list of commands, 'help' for more detailed help.
                                          OK
                                          OK
                                          OK
                                          OK set kern.cam.boot.delay=10000
                                          OK
                                          OK
                                          OK
                                          OK boot
                                          Copyright (c) 1992-2012 The FreeBSD Project.
                                          Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
                                                  The Regents of the University of California. All rights reserved.
                                          FreeBSD is a registered trademark of The FreeBSD Foundation.
                                          FreeBSD 8.3-RELEASE-p11 #0: Wed Sep 11 19:29:56 EDT 2013
                                              root@snapshots-8_3-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.8.amd64 amd64
                                          Timecounter "i8254" frequency 1193182 Hz quality 0
                                          CPU: AMD G-T40E Processor (1000.00-MHz K8-class CPU)
                                            Origin = "AuthenticAMD"  Id = 0x500f20  Family = 14  Model = 2  Stepping = 0
                                            Features=0x178bfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,fxsr,sse,sse2,htt>Features2=0x802209 <sse3,mon,ssse3,cx16,popcnt>AMD Features=0x2e500800 <syscall,nx,mmx+,ffxsr,page1gb,rdtscp,lm>AMD Features2=0x35ff <lahf,cmp,svm,extapic,cr8,abm,sse4a,mas,prefetch,ibs,skinit,wdt>TSC: P-state invariant
                                          real memory  = 2115411968 (2017 MB)
                                          avail memory = 2021490688 (1927 MB)
                                          ACPI APIC Table: <core  coreboot="">FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
                                          FreeBSD/SMP: 1 package(s) x 2 core(s)
                                          cpu0 (BSP): APIC ID:  0
                                          cpu1 (AP): APIC ID:  1
                                          ioapic0 <version 2.1="">irqs 0-23 on motherboard
                                          wlan: mac acl policy registered
                                          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, 0xffffffff8041ca10, 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, 0xffffffff8041cab0, 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, 0xffffffff8041cb50, 0) error 1
                                          cryptosoft0: <software crypto="">on motherboard
                                          padlock0: No ACE support.
                                          acpi0: <core coreboot="">on motherboard
                                          acpi0: [ITHREAD]
                                          acpi0: Power Button (fixed)
                                          Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
                                          acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
                                          cpu0: <acpi cpu="">on acpi0
                                          cpu1: <acpi cpu="">on acpi0
                                          acpi_hpet0: <high precision="" event="" timer="">iomem 0xfed00000-0xfed003ff on acpi0
                                          Timecounter "HPET" frequency 14318180 Hz quality 900
                                          pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff iomem 0xa0000-0xbffff,0x7f000000-0xffffffff on acpi0
                                          pci0: <acpi pci="" bus="">on pcib0
                                          pcib1: <acpi pci-pci="" bridge="">at device 4.0 on pci0
                                          pci1: <acpi pci="" bus="">on pcib1
                                          re0: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" f="" pcie="" gigabit="" ethernet="">port 0x1000-0x10ff mem 0xfe600000-0xfe600fff,0xfe500000-0xfe503fff at device 0.0 on pci1
                                          re0: Using 1 MSI-X message
                                          re0: ASPM disabled
                                          re0: Chip rev. 0x2c000000
                                          re0: MAC rev. 0x00000000
                                          miibus0: <mii bus="">on re0
                                          rgephy0: <rtl8169s 8110s="" 8211b="" media="" interface="">PHY 1 on miibus0
                                          rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
                                          re0: [ITHREAD]
                                          pcib2: <acpi pci-pci="" bridge="">at device 5.0 on pci0
                                          pci2: <acpi pci="" bus="">on pcib2
                                          re1: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" f="" pcie="" gigabit="" ethernet="">port 0x2000-0x20ff mem 0xfe800000-0xfe800fff,0xfe700000-0xfe703fff at device 0.0 on pci2
                                          re1: Using 1 MSI-X message
                                          re1: ASPM disabled
                                          re1: Chip rev. 0x2c000000
                                          re1: MAC rev. 0x00000000
                                          miibus1: <mii bus="">on re1
                                          rgephy1: <rtl8169s 8110s="" 8211b="" media="" interface="">PHY 1 on miibus1
                                          rgephy1:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
                                          re1: [ITHREAD]
                                          pcib3: <acpi pci-pci="" bridge="">at device 6.0 on pci0
                                          pci3: <acpi pci="" bus="">on pcib3
                                          re2: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" f="" pcie="" gigabit="" ethernet="">port 0x3000-0x30ff mem 0xfea00000-0xfea00fff,0xfe900000-0xfe903fff at device 0.0 on pci3
                                          re2: Using 1 MSI-X message
                                          re2: ASPM disabled
                                          re2: Chip rev. 0x2c000000
                                          re2: MAC rev. 0x00000000
                                          miibus2: <mii bus="">on re2
                                          rgephy2: <rtl8169s 8110s="" 8211b="" media="" interface="">PHY 1 on miibus2
                                          rgephy2:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
                                          re2: [ITHREAD]
                                          atapci0: <ati 800="" ixp700="" sata300="" controller="">port 0x4020-0x4027,0x4040-0x4043,0x4028-0x402f,0x4044-0x4047,0x4000-0x400f mem 0xfeb08000-0xfeb083ff at device 17.0 on pci0
                                          atapci0: [ITHREAD]
                                          atapci0: AHCI v1.20 controller with 4 6Gbps ports, PM supported
                                          ata2: <ata channel="">at channel 0 on atapci0
                                          ata2: [ITHREAD]
                                          ata3: <ata channel="">at channel 1 on atapci0
                                          ata3: [ITHREAD]
                                          ata4: <ata channel="">at channel 2 on atapci0
                                          ata4: [ITHREAD]
                                          ata5: <ata channel="">at channel 3 on atapci0
                                          ata5: [ITHREAD]
                                          ohci0: <ohci (generic)="" usb="" controller="">mem 0xfeb04000-0xfeb04fff at device 18.0 on pci0
                                          ohci0: [ITHREAD]
                                          usbus0: <ohci (generic)="" usb="" controller="">on ohci0
                                          ehci0: <ehci (generic)="" usb="" 2.0="" controller="">mem 0xfeb08400-0xfeb084ff at device 18.2 on pci0
                                          ehci0: [ITHREAD]
                                          usbus1: EHCI version 1.0
                                          usbus1: <ehci (generic)="" usb="" 2.0="" controller="">on ehci0
                                          ohci1: <ohci (generic)="" usb="" controller="">mem 0xfeb05000-0xfeb05fff at device 19.0 on pci0
                                          ohci1: [ITHREAD]
                                          usbus2: <ohci (generic)="" usb="" controller="">on ohci1
                                          ehci1: <ehci (generic)="" usb="" 2.0="" controller="">mem 0xfeb08500-0xfeb085ff at device 19.2 on pci0
                                          ehci1: [ITHREAD]
                                          usbus3: EHCI version 1.0
                                          usbus3: <ehci (generic)="" usb="" 2.0="" controller="">on ehci1
                                          pci0: <serial bus,="" smbus="">at device 20.0 (no driver attached)
                                          atapci1: <ati 800="" ixp700="" udma133="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x4010-0x401f at device 20.1 on pci0
                                          ata0: <ata channel="">at channel 0 on atapci1
                                          ata0: [ITHREAD]
                                          ata1: <ata channel="">at channel 1 on atapci1
                                          ata1: [ITHREAD]
                                          isab0: <pci-isa bridge="">at device 20.3 on pci0
                                          isa0: <isa bus="">on isab0
                                          pcib4: <acpi pci-pci="" bridge="">at device 20.4 on pci0
                                          pci0: couldn't attach pci bus
                                          device_attach: pcib4 attach returned 6
                                          ohci2: <ohci (generic)="" usb="" controller="">mem 0xfeb06000-0xfeb06fff at device 20.5 on pci0
                                          ohci2: [ITHREAD]
                                          usbus4: <ohci (generic)="" usb="" controller="">on ohci2
                                          pcib5: <acpi pci-pci="" bridge="">at device 21.0 on pci0
                                          pci4: <acpi pci="" bus="">on pcib5
                                          ohci3: <ohci (generic)="" usb="" controller="">mem 0xfeb07000-0xfeb07fff at device 22.0 on pci0
                                          ohci3: [ITHREAD]
                                          usbus5: <ohci (generic)="" usb="" controller="">on ohci3
                                          ehci2: <ehci (generic)="" usb="" 2.0="" controller="">mem 0xfeb08600-0xfeb086ff at device 22.2 on pci0
                                          ehci2: [ITHREAD]
                                          usbus6: EHCI version 1.0
                                          usbus6: <ehci (generic)="" usb="" 2.0="" controller="">on ehci2
                                          acpi_button0: <power button="">on acpi0
                                          atrtc0: <at realtime="" clock="">port 0x70-0x71 irq 8 on acpi0
                                          orm0: <isa option="" rom="">at iomem 0xee800-0xeffff on isa0
                                          ppc0: cannot reserve I/O port range
                                          uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
                                          uart0: [FILTER]
                                          uart0: console (9600,n,8,1)
                                          uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 on isa0
                                          uart1: [FILTER]
                                          acpi_throttle0: <acpi cpu="" throttling="">on cpu0
                                          RTC BIOS diagnostic error ff <clock_battery,rom_cksum,config_unit,memory_size,fixed_disk,invalid_time>Timecounters tick every 10.000 msec
                                          IPsec: Initialized Security Association Processing.
                                          usbus0: 12Mbps Full Speed USB v1.0
                                          usbus1: 480Mbps High Speed USB v2.0
                                          ugen0.1: <ati>at usbus0
                                          uhub0: <ati 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
                                          ugen1.1: <ati>at usbus1
                                          uhub1: <ati 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus1
                                          usbus2: 12Mbps Full Speed USB v1.0
                                          usbus3: 480Mbps High Speed USB v2.0
                                          ugen2.1: <ati>at usbus2
                                          uhub2: <ati 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus2
                                          ugen3.1: <ati>at usbus3
                                          uhub3: <ati 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus3
                                          usbus4: 12Mbps Full Speed USB v1.0
                                          usbus5: 12Mbps Full Speed USB v1.0
                                          ugen4.1: <ati>at usbus4
                                          uhub4: <ati 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus4
                                          ugen5.1: <ati>at usbus5
                                          uhub5: <ati 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus5
                                          usbus6: 480Mbps High Speed USB v2.0
                                          uhub0: 5 ports with 5 removable, self powered
                                          ugen6.1: <ati>at usbus6
                                          uhub6: <ati 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus6
                                          SMP: AP CPU #1 Launched!
                                          Root mount waiting for: usbus6 usbus5 usbus4 usbus3 usbus2 usbus1
                                          uhub4: 2 ports with 2 removable, self powered
                                          uhub2: 5 ports with 5 removable, self powered
                                          uhub5: 4 ports with 4 removable, self powered
                                          Root mount waiting for: usbus6 usbus3 usbus1
                                          uhub1: 5 ports with 5 removable, self powered
                                          uhub3: 5 ports with 5 removable, self powered
                                          uhub6: 4 ports with 4 removable, self powered
                                          ugen6.2: <generic>at usbus6
                                          umass0: <generic 0="" 2="" flash="" card="" readerwriter,="" class="" 0,="" rev="" 2.01="" 1.00,="" addr="">on usbus6
                                          Root mount waiting for: usbus6
                                          Trying to mount root from ufs:/dev/ufs/pfsense0
                                          ROOT MOUNT ERROR:
                                          If you have invalid mount options, reboot, and first try the following from
                                          the loader prompt:

                                          set vfs.root.mountfrom.options=rw

                                          and then remove invalid mount options from /etc/fstab.

                                          Loader variables:
                                          vfs.root.mountfrom=ufs:/dev/ufs/pfsense0
                                          vfs.root.mountfrom.options=ro,sync,noatime

                                          Manual root filesystem specification:
                                            <fstype>:<device>  Mount <device>using filesystem <fstype>eg. ufs:/dev/da0s1a
                                                                eg. cd9660:/dev/acd0
                                                                This is equivalent to: mount -t cd9660 /dev/acd0 /

                                          ?                  List valid disk boot devices
                                            <empty line="">      Abort manual input

                                          mountroot></empty></fstype></device></device></fstype></generic></generic></ati></ati></ati></ati></ati></ati></ati></ati></ati></ati></ati></ati></ati></ati></clock_battery,rom_cksum,config_unit,memory_size,fixed_disk,invalid_time></acpi></isa></at></power></ehci></ehci></ohci></ohci></acpi></acpi></ohci></ohci></acpi></isa></pci-isa></ata></ata></ati></serial></ehci></ehci></ohci></ohci></ehci></ehci></ohci></ohci></ata></ata></ata></ata></ati></rtl8169s></mii></realtek></acpi></acpi></rtl8169s></mii></realtek></acpi></acpi></rtl8169s></mii></realtek></acpi></acpi></acpi></acpi></high></acpi></acpi></core></software></version></core ></lahf,cmp,svm,extapic,cr8,abm,sse4a,mas,prefetch,ibs,skinit,wdt></syscall,nx,mmx+,ffxsr,page1gb,rdtscp,lm></sse3,mon,ssse3,cx16,popcnt></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,fxsr,sse,sse2,htt>

                                          1 Reply Last reply Reply Quote 0
                                          • jimpJ
                                            jimp Rebel Alliance Developer Netgate
                                            last edited by

                                            It is not kern.cam.boot.delay, it is kern.cam.boot_delay

                                            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                                            Need help fast? Netgate Global Support!

                                            Do not Chat/PM for help!

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