Intel RAID

[Wolfbane8653]

Have you tried changing your “Image Type” to “Multiple Partition Image - ALL Disks (Non-resizable)” ?

[Tom Elliott]

I don’t have a mapper (dm-raid or mdadm) applied to the init, nor the kernel.

Something, possibly, for the future?

[Adam Taylor]

Yea…that is what is required(mdadm). I looked for it and could not find it in init so that’s why i asked. I just know that RAID 1 is starting to become standard (we even have some laptops now with 2 drives in raid 1…lol) in ALOT of cases around here where i work. Just figured i would see if it was on anybody’s radar.

Thanks,

[Adam Taylor]

Sorry Wolf…didn’t see yours. Yes, i was using MPI - non-resizeable for the image type as to try and not break the array while imaging.

[Tom Elliott]

Rebuilding inits with dmraid and mdadm tools, as well as currently compiling 3.18.0 kernels with support for RAID devices.

When it’s pushed, do you mind trying it out, and see if anything better happens?

[Tom Elliott]

2759 has the mdadm/dmraid tools in the init and raid tools built into the kernel.

Hopefully this will suite your needs.

[eddy]

Hi,

this is an old thread but I have the same problem.

I’m using Dell Precision Rack 7910 with RAID1.

Is the INTEL RAID working now with FOG?

[Wayne Workman]

@eddy According to Tom’s last posts, the support should be there… no way to really know but to try. Either way, you’ll need to move to the latest FOG Trunk version to find out. Here’s how you do that:

https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

[nengelhardt]

It wouldn’t be optimal, but have you tried the dd method?

[mutant]

The issue is still there
Test on trunk version: 4702 with Optiplex 9020 Raid 0.

[Tom Elliott]

@mutant What is the issue that is still there?

[Tom Elliott]

I don’t know if this will help anybody.

https://github.com/FOGProject/fogproject/pull/53

But I’m not going to try auto mounting raid myself.

Follow the instructions (essentially set the host’s kernelArgs to contain mdraid=true)

[mutant]

putting Host Kernel Arguments “mdraid=true” still result in the same issue that when deploy image it will break the raid and only image one disk.

[Sebastian Roth]

Did you download the new init and kernel files before testing?

[mutant]

Kernel was updated last week when upgrade using git to trunk version 4702.
The git source “S99fog” file does have the $mdraid change.

[Tom Elliott]

Again,

I need more information.

What is happening, what isn’t working? Does the system recognize the volumes at all?

[Wayne Workman]

@mutant said:

9020

I have Dell Optiplex 9020s at work. The factory firmware settings come with the hdd operating in “RAID ON” mode instead of AHCI. I’ve been able to successfully image this system with FOG Trunk. Have you played with these HDD operation mode settings? Does the 9020 have two physical hard drives, or just one? What is not working? Can the system network boot? Can you upload an image? Can you download an image? Can you provide a photograph of the issue you’re seeing?

[mutant]

Upgrade the official published kernel from 4.2.0(Sept 17 2015) to 4.2.1 TomElliott (Sept 22 2015) and test again

Optiplex 9020 with two 500GB physical hard drive.
The system can network boot.
Both of Raid0 and Raid1 test with deploy successfully to boot OS but only deploy to one disk.

Raid1 (Mirror) 465.8GB
Deploy a sysprep windows7 image result in degraded raid as it only deploy to one disk.
Raid0 (Stripe) 931.5GB
Deploy a sysprep windows7 image result in failed raid as it only deploy to one disk.
Raid0 Image


Raid1 Image

[ch3i]

@mutant Not sure but I think that FOG only see the disk not the volume.

[Sebastian Roth]

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!