@george1421 said in FOS fails to capture image from md RAID host:

since you referenced my tutorial I assumed you are using the intel raid.

I referenced your Intel RAID tutorial because I found another forum post on mdadm where you linked to it and stated that it was similar in principle. I am actually working on capturing an image from a Linux host with md RAID, and deploying the same image to other hosts with identical hardware.

By way of update, I removed the large sda device (a hardware RAID) and the USB stick, so my disk layout was thus (from the running host OS):

# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 139.8G 0 disk ├─sda1 8:1 0 300M 0 part ├─sda2 8:2 0 30G 0 part │ └─md0 9:0 0 30G 0 raid1 / └─sda3 8:3 0 2G 0 part └─md127 9:127 0 2G 0 raid1 sdb 8:16 0 139.8G 0 disk ├─sdb1 8:17 0 300M 0 part /boot/efi ├─sdb2 8:18 0 30G 0 part │ └─md0 9:0 0 30G 0 raid1 / └─sdb3 8:19 0 2G 0 part └─md127 9:127 0 2G 0 raid1

I then configured the following in FOG, with the noted outcomes:

Host Primary Disk: /dev/md126 (equivalent to md0 on live system above)
Image Type: Multiple Partition Image - All Disks (3)
Host Kernel Arguments: mdraid=true
Outcome: fails to find disks

Host Primary Disk: /dev/md126 (equivalent to md0 on live system above)
Image Type: Multiple Partition Image - Single Disk (2)
Host Kernel Arguments: mdraid=true
Outcome: fails to read partition table

Host Primary Disk: /dev/sdb
Image Type: Multiple Partition Image - Single Disk (2)
Host Kernel Arguments: [not noted. I forget]
Outcome: fails to read partition table

Host Primary Disk: /dev/sda
Image Type: Multiple Partition Image - All Disks (3)
Host Kernel Arguments: [none]
Outcome: capture succeeds. Deployment on new system succeeds. System boots and partition table on sda looks correct. md127 is lost. Partition table on sdb is not correct:

# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 139.8G 0 disk ├─sda1 8:1 0 300M 0 part ├─sda2 8:2 0 30G 0 part │ └─md0 9:0 0 30G 0 raid1 / └─sda3 8:3 0 2G 0 part sdb 8:16 0 139.8G 0 disk ├─sdb1 8:17 0 1G 0 part └─sdb2 8:18 0 138.8G 0 part

I’m not sure if the deployment procedure touched sdb or not. I suspect not. I will try again and watch closer or record it. I suppose I can rebuild my RAIDs from here, but I would of course prefer to have FOG automate that process to the extent possible.

Edit: added FOG settings detail.

@duemti I added an entry in DNS of the router with hostname of a computer. I can ping it from host shell yet in gui it is still connection timed out!
fe8206ef-9c6b-4c6e-a7d8-1075a26f82e6-image.png

9edbc8ed-dbc4-4ec8-aa27-ccb897de0e9a-image.png

Also i can’t do a full registration because it fails with: ‘unsafe hostname entered please try again’

@david-burgess @Wayne-Workman Using the latest dev-branch version you should be able to use disk size or WWN or disk identifier to force disk order. It’s a known issue that NVMe drives get enumerated in different order by the Linux kernel.

Search the forums for “nvme wwn” and you should find a topic with helpful information on this.

@george1421 all good then. Thanks

@begelmir If you look at your config it very similar to what FOG creates if you were to use FOG’s built in dhcp server.

https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Example_1

I’m only providing this as a reference.

In the case of your dhcp server its looking to see if the pxe booting computer is bios or uefi. Then its chaining to 10.10.205.100. I assume that system is where your menuing system is. This menuing system could be duplicated in FOG using ipxe instead of grub, but that’s a bit off point.

From a quick check it appears once you enter the grub world it can’t chain load out of grub except for local devices. Maybe your developers know of a way. I don’t work with grub but only at a basic level.

If you could insert the fog server between pxe booting and your grub menu then we can make it work. So the idea is to pxe boot into FOG menu then either have the default FOG menu be your Grub menu or have a menu selection for Grub.

Now that I think about it I made a usb boot menu using grub that connects to FOG. You don’t get all of the features of FOG, but imaging works. Maybe your developers can take this and update your grub menu. https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image

Forum post ordering. I know the ordering took me some time to get use to. Just remember the latest posts are always right under the original post. When looking at the thread above remember this because if the tutorial takes multiple posts the second post in the thread is always at the bottom of the thread.

We can get a solution for you because we have multiple ways to approach this. You just need to pick the path that works best for your network.

Not all buttons are supposed to be compulsively clicked. 😉

@mgoh I think I can fix the thread for you. Glad you found a solution.

the hint you sent me via chat has solved the problem great.

thank you very much.

@brechtvervaeke For DNSMASQ install I would follow this guide exactly: https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server

To the error, is the fog server on the same IP subnet as the target computer?

@fogbrain That message has 2 causes.

It can’t get an IP address It can’t make a http call to the fog server.

If you watch it boot you should see it get an IP address, if yes then that rules out #1. The second is the FOS Engine will attempt to reach the fog server (as you posted in the error above). If it can’t it will start the sequence over again of querying for dhcp then attempting to contact the fog server. It should do this 3 times then give up. You need to test from the same subnet as the pxe booting computer if you can reach the url you defined in your original post with a different computer on the same subnet as the pxe booting computer.

I don’t think its a spanning tree issue right now. That would usually (but not always) show up in the FOG iPXE menu not loading. You do need to have your switch ports in portfast mode. You can test to see if its spanning tree issue by placing a dumb (read cheap, unmanaged) switch between the building switch and the pxe booting computer. That cheap switch typically would not have spanning tree plus it keeps the building switch port from winking as the pxe booting computer starts up.

I was having the same problem and didn’t read all the way to the bottom. I was looking at the files in /tftpboot and found that the default.ipxe file had a string containing http://ip-address/service/ipxe/boot.php#params or something similar. I inserted fog and it booted up.

@wayne-workman It’s a Dell OptiPlex 3080. I am using FOG’s DHCP because I don’t have access to our company’s router. I have it working now. I’ve captured an image and going to try to deploy it tonight (I work second shift).

I’d love to get packets back and fourth between the wlan0 and eth0 devices so I can join systems to the domain without switching ethernet cables. Trying to work this out.

@207-tech said in Fog Service address is wrong:

/bin/fog.download it states it is unable to locate that directory

fog.download comes from the FOS Linux engine. When it throws that error it should printout the kernel parameters in the error message. Look to see if the old address is still displayed. If yes then look at the storage node configuration to make sure the default storage node has the proper IP address.

@george1421 I want to say thank you very much for your support and help.\It was very professional and fast, thanks again now I can continue enjoy a FOG solution in my environment

Best regards, Boris

@mashley With multcasting only one image is sent out from the server. So all the clients that participate in the multicast image work in lock step. So the speed of your image deployment is based on the slowest computer in the group. You do want to kind of group like systems (performance wise) together in a deployment group to get the best performance. If you have fast computers but one is behind a 100Mb/s link, that one behind the slow link will slow down the entire group.

@bsedash cross linking similar issue: https://forums.fogproject.org/topic/16244/fog-cannot-load-qlogic-network-driver-on-poweredge-r640/2

One solution two fixes. We might have a custom kernel soon to address this issue. I’m just waiting on feedback from the other thread.

@george1421 said in Database connection unavailable:

botched uploads

Nice thanks for the tips, worked