unable to deploy RAID 1 disk

[eistek]

@Jonathan-Cool

then i have added “/dev/md/BALKAN_0” to Host Primary Disk

and i got following error

[eistek]

I have enabled debug mode ;

[george1421]

@eistek Sorry my real job has been very busy today so I have little time at the moment. Jonathan has you on track for a solution. I can say if you are starting with FOG, you started with a very hard target computer. These intel raid controllers are a problem to work with in linux.

I can see from your last image the raid array is /dev/md126 and its currently configured for read only (same problem as Jonathan) as in your case resync=PENDING (means that you just created the array but it hasn’t completed the mirroring as of now). I have a system in my test lab at the same point as you. I hope to spend some time after work hours to see if I can get my test system to activate the array and sync the sectors. If I can then I can give you guidance.

I can say the info you have provided will get us to a solution for you. So please wait until I can get into the lab.

[eistek]

@george1421 You are correct the Raid is just created. Because fog broken my raid configuration. I have deleted and rebuilt raid configuration. I am waiting for your solution thanks for your support

[george1421]

@george1421 Only note to myself

[Wed May 31 root@fogclient ~]# mdadm --create --verbose /dev/md/imsm /dev/sd[a-b] --raid-devices 2 --metadata=imsm
[Wed May 31 root@fogclient ~]# mdadm -C /dev/md124 /dev/md125 -n 2 -l 1
mdadm: array /dev/md124 started.
mdadm: failed to launch mdmon. Array remains readonly

Ok after about 5 hours of working on this I have a solution, there is a missing array management utility that needs to be in FOS to get the array to switch from active (read-only) to active (auto-read-only) [small but important difference]. Once I copied the utility over and recreated the array by hand it started syncing (rebuilding) the raid-1 array. I need to talk to the developers to see if we can get this utility built into FOS.

The document that lead to a solution: https://www.spinics.net/lists/raid/msg35592.html

[Jonathan Cool]

@george1421 said in unable to deploy RAID 1 disk:

Ok after about 5 hours of working on this I have a solution

5 hours ! It’s unbelievable !!
So, if you want some command tests output, tell us and we will help you with pleasure to debug FOG

Many thank for your investigation !

[george1421]

OK we have a functional fix in place now. This fix will only work for FOG 1.4.0 and 1.4.1. You will need to go to where you installed fog from. For git installs it may be /root/fogproject or for svn it may be /root/fog_trunk or what ever. The idea is that there are binariesXXXXXX.zip files. remove all of those files the fog installer will download what it needs again. There will be one binariesXXXXX.zip for each version of fog you installed.

Once those files are removed, rerun the installer with its default values (you already configured). This will download the updated kernels and inits from the FOG servers.

Now pxe boot your target computer with the raid using debug deploy [or capture depending on what you wanted to do] like was done before. Once you are at the fog key in cat /proc/mdstat if md126 now says (auto-read-only) then you win!!. IF it still says (read-only) then you might not have the most current inits. We will deal with that once we see the output of the cat /proc/mdstat.

I was able to deploy an image to a test system in the lab using the intel raid so I know it does work with the new inits.

[Tom Elliott]

@george1421 Correction, it will only work for 1.4.1

[Sebastian Roth]

@george1421 You are absolutely great!!

[george1421]

@Tom-Elliott said in unable to deploy RAID 1 disk:

@george1421 Correction, it will only work for 1.4.1

Then corrected, I do stand.

[eistek]

@george1421
I have downloaded fog.1.4.1.tgz. After extract this file removed binary1.4.1.zip file. Then started the
./installfog.sh file.
After installation finished.

I have checked md126 on debug mode . It was not readonly;

Then i have started to deploy image;

It looks good. I have to leave from Office. we will see the result tomorow
Thanx for everything

[george1421]

@eistek That first screen shot is prefect!!

What it tells us that the newly created raid array is resyncing (copying the master disk to the slave disk and thus building the array). It rebuilding the array at 70MB/s (which is about the top speed of your sata disks).

[eistek]

@george1421

I have got following error when process was about %5

[eistek]

@george1421

i have changed undionly.kpxe to undionly.kkpxe

and now ;

[george1421]

@eistek said in unable to deploy RAID 1 disk:

i have changed undionly.kpxe to undionly.kkpxe

The iPXE kernel only manages the FOG iPXE menu and launching of the FOS image. Once FOS Linux has started the iPXE kernel (undionly.kpxe) is discarded. Changing this boot kernel will not have an impact on the error message you now have.

What these images show is that the FOS linux kernel is crashing. This is typically related to a hardware error. This is only a wild guess but I would say memory (RAM chip) or hard drive.

[george1421]

@eistek Do you have a smaller image you can deploy to this system? The image doesn’t have to run on the target computer, I’m more interested in if it deploys completely to the target computer. I’m looking for one in the 20-40GB range to test deployment. 135GB is a bit rare and I can’t say for sure if FOG can handle that size, I simply don’t know.

According to the partclone info the image failed at about 28GB of the file being transferred to the target computer.

[eistek]

@george1421

Here is the my solution;

1- i have created new clean raid.
2- i have added mdraid= true and /dev/md126 to my host configuration.
3- I have removed one of the raid disk from PC.
4- Started to deploy. Deploying image is finished without any error.
5- Restarted PC and Windows has started without any problem.
6- Then power off the PC and plugged in second disk to PC and turned on .
7- Raid started to rebuild.
8- Rebuild is finished and everything is looks well now

[george1421]

@eistek Well done!!

[eistek]

@george1421

I don’t know why but if i try to deploy with 2 disk pluged in it gives kernel panic.

Special thanx to @george1421 @Jonathan-Cool @Tom-Elliott

[x23piracy]

@eistek well nice that you found a solution but you need to work physical at the machine to solve this, it would be really nice if the problem could be solved while deploying to a working raid instead of letting it rebuild after deploying to just a single drive.

Regards X23