@nils98 I don’t know your prerequisities.
Our machines get delivered with a preinstalled windows.
The RAID1 is also already assembled.
We do not create a raid 1 via mdadm in fog. Also i did not inject any drivers for VROC.
I think /dev/md0 get’s created because of the use of the kernel-parameter “mdraid=true” but it’s empty.
If you check in bios/uefi. Is there a raid 1 shown? If not can you create one? I never had problems to see my preassembled VROC raid1 with “lsblk” in debug mode.
@nils98 I don’t know your prerequisities.
Our machines get delivered with a preinstalled windows.
The RAID1 is also already assembled.
We do not create a raid 1 via mdadm in fog. Also i did not inject any drivers for VROC.
I think /dev/md0 get’s created because of the use of the kernel-parameter “mdraid=true” but it’s empty.
If you check in bios/uefi. Is there a raid 1 shown? If not can you create one? I never had problems to see my preassembled VROC raid1 with “lsblk” in debug mode.
@Ceregon said in Problem Capturing right Host Primary Disk with INTEL VROC RAID1:
Also it seemed that one partition of my disk (40 GB / NTFS / 64k Clustersize) get’s borked at capture. Partclone recognized it as raw. After the deployment i had to format that partition again.
So after a few tests i can say, that a freshly formated parttion with that parameters is borked on the source-host directly after capturing.
The deployed image also has the borked partition. Maybe the clustersize is the problem here? Sadly we need it.
So i guess we will have to manually format the partition and set the correct NTFS-rights.
@george1421 Nice i will do that. I had the fear, that when we will have machines without software-raid that will make problems. Thank you
Hi there,
after my recent post i wanted to work out a method to simplify setting the Host Kernel Arguments to “mdraid=true” for new clients.
I created in the web-management a new group and set the Group Kernel Arguments to “mraid=true”.
When i add a Host to this group in the web-management this argument gets correctly applied to the Host.
When i boot into PXE and add the Host to this Group while Full Registration the argument doesn’t gets applied to the Host correctly. I select in Full Registration, that i want to deploy an image directly. I need to get into web-management and simply click update in the group.
Always updating the Group in web-management is not that practical.
Is there a method to get this running?
So i think i got a solution.
With “Host Primary Disk = /dev/md124” i could never let Partclone capture the whole drive of the RAID 1 i needed, because it always jumps to /dev/md0.
So i tinkered around a bit and first tried to stop the RAID with:
mdadm --stop /dev/md124
After that i made it reassemble at md0 with:
mdadm --assemble --run --force /dev/md0 /dev/sda /dev/sdb
Capturing went fine. But when i tried to deploy to the same machine i got the error “Fsync error: errno 5”
After some searching around i tried to recreate the array with:
mdadm --create /dev/md0 --assume-clean --level=1 --verbose --raid-devices=2 /dev/sda /dev/sdb
This let me deploy the image without a partclone error. But after all partitions got written i got a mount error. A reboot into the Windows got me a bluescreen. So i assumed i had a dead end here. Has maybe something to do with the Supberblock.
So i took in the idea of mounting the drive what brought me finally to Symlinks.
/dev/md0 get’s initialized but is empty. I personally don’t really now why it’s there.
So i just removed it:
rm /dev/md0
And created my Symlink:
ln -s /dev/md124 /dev/md0
This way i am abled to capture the image with the Setting "Multiple Partition Image - Single Disk (Not Resizable) without an error or a warning.
The deployment went good. System boots and the RAID 1 is fine. Will try on monday “Single Disk Resizable” capture and deployment. After that i will try to implement the commands in a postinit script. Maybe i can work with groups of hosts to decide when this postinit script is used. I haven’t read myself into that part of fogproject yet.
Also it seemed that one partition of my disk (40 GB / NTFS / 64k Clustersize) get’s borked at capture. Partclone recognized it as raw. After the deployment i had to format that partition again.
I am not 100% sure. Maybe i got something messed up before capture and the partition was borked from the beginning. Will check on that.
If that’s not the case i had the idea to run a postdownload script to format that partition and create some folders for me.
Besides a folder structure we prepared for a database server the partition is an empty placeholder anyway.
Thanks for your input. I play around a bit.
Hi there,
i am relatively new to the fogproject.
I got it up running and working correctly.
The problem is, that we want to capture Windows 11 Machines with INTEL VROC RAID1.
At the first look capturing default works fine. But at deployment just one disk of the RAID 1 gets written. Because of that the RAID 1 is borked and needs to get set up again.
I checked other articles in this forum and set the kernel-parameter “mdraid=true”.
In debug-mode i checked with the command lsblk that my RAID1 needs to be adressed as “/dev/md124” and set Host Primary Disk to that value.
But if i try to capture as Single Disk Resizable fog still adresses /dev/md0
Where did i turn wrong?
