Posts made by danieln

@sebastian-roth

@danieln said in Clients imaging despite recieving "Read ERROR: No such file or directory" and "ata1.00: failed command" errors:

The output of md5sum /images/DellE5450-80-Non-Office/d1p1.img on the Master node was:
e929a14a17c60b2b9a7dfdf18f526232 /images/DellE5450-80-Non-Office/d1p1.img

The output of md5sum /images/DellE5450-80-Non-Office/d1p1.img on the problematic node was:
1d4bf4ac2bcef83013fe4589149b0e30 /images/DellE5450-80-Non-Office/d1p1.img

That’s very interesting. I did not expect the checksums to be different but good that I asked. To me that means that the file was not replicated from the master to the storage properly. So please delete /images/DellE5450-80-Non-Office/d1p1.img on the storage node and wait till it’s being replicated from the master. Then check md5sums again. The FOG replication services checks filesize and checksums (this check only happens for smaller files because it puts too much load on the server if checksums for large files are calculated on every run) but seems like this is a seldom case where filesize matches but checksum doesn’t.

I cannot exagerrate how useful this information is for me to know for the future. So thanks a million! I will try that and report back. However, just for my own clarification, those two checksum outputs should be the same if it replicated correctly?

I am using Zstd for compression. Do you recommend Gzip? What are the pros/cons of both?

Both are fine. I tend to use Zstd more and more.

Good to know.

@sebastian-roth Thanks very much for the response and for the very helpful info!

I should have explained this a bit more in depth earlier. FOS (the Linux OS doing all the work) reads from the file (e.g. d1.p1.img) piping it through a decompression fifo. So if partclone says “No such file” it’s very likely the decompression fifo died for some reason (file corrupted, RAM issue, …) and partclone is not able to read from it anymore.

Please run file /images/DellE5450-80-Non-Office/d1p1.img and md5sum /images/DellE5450-80-Non-Office/d1p1.img on both your nodes and compare the output. Which compression do you use, Gzip or Zstd?

That makes sense. It’s just weird to me that it would die on this node when it’s brand new, but i suppose it’s possible. Perhaps I’ll just try a recapture. Or, if I go into the node and manually delete the DellE5450-80 directory, will the Master know to repropogate it? If not, I could try a recapture and see if that works.

The output of file /images/DellE5450-80-Non-Office/d1p1.img on both the Master node and the node I was having issues with was the following :

/images/DellE5450-80-Non-Office/d1p1.img: Zstandard compressed data (v0.8+), Dictionary ID: None

The output of md5sum /images/DellE5450-80-Non-Office/d1p1.img on the Master node was:

e929a14a17c60b2b9a7dfdf18f526232  /images/DellE5450-80-Non-Office/d1p1.img

The output of md5sum /images/DellE5450-80-Non-Office/d1p1.img on the problematic node was:

1d4bf4ac2bcef83013fe4589149b0e30  /images/DellE5450-80-Non-Office/d1p1.img

I am using Zstd for compression. Do you recommend Gzip? What are the pros/cons of both?

Do you think it’s maybe isolated to the image? I’d assume the ATA errors have something to do with the hard drive but I’m not sure what.

The ATA errors stem from the same FOS (FOG Linux OS) and I would read that as kind of an issue with the Linux kernel with those particular notebooks. It is possible the deploy is fine despite the messages but I am not sure. When you search the web for those ATA messages people say that very often the SATA cable or even power supply (in PCs) can cause such messages. Often Windows is less picky with this kind of things and so I can imagine for Linux to complain (still trying hard) but Windows not so.

I will say that I replaced the hard drive on one of the client laptops that was having that issue and it was resolved, but I attempted a hard drive replacement on a separate client and it was still throwing the ATA errors, so maybe it was something else. But you’re thinking its more along the lines of hardware issues with the laptop and not with FOS or the Node itself? I feel like it only throws those ATA errors when connecting to that one node, but I could be wrong. Maybe that’s the next thing i’ll test.

@sebastian-roth said in Clients imaging despite recieving "Read ERROR: No such file or directory" and "ata1.00: failed command" errors:

@danieln Have you tried imaging that exact same machine from both servers and you only get the “No such file or directory” error on the later one?

And asking again, do you have another notebook - exact same model - that you can deploy to, just to see if you get the same ATA errors?!

I only appear to get the “No such file or directory” error on the node I set up yesterday. However I am getting ATA errors on the other nodes now too with multiple Dell E5480s. Here’s a screenshot of what i’m seeing of one I am currently imaging from a different node:

And again, it finishes correctly. This is a picture of the same screen moments later:

Do you think it’s maybe isolated to the image? I’d assume the ATA errors have something to do with the hard drive but I’m not sure what.

@sebastian-roth Weird, right?

Here is the output of ls -al /images/DellE5450-80-Non-Office/ on the Master Node:

and here is that same output on the Node that was throwing those errors:

OS: Debian
FOG Version: 1.5.9-RC2

I set up one additional node to my FOG server and sometimes (only with certain images), it PXE boots normally and will throw the following error right before Partclone starts:

However, once it continues in one minute, it begins to image.

Then, usually during imaging it will display the following message:

But FOG will still image the device correctly once Partclone is completed. It’s bizarre to me that it would say that it could not write the image due to “no such file or directory” and then image it. I also double checked on the node to make sure the image file was in /images and it’s definitely there.

Perhaps one of my drives on the node is failing? It’s brand new though.

I’m also curious as to what the ata1:00: failed command could possibly mean. Especially in the context of it imaging a client successfully.

Any ideas on what may be going on?

Thanks in advance, this community has been a lifesaver and is much appriciated!

@sebastian-roth said in ipxe/boot.php and bzImage running very slow:

