Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-17150

Installation when using raid

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Not an issue
    • Affects Version/s: 13
    • Fix Version/s: None
    • Component/s: Installation
    • Labels:
      None
    • ToDo:
    • Asterisk Version:
      13
    • Distro Version:
      1712-2
    • Distro:
      FreePBX Distro

      Description

      We have a demo PBX using a gigabyte motherboard with built in raid that had an older version of FreePBX on it that installed with out issue.

      We tried to install 1712-2 on a new PBX with a gigabyte motherboard with raid and the software would not get past the storage selection.  We then tried to install 1712-2 on the demo PBX with same results.  Both PBX's installed fine with an older FreePBX distro (I do not know the exact version they tested).

       

      We had to disable raid on the motherboard and let FreePBX handle raid.

      Motherboards we had this trouble on: 

      Gigabyte - GA-H270N-WIFI Mini ITX LGA1151 Motherboard (no longer in our possession)
      Gigabyte - GA-H97N-WIFI Mini ITX LGA1150 Motherboard 

      We keep running into this issue (about 3 times now) and the solution is to always disable the built in raid.. but honestly I'd prefer Freepbx to not care about the motherboard raid and just see the single drive (it does see the drive, just will never format/install to it).

       

       

       

       

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                atcs atcs
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

                  Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.