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

    RC3 and kern.cam.bootdelay

    2.0-RC Snapshot Feedback and Problems - RETIRED
    3
    4
    5.4k
    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.
    • P
      pp
      last edited by

      I know this is considered a solved problem, but I can't seem to get RC3 to boot from a USB memory stick without intervention, whereas I could get RC2 to boot OK.  In short, setting kern.cam.boot_delay solves the problem if I type it in at the prompt, but not if I put it in loader.conf.local.  Not sure if anything related to this changed from RC2 to RC3, or if I'm just doing something (new) wrong.  I am not all knowledgeable about the nanoBSD boot process, so I'd be grateful for any suggestions or pointers.

      I'm getting the rootmount error described in the doc, i.e.

      
         Root mount waiting for: usbus4
         Trying to mount root from udfas0: 
      

      If I wait for

      
         mountroot> GEOM: da0s1: geometry does not match label (16h,63s != 255h,63s).
         GEOM: da0s2: geometry does not match label (16h,63s != 255h,63s).
      
      

      and type

      
         ufs:/dev/da0s1a
      
      

      it boots OK.  So then I reboot and try breaking at the "press any key" prompt, and typing

      
         set kern.cam.boot_delay=10000
         boot
      
      

      and sure enough it boots OK.  So then I follow the doc instructions and create /boot/loader.conf.local

      
         $ ls -l /boot/loader.conf*
         -rw-r–r--  1 root  wheel  219 Jul  8 13:41 /boot/loader.conf
         -rw-r--r--  1 root  wheel   26 Jul  8 13:23 /boot/loader.conf.local
      
         $ cat /boot/loader.conf.local
         kern.cam.boot_delay=20000
      
      

      but I continue to get the boot error.  I believe I did the exact same thing, successfully, with RC2.  I thought perhaps kern.cam.boot_delay wasn't working at all, and that it was just the time it took me to type "set …" that made things work, so I tried just counting to 20 after escaping, but no go.  So kern.cam.boot_delay solves the problem if I type it in at the prompt, but not if I put it in loader.conf.local.  There was some indication at the console (though not in the log) that loader.conf was getting sourced (or whatever the right term is), but no explicit mention of loader.conf.local.  So I tried putting it in loader.conf, but no go.

      This is on:

      Version 2.0-RC3 (i386)
      built on Tue Jun 21 18:21:10 EDT 2011
      Platform nanobsd (2g)
      NanoBSD Boot Slice / da0s2
      CPU Type Intel(R) Atom(TM) CPU D525 @ 1.80GHz

      Thanks for any help.

      1 Reply Last reply Reply Quote 0
      • W
        wallabybob
        last edited by

        It helps to get the syntax correct. I think you need

        $ cat /boot/loader.conf.local
        kern.cam.boot_delay="20000"

        rather than

        $ cat /boot/loader.conf.local
        kern.cam.boot_delay=20000

        1 Reply Last reply Reply Quote 0
        • P
          pp
          last edited by

          @wallabybob:

          It helps to get the syntax correct. I think you need

          $ cat /boot/loader.conf.local
          kern.cam.boot_delay="20000"

          I will try that at the next opportunity, but neither the doc I cited, nor the bug report from 2.0-BETA1, had quotes around the value.

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by

            In that instance you can do it with quotes or without, the way you have it is fine. Not sure why that doesn't work in your case.

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