@arnaudrigole Please try defragmenting the partitions (nvme0n1p3 in your case so I guess this would be drive - but better defrag and as well). Then try again.
I am fairly sure the issue has nothing to do with the new model using a NVMe disk!
@arnaudrigole Please try defragmenting the partitions (nvme0n1p3 in your case so I guess this would be drive - but better defrag and as well). Then try again.
I am fairly sure the issue has nothing to do with the new model using a NVMe disk!
@Florent Both binaries (old legacy and new client) are still shipped with FOG. Definitely use /var/www/fog/client/FOGService.msi which is the new client.
@jeevan517 Please provide more information on whatās not working or what you need help with.
@mmoore5553 We need more information to be able to help! What is your DHCP pointing to? Is it pointing to the FOG server IP? Is TFTP running on your FOG server (run netstat -antup | grep ":69"
and post here)?
Please go through the troubleshooting guide to see if you can manually download via TFTP: https://wiki.fogproject.org/wiki/index.php?title=Tftp_timeoutā¦
@noob Where do you see the 50 GB node size? Please run the command df -h
an your storage nodes an post result output here.
@meatloaf4dayz Firmware (UEFI) is upgraded to the very latest version?
@george1421 Thanks heaps for bringing this up! I will continue to answer in a minuteā¦ Ok, deleted mine as well to not confuse anyone.
I donāt see your points as something we need to delay for FOG 1.6 but could possibly bring into 1.5.x already as a testing stage.
- Force the installer to provide a database password for root in mysql. [ā¦]
Absolutely! Funny but I have started looking into this already before Christmas as I really would like to have FOG enforce secure passwords for exactly the same reasons. I just have not found enough time to think it through and test things. Iād even go as far as creating a FOG database user to be used (good practice) but still enforce passwords for root and fog DB user! Will look into that in the first days of 2019.
- Change the default webgui admin account from
fog
andpassword
to [ā¦]
I am with you here about the default password
. But as we have briefly discussed in another thread I tend to rename the FOG web UI user (instead of the fog
linux account). Maybe default to admin
but even make it so people can choose their own.
- Change the fog service account from
fog
tofogsvc
to avoid confusion with the webui user of the same name [ā¦]
As mentioned above Iād prefer renaming the web UI account name and leave this one. Iād still force the account to be no-login! I need to think more about how we prevent users from using this account like create it beforehand and then being locked out or if they do use it right now on an existing installation. There are options like checking wtmp and stuff to see if the account has been used for login and warn the user but I have not gone into depth here.
@george1421 Letās see if we can discuss this a different way other than through hidden posts. Might move the discussion a chat session here in the forums or to slack.
@Tom-Elliott What are your thoughts on this? Would be great to get your comments on this topic before I start changing this in 1.5.x already.
@michIGY said in Computer Name not changing to Host Name:
HostnameChanger Users still logged in and enforce is disabled, delaying any further actions
Good you got it to work but if you ever see this again you can set an option in the FOG web UI to force even if a user is logged on.
If you see āResponse Invalid security tokenā again you might want to try āReset Encryption Dataā in the hostās settings in the web UI.
@fogger1 said in Stuck at Stopping FOG status reporter:
Stupidly I decided to download copies of init.xz and init_32.xz from sourceforge
Why?
Get the latest inits here: 32 bit and 64 bit.
But keep in mind that inits do match certain kernels - not an exact version but if you have the latest inits and year old kernels it will fail for sure.
@salted_cashews I cannot imagine what would cause the filesystem to not be clean all the time!? Does the machine shut down properly before you do the capture? Is it a VM or hardware machine?
@jeevan517 We need more information to be able to help. Please take a picture of the error and post here.
@michIGY Please check the fog-client log file on the host machine. Hopefully this will shed a light on whatās going on.
Not sure if we have many people with win10 1809 using the fog-client yet.
@JJ-Fullmer Iāll look through the code again in the next days and post new kernels to test if you are available and have a device to test.
@salted_cashews said in Trying to capture Ubuntu 18.04.1 and I get this.:
So after running that command it captures fine, but during deployment I get a similar error.
What error message do you get on deploy? I kind of doubt you see the same message. Please take another picture and post here.
If I try and capture again on a fresh base image, (different machine same OS/config) I get the same error.
This seems very strange. Sounds as if Ubuntu does not close the filesystem on shutdown properly. Canāt really imagine that but what do I know. When you run fsck.ext4 ...
does it actually fix an issue? Please take a picture of the output and post here as well.
@mary-montesanto Edit the host settings for this particular client in the FOG web UI. There is an option called Kernel Arguments (or maybe Kernel Parameters - donāt have a server to check at the moment). Put irqpoll
and save settings. Then schedule a new deploy job and see if it works.
@china-boy said in Fogproject can only clone C disk:
Sorry, what I want to say is that the captured image should be installed on other user machines in bulk, but other disk characters other than C disk cannot be erased.
Hope you are still around. Weāve kind of lost track of this as you havenāt posted the picture of disk management of the target PC before deploy.
Without knowing the details I guess that you are trying to simply update after you have initially cloned the PCās full disk. So steps I would recommend: In your FOG image definition set Partition to āPartition 2 only - (4)ā and deploy the image to the target machine. This way only partition 2 (hope this is in your case) will be deployed and the other partitions wonāt be touched.
@salted_cashews It means that the filesystem on /dev/sda1 seems unclean/to have an inconsistency. Is /dev/sda1 the root or boot partition?
You might just schedule anther capture task for the client but tick the checkbox for debug this time. Boot it up and hit ENTER twice to get to the shell. Now run fsck.ext4 -f -v /dev/sda1
and see what you get. Hope this will find issues and fix them. Maybe even run multiple times if it keeps returning with an inconsistency. When filesystem is clean just start the capture with command fog
ā¦
@salted_cashews Here you find an easy to use tutorial on mysql command line access. Just skip the step in installing mysql as this is already done on your system. Find the password of your database (root) user in /var/www/html/fog/lib/fog/config.class.php (might be ''
-> empty) and got ahead try out things: https://www.digitalocean.com/community/tutorials/a-basic-mysql-tutorial
Creating a new database / table as in the examples might be a idea to play with things and not break any FOG tables.
@mary-montesanto Have you tried setting irqpoll
as Kernel Argument in the hostās settings?
@seniorvodka There seems to be no image defined for the hostā¦