@sebastian-roth here is the video of 05 on flickr https://www.flickr.com/gp/138098812@N03/D0569a

@sebastian-roth OK have a ~1Gb video file I’m trying to upload to flickr of 05 but a quick glance tells me it’s scrolling the same info in a loop. Here is a screenshot:

@sebastian-roth Unfortunately I can’t capture 60 FPS video on a Motorola Droid Turbo. I thought it was an artificial limitation since the camera is capable of it spec-wise but when I tried in Open Camera, I got the same message. I’ll see if I can get our photographer buf to do it on her iPhone 6.

@sebastian-roth

RE: 05 = Wowsa! Yea, much output. My phone won’t let me video yet because the battery is too low (???). I’ll capture a video later but I cant even read it in person it scrolls by really fast. I’ll do what I can.

RE: 06 =

@sebastian-roth 04_ipxe.efi:

@sebastian-roth
Here is from 03_ipxe.efi (after chmod 655)

Sits there for 15 mins or so and reboots

Thank you Sebastian, yes I can. I’ve been doing all the images/pxe at my work with FOG & CloneZilla for ~3 years and ghosting in general for ~20.

I’ll outline an infrastructure high level doc so you know what we’re working with. I technically have untill March (no hard deadline) and it’s a ‘priority project’ so this IS what I’m supposed to be doing. The infrastructure is very stable. I am a Sr admin but don’t have direct access to the Cisco network gear. I do ‘own’ the servers though. The net admin is very responsive. That said, I do general IT for a small yet global company and stuff happens.

Although I said all gens of X1 Carbon are working fine with UEFI, the original X1 isn’t working with ipxe.efi but I didn’t test other *.efi. UEFI does work but not from PXE. It’s a great loaner laptop due to built-in ETH port which I’d like to learn how to diagnose, in addition to the Dell. Seems like a great skill to have. So what do I need? Wireshark? Other tools?

@jgallo Yea. It works fine with legacy and undionly.kpxe but some of the features in the Win10 Fall Creators Update only work with UEFI. I don’t think this is a strictly FOG-related issue but some of the guys in this thread https://forums.fogproject.org/topic/4728/dell-7010-lenovo-l530-with-uefi-enabled-won-t-network-boot/59 went nuts and started building their own binaries for the 7010. Doesn’t look like the issue was ever resolved though or even identified. That thread is from 2015 so I was hoping someone had gotten it to work since UEFI boot to disk works fine on the 7010.

@bardwood Dell has a BIOS A25 for this machine but flashing it, load defaults, and switching to UEFI only made no difference. This machine has Win10 Fall Creators Update installed on a GPT\UEFI disk which boots normally.

…gets to ‘ipxe is initializing devices’ and hangs.

This does work on our network with the Lenovo X1 Carbon series (all gens). I’ve tried all the *.efi boot files in /tftpboot but no luck. I even downloaded and tried the latest ‘ipxe.efi’ from ipxe.org. MS Server 2016 DHCP. I did do all of the setup listed here: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence but in this case, I made a DHCP reservation and modified Opt 67 of this single machine so I could play with different boot files. Legacy boot (with undionly.kpxe) works fine this way. If I switch to ‘UEFI only’ in the bios, I do get the NIC as a boot option. It does load PXE but hangs at init. This is Dell BIOS revision A24 which I believe is the latest but I’m about to go double-check for new BIOS. Options? Tips? I’ve looked at the DHCP logs on Server 2016 but there’s nothing damning. That part appears to be working. The Dell just doesn’t want to boot off any *.efi boot file.

Server

• FOG Version: 1.3.5
• OS: CentOS 7.3 (server), CentOS 6.8 (storage nodes)

Description

Doing a full replication of all images to the storage nodes is not possible due to a 200GB limit on the nodes themselves (minus OS). What I’m attempting to work out, would be a scenario where nodes have specific images just for their storage group. I know you can assign images to groups but since I’d have to move potential group masters into the default group, they will sync all images and fill up the 200GB disk. No bueno.

