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

    APU2: mount fails with error 19 (SD card)

    Scheduled Pinned Locked Moved Hardware
    14 Posts 6 Posters 14.5k 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.
    • K
      ktk
      last edited by

      Hi group,

      I tried booting the 2.3 release of PFsense on my brand new APU2 board (BIOS 160307) but it fails on mounting UFS:

      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

      mountroot>

      When I list the devices I see:

      mountroot> ?

      List of GEOM managed disk devices:
        diskid/DISK-7C9DD41D mmcsd0

      Anyone got some ideas what to do? Couldn't find much help googling around and it seems at APU2 is pretty new.</empty></fstype></device></device></fstype>

      1 Reply Last reply Reply Quote 0
      • PippinP
        Pippin
        last edited by

        Just for info and probably not going to help you but I got this error 19 too.
        In my case with a N3150N-D3V board.
        I installed from a USB stick in a USB 3 port.
        After putting it in a USB 2 port the installation went fine.

        I gloomily came to the ironic conclusion that if you take a highly intelligent person and give them the best possible, elite education, then you will most likely wind up with an academic who is completely impervious to reality.
        Halton Arp

        1 Reply Last reply Reply Quote 0
        • N
          Nylan
          last edited by

          Same problem with apu2 board.
          After putting usb stick in different port, writing image file to sdcard and removing usb stick before next power up everything went fine.

          1 Reply Last reply Reply Quote 0
          • ?
            Guest
            last edited by

            @Nylan
            Do you have flashed the latest BIOS image onto the APU2 board.

            1 Reply Last reply Reply Quote 0
            • K
              ktk
              last edited by

              @Nylan:

              Same problem with apu2 board.
              After putting usb stick in different port, writing image file to sdcard and removing usb stick before next power up everything went fine.

              so you installed the SD card from the USB stick instead of simply dd-ing the image to SD?

              1 Reply Last reply Reply Quote 0
              • N
                Nylan
                last edited by

                @ktk:

                @Nylan:

                Same problem with apu2 board.
                After putting usb stick in different port, writing image file to sdcard and removing usb stick before next power up everything went fine.

                so you installed the SD card from the USB stick instead of simply dd-ing the image to SD?

                Yes, I've followed the manual from http://pcengines.ch/pdf/apu2.pdf out of curiosity (with tinyCore 6.4). Note : the specified command doesn't work, since pv is missing. I've used "zcat imgFile | dd of=/dev/deviceName bs=10M" instead.
                The import of my old config didn't work out and after the reboot left me with the error message mentioned above.

                I've tried again to write the pfsense image and after every reboot I've got the error message failing to mount the partition until I've found this posting here. The hint to change the usb port solved the issue and also the import of my config worked perfectly.

                Don't know if the problems are related or if there is some bios issue.

                1 Reply Last reply Reply Quote 0
                • N
                  Nylan
                  last edited by

                  @BlueKobold:

                  @Nylan
                  Do you have flashed the latest BIOS image onto the APU2 board.

                  Not the last one. Current version installed = 20160307.

                  1 Reply Last reply Reply Quote 0
                  • ?
                    Guest
                    last edited by

                    Not the last one. Current version installed = 20160307.

                    I would go to install the last one and then have a look on the next clean, fresh and full install.
                    If this is matching then right you could expect from that version to be the best running according
                    to pfSense and your needs. If something is occurring you are freely able to get a SPi1A EPROM flasher
                    that can easily rewrite that BIOS to the ROM so that you couldn´t brick that board really to be unusable.

                    For all other boards from PC Engines this will be a different one but they are also having existing devices
                    such as this one. SPi1a

                    1 Reply Last reply Reply Quote 0
                    • K
                      ktk
                      last edited by

                      @Nylan:

                      Yes, I've followed the manual from http://pcengines.ch/pdf/apu2.pdf out of curiosity (with tinyCore 6.4). Note : the specified command doesn't work, since pv is missing. I've used "zcat imgFile | dd of=/dev/deviceName bs=10M" instead.
                      The import of my old config didn't work out and after the reboot left me with the error message mentioned above.

                      I've tried again to write the pfsense image and after every reboot I've got the error message failing to mount the partition until I've found this posting here. The hint to change the usb port solved the issue and also the import of my config worked perfectly.

                      Don't know if the problems are related or if there is some bios issue.

                      I tried the method described in the PDF, did it both for a USB stick and for the SD card. Result is always the same: it cannot mount and I end up in mountroot.

                      regards

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

                        @ktk:

                        I tried the method described in the PDF, did it both for a USB stick and for the SD card. Result is always the same: it cannot mount and I end up in mountroot.

                        Just received the apu2c4 and 16GB mSATA from PC Engines. The BIOS is 20160307 and  had no problems booting TinyCore from USB stick and installing the pfSense 2.3 (nano image with serial console) onto mSATA.

                        I have followed instructions in the apu2 pdf but as mentioned before, there is an error in the commands to extract the image file. The "pv" program is not present in the TinyCore and can be removed from the command sequence. It only displays the progress of image extraction onto the target device.

                        After extracting the image onto mSATA and rebooting, the pfSense booted successfully and I got the GUI in the browser.

                        1 Reply Last reply Reply Quote 0
                        • ?
                          Guest
                          last edited by

                          I tried the method described in the PDF, did it both for a USB stick and for the SD card. Result is always the same: it cannot mount and I end up in mountroot.

                          In some older BIOS versions there was a problem booting from the SD card, and if you have not installed
                          the last available BIOS version that could be pointed to that circumstance! Inthe german speaking part of
                          this forum some peoples where able to install the 64Bit version of pfSense either 2.2.6 & 2.3 onto that
                          Board in different ways, so it should be able for you too as I see it right. Also the SDCard itself could be
                          buggy and/or to small! Since version 2.3 1 GB images are not really any time supported and there to
                          download. What I really mean is this perhaps a 1 GB SD Card?

                          Just received the apu2c4 and 16GB mSATA from PC Engines. The BIOS is 20160307 and  had no problems booting TinyCore from USB stick and installing the pfSense 2.3 (nano image with serial console) onto mSATA.

                          The latest BIOS version is 20160311 so I would really update to that one if anything is not really running fine.

                          (nano image with serial console) onto mSATA.

                          This might be going but is not the really way anybody should use here, related to the circumstance that
                          this board is pretty new and the mSATA was produced for many write cycles, so there will be today no
                          need to use the NanoBSD. I would go with Nano on the USB stick or a full and fresh install on the mSATA.

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

                            Thanks for the tips Frank.

                            I've flashed the latest BIOS and installed the full version of pfSense on mSATA SSD.

                            1 Reply Last reply Reply Quote 0
                            • ?
                              Guest
                              last edited by

                              Thanks for the tips Frank.

                              I was changing from NanoBSD to a fresh and full install too! No hassle with updates, Snort and pfBlockerNG
                              or Squid can be used now and other things would be running more smooth and liquid.

                              I've flashed the latest BIOS and installed the full version of pfSense on mSATA SSD.

                              They are telling around now this or this will be running fine, but mostly other things get solved too!
                              And so this would be a "must be" during the time they are working on, you can be sure so long as
                              they work on I will update it if no other issues or failures will be reported about that one. Many of
                              us are doing in that order until all is fixed, this unit is really really wide spread in Germany, Austria
                              and Switzerland.

                              1 Reply Last reply Reply Quote 0
                              • L
                                lovoltage
                                last edited by

                                Ran into the same error when trying to install pfSense (current version 2.3.4) to a new embedded appliance (IBOX-501 N10/Protectli type device) with SSD or CF from a USB or CDROM. Cause of the issue is related to GPT (GUID Patition Table) marked media, and can affect either the new SSD, CF and/or the USB install media. The media needs to be adjusted from GPT to MBR. Using Windows, this is how I was able to correct the issue.

                                Using Windows 7 PC with administrative rights

                                • Connect SSD or CF media to the Windows PC
                                • Open a command prompt (with admin rights)
                                • Start the DISKPART utility by typing DISKPART
                                • type LIST DISK and note the number of the drive that will contain the pfSense installation
                                • type SELECT DISK (number)
                                • type CLEAN and wait for the task to complete
                                • type CONVERT MBR and wait for the task to complete
                                • type EXIT
                                • remove the SSD or CF drive from Windows and install into pfSense device

                                Seems that some USB thumb drives are shipped from the factory with GPT instead of MBR. If installing from a USB drive use the same steps above to prepare the USB media. Seems SanDisk and some Corsair USB drives are shipped from the factory with GPT.

                                After completion, a USB drive can be set up to install pfSense using Rufus.

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