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

    PowerEdge 1950 Boot Failure

    Problems Installing or Upgrading pfSense Software
    2
    6
    2.4k
    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.
    • A
      astrivoip123
      last edited by

      I am currently having an issue getting PFSense to install on some of my Dell PowerEdge 1950 III servers.  I do however, have a few Dell PowerEdge 1950 II and III servers that are running PFSense just fine. (details below:)

      Failing System (actually 3 different systems, all with identical hardware…)
      PowerEdge 1950 III
      CPU:  2x Intel XEON L5420
      RAID:  PERC6/i Integrated  (fw:  6.3.0-0001)
      PFsense builds attempted:  "pfSense-LiveCD-2.1.5-RELEASE-amd64-20140825-0744", "pfSense-LiveCD-2.0.3-RELEASE-amd64-20130412-1027", "pfSense-2.0.1-RELEASE-amd64"

      No matter which ISO i use, the results are the same.
      Last message when system hangs on boot [default]:  device_attach: fdc0 attach returned 6
      Last message when system hangs on boot [Verbose Logging]:  device_attach: fdc0 attach returned 6
      Last message when system hangs on boot [Without ACPI]:  IPsec: Initialized Security Association Processing.

      Working System
      PowerEdge 1950 II
      CPU:  2x Intel XEON L5335
      BIOS:  2.7.0
      RAID:  PERC6/i  (fw:  6.3.0-0001)
      Server was built with "pfSense-2.0.1-RELEASE-amd64", and has been upgraded and currently running to "pfSense-LiveCD-2.1.5-RELEASE-amd64"
      Note:  The next message displayed after "device_attach: fdc0 attach returned 6" is:

      uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0

      Another Working System (most like the non-working server):
      PowerEdge 1950 III
      CPU:  2x Intel XEON L5420
      BIOS:  2.7.0
      RAID:  PERC6/i Integrated  (fw:  6.3.3-0002)
      Server was built with "pfSense-2.0.1-RELEASE-amd64", and has been upgraded and currently running to "pfSense-LiveCD-2.1.5-RELEASE-amd64"
      Note:  The next message displayed after "device_attach: fdc0 attach returned 6" is:

      uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0

      I'm really at a loss, any guidance would be much appreciated.

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        Get into the BIOS and turn off the floppy controller?

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

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

          Sorry i meant to add a bit more before submitting…

          I have ready many many posts, that say to try the following:
          Disable Floppy drive in BIOS.  -- No FD installed, nor anywhere in BIOS to disable.
          Disable ACPI in BIOS, and boot PF with no ACPI -- Tried no change.
          Uninstall 1 CPU -- Did not try, since i have other servers with 2x CPUs.  maybe last resort, but that doesn't seem to be likely...  Though i did try and change from 4 cores to 2 cores, no change...
          Escape to Loader Prompt and use the "hint...."  to disable Floppy.  No change, still tries to load/detect FD0
          Some say PERC isn't supported -- That seemed to be related to much much older versions of FreeBSD and pfSense, as again i have a 2nd gen and 3rd gen that are in production and working properly.

          I in fact have 1 confirmed 3rd Gen 1950, with the same exact components (CPU, RAM, HDDs, Raid Controller), as 3 others.  1 works, and has been in production for about a year now, the other 3 do not boot.

          On my similar 3rd gen, i will see about breaking the Raid 1, by removing 1 drive, and installing/importing the single disk into the new system.  I'll try that and post the results

          Unless someone thinks it has to do with UART component, as that is the next item in line to be loaded when pf boots properly?

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

            I've attempted to swao in a Hard-Drive from a running and working system (identical hardware components), and no go.  Still fails at the floppy drive attach.

            I went through all BIOS settings on the working, and compared to the non-working.  Still no boot.

            I do also have an ISO "pfSense-LiveCD-2.1-RELEASE-amd64-20130911-1816" that i'll try next.  This is the only one i haven't tried.  I'd like to stick to what I already used in the past, ie same ISO.
            I'll be updating firmware and bios on the machine now as well.

            1 Reply Last reply Reply Quote 0
            • DerelictD
              Derelict LAYER 8 Netgate
              last edited by

              I'd try 2.2RC before going backwards.

              Chattanooga, Tennessee, USA
              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
              Do Not Chat For Help! NO_WAN_EGRESS(TM)

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

                Noting the version of Firmware for the Raid Controller between the 2 systems.

                The working system was running Perc 6i Integrated with firmware 6.3.3-0002
                The non working system was running Perc 6/i Integrated with firmware 6.3.0-0001 and 6.3.1-0003

                However when i tried to find 6.3.3-0002 for a Perc6i on Dells Support site under PowerEdge 1950, i could not find it. I then searched Dells site specifically for Perc 6i firmware, and found the proper version 6.3.3-0002 (note NOT for a PERC 6E, but PERC 6i).

                Booted to a live CentOS disk, upgraded the firmware and viola, success!

                Below is the link to the proper firmware:

                http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=F96NR

                This can be marked as Solved.  I see that many people out there find this same issue, and i hope they find this.

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