Posts made by Tom Elliott

@marted what OS are you trying to get installed?

Was somebody playing in the BIOS settings? I know this is too generic of a question, but this sounds more like somebody set these hosts to a “SATA” mode of RAID. Can you ensure all machines sata operation mode is set to either AHCI or IDE?

AHCI would be the best case.

The fact that Windows doesn’t see the drive is what’s leading me to believe there’s an issue with the setting. This is because if Windows cannot see it, then the driver is missing. My guess, is the other machines had a driver installed as part of the original setup.

I’ll even further surmise that the other machines have a “Recovery” partition. Because of this partition, restoring the windows os on these machines has the missing driver as an option.

By wiping the disks, you’re effectively removing the recovery partition as well. So windows doesn’t have a driver for the IDE contrller.

FOG shouldn’t have an issue deploying the image unless the driver is also missing from the kernel. That being said, you wouldn’t have been successful in wiping the disks either.

What version of FOG are you using?

@rets34 you probably need to remove MySQL proper. apt-get remove --purge mysql-server

Followed by the commands I gave below.

I gave the gist to get you up and running right away. Why you would reboot again, when that broke this the first time, seems strange. This is a server and should not need to be restarted every time you want to update fog.

@bluedark And you’re 100% certain this ISO is capable of installing XP?

Exactly how large is the ISO, how much memory is available to the machines you’re trying to load the ISO from?

If the ISO is 2GB for example, then you need at least 2GB of RAM for the ISO to load to the machine.

@rets34 said in MySQL Failed:

systemd[1]: mariadb.service: Failed with result ‘timeout’.

Please follow this information:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1806263

The gist:

echo "/usr/sbin/mysqld { }" > /etc/apparmor.d/usr.sbin.mysqld
apparmor_parser -v -R /etc/apparmor.d/usr.sbin.mysqld
systemctl restart mariadb

Then wait a couple of seconds and do the systemctl -l status mariadb

@rets34 I’m not seeing anything that stands out as problemattic.

It appears mariadb started okay, though I’m unsure.

Can you also provide systemctl -l status mariadb

@rets34 Please try:

systemctl restart mariadb
journalctl -xe
systemctl -l status mariadb

I’m having a hard time seeing this as a bug.

What’s the disk space available on the machine?

what’s the output of journalctl -xe?

What’s the output of df -h

While we don’t mind helping people out, this is a forum for FOG, not for iPXE. While we use iPXE in our application, we do not have all the answers for it.

How much memory is available on this old Windows XP’s machine?

What version of FOG are you using?

Of note, RAM disk size was updated in 1.5 to use 275000 kilobytes, or about 270 MB minimum. I am guessing this machine has around 256 or less memory?

UEFI booting doesn’t Magically, typically, detect the Boot partition.

UEFI uses NVRAM space to store the boot location.

Essentially, once you image the machine, you’ll need to tell the BIOS to look at the Hard Drive and select the boot file as appropriate.

Once you do that, I’ll bet you’ll have success with booting the machines.

This isn’t a FOG problem, persay.

This is not a bug. This is intended behavior.

Welcome to FOG.

I cannot be the “hand holder” persay, but we have a fairly outgoing community here and I’m sure we’ll be able to help you, or at least help direct you where to go and what to look for.

Some questions come to mind, and are important:

Does your organization have Volume Licenses of Windows 10?

Are all the laptops using the same “version” of Windows 10? (I.E. Windows 10 Enterprise, Windows 10 Pro)

How many laptops are you planning to image?

Is the imaging going to be happening at a central location?

Are these going to be required to Join a Domain? (This can be handled using FOG Client or unattend setups).

There’s likely many more questions others may have, but I think these are pretty good starting point.

The laptops, I would suggest getting Volume Licenses if you don’t have them already. In particular you would need 1 Volume License per Version per Model. Meaning 1 VL for Windows 10 Pro for Dell E7750 and 1 VL for Windows 10 Enterprise for Dell E7750. Volume Licensing is a messy beast on its own (sorry). The 1 for each model and per version is important. You do not need X number of licenses = the number of laptops you have, as you have purchased OEM licenses for the model of laptop and version of Windows installed. (Anybody please correct me if I’m saying something incorrect here as I’m not a Lawyer or an Microsoft Licensing person.)

Once you are situated with the volume licenses, I would highly suggest doing what’s called a Hardware independent image strategy. I believe @george1421 might even have a suggestion for MST for building a VM image nice and quickly (allowing you to update all your software easily) with the software and windows updates, then grabbing the “Fat” image required at the frequency you requested. The image would need to be a little heavy on base size if you have many different Laptop Models.

Hopefully this helps you get started, and welcome to FOG.

Hello all,

I wanted to inform you all that on attempting to upgrade the forum software this morning, the folder was accidentally cleaned. While we do keep backups of most of our stuff, the forum folders is not one of them due to the dynamic nature of all the data contained within.

The database was unaffected, just the upload of images were.

I’m attempting to see if any of the backups we have contain some of the data, but I’m not holding my breath at this point.

I’m sorry for any issue this may have caused. I will repost here with any update I can provide.

Thank you,

I’ll try to answer as succinctly as I can:

Changing the Master Storage Node to another Node means, that new master node is what will be handling the replication of images. This means, other nodes within the group will be receiving the images and image layout of the Master node. This means, if an image is missing on the new master node that exists on other nodes within the group, there is potential those files will be deleted as it will be wanting to make all nodes have the same kind of file/layout structure as the Master node of that group.

When you change a master node, you are effectively telling the system that it must follow a new structure based on your request. If you do not define a master node to a group, one will be attempted to be defaulted using the Lowest ID of the nodes within the same group. (Assuming Lowest ID = the oldest node within that group.)

Changing the Node’s Group means just that. If you are changing the master node, a new master for the group you’re removing this node from will need to be defined. Simply moving it to the new group will not make it the master of that group. You would need to define that, unless it is going to be the ONLY node within that group. If you want it to be the “master” node of the new group, before you make the move, I would suggest disabling the FOG Services for all nodes within the group you’re moving the node to so you don’t accidentally have replication happening and potentially removing data from the node accidentally.

Hopefully this helps and makes sense.

@banbuduo-2020 we need information. This might also work better as it’s own post, as this posting is quite old.

From what I can see of the pics you provided, you’re using a USB stick?

What version of FOG is your server running?

What instructions did you use for the USB?

The image should not be joined to the domain.

Other than that, if you want to create the objects and put them in their respective OUs have at it.

Renaming a PC and joining the domain should work without issue. If you have a machine that fails to do this after imaging, can you get the machines client log so we can try and troubleshoot it with you? This isn’t normal.

Logging was configured to try to make things more easy to track.

I’ve just added the ability to select whether or not to actually write the information to disk.

They’re labelled appropriate as FOG Configuration Page -> FOG Settings -> Logging Settings.

Thank you,

So, change your query from:

mysql -u root -p -D fog -e "select * from groups"

To:

mysql -u root -p -D fog -e "select * from `groups`"

mysql has made groups a keyword now, so you will need to escape the word when referencing it in the future.