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

    Getting 'not currently mounted /cf' on embedded system running on flash

    Scheduled Pinned Locked Moved Hardware
    12 Posts 3 Posters 4.0k 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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      Hmm, well that looks odd. /cf should definitely be mounted otherwise the config file cannot be read. Or anything in conf for that matter.
      What do you see if you run the mount command from the CLI?
      Here's some output from my local nanobsd box:

      
      [2.0.1-RELEASE][root@pfsense.fire.box]/root(1): mount
      /dev/ufs/pfsense0 on / (ufs, local, noatime, read-only, synchronous)
      devfs on /dev (devfs, local)
      /dev/md0 on /tmp (ufs, local)
      /dev/md1 on /var (ufs, local)
      /dev/ufs/cf on /cf (ufs, local, noatime, read-only, synchronous)
      devfs on /var/dhcpd/dev (devfs, local)
      [2.0.1-RELEASE][root@pfsense.fire.box]/root(2): cd /cf
      [2.0.1-RELEASE][root@pfsense.fire.box]/cf(3): ls
      .snap conf
      [2.0.1-RELEASE][root@pfsense.fire.box]/cf(4): cd conf
      [2.0.1-RELEASE][root@pfsense.fire.box]/cf/conf(5): ls
      WGXepc                                  ez-ipupdate.cache                       rrd.tgz
      backup                                  fdisk_upgrade_log.txt                   sshd
      config.xml                              file_upgrade_log.txt                    upgrade_log.txt
      dhcpleases.tgz                          firmware_update_misc_log.txt
      dyndns_wannoip'******.hopto.org'.cache  readio
      
      

      Steve

      1 Reply Last reply Reply Quote 0
      • T
        ttblum
        last edited by

        2.0.1-RELEASE][admin@pfsense.localdomain]/root(1): mount

        /dev/ufs/pfsense0 on / (ufs, local, noatime, read-only, synchronous)
        devfs on /dev (devfs, local)
        /dev/md0 on /tmp (ufs, local)
        /dev/md1 on /var (ufs, local)

        [2.0.1-RELEASE][admin@pfsense.localdomain]/root(2): cd /cf

        [2.0.1-RELEASE][admin@pfsense.localdomain]/cf(3): ls

        conf

        [2.0.1-RELEASE][admin@pfsense.localdomain]/cf(4): cd conf

        [2.0.1-RELEASE][admin@pfsense.localdomain]/cf/conf(5): ls

        backup            config.xml        dhcpleases.tgz    ez-ipupdate.cache rrd.tgz          sshd

        [2.0.1-RELEASE][admin@pfsense.localdomain]/cf/conf(6):

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          Hmm. So the config slice is not mounted as /cf but you can still cd into it and list it's contents. What….  :-\

          How does that compare with your other Alix boxes?
          Not something I know about I'm afraid.  :(

          Steve

          1 Reply Last reply Reply Quote 0
          • T
            ttblum
            last edited by

            Hi,

            My other Alix routers look normal like the example you posted.

            I'm just concerned about rebooting it in case there is a hardware problem, such as bad disk, etc.

            Thanks,

            Todd

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Is that the only one running bandwidthd?

              Steve

              1 Reply Last reply Reply Quote 0
              • T
                ttblum
                last edited by

                I have bandwidthd running OK on at least two other Alix routers.  I have had the CF card fail on one of them before, but never this specific error.

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

                  If the /cf slice fails to mount, it would still write files into /cf/ on / - a little odd, but it happens.

                  I'd run:

                  fsck -y /dev/ufs/cf
                  

                  And then see what that reports. If it's dead/not mounting, you may have a disk issue.

                  The main problem you'll have in your current state is that if you do a firmware update, you will lose your config because it's not on the shared config slice.

                  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
                  • T
                    ttblum
                    last edited by

                    OK. If there were a disk problem, any chance the fsck would bring the router down?

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

                      No, the /cf slice is already unmounted so unless the entire CF is about to blow, it's unlikely running a check on an unmounted/inactive slice will hurt anything.

                      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
                      • T
                        ttblum
                        last edited by

                        [2.0.1-RELEASE][admin@pfsense.localdomain]/root(1): fsck -y /dev/ufs/cf

                        Can't stat /dev/ufs/cf: No such file or directory
                        Can't stat /dev/ufs/cf: No such file or directory

                        [2.0.1-RELEASE][admin@pfsense.localdomain]/root(2):

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

                          sure you didn't do something like write an image to the card that was far too large?

                          I can't think of any reason why the slice would have just disappeared like that unless it was never written to the card. And since the cf slice is at the end of the card, if the image was too big (think writing a 2GB image to a 1GB card) then it may behave like that.

                          I suppose if the CF had a large number of bad sectors causing the disk to "shrink" it may also do that, but I don't think I've seen one act quite like that when it happens.

                          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.