host restarted when deploy image

[saif]

@Wayne-Workman i will try now
thx

[Sebastian Roth]

To me this sounds like a soft RAID thing as RAW capture and deploy seem to work. I don’t really think we can handle this in FOG. You need to create the RAID arrays by hand before deploying. Then it might work. Or just use raw image type as the soft RAID infos will be in the RAW image then.

[george1421]

@Wayne-Workman said in

Beyond that, I think that @george1421 knows about RAID in this particular model.

If this is the built in raid controller in the T3500, that is what is known as “fake raid”. Really that is a software raid running on an intel ich9 or ich10 raid controller. This is a windows only RAID or a windows software raid. Without the windows raid driver you may be hard pressed to read this array for cloning. To linux I believe this raid controller will just present the disk array as jbod.

It would be interesting to know if you booted a live linux distro like ubuntu desktop from CD, can it see this raid array? If so then there might be some hope to image this with fog.

[saif]

@Sebastian-Roth the RAID is configured and i have windows working on it
do you mean that FOG cant deploy RAID?
thx for reply

[saif]

@george1421 yes its built in RAID, i will try to boot from live linux and check
BUT why do i need a RAID driver under windows? the FOG will make a clone for the volume and the windwos will not start to use this driver
thx

[saif]

i tried to boot from ubunto or centos and it didnt show the RAID volume

[george1421]

@saif said in host restarted when deploy image:

@george1421 yes its built in RAID, i will try to boot from live linux and check
BUT why do i need a RAID driver under windows? the FOG will make a clone for the volume and the windwos will not start to use this driver

Sorry I should have explained my self a little better. There are 2 main types of raid controllers (generally) and one hybrid. There are hardware raid controllers, software only raid controllers, and then hybrid raid controllers.

The more common is a hardware raid controllers where it has its own microcontroller that manages the disks. It runs its own special software and then presents the disk array to the operating system or bios as just a single disk volume. There are software raid controllers that typically function as part of the OS. You will find this type of raid controller in higher end unix systems. The software only raid controller us all done in the OS and uses the main processor to manage the disks. The last type is a hybrid raid. In that some of the disk control functions are done in hardware and some in the OS software, this kind of gives you the best of both worlds. You will get some performance acceleration with the hardware without the expense of having a dedicated raid microcontroller. The hybrid raid is managed by the OS so it requires to OS to maintain the integrity of the raid. Without the OS you have no raid functionality.

So with the T3500 they have the hybrid raid setup that comes with a windows driver. To linux (or actually windows without the software raid driver) your raid array looks just like a just a bunch of disks (jbod). Individual disks with no real structure, and in your case since they are in a raid 5, no intelligent data because of the disk striping.

While I can’t speak for the FOG developers, but cloning this type if disk structure is beyond the scope of the fog project.

[saif]

@george1421 thanks for the explaining
appreciate
i will try to test a non RAID disk and see

[Wayne Workman]

@george1421 Well that explains a whole lot… I have RAID cards that present multiple disks to the OS, and I’ve found that ONLY CentOS 7 has the right kernel parameters/modules out-of-the-box that can make it work… Fedora fails miserably at trying to use the RAID card with simple configurations like RAID 1, and RAID 0.

I will be sure to get a real RAID card in the future when I buy one.

[Sebastian Roth]

I am marking this solved as I think George’s answer is excellent and should point most users the right way… Couldn’t have phrased it any better