Posts made by zfeng

@sebastian-roth thx for ur info

Hi guys, can anyone give me the definition of the image manager, like what those options mean on setting up the image or deploying the image? Any tutorial would be helpful. thanks in advance

@sebastian-roth I successfully built image from the type of computer that don’t work on image deployment. It seems to me that there must be some kind of hardware config that prevents the image deployment to expand the disk properly

@sebastian-roth I cannot update the image here as the platform keeps saying it is too large. Here is the link for it

https://drive.google.com/file/d/1J8FarpqD-0dhHdWd0BCSairqnL84e5Wa/view?usp=sharing

@george1421 Sorry for this late message. Just want to rephrase what we discuss little. The capturing task works fine that it allows me to capture the image properly. The problem is the deployment of image.I just tried deploying image and used the instruction u provided on both computer that works and computer that does not. The outputs from both computers are:

Computer that does not work with image deployment:
Pass 1: Checking inodes, blocks, and sises
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda2: {certain number}/{certain number} files (0.3% non-contiguous)

Computer that works with image deployment:
Pass 1: Checking inodes, blocks, and sises
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda2: {certain number}/{certain number} files (0.2% non-contiguous)

Basically, the outputs are the same except that percentage of non-contiguous

@sebastian-roth good to know. thanks

hi guys, any plan to release a new version of the fog project, making all the dev work into prod? thanks

@george1421 when you have a moment, can you look at my previous comment? thanks

@george1421 the dev ranch seems not solving the image deployment issue.

@george1421 all good then. Thanks

@george1421 hi, maybe it is just me little too concerned. The production branch does not have that message, ACPI error. Like what you said, this is the power management thing which I should just ignore.

@george1421 Thanks so much

Hi guys, I found an issue on the development version of the Fog. When I capture the image or deploy the image, there is an error message pops up
“”"
ACPI BISO Error (bug): Could not resolve symbol \SB oSC CDW1 AE not found 20210730 psparse
ACPI Error Aboriting method due to previous error (AE not found)
“”"

However, the installation completes without any problem, and my computer works fine as well. I just want to see if this is actually a problem. Thanks

Fog Server Version: Latest Development Version:1.5.9.154
Fog Server on Computer: Ubuntu 20.04
Image Captured Computer: Ubuntu 20.04

@george1421 when you say the dev branch, I believe you mean in this link.

@george1421 Also, it seems to me that due to the change from Microsoft, the manufactures of computers, motherboard or disk, must follow what Microsoft changes, right?

@george1421 That means I cannot revert the version of fog like 1.5.6 or earlier to resolve the issue? Seems that is the case. For the next release, do you have a timeline for this?

@george1421 Thanks for you quick response.

FOG Project: v1.5.9
Ubuntu OS Kernel: v5.4
Target OS: Ubuntu 20.04
Successfully deployed to other computers: yes

I bought new computers and the image deployment fail. The message at the end of the deployment right before it finishes, “An error has been detected” “could not resize /dev/sdas2” “please run e2fsck -f /dev/sda2 first” “Args Passed: /dev/sda2 1”. Any idea why I have this issue?

I think there something has to do with the newer computer I have, nothing wrong with the Fog project itself. Sorry for the false alarm

That is the odd part. If there is something wrong with the new user while the default user is gone, the problem should happen to all computer deployment. However, the problem happens to certain deployment. If I remember correct, I also saw the issue when expanding the “/dev/sda2” while capturing the image. It just says that it cannot expand th “/dev/sda2”