@sourceminer I am fairly sure your case is different to what is being discussed in this fairly old thread. Please open a complete new one, refer to this and add your information: FOG version, more specific details about the client hardware, what exactly you are trying to achieve… all that!
Best posts made by Sebastian Roth
-
RE: make customized option as default on boot menu
-
RE: Upload Task Completes But Then Repeats & Repeats...
@jimsngc Do you have any post download (aka deploy) scripts in place? Take a look at
/images/postdownloadscripts/fog.postdownload
Other than that, I think we need to know exactly what’s going on. So please take a steady video of what you see on screen after the last blue partclone is gone. Upload the video to your dropbox/gdrive and post a link here.
-
RE: Issues with disk in an unsafe state
@sjensen said in Issues with disk in an unsafe state:
When I choose the not resizable option Fog wants to clone the entire disk
What exactly do you mean by that? Sure FOG wants to clone the whole disk but as Wayne said it only reads the blocks used by files/directories. So the resulting image is way smaller than the partition. What could cause a RAW image is if your drive is bitlocked - see here: https://forums.fogproject.org/topic/10824/image-upload-deploy-taking-a-long-time
As well check to see if fast boot is on. This can cause some major trouble as well!!
-
RE: Issues with disk in an unsafe state
@sjensen Unfortunately we don’t have enough resources to support older versions of FOG. Please upgrade to 1.4.4 at least! The error mentioned is not present in 1.4.4 and newer versions!
-
RE: Possible Proxy issue with MAC Address Update
@RipAU Hmmm, seems like your proxy server does have a problem with that URL. Not sure why. There is nothing FOG can do about it if even you can’t load the URL in Chrome.
I can only offer a workaround on this. It’s kind of a hack but should work.
- Download that
oui.txt
somehow (at home or whatever). - Create a directory
/var/www/html/ieee
on your FOG server and drop that file into that folder. - Edit
/etc/hosts
on your FOG server and add the following line:
127.0.0.1 linuxnet.ca
Then try updating the MAC address in the web UI again. Not sure if I got all the paths and stuff right just from the top of my head.
- Download that
-
RE: Error 'Could not open inode 'XXXXXX" through the library'
@Jarl2-0 Please make sure you have fast boot disabled before trying to capture that image. As well read through this wiki article: https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit
-
RE: Error 'Could not open inode 'XXXXXX" through the library'
@Jarl2-0 We have had the issue posted in the forums a couple of times lately. Unfortunately we are not able to pin it down exactly. Possibly M$ has changed something with 1709 but on the other hand not all users see this issue. Quite often it can be fixed by disabling fast boot - which should be disabled on all machines anyway!
I’d advise you to run a full
chkdsk
on Windows, maybe even defrag the disk and runchkdsk
again. But this is just wild guessing.The
Input/output error
at the end of the message to me sounds like the filesystem inode is pointing to a sector that is beyond the disk. But I have no idea really. -
RE: Manage scheduled task
@lebrun78 Though I haven’t played with the API much yet (Tom is doing most of that) I’d think that DELETE URLs are a bit different - from the simplified API documentation. Have you tried the following yet?
curl -H 'fog-api-token:NWE...MWU=' -H 'fog-user-token:ODc....mNDE=' -X DELETE http://fogus/fog/scheduledtask/86
-
RE: WOL working too good
@tmerrick The logs you posted don’t show anything WOL related. Any PC doing a PXE boot will request files via TFTP, so that’s not an argument for WOL causing the PCs to startup.
If it’d be the FOG server sending WOL packets you would see those in tcpdump on the FOG server!! Maybe connect a Windows PC in the client subnet and look at the packets using Wireshark from there. If the network switch forgot about the client MAC address it needs to send out the WOL as broadcast I think.
-
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.
-
RE: FOG will not resize a hard drive after deployment.
@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
andd1.original.fstypes
. -
RE: FOG will not resize a hard drive after deployment.
@m-fitzgerald Can you please edit
d1.fixed_size_partitions
and make it1:3
. Then re-deploy that image to a fresh machine and see what you get.As well can you take a picture of the disk management view in Windows on the source machine and post here?
-
RE: FOG will not resize a hard drive after deployment.
@m-fitzgerald Good to hear this fixed the issue for you. Though from my point of view it’s only partly solved. If you capture the image again you will need to edit that file again. So question remains why it does not recognize your boot partition as such. Usually this happens if Windows is not installed as English version or partition labels have been modified by hand. As I said, take a screen shot of the disk management view in Windows and post here. I am fairly sure we can figure out why that is.
Follow on question though. How do I edit the order of Storage Nodes?
We try to keep topics separate. Please open a new thread for this! Won’t answer here.
-
RE: How do I change to order of the Location ID's?
@m-fitzgerald Thanks for opening a new one on this.
The problem is that if a PC has not been assigned to a node it will try and pull an image from the wrong node
But why don’t you assign the correct location as being asked when registering? Sorry, this might sound like a stupid question but I don’t get where exactly you are headed with this.
-
RE: Uncompleted multicast
@kkroflin The important error message here is
pigz: skipping: <stdin>: corrupted -- incomplete deflate data
It means that the image is somehow corrupt and cannot be extracted because of that. We had someone with that not long ago and in his case it turned out that he had a FOG storage node where the image hasn’t been transfered to properly. After he fixed that (re-transfer the image from master to storage) the deploy went fine.
Previously I haven’t used multicast with FOG so I don’t know if this is a new issue or an old one.
Multicast is one of FOG’s key features and it’s part of it since years.
Also, in case of an error like this, I would expect to receive some clear error state …
Tom changed that behavior not that long ago - see here. Though I don’t know why from the top of my head. I think there was an issue with some devices (maybe MS Surface) that would fail “lightly” and we wanted to make those work. Maybe see if you can find a discussion on this in the forum from around that date (4th of April 2017).
-
RE: ipxe menu problem
@stiger Sorry for taking so long to look into this. I can confirm this being an issue but only if a number is used as first character in the name! If you name it
ape
or justpe
you don’t have that issue. I have looked through the JS and CSS code but as I am not an expert with that stuff I couldn’t come up with a quick fix yet.Playing with an example of
fadeToggle
(which we use in the web UI) I see that this is not generally impossible the way we use it - our code and example website. Maybe someone else has some time to play with this and can figure this out.So back to your problem of not being able to edit that entry. Till we find a fix in the web UI you can modify the entry in the database by hand.
shell> mysql -u root -p Enter password: ... mysql> use fog; ... mysql> UPDATE pxeMenu SET pxeName='fog.0pe' where pxeName LIKE '%0pe%'; ... mysql> quit; shell>
Then reload the
iPXE Menu Item Settings
page and you should be able to edit the menu entry. You can still have0pe
as Description to be seen by users in the FOG menu on boot. -
RE: Storage nodes opening multiple mySQL connections to Master DB
@dsloan-ethra Try the following mysql queries to see if
max_connection
is properly set after a reboot:mysql> show variables like 'max_connections'; +-----------------+-------+ | Variable_name | Value | +-----------------+-------+ | max_connections | 151 | +-----------------+-------+
… and connection limit (
Connection_error_max_connections
) is being hit at all:mysql> show status like '%onn%'; +----------------------------------+-------+ | Variable_name | Value | +----------------------------------+-------+ | Aborted_connects | 0 | | Connections | 8 | | Max_used_connections | 4 | | Connection_error_max_connections | 1421 | | Ssl_client_connects | 0 | | Ssl_connect_renegotiates | 0 | | Ssl_finished_connects | 0 | | Threads_connected | 4 | +----------------------------------+-------+
-
RE: Storage nodes opening multiple mySQL connections to Master DB
@dsloan.ethra Take a look at this: https://www.rfc3092.net/2017/06/mysql-max_connections-limited-to-214-on-ubuntu-foo/ and/or https://support.plesk.com/hc/en-us/articles/213393029-MySQL-values-open-files-limit-and-max-connections-are-not-applied and/or https://codepoets.co.uk/2015/mysql-max_connections-stuck-on-214/ (depending on which distro/version you use)
-
RE: Uploading Image Issues
@F-kos Wayne is absolutely right. Just to add to this, I seem to remember an issue with FOG 1.2 deploying to an empty disk… Not an issue in FOG 1.4.4 anymore.
-
RE: Selected boot device failed
@sjensen To add to Waynes important questions:
- System seems to boot in legacy BIOS mode. Why not going UEFI?
- BIOS firmware is the latest? Please upgrade if not.
- Is secure boot disabled?
The error message is kind of new to me. Seems like this is happening inn the middle of iPXE init. But searching for
pxe "selected boot device failed"
on the web I found a lot of WDS/SCCM posts. Do you have something like that in place?