@Tom-Elliott said:
32 bit Init: https://mastacontrola.com/init_32.xz
64 bit Init: https://mastacontrola.com/init.xz
Just in case someone else is reading this and having the same problem and is new to fog and ipxe and what not…
To test out this fix do this…
cd /var/www/fog/service/ipxe
sudo mv init.xz init.bck
sudo mv init_32.xz init_32.bck
wget https://mastacontrola.com/init.xz --no-check-certificate && wget https://mastacontrola.com/init_32.xz --no-check-certificate
sudo chmod -R 775 ./
@Tom-Elliott is on top of this problem
Check out this forum post https://forums.fogproject.org/topic/6315/hp-z640-nvme-pci-e-drive/37
I’m posting my results of testing on the /dev/nvme0n1 type drives with his current inits found here
32 bit Init: https://mastacontrola.com/init_32.xz
64 bit Init: https://mastacontrola.com/init.xz
To use them do the following
cd /var/www/fog/service/ipxe
sudo mv init.xz init.bck
sudo mv init_32.xz init_32.bck
wget https://mastacontrola.com/init.xz --no-check-certificate && wget https://mastacontrola.com/init_32.xz --no-check-certificate
sudo chmod -R 775 ./
Granted by the time dell gets you a replacement it might already be tested enough and the fix will just be in the latest trunk. But that’s what to do in case anyone else is looking.
@Tom-Elliott
Ok I will test every which way just for funzies and report back by editing this post
I won’t test the multiple disk images because I only have one disk in there right now. But I can add in a drive that would get recognized as /dev/sda and make sure it can image that combination if you want.
Download
Single Partition/Resizable - Working!
Multiple Partition/Single Disk - Working!
Multiple Partition/Multiple Disk - Working!
Upload
Single Partition/Resizable - Working! - a few error messages that don’t stop anything
Multiple Partition/Single Disk - Working!
Multiple Partition/Multiple Disk - Working!
@Tom-Elliott
Sorry that it took me so long, I kept getting distracted by some other stuff.
It’s Alive!
It Works!
Amazing!
You’re the best!
I did a debug deploy so I can also confirm that all the variables are now correct…
Shall I test a resizable and a not so unresizable upload?
I’m guessing that you did a uefi image since it wants to use windows boot manager, which I believe is window’s uefi method.
Was secure boot enabled on the computer that you uploaded from, could that cause a problem? I haven’t actually done any successful uefi imaging and haven’t really tried that hard because I’m personally yet to see why it’s worth it when mbr/bios/legacy works so well and I don’t have any 3+TB drives in my windows workstations at work.
I have had success imaging windows 10 with legacy mode, just for a reference, I’m on the latest trunk, but I would bet 1.2 works with it.
Granted I don’t use sysprep, I find that it likes to kill off my default profile. So I just manually uninstall devices in the device manager before imaging. It’s trickier, and involves more work, but it’s done sooner than it takes sysprep to run. But I’m getting off topic.
Have you tried repairing the install with a win 10 disk. Auto repair. What ever the gpt/uefi equivalent of
bootrec /rebuildbcd
bootrec /fixboot
bootrec /fixmbr
is. (Fun fact shift+F10 gets you straight to a command line on a windows install disk instead of waiting to click through the menus)
Or try the windows automatic repair that works like 10% of the time.
You can also use diskpart to make sure the volume/disk/partition that got imaged is active.
disk part
select disk 0
list partition
select partition 1
detail partition
something like that, and then you can set it to active. That was a problem I used to have when I used the altiris imaging system, I’ve never had the problem with FOG.
Granted you shouldn’t have to repair the install after imaging, especially if you run sysprep all proper, but if you can make it work then that might narrow down some possibilities.
Can you disable secure boot in the bios settings on the computer not booting?
Can you make sure secure boot was disabled on the computer you uploaded from, or if it was disabled try imaging with it enabled?
I’m just guessing on the secure boot thing, might not even be a thing, but it seems like it could be relevant.
I hate to suggest starting over on an image, but I would recommend making sure that you’re using bios/legacy/mbr boot mode. Unfortunately there is no way (that I have ever found anyway) to switch a computer between the two without reinstalling the OS because they use different partitioning types MBR and GPT. Also, when installing the OS in mbr mode, the easiest way I’ve found to ensure it’s a single disk (This hasn’t worked for uefi/gpt mode when I’ve tried) is to hit shift+f10 at the partition screen then do the following in the command line to clear the partitions and make only 1 full size partition
diskpart
list disk
# select your disk, usually disk 0 unless you have more
select disk 0
clean
create partition primary
exit
exit
Hit refresh on the partition selection screen and viola. I got that from a forum post on here or related to fog somewhere many moons ago and have been using it forever.
I seem to be rambling again.
To sum up
@Tom-Elliott I’m giving it a go now!
Have you tried a proxy dhcp using dnsmasq like they’re talking about?
I do realize that you are using a redhat not a debian, so unless you switch to a debian flavor of linux like ubuntu server or what have you, the commands would be slightly different, but I’m pretty sure that there should be equivalents for this all in redhat if you don’t want to switch distros again, and I wouldn’t blame you at all.
I only know how to set it up on debian based linux with apt-get, but I imagine the yum RHEL package is probably the same name.
From what I recall to set it up…
sudo apt-get update
sudo apt-get install dnsmasq
sudo nano /etc/dnsmasq.d/ltsp.conf
In the ltsp.conf file put this…
port=0
log-dhcp
tftp-root=/tftpboot
dhcp-boot=undionly.kpxe,fog-server,10.1.8.1
dhcp-no-override
pxe-service=X86PC, "Boot from network", undionly
dhcp-range=10.1.8.1,proxy
You may need to make symlinks for dnsmasq to see the undionly file, and I’ve had some luck putting copies of the bootfile in the ipxe folder too, that very well may do nothing, but I think it fixed something once so I just kinda still do it to be safe since it doesn’t hurt anything.
sudo cp /tftpboot/undionly.kpxe /tftpboot/undionly.0
sudo cp /tftpboot/undionly.kpxe /var/www/fog/service/ipxe/undionly.kpxe
sudo cp /tftpboot/undionly.kpxe /var/www/fog/service/ipxe/undionly.0
Then restart the dnsmasq service (also do this whenever you make changes to this file)
sudo service dnsmasq restart
You can play with the dhcp-range value a bunch to try to get it to work. This is the method I used when I didn’t have access to the DHCP server.
You can try setting the range to just your FOG server’s ip. You can set it to the router gateway, you can set it to the dhcp server too. And you can try interchanging I’ve had some
In the event that enabling dnsmasq kills your resolvconf dns configuration (which it often does…) the easiest solution is to add your dns servers in /etc/resolvconf/resolv.conf.d/base
You would also want to edit /etc/resolvconf/interface-order to have your main network interface at the top. It defaults to local host first and makes it so 127.0.0.1 becomes your dns server and breaks the internet. At least it’s done that every time I’ve installed it on ubunutu.
so like this…
sudo nano /etc/resolvconf/resolv.conf.d/base
Then lets say you use google’s dns servers and google.com was your domain for a simple syntax example, you would do this…
nameserver 8.8.8.8
nameserver 8.8.4.4
search google.com
Then restart the resolvconf service
sudo service resolvconf restart
If that doesn’t take care of it and it is a problem, check out this forum post for more info
https://forums.fogproject.org/topic/2799/dnsmasq-kills-dns-lookup-on-fog-server/6
A basic rundown of my understanding of dnsmasq is this
More information on dnsmasq and fog here https://wiki.fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/Using_FOG_with_no_DHCP_server
and here https://wiki.fogproject.org/wiki/index.php/ProxyDHCP/dnsmasq-_DRAFT
Another option, albeit an extremely advanced and difficult option, is to set up fog as a tertiary dhcp server. You would have to look into configuring a linux dhcp server, not something I have personally done at that in depth of a level. Because you would have to figure out how to make it act as a separate vlan or something like that, or maybe just have a separate network for imaging rather than having it on your whole organization. Something like a switch and a workbench in your office. But those are just a couple fall back ideas.
Also a side note, @george1421 and @Wayne-Workman Wayne is right here. I’ve actually gotten dnsmasq to work on multiple subnets and buildings. Granted it was a complicated university environment, and I had to do some tricksy stuff. But don’t underestimate the power of dnsmasq.
@Tom-Elliott The first test I did was with a multi-disk image that I made from a vm and it went back to the behavior it did before where it acted like it was working but never gets into partclone.
I’ll do a debug session for that one since it happened to fast to snap a picture.
@Tom-Elliott I will gladly test them!
I’m currently trying the inits that came from the most recent btsync and they seem to be working too for the hardware inventory task anyway, haven’t tried an image yet.
Where are the new inits to test? Oh wait you posted while I was typing this, I’ll download those and give them a go right now.
Well it only seems to work when it was uploaded from nvme drive. That’s kind of odd.
@Sebastian-Roth No problem. I’m happy to help.
So I can’t upload a resizable image. It says
“Problem opening /dev/nvme0n1p for reading”
I’m going to try uploading my base image as a multi-partition and see if I can download that one.
So downloading a multi-partition image that was uploaded from an nvme drive works on an nvme drive. But I can’t download one that was made before I updated the init
I’m going to try uploading and downloading a resizable image and then I’ll also try reuploading my main image to see if uploading it using the new init makes some sort of difference.
So here’s some good news, image capture works!
I did just a default multiple partition install of windows and it uploaded no problem.
I had still set the host primary disk to /dev/nvme0n1 in the gui.
I’m going to try re-downloading the image to the same computer
Then I’ll try to downloading the image I actually need on it that is single disk resizable.
Thanks for all the help thus far.
Here’s the information from the debug session with the new init. Looks mostly the same. I’m going to try installing windows with default partitions the old fashioned way and I’ll see if image capture works by chance.
@Sebastian-Roth Similar problem with a non-resizable disk, it doesn’t seem to add a 1 at the end of /dev/nvme0n1p
I’m going to do a debug session and see if the lsblk is any different from before and such. Let me know if there’s any other information you need. I’m here to help 
On a side note, I did take out the primary hard disk specification and ran a hardware inventory and it found the hard drive just fine on its own. It didn’t get a harddrive manufacturer, model, or s/n but it knows it exist now. Yay progress!
@Sebastian-Roth I just tested with a resizable image to no avail. I got some error messages. It looks like some numbering didn’t quite work as expected. Mainly when it is searching for /dev/nvme0n1p instead of /dev/nvme0n1p1 and when it tries to find the image file named d1pp1.img instead of d1p1.img
My apologies that some of these pictures have duplicate information, this happened twice I was just ready with the camera the second time since it happened so fast.
I am currently uploading a non-resizable version of that image to test that idea. I should be able to post results on that test in like 10 minutes or so.
@mrdally204 I usually set the owner and group of images to fog
sudo chown -R fog.fog /images
And I set the permissions to 775
sudo chmod -R 775 /images
Whether or not that’s the best security practice is arguable, and since your permissions are already 777 the owner being root probably doesn’t matter. But changing the owner might be worth a shot.
Awesome! I’m giving it a try right now. And my apologies if I seemed impatient in my asking, I was just curious and getting all excited.
I currently only have one image and it is a resizable one, we’ll see what happens.
Thanks,
-JJ
Assuming that your original is still up and running, you could try doing a manual database dump and import. This is essentially what the gui is doing so that you don’t have to worry about the command line aspects, but it doesn’t
In the command line on the original server, assuming you went with the default blank password…
mysqldump -u root fog > /home/fog/fog.sql
Then open up winscp, filezilla, cyberduck, or whatever ftp client you prefer (or just use scp in command line to copy straight to the vm) and download the fog.sql file you created.
Then in the new vm server put the fog.sql file in /home/fog and then run this command
mysql -u root fog < /home/fog/fog.sql
And that should take care of it.
Alternatively, especially if it looks like the gui export is working, you can just use the downloaded file from the gui for the second part there.
Hope that helps