Posts made by Foglalt

And is there a solution if i see that some hw works with this and some with them? I mean a general solution or a kind?

@Wayne-Workman

My problem is that it is struggling to change pxe boot file to another for test purpose. I mean several ppl use fog service to deploy images. There come a problematic hardware for which changing the image name in dhcp is too slow. I am as I stated before, not a dhcp guru so i dont know its all capabilities. Is there any way to “chainload” maybe? It would be ugly to change the binary under the name undionly.kpxe untill the testhardware loads then back fast to let others work properly with previous one.

(sorry for slow replies, somehow i dont get notices of topic replied. i will work on it, maybe i did something wrong)

@george1421

Unfortunatelly the laptop and its clones are not available for the test atm. but in the shipment we will have some as far as we are informet. So, test will be possible maybe.

As for your question about pxe file we send to clients:

filename “undionly.kpxe”;

If i recall well, i found some dhcp config sample for solving ipxe issues with different types of ipxe implementations. If that can be working out somehow it can be a solution if finally it comes out that not the spanning tree but the ipxe implementation somehow. I am not a dhcp guru and not in charge of managing that machine i have some delays to implement my needs in that part, i must admit.

@george1421

sorry, was a bit busy lately, cant reply in time. so, here comes my photo of the failure:

as for the ipxe file i cant tell you atm as i cant ask for the config of the dhcp from the administrators in the night i will ask them as i dont remember what i told them to set (something really default after the fog setup).

i will make the test what u wanted with the dumb switch (i hope i can reproduce it as the original laptop was sent back to the owner, so i need to get another one. i think it has clones somewhere).

Re: Pxe boot problem with HP Pavilion x360

I have an issue with a laptop what fails like the above linked one. You suggested a different pxe file and here comes in my lack of knowledge. How can I give a different pxe image to load for a specific client? dhcp send image for the whole network, same. It seemed not best to mess with dhcp config for machine based cofig.

The laptop gets ip the ipxe fails to get configuration. Just as it those with the mentioned hp. How is it properly handled?

Hm that article part for me was new, thanks, it helped (i checked some and they are gone now normally). How can it happen anyway?

I see. And how can i recover it? As if i dont see, i cant delete. (btw the new search function for me is strange a bit; i will post question in that regard if i have time to see if other info on that helps )

Hi!

We noticed a strange issue since 1.3.0 installed. Formerly well known hosts are no visible if listed (like all hosts or group memberships). At first we thought those hosts are not there we only just remembering wrong, but in group list or host lists it is counted (group shows 5 pc but 4 listed) and if we try to create a new host by that name it says there are already a host with that name.

How can we kill this bug?

additional info: the mentioned hosts are for cloning processes only. Name is permanent, but sometimes MAC or image changed for the new cloning procedure.

Anyone have seen it maybe?

@Tom-Elliott

What do you mean by maybe incorrect image path? images havent changed location. Those files are there since months. From creation up to now.

Please tell me about the second option. I must admit that maybe i am underinformed about the need of imaging. New disc comes in (unboxed, etc, installed into box, cables, etc etc). Does it need to have preset partiotion table to deploy images onto it? I mean up to now i was not aware if it is a must before new image come to deployed.

Please tell me what do you mean by that you told.

