• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Intel RAID

Scheduled Pinned Locked Moved
Hardware Compatibility
11
30
16.6k
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.
  • S
    Sebastian Roth Moderator
    last edited by Sep 24, 2015, 4:45 PM

    What does it look like on the original system?? If this is a real RAID controller you shouldn’t see the two disks in Windows! A real RAID is not configured in Windows/Linux but has it’s own (BIOS-like) configuration. You’d have to configure the RAID on the target system before cloning. This cannot be done by FOG!

    Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

    Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

    W 1 Reply Last reply Sep 24, 2015, 6:09 PM Reply Quote 1
    • W
      Wayne Workman @Sebastian Roth
      last edited by Sep 24, 2015, 6:09 PM

      @Uncle-Frank Very true.

      When you’re using hardware RAID, the OS is oblivious to it. Even FOG would be oblivious to a good hardware RAID setup.

      Since it’s clearly not hardware RAID, or a good hardware RAID - use “Multiple Partition Image - All Disks”

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
      Daily Clean Installation Results:
      https://fogtesting.fogproject.us/
      FOG Reporting:
      https://fog-external-reporting-results.fogproject.us/

      1 Reply Last reply Reply Quote 0
      • S
        Sebastian Roth Moderator
        last edited by Sebastian Roth Sep 25, 2015, 4:14 AM Sep 25, 2015, 10:11 AM

        Re-reading your post and trying to find out a bit more about the RAID in Optiplex 9020 I noticed that I was totally wrong, sorry! This is not a real RAID but a fakeraid (as you already said in your first post 😉). It is Intel ICH8R (82801HR) southbridge which they call a ‘firmware RAID’. After setting it up properly on the target machine (http://www.dell.com/support/article/us/en/19/SLN153494/EN) you still need to address this in linux as well.

        Do you have ‘Host Primary Disk’ configured for those hosts? FOG is not intelligent enough yet to find out about (fake)RAID setup and use the correct device just by itself! You might be fine not setting ‘Host Primary Disk’ for the host you are getting the image from as /dev/sda should be equal to /dev/sdb (FOG uses /dev/sda as default). But you need to set this to /dev/md0 to make FOG properly deploy to your RAID.

        By the way: “Multiple Partition Image - All Disks” probably won’t help you as the RAID array won’t be in sync if it is not properly deployed through the correct device file AFAIK.

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        1 Reply Last reply Reply Quote 1
        • M
          mutant
          last edited by mutant Sep 25, 2015, 10:31 AM Sep 25, 2015, 4:17 PM

          Set the “Host Primary Disk” to /dev/md0 and test again and still no go.

          Went into debug mode to check the raid status

          mdadm -D /dev/md0
          shows the status of md0 is “inactive”

          cat /proc/mdstat
          shows only md126 is “active” and md127 is inactive

          The problem seems that FOG does not assemble /dev/md0 properly

          Re-run the task after setting the “Host Primary Disk” to /dev/md126
          still not go , it shows “Problem opening /dev/md126p1 for reading! Error is 2. The specified file does not exist!”

          The problem seems that FOG try to read from /dev/md126p1 instead of /dev/md126

          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by Sebastian Roth Sep 25, 2015, 5:53 PM Sep 25, 2015, 11:36 PM

            Well, seams like it all depends. I cannot give you an easy solution like “just do it this way and you’ll be ok” as I don’t have a similar machine here to test.

            What do you see when running the following command in debug mode: gdisk -l

            Maybe those links are helpful: http://serverfault.com/questions/226053/intel-matrix-storage-raid-and-linux-mdadm and https://forums.gentoo.org/viewtopic-t-888520-start-0.html

            Also check out the device files you have in /dev/md/ and let us know.

            Edit: fakeraid is even more complicted than I had in mind: https://raid.wiki.kernel.org/index.php/RAID_superblock_formats
            See if you can find out how your RAID was setup in the first place. Then we might be able to find a solution to image this thing too.

            Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

            Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

            1 Reply Last reply Reply Quote 0
            • W
              Wayne Workman
              last edited by Sep 26, 2015, 4:35 AM

              Just posting some of my own success with RAID and fog.

              I have a genuine hardware RAID setup at the house, I just got done installing CentOS 7 on it.

              It’s setup with two sata hard drives in RAID 1 configuration.

              I was having a very hard time trying to access the logical RAID 1 volume, and the below kernel options weren’t working, and I wasn’t having luck with finding what the system was refering to it as either.

              However - I think I might have come across a better solution.

              fdisk -l clearly shows two disks with exact size, model, and partitions.

              I simply created a new a new image using multiple partition image - single disk (not resizeable)

              and obviously I assigned that to the host, and for “host primary disk” I just entered /dev/sda and it worked like a charm.

              I’m a little curious about how my RAID 1 controller card would react if FOG tried to resize /dev/sda alone…

              Perhaps the RAID card will make those changes to sdb ? maybe the RAID 1 volume will degrade! lol

              I have no idea… but…

              this is a really good way to get an image off of a RAID 1 system and then put it onto a NON-RAID system. 🙂

              I’ll experiment with this and the resizable images.

              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
              Daily Clean Installation Results:
              https://fogtesting.fogproject.us/
              FOG Reporting:
              https://fog-external-reporting-results.fogproject.us/

              1 Reply Last reply Reply Quote 0
              • M
                mutant
                last edited by Oct 15, 2015, 2:37 PM

                When setting the “Host Primary Disk” to /dev/md126 because there is no /dev/md0.

                The following error message show up when restore a resizable windows 7 sysprep image.

                Problem opening /dev/md126p for reading! Error is 2.
                The specified file does not exist!
                Problem opening /dev/md126p for reading! Error is 2.
                The specified file does not exist!

                • Processing Partition: /dev/md126p1 (p1)
                • Partition File Missing: /images/W7/d1pp1.im*
                  Problem opening /dev/md126p for reading! Error is 2.
                  The specified file does not exist!
                  Problem opening /dev/md126p for reading! Error is 2.
                  The specified file does not exist!
                  Problem opening /dev/md126p for reading! Error is 2.
                  The specified file does not exist!

                It looks some kind of fog bugs when processing fakeraid Raid0 partition.

                It has problem to properly read the raid0 partition and it tries to read d1pp1.im* file instead of d1p1.im* file.

                1 Reply Last reply Reply Quote 0
                • S
                  Sebastian Roth Moderator
                  last edited by Sebastian Roth Oct 15, 2015, 11:25 AM Oct 15, 2015, 5:10 PM

                  I am sorry but I feel pretty lost with this as I don’t have such a machine here to test!

                  The only thing I can offer is to go through this again from the start step by step. Just an offer. It’s up to you if you want to.

                  Let’s start with the client you are getting the image from. Configure a complete new image for that client in FOG and make it Multiple partition image - single disk (not resizeable). The run a debug session for that client, boot it up and wait till you get to the command shell. Then run the following commands and post the full output here in the forums or upload the text files. Replace x.x.x.x with the IP address of your FOG server.

                  mkdir -p /mnt
                  mount -t nfs -o rw,nolock x.x.x.x:/images/dev /mnt
                  mdadm --examine /dev/sd? > /mnt/mdadm_examine.txt
                  cat /proc/mdstat > /mnt/mdstat.txt
                  mdadm --assemble --scan --verbose > /mnt/mdadm_assemble.txt
                  ls -al /dev/md* > /mnt/md_devices.txt
                  umount /mnt
                  

                  I just typed and copied those commands without testing. There might be typos.

                  Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                  Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                  J 1 Reply Last reply Jun 20, 2016, 6:19 PM Reply Quote 0
                  • J
                    jpmartin @Sebastian Roth
                    last edited by jpmartin Jun 21, 2016, 8:52 AM Jun 20, 2016, 6:19 PM

                    @Developers , @Senior-Developers

                    I’m attempting to capture an image of a Lenovo Thinkpad W530 in Raid0.

                    On latest trunk as of today at 9am.

                    mstat.txt
                    mdadm_examine.txt
                    mdadm_assemble.txt (This file is empty. I ran the command several times and it never dumped any data into the .txt file)
                    md_devices.txt

                    Host options are :

                    kernel arguments: mdraid=true
                    primary disk: /dev/md126

                    When running as “single disk - multiple partitions”, it goes great until it checks for partitions and then returns:

                    “Could not find Partitions”

                    Running a capture now as “Multiple Partitions - All Disks”

                    Host options:

                    kernel arguments: mdraid=true
                    primary disk: [Empty]

                    Only showing sda1 in part clone view, hopefully it will start sdb immediately after.

                    EDIT: It appears it didn’t. Only made a RAW image of sda1.

                    1 Reply Last reply Reply Quote 0
                    • george1421G
                      george1421 Moderator
                      last edited by Jun 22, 2016, 12:35 PM

                      Cross linking post: https://forums.fogproject.org/topic/7851/intel-raid0-image-capture

                      We now know what is going on with this and there is a work around pending.

                      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                      1 Reply Last reply Reply Quote 2
                      • 1
                      • 2
                      • 2 / 2
                      • First post
                        Last post

                      147

                      Online

                      12.0k

                      Users

                      17.3k

                      Topics

                      155.2k

                      Posts
                      Copyright © 2012-2024 FOG Project