Advice?

Server

• FOG Version: 1.3.5
• OS: CentOS 7.3 (master), 6.8 (storage)

Description

The service master is happily capturing/applying images. There are no errors in the logs.

My issue is with my storage node:

• Node storage is not visible (blank, no pie chart)
• I created a new storage group ‘DUB’ and added this node to the ‘DUB’ group.
• In properties for the storage node, ‘Is master’ is unchecked.
• In the node’s /opt/fog/log/fogreplicator.log I see “Image replication is globally disabled”
• In properties of the single image I’m attempting to replicate, it’s associated with both ‘default’/service master and the new group ‘DUB’ mentioned above.
• Both ‘Image enabled’ and ‘Replicate?’ are both checked.

Should it be working at this point? Do I need to check ‘Is master’ while it’s in the new ‘DUB’ group?
Why am I seeing ‘replication is globally disabled’ in the node’s logs?

@Tom-Elliott No. Also, yes. Initiating ‘Plan B’.

I still had the CentOS 7 VM from a prior BETA of 1.3 so I dusted it off and installed 1.3.5. Did some tests with new images (just a junk, non-prepped image) and that worked. So please tell me how feasible this is:

I currently have 2 FOG servers on CentOS 6.7 and 7.3. I want to keep the 7.3 but it has no (real) images.

I’d like to roll the 6.7 back to 1.2.0, write the images to like hardware, re-direct clients to 7.3 and do fresh captures. The images themselves could use an update so if I can’t roll back to 1.2.0 it’s not a huge deal but would save some time. Is it as simple as just running the 1.2.0 install script?

@Tom-Elliott When I wrote this, I had only tried to capture once, many RCs ago. I just tried again and it did work. I love the new status bar in the web interface showing progress, size, and estimated task time.

@Tom-Elliott Didn’t work but I did get a different message:

@Wayne-Workman Actually, it’s about getting any images to work. I can’t record new images either. I definitely want to upgrade CentOS at some point. I do have VMWare. Perhaps on the side I’ll start building a CentOS 7 server. I did have an early beta of 1.3 working on CentOS 7. The master worked great but wasn’t having luck with the storage nodes so I wiped it out. In fact, I’m going to do this tomorrow. Our imaging system has been down for a week but I could really use some of the features in 1.3.

@Tom-Elliott No luck. Fails the same way when trying to recreate the main partition at init. This was on the ‘Gen1’. I’ll try a couple others.

@Tom-Elliott

Optiplex 7010
Image path: /images/O7010V3
Contents of d1.original.partitions:
/dev/sda1 : start= 2048, size= 204800, Id= 7, bootable
/dev/sda2 : start= 206848, size=976566320, Id= 7
/dev/sda3 : start= 0, size= 0, Id= 0
/dev/sda4 : start= 0, size= 0, Id= 0

Lenovo X1 (non-carbon, AKA ‘Gen1’)
Image path: /images/X1NCV2
Contents of d1.original.partitions:
/dev/sda1 : start= 2048, size= 204800, Id= 7, bootable
/dev/sda2 : start= 206848, size=312374960, Id= 7
/dev/sda3 : start= 0, size= 0, Id= 0
/dev/sda4 : start= 0, size= 0, Id= 0

Lenovo X1 Carbon (NVMe/AKA ‘Gen5’)
Image path: /images/X1CG4V3
Contents of d1.original.partitions:
/dev/sda1 : start= 2048, size= 204800, Id= 7, bootable
/dev/sda2 : start= 206848, size=499911344, Id= 7
/dev/sda3 : start= 0, size= 0, Id= 0
/dev/sda4 : start= 0, size= 0, Id= 0

@Tom-Elliott Parted - 100% switch:

@Tom-Elliott I will try the 100% switch. Also, no change with RC16.