We up to now could do debug with that image, as we did some else for gathering more information. We did test with other hw, other images of same kind (partiotioning, etc). Result: same error message. As here we are during a bit fiery schedule (1k+ pc reimaging) had less time for detailed tests, therefore i did a choice: keep or rollback. I kept so i needed more test: with new infrastructure (1.3.0) did a random win10 imaging (fully no care of details, just next-next finish setup of win10, upload image and redo image on different hws. all went well (resize, too, etc).

So, i can say 1.3.0 single target imaging works, it is not system failure that we had in general. As of time we had, we will remake the original image and use that (store and deploy in 1.3.0 environment). BUT, as always, there is a but. I did a multicast order from colleague with a bit of fear and it come out as i was right, nothing can be fully successful multicast has some issue (well, actually run into some hw failure too, so not 100% sure it was multicast failure, will test later. Most urgent was at least a working imaging.

Can you tell me, for debuging the original problem of this topic, what you mentioned about u guess what can be the problem? did it changed with info i am posting now? (if i have time i post the debug details ofc)

Ok, thanks for the help and the super fast support response time! Hat risen before you!

as for debug, tomorrow we do it (i have to reread our posts as i forgot the steps but i hope i can do it fast). will report tomorrow.

I see no problem with code, all can have, it is normal. Why i am surprised that it was working, no upgrade, and it stopped working. THEN we did upgrade in hope that it will solve it cos of hw change (and why not use newer ofc). It only havent changed it then i tried to find solution and up to now i did not found. as to be honest i dont want to downgrade, but i dont know if collegague has options to retake images.

btw, where can i find info on other changes, like i found on gui (host settings are more detailed, some info i dont even know what are, etc). I maybe can find a solution if i read these all (actually documentation is the… hm… less super thing in fog, but take it no as offense pls i hate to write mines; many times i try to find info i bump into old versions).

Hm… I am actually not aware about a part you mention “empty disk” (new hw, so it must be empty, y. it is not a redo, it is cloning from the master image; is it somehow wrong? i will try to ask recapture the master, but it still is interesting as it was working for a long time and was ok till new hw (maybe this is not the clue to solve? i have zero things in my mind that something has changed in any way, 1.2.0 was up and running last issue was about multicast, ages ago. “i dont click if i dont need to”, so normal system updates was only what happened to fog system os.

the message before failure. i will try to check i only took a glimpse of it at last point when i saw no clue to solve otherwise on serverside. it was fastly taken away, scrolled up. actually other IRL problems burning our hands, so only tomorrow is when we can try to debug more detailed.

All file are there, like:

-rwxrwxrwx 1 root root 1nov 24 07:51 d1.fixed_size_partitions*
-rwxrwxrwx 1 root root 15 nov 24 07:51 d1.original.fstypes*
-rwxrwxrwx 1 root root 259 nov 24 07:51 d1.original.partitions*
-rwxrwxrwx 1 root root 0 nov 24 07:51 d1.original.swapuuids*
-rwxrwxrwx 1 root root 10911329117 nov 24 09:18 sys.img.000*

(sry for formating fail)

Hi!

We have a working fog setup which we used with ease (v1.2.0). There come some new hardware and problems emerged which forced us to upgrade to 1.3.0 to test that it can be solved with new version maybe. The image is same, not changed, only hardware changed (new mainboards, etc).

Client loads and at the imaging start point it says that "no image found that would match the partiontion to be restored (perform restore).

Before update problem was same with that hardware we try now but colleague who found it says it was a bit less specific about reason.

The image is about a windows 10, single partition in reality OS type was set 8.1 and worked well actually. Now we even tried with OS set zo windows 10, it changes the error, so it must be a key to problem itself. I must admit that imageing is not my job, i only keep fog server working but colleagues use it so i dont know why was os set to win 8.1. Maybe it had reason. (we use single partition deployed systems, ntfs, win7. and now started with windows 10 mass deployement; it worked properly then now stuck with new hardwared as a pain in the ass ofc)

Does it have a clearly visible reason and we can solve fast or need more investigation or more information to find solution?

As extra information the image size in image list is 0b, ofc the files are not zero length.

I hope you guys can help as candle burns low in our deployment project

You may be right. For me collecting informations about image creating statistics, doing automation about storage spaces can be done after new images came alive. I can manage it elsewhere, just was wondering if post-upload scripting is possible somehow

@Wayne-Workman

no it was just an example. I was wondering why not post-upload option if post-download exist. normally backups made now with cron actually

@Wayne-Workman email notice? well, if no else, can be ok, but not image deployment, image upload! (look, like if i am noticed about all new image creation. if it is somehow noticed, an automating process can backup the new image or the like. for now i dont know any better occasion, but it one

@Tom-Elliott just for a rare example: when colleague creates a new image, i would like to notice it, like the scripts that works for backups, or so. best if fog mechanisms do it, that something on clientside. as far as i know snapins do things on client, from which I would do uploaded image. If that computer is never siwtched on, will never notice from that side.

If possible the imaging client somehow can help. Is it possible?