Posts made by KnightRaven

@Wayne-Workman
Yes. Had to to match our new subletting rules. Followed the steps to change it from the wiki in fog.

@Tom-Elliott
Sorry, was called to another matter.

I access the webgui by http://10.114.56.67/fog…
This is from other pcs as well. Not just locally from the server.

well it’s my only node for this campus. everything else is working from it. Just not imaging. The web gui is on this node and works. so are the other services.

I imagine after changing info it may be a hiccup somewhere. an address mismatch in a file, but I dont know what other settings to check. The boot.php is accessible from other machines. But unable to get to imaging. The error only presents itself when imaging. either by task from gui or by choosing image from pxe/fog menu.

I am also noticing that some of the imaging info is not pulling up on the home page webgui.
Bandwidth image does not show but title bar does. And Pie charts/graphs not showing for storage group/node. The boxes are there but no graph. Not sure if related but thought I’d make a note if it is.

@KnightRaven
So it appears to happen when trying to do a deploy as well. Tried to deploy from pxe/fog menu and choosing the image and is getting stuck at same place. Same error i think but it exited to fast to be sure.

Maybe a rights issue? but it was working yesterday before network changed.

I am getting an error when trying to capture a new image.

This could be a networking error as we are re-subnetting and changing IPs. But so far after following the steps for changing IP other aspects are working.
I.E. dhcp boot (using dnsproxy) tftp boot are working. Web interface is working.

When no task is assigned I can get to the pxe/fog menu. Even re-registered host.

When A task is assigned at least in this case a capture task it fails at the boot.php file. Getting the ipxe error: input/output error http://ipxe.org/1d0c6139
Which didn’t help me much.

I installed rc-4 yesterday(7-27-2016). When seeing I needed to change ip/subnet i re-ran the rc-4 install per the ip change instructions. I have checked/double checked the settings in fog settings/web server and all the others to be sure I didn’t miss something. I changed the setting in .fogsettings before re-installing.

would appreciate some ideas on troubleshooting this.

running 1.3.0 rc-4
client PC Dell 760.

Thanks.
Jason

@Tom-Elliott
Yeah that makes since. I just rem there being an issue with the resizable option with ntfs at one time. And the fixed size worked better or was more stable. I don’t remember exactly and I’ve slept alot since then. Old habits I suppose.

Thanks.
Jason

So… I found a PC with a matching HDD size and the imaging is working. At least partclone didn’t fail.
I also updated to rc-3 just to be sure. But results were the same with smaller HDD.

So is there an easy way to force the cloning? Is it better to do a resizable image for this problem?

I copied an image from another server. Current server using fog 1.3.0 RC2. When deploying image it gets to the windows partition and fails saying the HDD is too small/image to big. The image was created on a PC with a bigger HDD but the actual data would fit fine. As in the original image HDD was say 160GB but new source is 80GB but image is much smaller. I don’t rem. expanded size but certainly under 40GB.

Is there a way to use partclone -C to skip this size check or some option I’m missing GUI wise to force the clone?

I don’t rem this being a problem before. So maybe there is something between the server versions causing a problem? Or maybe I need to create the Image in fog first before copying? Just throwing out ideas.

your help is appreciated,
Jason

Just wanted to note that I recieved these same errors. Was looking for something else that went awry and saw this and some other errors related to dashboardPage->Bandwith. Not sure if that is related. But can post if needed/interested.

@kinger37
You might try adding the dhcp option(s) to
/etc/dnsmasq.conf
I was having issues with getting the file from the right address. Adding the info to dnsmasq.conf helped where having it in ltsp.conf didn’t work for me.

Have a look at my post here…
https://forums.fogproject.org/topic/7723/pxe-ipxe-dnsmasq-next-server-undionly-config-tip-s

@george1421
Just wanted to add some more notes after using/trying this setup in another location.
You may encounter rights issues and errors if nothing is changed. I opened up the File Browser as root to copy and paste files for Win setup along with other tools.

You very likely may need to use chown and chmod to give proper access to your files. By default on my testing the user and group was set to root:root. I did NOT use root as my user when mapping my drive for pxe setup. So I needed to change.

