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

    Root Mount Error

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    6 Posts 3 Posters 7.4k 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.
    • W
      wonko93
      last edited by

      I am running pfSense 2.0.3 with no problems on an Atom D525 board (ASUS AT5NM10T-I), booting from a compact flash card connected via SATA-CF adapter (Syba SD-ADA40001).

      I would like to do some experimenting with IPV6, so I tried to upgrade to pfSense 2.1 RC0. At first, I tried upgrading through the web interface but I have since tried re-writing the CF card completely with the same result.

      The problem is that 2.1 will not boot and fails with a Root Mount Error. If I type ? to list the available drives, there are no drives listed. I have tried disabling ACPI and DMA from the boot command line with no luck.

      I think perhaps there is a driver missing in 2.1?

      After re-writing 2.0.3 to the CF card, everything is back to normal and booting as expected.

      Anyone have any ideas how I can get 2.1 up and running with this hardware? I'd love to give IPV6 a try…

      Thanks,

      Pete

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

        I think I will need a bit more information to seed the growth of ideas about this: specifically the half dozen lines or more before the root mount error is reported and the response when you type the question mark.

        It is quite possible that won't be enough information so it would probably be worthwhile to get an additional CF card to save you having to write pfSense 2.0.3 again on your card and then write 2.1 on the card so you can get additional information.

        What build of pfSense 2.1 are you working with?

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

          Hi Wallabybob,

          Thanks for your reply and sorry to take so long to get back to you.

          @wallabybob:

          I think I will need a bit more information to seed the growth of ideas about this: specifically the half dozen lines or more before the root mount error is reported and the response when you type the question mark.

          Here is the relevant output:

          
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.0
ugen0.1: <intel>at usbus0
uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
ugen1.1: <intel>at usbus1
uhub1: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus1
usbus2: 12Mbps Full Speed USB v1.0
usbus3: 12Mbps Full Speed USB v1.0
ugen2.1: <intel>at usbus2
uhub2: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus2
ugen3.1: <intel>at usbus3
uhub3: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus3
usbus4: 480Mbps High Speed USB v2.0
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
Root mount waiting for: usbus4 usbus3 usbus2 usbus1 usbus0
uhub0: 2 ports with 2 removable, self powered
mgeunh4u.b11::  <2I nptoerlt>s  awti tuhs b2u sr4e
 ovable, self powered
uhub4: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus4
uhub2: 2 ports with 2 removable, self powered
uhub3: 2 ports with 2 removable, self powered
Root mount waiting for: usbus4
Root mount waiting for: usbus4
Root mount waiting for: usbus4
uhub4: 8 ports with 8 removable, self powered
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</empty></fstype></device></device></fstype></intel></intel></intel></intel></intel></intel></intel></intel></intel>

          and here is the output from my working 2.0.3 CF:

          
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.0
ugen0.1: <intel>at usbus0
uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
ugen1.1: <intel>at usbus1
uhub1: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus1
usbus2: 12Mbps Full Speed USB v1.0
usbus3: 12Mbps Full Speed USB v1.0
ugen2.1: <intel>at usbus2
uhub2: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus2
ugen3.1: <intel>at usbus3
uhub3: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus3
usbus4: 480Mbps High Speed USB v2.0
ad0: 3847MB <elite pro="" cf="" card="" 4gb="" ver2.21k="">at ata0-master PIO4 SATA
ugen4.1: <intel>at usbus4
uhub4: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus4
uhub0: 2 ports with 2 removable, self powered
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
uhub1: 2 ports with 2 removable, self powered
uhub2: 2 ports with 2 removable, self powered
Root mount waiting for: usbus4 usbus3 usbus2
uhub3: 2 ports with 2 removable, self powered
Root mount waiting for: usbus4
Root mount waiting for: usbus4
Root mount waiting for: usbus4
uhub4: 8 ports with 8 removable, self powered
Trying to mount root from ufs:/dev/ufs/pfsense0
Configuring crash dumps...
Mounting filesystems...
Setting up embedded specific environment... done.</intel></intel></elite></intel></intel></intel></intel></intel></intel></intel></intel>

          As you can see, 2.0.3 detects the CF card as ad0, but 2.1 does not.

          If I type ? to get a list of known devices in 2.1, it gives me:

          
mountroot> ?

List of GEOM managed disk devices:

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</empty></fstype></device></device></fstype>

          It doesn't list any available disk devices.

          @wallabybob:

          What build of pfSense 2.1 are you working with?

          I am using a freshly written (dd from a Mac) CF card with the pfSense-2.1-RC0-4g-i386-nanobsd-20130630-0822.img.gz image.

          Please let me know if you need any further information.

          Thanks,

          Pete

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

            There is a similar looking problem reported in http://forum.pfsense.org/index.php/topic,63961.0.html though in different hardware.

            1 Reply Last reply Reply Quote 0
            • D
              DerTrickreiche
              last edited by

              I also discovered this strange behavior.
              What I found out ist, that it won't boot from a fresh copyed nanobsd-Image if there ist no USB-keyboard detected.
              A PS/2 keyboard won't work!
              It doesnt matter, if you use the serial or normal console. A boot of nanobsd-image seems to be impossible without a connected USB-keyborad.

              Harry

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

                @DerTrickreiche:

                What I found out ist, that it won't boot from a fresh copyed nanobsd-Image if there ist no USB-keyboard detected.

                Hi Harry, thanks for the suggestion. I tried plugging an Apple USB keyboard into my pfSense box. The keyboard was detected, but pfSense still failed to boot with the same Root Mount Error:

                
Root mount waiting for: usbus4
Root mount waiting for: usbus4
Root mount waiting for: usbus4
uhub4: 8 ports with 8 removable, self powered
Root mount waiting for: usbus4
ugen4.2: <apple, inc.="">at usbus4
uhub5: <apple, 2="" 9="" inc.="" keyboard="" hub,="" class="" 0,="" rev="" 2.00="" 96.15,="" addr="">on usbus4
uhub5: 3 ports with 2 removable, bus powered
Root mount waiting for: usbus4
ugen4.3: <apple, inc="">at usbus4
Trying to mount root from ufs:/dev/ufs/pfsense0
ROOT MOUNT ERROR:</apple,></apple,></apple,>

                Pete

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