@sebastian-roth said in FOG will not resize a hard drive after deployment.:
@m-fitzgerald I was not fast enough to look at the d1-files you posted to give you a hint on that. To me it seems like something prevents FOG from seeing your boot partition (which I expect to be sda1) as such. But to be sure I need to see those files again now that you upgraded FOG and recaptured the image. So please post the contents of the files from your image directory again: d1.partitions
, d1.minimum.partitions
, d1.fixed_size_partitions
and d1.original.fstypes
.
Posts made by Sebastian Roth
-
RE: FOG will not resize a hard drive after deployment.
-
RE: Partclone or Partimage
@Quazz No nothing in the apache error logs and can’t seem to find anything related in the browser debug console either.
-
RE: FOG will not resize a hard drive after deployment.
@m-fitzgerald Please post the contents of the following files from your image directory:
d1.partitions
,d1.minimum.partitions
,d1.fixed_size_partitions
andd1.original.fstypes
. -
RE: No more network device - failed
@palermo Please post the contents of your
/etc/dhcp/dhcpd.conf
file. -
RE: No more network device - failed
@palermo Ok, so this time you decided to let FOG be the DHCP server which should be fine. But this time the client does get an answer pointing to 192.168.2.1 as being the next server why FOG is on 192.168.2.25… So I am wondering if there is another DHCP server again. As you seem to use virtual box (sorry I didn’t talk about this earlier) I am wondering how your virtual network setup in virtualbox looks like. Is it set to bridged, NAT, host-only?
i installed fog server v0.32 before
he workedFOG is a set of tools put together as imaging solution. So it’s kind of a complex setup and it does sometimes work out of the box but you can’t ask for this being the case all the time. Especially using a virtual environment there are too many variables in the equation so it’s very likely to go wrong especially if you don’t have much experience with DHCP, PXE and such things.
-
RE: Help-could not verify mount point
@batchenr Good to hear you are up and running again. Though you might have used the GUI but just as well things can go wrong when you copy on the console. Using
cp /images/* /target-dir/
does not copy hidden files (files starting with a dot - like.mntcheck
) because Linux bash does not include those hidden files when using the*
glob. It’s as simple as that. -
RE: Windows 7 Image
@imagingmaster21 I don’t see why any of the things you just posted (UEFI boot, secure boot, CSM) has anything to do with an imaging problem (be it resizable or non-resizable). If you want proper help you better post pictures of errors you see on screen.
And by the way - to use FOG you need to turn off secure boot anyway. I haven’t seen anyone who is able to do iPXE in secure boot yet (not saying this cannot be done but we don’t provide signed binaries for that to work!).
-
RE: Help-could not verify mount point
@batchenr Ok the images are still there. Let me guess, you copied those in the GUI? So you’re only missing a file that FOG uses to check after mounting the filesystem over NFS. Run the following commands and you should be fine:
sudo -i touch /images/.mntcheck /images/dev/.mntcheck chown -R fog:root /images
About the warnings in /var/log/messages - I don’t seem to find those fopen/unlink calls in the same lines in the code. So I am wondering which version you have actually installed. On the screenshot it says 6971 but that doesn’t ring a bell for me. I found an old post talking about this version but that’s from March 2016. Can you please tell us how you installed (tar.gz, svn, git) and which version/branch?
By the way - why do you use different kernel versions for 64 bit (bzImage) and 32 bit (bzImage32)??
-
RE: Partclone or Partimage
@Quazz Good point, thanks for pointing this out. I am on Linux (debian) client + Firefox 52.3 / Chrome 57 / Opera 48 and see this issue in all the browsers. Can you try Firefox and Edge on Windows as well?
-
RE: Help-could not verify mount point
@batchenr The message “EXT4-fs (ram0): couldn’t mount as ext3…” on boot is just a warning and not problematic. It’s got nothing to do with you trying to extend the /images partition! The message has been there for a long time and it’s not new.
But the other message is a problem. I guess something went wrong when you tried to extend/move your /images store! Maybe start by running the following commands and posting the output here:
mount
andls -al /images
andcat /etc/fstab
-
RE: Partclone or Partimage
@Tom-Elliott I just had a look at one of my test FOG servers and it also defaults to “Partimage” when creating a new image definition. This is RC 10 on CentoOS 7. Do you see this as well or have you got an idea why this might be the case?
-
RE: No more network device - failed
@palermo Yeah from the picture of the modem configuration you posted it looks like you cannot add PXE settings to the DHCP configuration there. So as Tom said you might look into proxydhcp. Find stuff on that in our wiki: https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_with_dnsmasq
But be warned: Some modems still send half of the PXE information and really do confuse the clients with that. So give it a try but don’t blame us if it’s not working out of the box.
-
RE: Realtek GBE 10/100/1000 boot issuses
@zingaro Please post the PCI IDs as a reference as well.
Did you try my suggestion on using a dump mini switch?
Other than that you could try different iPXE binaries like undionly.kkpxe (note the double k), ipxe.pxe, realtek.kpxe or realtek.kkpxe
The other question is, why not going UEFI all the way?
-
RE: No more network device - failed
@palermo said in No more network device - failed:
can you help me please?
Well I am trying to but you need to give us more information, so I ask again, what is serving DHCP in your network?
If you can’t answer that question you definitely need to read up on DHCP, PXE boot and that sort of stuff…
-
RE: Super newbie guide for creating image to w10?
@motto Pictures tell more than a thousand words. The MEMDISK error bootstrap too large to load` to me sounds like that machine doesn’t have enough RAM to load that ISO…
-
RE: Windows 7 Image
@imagingmaster21 said in Windows 7 Image:
I tried both resizable and not resizable and no luck.
This is not of much help. We would like to give you a hand with this but need more information on what exactly goes wrong. Please try non-resizable again and take a picture of the error, post that here.
-
RE: No more network device - failed
@palermo What is serving DHCP in your setup?
-
RE: Network boot of host comes up with mount permission denied
@majikins See in that picture it says
storage=x.x.x.x:/media/dev
which is different to the other information we have. Seems like someone has messed with that setup a fair bit. Not sure what advice I should give. Maybe a clean reinstall would be best, not sure. -
RE: Unique-Identifier Branch
@astrugatch As this is still in kind of an untested alpha stage you are pretty much the first to give it a try as far as I know. But I can’t think of anything that can go wrong if you simply register machines through the FOG menu (we need a proper registration with inventory data as we rely on Parts of that). If I got the logic correct you should be able to register several machines using the same USB adapter all the time…
Ohhh, I just remembered that I might still miss a database change. Forgot about that. Give it a try and we see what happens. I will look into pushing a fix for that soon.
Edit: Just noticed another problem. I think we haven’t build new init files that including those changes yet. Sorry but this is not going to work yet. Will push this now that you are keen to test. Stay tuned.
-
RE: join domain Fog client log error windows 10
@Sunks I expect there to be more errors in the log before those you posted. Please restart your client and provide the full client logs beginning from the reboot.