so you may need to try:

#to change who owns the folder or files

sudo chown -R jdoe:root /location/of/folder

# use a "*" wildcard to do all items at named location or at 
# current location
sudo chown -R jdoe:root /location/of/files/*
sudo chown -R jdoe:root *

# you can use ls -l to check

#for ref: https://en.wikipedia.org/wiki/Chown

#to change the actual rights, as in read/write/execute...

sudo chmod 774 /location/of/folder/or files  (or again use a *)

#again use ls -l to check


# 774 will give user and group full rights. the 4 gives guest read only.  Not sure that full rights are needed but used to test and didn't reduce as of yet to know if just read or anything less will work.

for ref: https://en.wikipedia.org/wiki/Chmod

To recap my trials…
At first I forgot to change user and mapped drive wouldn’t work. After changing user I would get access denied to setup.exe. After making sure I had rights to setup.exe, I got a winsetup.dll error. Saying it was corrupted or missing(Something like that I forget the actual wording now).

I ended up recopying to be sure but ended up being a rights issue to the whole sources directory.

Just wanted anyone else reading to know what you might run into. While I dont yet consider myself an expert here, I will be glad to answer questions if something is not clear. My knowledge has come from trial and errors, and then finally asking questions.
thanks to all who have helped answer or wrote other related topics to get me/us here.

Hope this helps someone.

Jason
KnightRaven

@george1421
Another potential tip… When booting into winpe this way, it asks you to press a key to boot from cd/etc. You can delete(or rename as i did) the bootfix.bin file in the ISO/boot directory. When saving and creating the bootable iso it will be able to boot without prompting.

@george1421
So for that update. Yes HP has a winPE driver pack. Several depending on version needed. I tried booting the HP laptop with out injecting and it worked. So I may have just gotten lucky and the same drivers existed. Whatever the case I’m not complaining.

It may be worth noting so there is no confusion(especialy in a more detailed tutorial) that the actual WinPE from the AIK appears to be needed. As opposed to using a boot.wim from regualr install media. It must point to a location that no longer exists(like USB/CD drives) causing setup to think it doesnt exist. Although an educated one, that is a completely wild guess.

At any rate, rather it be drivers or a hard coded location of sorts, there is a difference in the WinPE boot environment and regular/Full boot environment.

I’d be glad to offer help from my experiences if you write a tutorial. I was thinking of doing the same but my thoughts/writings can get off track sometimes.

I really do appreciate your time and efforts.

@george1421
So I took the time and tested. IT Worked! I don’t know if the difference is running the driver pack you listed(injecting it). Or running it as an ISO as opposed to the individual files. But at least I have a working concept. I have to go back and edit my startup cmd file. I didn’t put the full user context(<pcname\userid>) when mapping my share.

I don’t know if its an added driver or the fact that this time the default setup never ran. Just the one from the share.

The next trick will be seeing if I can get it to work on an HP laptop. If it’s a driver issue that is.
I am excited that there is a working model to go from though.
Thank you very much for all of y’alls time!

Jason

@george1421
good to know it was tested all the way through and worked. So I will remake may boot.wim file and sources, and make a bootable .iso from it and see what happens.

The current ISOs I have are too big. The PCs need more ram to support the full bootable ISOs as opposed to the win_pe versions.

Thanks for testing. I will report back when I get a chance to try it out.

@george1421
Awesome. I’ve ran through some of this before but I will do it over again and see if it helps. Maybe I missed something before. Thanks for the refresher. I hope to try it tomorrow.

@Wayne-Workman
I do map a drive and run setup from the share with same results. Could it be that it is still looking at a different location? Could it be looking for the original usb location or some such? Or does it use the current path? Does the new mapped drive need to be a part of the PATH statement in winpe?

@Wayne-Workman
I can try that. I have tried browsing the usual setup drivers and not getting very far.

But the HDD is seen by winpe. At least when I browse files it shows up. But maybe there is something missing. The mini laptop does not have a cd/DVD but the desktop I tried on did with same results. Just ruling out that it was looking for a physical DVD drive.
I’ll try loading HDD drivers but I’m not optimistic about that.

Thanks