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

    Proxy server question

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    27 Posts 5 Posters 5.3k 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.
    • KOMK Offline
      KOM
      last edited by

      Ok, so it sees your disk.  I'm not sure what your problem is then.  Just partition, format and mount it as per the guide I linked to:

      # gpart create -s GPT da1
      # gpart add -t freebsd-ufs da1
      # newfs -U /dev/da1s1
      # mkdir /newdisk
      # mount /dev/da1s1 /newdisk
      

      Add this to /etc/fstab so that it mounts at boot:

      /dev/da1s1	/newdisk	ufs	rw	2	2
      
      1 Reply Last reply Reply Quote 0
      • J Offline
        Jamerson
        last edited by

        @KOM:

        Ok, so it sees your disk.  I'm not sure what your problem is then.  Just partition, format and mount it as per the guide I linked to:

        # gpart create -s GPT da1
        # gpart add -t freebsd-ufs da1
        # newfs -U /dev/da1s1
        # mkdir /newdisk
        # mount /dev/da1s1 /newdisk
        

        Add this to /etc/fstab so that it mounts at boot:

        /dev/da1s1	/newdisk	ufs	rw	2	2
        

        Thank you KOM
        the problem is when i run the command

        newfs -U /dev/da1s1

        it said command not found !

        [2.2-RELEASE][root@firewall.pfsense.lan]/root: # newfs -U /dev/da1s1
        #: Command not found.
        [2.2-RELEASE][root@firewall.pfsense.lan]/root:

        1 Reply Last reply Reply Quote 0
        • KOMK Offline
          KOM
          last edited by

          #: Command not found.

          The # character is meant to represent your shell prompt.  You don't actually type that part.  No wonder you've been having trouble.

          1 Reply Last reply Reply Quote 0
          • J Offline
            Jamerson
            last edited by

            @KOM:

            #: Command not found.

            The # character is meant to represent your shell prompt.  You don't actually type that part.  No wonder you've been having trouble.

            sorry mommy mistake
            does the commands that has /dev/da1s1 means  /dev/da1 for me right ?
            i believe dev/da1 is my current install pfsense and dev/da1pl1 is the attached disk ?

            1 Reply Last reply Reply Quote 0
            • KOMK Offline
              KOM
              last edited by

              I did explain earlier that when they reference /dev/ada1, you would use/dev/da1.  When they use /dev/ada1p1, you would use /dev/da1s1.  p means partition, s means slice, but they are basically the same.

              1 Reply Last reply Reply Quote 0
              • J Offline
                Jamerson
                last edited by

                @KOM:

                I did explain earlier that when they reference /dev/ada1, you would use/dev/da1.  When they use /dev/ada1p1, you would use /dev/da1s1.  p means partition, s means slice, but they are basically the same.

                is exactly what i am doing
                [2.2-RELEASE][root@firewall.pfsense.lan]/root: newfs -U /dev/da1s1
                newfs: /dev/da1s1: could not find special device
                [2.2-RELEASE][root@firewall.pfsense.lan]/root:

                1 Reply Last reply Reply Quote 0
                • K Offline
                  kejianshi
                  last edited by

                  I lost track.  Are you still trying to figure out how to cache dynamic content?  Don't waste too much time.  OK?

                  1 Reply Last reply Reply Quote 0
                  • KOMK Offline
                    KOM
                    last edited by

                    newfs: /dev/da1s1: could not find special device

                    OK, this one's on me.  When using gpart, it will make a partition, not a slice.  Try:

                    newfs -U /dev/da1p1
                    mkdir /newdisk
                    mount /dev/da1p1 /newdisk
                    

                    I lost track.  Are you still trying to figure out how to cache dynamic content?

                    We're still going over Unix disk basics at this point.

                    1 Reply Last reply Reply Quote 0
                    • K Offline
                      kejianshi
                      last edited by

                      Yeah - Its a nice mental exercise and is good to know (-:

                      1 Reply Last reply Reply Quote 0
                      • J Offline
                        Jamerson
                        last edited by

                        @KOM:

                        newfs: /dev/da1s1: could not find special device

                        OK, this one's on me.  When using gpart, it will make a partition, not a slice.  Try:

                        newfs -U /dev/da1p1
                        mkdir /newdisk
                        mount /dev/da1p1 /newdisk
                        

                        I lost track.  Are you still trying to figure out how to cache dynamic content?

                        We're still going over Unix disk basics at this point.

                        Thank you so much for this KOM,
                        the Disk is mapped now going to configured it for the cache
                        Mucht appreciate really and your patients as well

                        when i try to navigate to the new mounted disk i get "access denied "
                        trying to create a folder for the cashing.

                        1 Reply Last reply Reply Quote 0
                        • KOMK Offline
                          KOM
                          last edited by

                          You probably have to give the proxy user ownership of the folder:

                          chown proxy:proxy /your_disk_mount_point
                          
                          1 Reply Last reply Reply Quote 0
                          • J Offline
                            Jamerson
                            last edited by

                            @KOM:

                            You probably have to give the proxy user ownership of the folder:

                            chown proxy:proxy /your_disk_mount_point
                            

                            KOM you are the man,
                            thank you

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