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

    Installing pfSense 2.0 on a Dell PowerEdge R210

    Scheduled Pinned Locked Moved General pfSense Questions
    44 Posts 31 Posters 64.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.
    • L
      lunar12
      last edited by

      Hi all, :)

      This is my first post in this forum
      I hope to contribute with friends.

      Well, I have the following problem.

      I bought a Dell server in the following configuration:

      PowerEdgeR210
      Intel(R) Xeon(R) Processor X3430(2.40GHz, 8MB cache, 1333MHz)
      2GB(2X1GB/1R/1333MHz/DDR3UDIMM)
      160GB 3.5 inch SATA II (7,200rpm) x 2
      SAS6iR controller Cards  (RAID1)
      Onboard LAN x2

      I tried to install pfsense 2.0 but the installation always stops at 38% in step
      /usr/local/bin/cpdup -vvv -l -o /usr/mnt/usr

      I downloaded the latest version
      pfSense-2.0-BETA5-20110105-1017.iso.gz

      I also tried to install the Stable Version 1.2.3 release but can not detect the network cards.

      Thank for the help.

      Lunar12 :)

      1 Reply Last reply Reply Quote 0
      • A
        Aziz
        last edited by

        I'm having the exact same problem, thoguh I've only tried 1.2.3

        Here are my specs:
        Jetway JNC9C MiniITX board with Atom N550
        Realtek onboard LAN x 2
        2GB DDR3 RAM
        Intel LAN x 3 Daughterboard
        2.5 Seagata SATA HD

        I've tried both option 1 and option 2 (without ACPI) and disabled ACPI in BIOS.

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

          Just for try, do a install partitioning the disk witsh a small size, like 4gb and see if the install stops at 38% i have this problem in certain pcs with larger disk.

          1 Reply Last reply Reply Quote 0
          • A
            Aziz
            last edited by

            I tried setting this up with the following config but still the same problem:

            Slice - 250GB (whole HD)
            / - 4GB
            SWAP - 4GB

            I'll try with a different Hard Drive. Unfortunately I can't use PfSense 2.0 as this is for a productino server…

            1 Reply Last reply Reply Quote 0
            • A
              Aziz
              last edited by

              Tried with a dfferent hard drive and it worked! (even though first hard drive was brand new)

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

                i have a Dell R210 and can not get 2.0 to install on any drive at all.  What exact drive did you use?  What 2.0 release are you using?

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

                  Ok I think I solved it (worked for me).

                  You must be sure to enable Virtual Technology in the BIOS for the CPU settings.  After that 2.0 Feb 8 installed all the way, (use to hang at 45%).

                  I think Pfsense sees that the CPU is VT capable and attempts to load a module or service to interact with that ability.  However, even though the CPU advertises this capablity, it may not actually have the feature turned on, thus breaking the install.

                  Anyway, no promises, but this worked for me.

                  1 Reply Last reply Reply Quote 0
                  • H
                    hikeonpast
                    last edited by

                    I have the same issue on an R310 (installation stalling at 38% complete), BIOS 1.5.3 with an Intel X25-V SATA SSD trying to install 2.0 BETA5-amd64-20110216-1710.

                    Setting processor Virtualization Technology did not work for me.

                    Using a 2GB primary partition instead of the whole 40GB disk got me from stalling at 38% (/usr/local/bin/cpdup -vvv -I -o /usr /mnt/usr) to stalling at 45% (/usr/local/bin/cpdup -vvv -I -o /usr /mnt/usr) complete.

                    Using a regular 250GB SATA drive yields the same results–I can get to 45% if I use a 2GB partition.

                    Any other suggestions?

                    1 Reply Last reply Reply Quote 0
                    • H
                      hikeonpast
                      last edited by

                      I was able to get the installation to complete by setting:

                      Turbo Mode = OFF
                      C-states = OFF
                      Virtualization Tech = ON

                      BUT…when I went to repeat the install on a second, identical machine, it did not complete.  :-\

                      I was unable to find a configuration that would allow installation to complete, but cloning the first disk seems to have worked.  I still don't understand why processor settings would impact the installation process, but they definitely seem to have an effect.

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

                        power edge R210
                        how not detect ide or scsi ?, pf 2.0 Feb 8 installed
                        what bios setting on ?

                        thks

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

                          @Aziz:

                          Tried with a dfferent hard drive and it worked! (even though first hard drive was brand new)

                          please help me

                          i cant detect ide or scsi ?, pf 2.0 Feb 8 installed
                          what bios setting on ?
                          i change HD seagate 80GB SATA

                          thks for all

                          1 Reply Last reply Reply Quote 0
                          • H
                            heper
                            last edited by

                            A "solution" to get passed hardware issues is to virtualize it using VMware ESXi (it's free)

                            I have a 2.0 Beta snapshot running on a Dell R310 with SAS 6IR controller with 2x SATA in raid1 using ESXi …. it works beautifully

                            Be sure to turn on virtualization stuff in bios as noted in previous posts

                            i never tried to install pfsense bare-metal .... A xeon quadcore is wasted when it has to run idle all the time ;)

                            1 Reply Last reply Reply Quote 0
                            • A
                              Alexios
                              last edited by

                              Hallo,

                              i had the same problem

                              PC HP DC7800 and my installation with Pfsense 2.0 RC1 stopped everytime at
                              38% in step /usr/local/bin/cpdup -vvv -l -o /usr/mnt/usr  -too.

                              I had installed earlier on the same PC Pfsense 1.23 and it worked.
                              First I checked the Bios settings, second different installation settings - no solution.

                              But then i remembered that the only difference on my PC between Pfsense 2.0 RC1 and my Pfsense 1.23 installation was my Keyboard.

                              It sounds suspicious but with my Fujitsu-Siemens Keyboard PX PS2 my installation stopped everytime at 38% in step  /usr/local/bin/cpdup -vvv -l -o /usr/mnt/usr .

                              With my Cherry Keyboard G83-6744 USB the installation with Pfsense 2.0 RC1 works fine now.

                              Someone made the same experience?

                              1 Reply Last reply Reply Quote 0
                              • J
                                jeebsion
                                last edited by

                                Just to share my experience with the machine recently after countless of tries ..

                                Instead of installing directly on the R210 machine, I did the installation on a desktop PC attached to the server's HDD (took the HDD of the R210 then connect it to the desktop PC). Then move the HDD back into R210. Everything went well after that :-)

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

                                  @jeebsion:

                                  Just to share my experience with the machine recently after countless of tries ..

                                  Instead of installing directly on the R210 machine, I did the installation on a desktop PC attached to the server's HDD (took the HDD of the R210 then connect it to the desktop PC). Then move the HDD back into R210. Everything went well after that :-)

                                  ohhh ya… nice info, thks all :)))

                                  1 Reply Last reply Reply Quote 0
                                  • B
                                    bpf
                                    last edited by

                                    Hello everybody, first post here…

                                    FYI: I just installed a R210 with an Intel PCI add-on card having 4 ports (Intel Gigabit ET appearing as igb0..3) so the complete system has 6 Ethernet ports. To pass the 38% mark when the install process shows '/usr/local/bin/cpdup -vvv -l -o /usr/mnt/usr', I had to disable all multi core features (virtualization and all).

                                    I kept this setup even after the install otherwise pfsense would freeze when booting (showing 'starting DHCP' while DHCP is not used) and even after installing the SMP kernel option at the end of the install process.

                                    Once the system worked, I did not try to restore the CPU features in the BIOS since one does not break something that works  :-\

                                    Currently I use pfsense to bridge 5 interfaces together to shape the WAN traffic and the system is stable using not much CPU (another reason why I did not made new tries with the BIOS features).

                                    Installing pfsense was fine once the BIOS features problem was understood (thanks to this topic), while first trying to use zeroshell lead nowhere: no easy install procedure, no operationnal NIC driver for the R210 (embedded ports or igb ports), I guess the kernel of ZS has no recent driver/modules for those NICs.

                                    I never used pfsense before and found the web configurator to be rather intuitive. However I did not find a way yet to use traffic shaping on custom ports (we have specific applications using port numbers not officially defined at IANA). I made the traffic shaping setup using the 'dedicated links' wizard.

                                    I setup the SNMP server (for MRTG) and the 'bridge0' interface does not show any activity while per interface traffic is available: being able to see the complete bridge activity would be nice.

                                    All in all I'm happy with pfsense, thanks for the good work !

                                    1 Reply Last reply Reply Quote 0
                                    • M
                                      m4rcu5
                                      last edited by

                                      Another R210 user here.

                                      I noticed the hanging at 38% also. Strange thing: this was with the 64bit Beta5, the 32bit worked.

                                      -m4rcu5

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

                                        I have running Ubuntu Server on Dell PowerEdge R310 (which is NOT gateway) and pfSense is installed on KVM-Qemu (BACKUP gateway), this is great becouse I can do volume snapshots or just copy VM hdd image without any problem with VM recovery and host-os is isolated from WAN. I did not experienced any network performance issue, yet. Also, no problem with installation.

                                        Most important is to have to use BRIDGE networking in HOST OS:
                                        cat /etc/network/interfaces

                                        # The loopback network interface
                                        auto lo
                                        iface lo inet loopback
                                        
                                        # Bridge: network card connected to the core switch
                                        auto br0
                                        iface br0 inet static
                                        	address 192.168.0.1
                                        	netmask 255.255.255.0
                                        	gateway 192.168.0.254
                                                bridge_ports eth0
                                                bridge_stp off
                                                bridge_fd 0
                                                bridge_maxwait 0
                                                #metric 1
                                        
                                        #bridge: network card connected to switch with 2 DSL modems
                                        auto br1
                                        iface br1 inet manual
                                        	bridge_ports eth1
                                        	pre-up ifconfig eth1 up
                                                bridge_stp off
                                                bridge_fd 0
                                                bridge_maxwait 0
                                                #metric 1
                                        

                                        cat /etc/libvirt/qemu/pfSense.xml

                                         <domain type="kvm"><name>pfSense</name>
                                          <uuid>6b279064-5f3e-aa45-1e78-1615e9759419</uuid>
                                          <memory>1048576</memory>
                                          <currentmemory>524288</currentmemory>
                                          <vcpu>2</vcpu>
                                           <os><type arch="i686" machine="pc-0.12">hvm</type></os>
                                           <features><acpi><apic><pae></pae></apic></acpi></features>
                                           <clock offset="utc"><on_poweroff>destroy</on_poweroff>
                                          <on_reboot>restart</on_reboot>
                                          <on_crash>restart</on_crash>
                                           <devices><emulator>/usr/bin/kvm</emulator>
                                             <disk type="file" device="cdrom"><driver name="qemu" type="raw"><target dev="hdc" bus="ide"><readonly></readonly></target></driver></disk>
                                             <disk type="file" device="disk"><driver name="qemu" type="raw"><source file="/var/lib/libvirt/images/pfSense.img">
                                               <target dev="sda" bus="scsi"></target></driver></disk>
                                             <interface type="bridge"><mac address="52:54:00:1b:2c:4f"><source bridge="br1"></mac></interface>
                                             <interface type="bridge"><mac address="52:54:00:22:1a:c4"><source bridge="br1"></mac></interface>
                                             <interface type="bridge"><mac address="52:54:00:21:2c:4d"><source bridge="br0"></mac></interface>
                                             <console type="pty"><target port="0"></target></console>
                                             <console type="pty"><target port="0"></target></console>
                                        
                                             <graphics type="vnc" port="-1" autoport="yes"></graphics></devices></clock></domain> 
                                        
                                        1 Reply Last reply Reply Quote 0
                                        • ?
                                          Guest
                                          last edited by

                                          On a machine I built from spare parts, I had the same issue. 32bit worked, 64bit did not, but that was almost a month ago now. I plan to try 64bit once 2.0 is stable.

                                          @m4rcu5:

                                          Another R210 user here.

                                          I noticed the hanging at 38% also. Strange thing: this was with the 64bit Beta5, the 32bit worked.

                                          -m4rcu5

                                          1 Reply Last reply Reply Quote 0
                                          • S
                                            scheidell
                                            last edited by

                                            same here, dell 850 and 860.  you might be right about the usb.. I see it waiting to mount usb… with no usb kb. 
                                            but my workaround was to wipe out the first 512 bytes of the boot drive and it worked find.

                                            some strange conflict between usb drivers and kb and hd?

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