Posts made by OmegaXis

@wayne-workman
im willing to call this resolved given that it seems to have been a time sync issue.

Hay Sebastian.

I think your theory on the bios clock is probably correct. Most of the laptops have been in storage for over a year. Once they started working, they had been plugged into network and power for a bit. I’ll take a look Monday at the other recommendations.

@sebastian-roth thanks

So after that one went through, everything seemed to start working fine again. Unfortunately, as its the weekend, its in a state at my office desk where I don’t trust it. I’m working this weekend on some other projects with my home lab. Let me know if you think of anything.

So, A funny thing (not really funny as much as annoying) has started happening. I have thrown the same laptop (Thinkpad L450) now at the fog server 5 times. All 5 times resulted in failure at the resizing sda2 partition.

For the purposes of sheer insanity, I threw it at the fog server one more time expecting the exact same results. Unfortunately (or fortunately, still not sure) With that one laptop, it worked.

This whole thing seems to be hit or miss all of the sudden. When I had this setup in my home lab (minus the lenovo laptops, I was using vm’s and desktops instead)

Update, running chckdsk scans did not solve anything.

im now at a point where i can get like one in 10 to image correctly, but its a different laptop every time. Worst part, nothing has changed.

There doesnt seem to be any reason that the ones that work do and the ones that don’t don’t. But this is not a good solution.

@sebastian-roth it does look similar. But unfortunately there doesn’t seem to be a solution. I will try running chkdsk on the gold and issuing a capture to see if that helps. Unfortunately my entire project is on hold till I can get this resolved

@sebastian-roth

Minimum partitions file

                                      d1.minimum.partitions                                                                                     
label: gpt
label-id: 5FC6A4FE-C9B9-48D1-85A1-04B915E5FD78
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 976773134
sector-size: 512

/dev/sda1 : start=        2048, size=     1048576, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=992E52CA-4E96-4DB0-813D-769534D59A54, name="EFI System Partition"
/dev/sda2 : start=     1050624, size=    23333108, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=D884B35F-887F-4265-B910-8F3FAD6D44DA

D1 partitions

d1.partitions

label: gpt
label-id: 5FC6A4FE-C9B9-48D1-85A1-04B915E5FD78
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 976773134
sector-size: 512

/dev/sda1 : start=        2048, size=     1048576, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=992E52CA-4E96-4DB0-813D-769534D59A54, name="EFI System Partition"
/dev/sda2 : start=     1050624, size=   975720448, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=D884B35F-887F-4265-B910-8F3FAD6D44DA

D1 Fixed_size

1

Ok, so continuing on with this. It might be me being an idiot and things not quite working the way i think they do. The issue seems to be deploying to “Dis similar” hardware. if i deploy to like hardware, everything is fine. Given that its ubuntu, this still doesnt really make sense.

EDIT
NOPE That wasnt it. Just had a l450 fail as well in the exact same ways the x250 was failing

EDIT AGAIN

Finally had the bright idea to remove the internet cable after imaging and try just booting. it works, but the resizing is not happening, im having to boot manually into a usb stick with gparted on it and manually resize after install. for obvious reasons, this is not a good solution.

This could be any number of issues. What is your network environment? what boot file are you using? without knowing about the full net stack your running its a bit more difficult to troubleshoot.

Also knowing what hardware your trying to deploy to would be a huge help.

@sebastian-roth And my issues are back

Below is all the images requested.

https://imgur.com/a/6UoLpWb

@sebastian-roth

Soooo, the worlds most annoying thing happened this morning. I went in, ran debug mode deploy to try and replicate everything using settings that were not working last night, and everything worked. I am not considering this resolved yet on account of the fact that i need to rebuild the image because I had it set to legacy mode vs uefi mode which is what is needed. I will keep people updated on if the UEFI Variant still works.

Additional info

Kernel Variables and settings
bzimage loglevel=4 initrd=init.xz root=dev/ram0 rw ramdisk_size=27500 web=https://(IPADDRESS)/fog/ consoleblank=0 rootfstype=ext4 nvme_core.default_ps_max_latency_us=0 mac=(MAC ADDRESS) ftp=(IP ADDRESS) storage=(IP ADDRESS)/images/ storageip=(IP Address) osid=50 irqpoll hostname=(MACID/HOSTNAME) chkdsk=0 img=MobileTClenovo imgType=n imgPartitiontype=all imgid=2 imgFormat=0 PIGZ_Comp=-9 hostearly=1 type=down

Hi there.
I have a fog server running as follows
Ubuntu 20.04
Fog 1.5.9

I am trying to deploy a single disk image containing a customized ubuntu-mate install

The image clones successfully, but fails at the step of Resizing extfs volume /dev/sda1

The only useful information that i am getting is Please run e2fsck -f /dev/sda1 first. I ran deployment in debug mode and ran that command first but am still getting an issue.

Any help would be greatly appreciated as we are getting ready to convert a former fleet of lenovo L440/450 to this image to turn them into VM Terminals

I am wondering if anyone has in the past used the fog snapin utility to install a .deb file on ubuntu and what that would look like? I am relatively new to fog and scripting as a whole so any help is appreciated.

The Plot thickens

I have 2 of these T510 Thin clients that im trying to get working. One of them works fine. The other one is still throwing the issues. I have made some configuration changes to the network, such as disabling stp.

@sebastian-roth I’ll have to check in about a week, sadly the server died today and i didnt have a backup as it was part of a home lab. The new one should arrive later this week/next

Hi all,

Currently running fog server in a ubuntu vm on a Proliant DL360p running unraid as the hypervisor. I am able to pxe boot vm’s within the server just fine. However, when I try to boot a thin client that is attached to the same cisco catalyst 2960g switch, i am getting the dreaded failed to get ip error.

Fog configuration info.
Fog V1.5.9
VM is Stock ubuntu 20.04.02

My network topology goes a bit like this
Meraki mx64 functioning as DHCP
Cisco Catalyst 3750-E as backbone
catalyst 2960g as endpoint switch where both the server and the computer I am trying to pxe are.

I have checked my configuration on the switches and STP is enabled.

Any suggestions?

right now, this is a lab environment test. The end goal is to create something that can be put into production at my company.

UPDATE:

I uninstalled fog client, and rebooted the vm, then reinstalled it. now everything is fine. I don’t get it.

When attempting to install Fog client in Ubuntu-mate 20.04, i am getting the following error at installing files.

What is the fix for this?

Thanks