multiple disk problem

[Sebastian Roth]

@badhonsoam Just had an idea what you could try as a workaround:

• Create three new image definitions (names img_vda, img_vdb and img_vdc)
• Set img_vda to type “Multiple Partition - Single Disk” but img_vdb and img_vdc to “Raw Image”
• Edit the host settings and set Primary Disk option to /dev/vda and Image Association to img_vda to and do a capture the first drive.
• Edit the host settings and set Primary Disk option to /dev/vdb and Image Association to img_vdb to and do a capture the second drive.
• Edit the host settings and set Primary Disk option to /dev/vdc and Image Association to img_vdc to and do a capture the third drive.

[badhonsoam]

@Sebastian-Roth

on this step

Edit the host settings and set Primary Disk option to /dev/vdb and Image Association to img_vdb to and do a capture the second drive.

[badhonsoam]

@Sebastian-Roth any suggestion

[Sebastian Roth]

@badhonsoam Too bad I didn’t check the actual script code when I came up with this idea to see if this could actually work. Seems like FOS needs to see partitions to be able to capture anything.

As I hope this might help you I did “quick-fix” this and build a new init file for you: http://fogproject.org/inits/init_allow-non-partition.xz

Rename the original init.xz in /var/www/html/fog/service/ipxe/ on your FOG server and put the newly downloaded as init.xz in that same directory.

With that new init file you need to manually change one of the FOG settings. Go to the FOG web UI -> FOG Configuration -> FOG Settings -> FTP Server and increase KERNEL RAMDISK SIZE from 127000 to 275000.

If you run into some compatibility issue with the kernel, try downloading the latest here: https://fogproject.org/kernels/ (or through the FOG web UI)

[badhonsoam]

@Sebastian-Roth said in multiple disk problem:

SIZE

as you asked i tried like this which is showing below error like previous

[badhonsoam]

This post is deleted!

[badhonsoam]

This post is deleted!

[Sebastian Roth]

@badhonsoam See there is a slight difference between the messages. This time it printed “A warning has been detected!” instead of “An error has been detected!”.

It should sit at the warning for 60 seconds and then go ahead! So you just need to be patient enough and leave it.

[Sebastian Roth]

@badhonsoam said in multiple disk problem:

is their any issue with lvm disk?

As I told you ceph filesystem is something very special. As well it uses LVM which FOG is not able to handle natively. Because of that I told you to try using RAW image type and modified the init for you.

[badhonsoam]

@Sebastian-Roth i am trying another vm doesnot contain ceph osd

[Sebastian Roth]

@badhonsoam Did you read my other message?? Just wait 60 seconds after you see the warning and it should proceed to upload the image!

[badhonsoam]

@Sebastian-Roth sorry for late reply. looks like its ok now