@danieln said in ipxe/boot.php and bzImage running very slow:

The only change was that I added one additional storage node.

Storage node being in the same subnet as well?

Correct. I double checked and it is on the same subnet.

@sebastian-roth Thank you for your comments and questions!

After having the weekend, I came in and shut the Master off for 2-3 minutes and rebooted it, and it seems to be working normally now. Turning the servers off and on was something I had tried multiple times when the issue was present and it did not seem to help at all. Very strange.

Are your hosts and the FOG server all on the same subnet?

Yes, they are all on the same subnet.

What changed since it worked fine? Update on the FOG server (new iPXE binaries)? Changed network components? Used different hosts (NICs, maybe USB ethernet adapters)?

The only change was that I added one additional storage node. Could this have been database related? Network components and hosts are all the same. No USB ethernet adapters used.

I’m obviously thankful that it’s working for the moment. But I will update this thread with any further issues that arise.

Thanks again,

OS: Debian
FOG Version: 1.5.9-RC2

My FOG deployment speeds seem to be normal, however, when any client pxeboots into FOG, /fog/service/ipxe/boot.php and bzImage are running very slow . They eventually work, but after each attempt to run there are maybe 30 or so dots after it.

So it looks like this:

/fog/service/ipxe/boot.php......................................................................................................................................................................................................................................................................................................................................................................................ok

This just started occuring today. As I said before, Partclone seems to be running at normal speeds, but it just takes each client maybe 5 minutes to get there.

Any insight as to why this may be happening? Thanks!

@Sebastian-Roth Thank you again for your reply.

I believe I found the fix. The colleague was not using “quick registration” to register the MAC addresses into the database before imaging. It seems that the Master needs to have the MAC address of each client in the database to delegate imaging tasks to each node.

I have a full bench of computers now (registered) and they are now pulling from all 8 nodes equally and tasks are showing. Thank you again.

@Sebastian-Roth It does not show up on the dashboard or in the task list, no.

But the bigger issue is that all of the computer imaging is only pulling from the Master when I have 8 other storage nodes. It is flooding the master when the master is only supposed to have an 11 client maximum. And the deployment task seems to not be created although it is deploying.

@Sebastian-Roth Thank you for the reply!

I can manually schedule tasks and they show up in the task list. But when I pxe-boot computers to the FOG network and depoy an image, it doesn’t show any active tasks for the deployment even though it’s deploying 25 copies of the same image from the master server.

Hello,

Before I begin, here are my specifications:
OS: Linux/Debian
FOG Version 1.5.8

I’m kind of at a loss here. I have a FOG setup with a Master and eight storage nodes. As of this morning I noticed that whenever I started imaging, all of the computers would connect and deploy from one of the storage nodes. Thinking this was odd, I disabled this node in the Storage Node settings of the FOG Dashboard just to see what would happen. Then the computers all began connecting to only the master node and began to oversaturate it. I currently have ~25 computers connected to FOG and imaging from the master node and they’re all pulling about 150MB/min (very slow compared to how it usually runs).

What even more bewildering is that there are no tasks showing up on the FOG dashboard either. It’s still showing that theres 68 free spots available and no activity at all. I also only have an 11 Max Client limit on the master and like I said, I easily have 25 computers connected to it pulling from the master. I have tried rebooting the master and every node and no luck.

All Linux and FOG services seem to be up and running after running sudo systemctl

Any ideas on what may be going on?

Thanks in advance,

@george1421 Thanks for that info!

So, disabling the Ubuntu firewall shows Apache2 Ubuntu Default page showing that it works. It is stating "This is the default welcome page used to test the correct operation of the Apache2 server after installation on Ubuntu systems. "

But still no fog managment dashboard page. This would be the WEB_SERVER right? Doesn’t it automatically generate this at setup?

My colleague and I are having difficulty getting our FOG server dashboard to generate and we’re wondering if it may be something with our current Static IP/DHCP setup.

We just installed FOG on Ubuntu Server LTS and we wanted to reserve the IP address(es) of the nodes to be static IPs. We are adding this FOG network to an already existing business network connection and we are not using FOG for DHCP and we wanted to defer to our regular DHCP server for the office. Sorry if this is a dumb question, but can we set static IPs on the computer side or would it need to be done on the DHCP server side?

We ran sudo nano 01-netcfg.yaml and our netplan is as follows:

network:
  version: 2
  renderer: networkd
  ethernets:
    enp59s0f1:
      dhcp: no
      addresses: [10.50.0.218/24]
      gateway4: 10.50.0.1

I am able to ping 10.50.0.218 with no packet loss, but when I attempt to go to 10.50.0.218 or 10.50.0.218/fog/management in a web browser I get no connection. Isn’t the dashboard managment link supposed to automatically generate once installation is complete? What could possibly be going on here?

Thanks all!

@george1421 Interesting. Thank you for that info. I have only ever done Quick Registration with FOG which seems to identify and register the hosts by their MAC addresses. I figured since FOG was handling DHCP and assigning IPs to MAC addresses anyways (is this even how it works?), it wouldn’t need DNS.

So it uses the MAC addresses as a DNS name?

@george1421 Thanks for the reply! That info is helpful. I am currently integrating a separate FOG server at my work. The first one was set up by someone who doesn’t work here anymore and it has a DNS server.

But even if FOG is on an isolated imaging network, I’m still struggling to understand why DNS would matter? What would it possibly need DNS translations for?

Please excuse my ignorance as I am fairly new to servers/networking in general, but why would FOG need a DNS server if it’s set up for just local imaging? Isn’t it just assigning MAC addresses to IP via DHCP and pushing the image that way? Why would FOG need to translate IPs into domain names and vice versa? Is it for the FOG dashboard maybe?

Thanks all!