Posts made by mjaskowski

We are using FOG Version 1.5.6

Yes, right after choosing Quick Registration and Inventory I see bzImage… 100% ok and next init.xz… 100% ok the screen goes black and nothing more happens and it never appears in All Hosts.

We just got 28 new Lenovo 300e WinBooks for our Math tutors that we’d like to clone with FOG with the following specs:

• BIOS: 6HCN23WW
• EC: 6HEC23WW
• MTM: 81FY000BUS
• CPU: Intel Celeron CPU N3450 @ 1.10GHz
• Sys Memory: 4096 MB
• eMMC Card: SanDisk iNAND 128GB
• OS: Win10 Pro Education
• Secure Boot Status: Disabled

No built-in NIC so I’m using a lenovo ThinkPad USB 3.0 Ethernet Adapter Model: PN:RTL8153

We can reach the Fog server registration page and start a Quick Registration but it never completes and neither does the Client System Information (Compatibility), the screen goes black and we get nothing after that. It will just sit that way for hours until I shut it down. Then I tried a manual registration which does get recognized and an image capture appears to start but also stalls and never proceeds.

I’ve even tried Acronis and Clonezilla already which load and then fail to find a hard drive. These units have 128gb eMMCs as primary drives.

Please advise. Thanks.

@tom-elliott I’ve got the same exact problem happening as @Jim-Graczyk and I’ll try to be more descriptive.

I have an image stored on a storage group “3r” but when I select the image and view its Storage Group two groups are listed “2r” and “3r” with a radio button check mark beside 3r, which I take to mean primary although there is no header text for that column so it’s not clear what that check is for. The available options include check boxes beside Storage Group name and beside each listed node, in this case 2r and 3r, and an Update primary group “Update” button and a Remove selected groups “Remove” button.

I’ve confirmed that the image does exist in both images folders on both nodes 2r and 3r but I only want it to occupy 3r, the image’s primary storage group. When I directly remove the image by deleting it from the 2r images folder it gets copied back, thereby suggesting an accurately reflected status on the Image Management/Storage Group page. When I select the checkbox beside 2r and click the Remove button an Image Update Success “Image Updated” popup appears but 2r never disappears from the list even after refreshing or navigating away and back again and the image still gets copied back to 2r if deleted directly.

Each node is set as a Master Node with its own Storage Group; node2r:group2r and node3r:group3r

I actually have this occurring with several images but not all, most images are fine being listed in only one storage group and existing in the one images folder. It appears something is gummed up with the database records that the GUI cannot correct.

Additionally, but a separate problem is, I have images in the database listed in 2r that are really in 3r and vise versa and I wish I could just change the reference via the GUI.