Posts made by bretfred

So that gave me the answer I needed. It’s not a problem with fog. These aren’t the machines they were supposed to be they sent us the 64gb emmc version instead of the 128gb m.2 thanks for your help.

All of a sudden I am getting this error? not sure what changed was working perfectly before. Not sure what to check. I was on kernel 4.15.2 to get past the erasing partition issue. Updated to 4.17.0 to see if that would fix it, also tried reinstalling fog and it updated to 1.5.4.8 didnt help either. It happens whether i do deploy or multicast. This is a known working image with this hardware. Have used it fine before with this hardware not sure what happened?

Fog version 1.5.4 Cent OS 7 php version 5.6.36

If Number is entered for session name session does not get created. Used to work fine. Not a big deal just thought I’d report it.

Yea not sure why the shrunk partition is listing the same size as the resizable one. So I went ahead and deleted the second recovery partition. Recaptured the image as not resizeable. Was able to get it to restore to the smaller drive. Even after i recaptured it still showed the data partition as 64GB not sure why but hey it worked. Thanks for your help.

@quazz I tried to update the kernel this is the error i get Type: 2, File: /var/www/html/fog/lib/fog/fogftp.class.php, Line: 708, Message: ftp_put(): Could not create file., Host: 10.100.0.250, Username: fog

No i was on 1.4.4 before and had done about 600 of these with it flawlessly.

Here is the contents of those files. I thought i shrunk this drive in windows before I did the capture. I could be mistaken as i was doing a bunch of stuff. Looks like the primary partition itself wants 64GB so its no wonder why its not working however i have included a not resizeable capture i did where i know its shrunk to around 33GB at the bottom that does the same thing. In windows the drive shows 30.8 however the partitions file shows 64Gb for the size.
fixed size

:2:3:1

minimum

label: gpt
label-id: CA2CF626-B6A1-BE98-571A-1A6FE2E6B6DE
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 250069646

/dev/sda1 : start=          40, size=      921600, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=2B630EF3-1CF9-42FB-846C-792BF8938857, name="Basic data partition"
/dev/sda2 : start=      921640, size=      104426, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=95A294AF-CC04-4743-AB0D-ADB83A5E365E, name="EFI system partition"
/dev/sda3 : start=     1026066, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=2967A63F-3AA1-4409-BDA8-305B43B9513E, name="Microsoft reserved partition"
/dev/sda4 : start=     1058834, size=    64605696, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=18916FDB-D9D2-4F31-AD1F-1F574B24070A, name="Basic data partition"
/dev/sda5 : start=   246730258, size=     3338240, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=17DDD755-5CBF-4FBE-AAA4-C20CE93D52A8, name="attrs="RequiredPartition GUID:63"

partitions

label: gpt
label-id: CA2CF626-B6A1-BE98-571A-1A6FE2E6B6DE
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 250069646

/dev/sda1 : start=          40, size=      921600, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=2B630EF3-1CF9-42FB-846C-792BF8938857, name="Basic data partition"
/dev/sda2 : start=      921640, size=      104426, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=95A294AF-CC04-4743-AB0D-ADB83A5E365E, name="EFI system partition"
/dev/sda3 : start=     1026066, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=2967A63F-3AA1-4409-BDA8-305B43B9513E, name="Microsoft reserved partition"
/dev/sda4 : start=     1058834, size=    64605696, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=18916FDB-D9D2-4F31-AD1F-1F574B24070A, name="Basic data partition"
/dev/sda5 : start=   246730258, size=     3338240, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=17DDD755-5CBF-4FBE-AAA4-C20CE93D52A8, name="attrs="RequiredPartition GUID:63"

Shrunk not resize

label: gpt
label-id: CA2CF626-B6A1-BE98-571A-1A6FE2E6B6DE
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 250069646

/dev/sda1 : start=          40, size=      921600, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=2B630EF3-1CF9-42FB-846C-792BF8938857, name="Basic data partition"
/dev/sda2 : start=      921640, size=      104426, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=95A294AF-CC04-4743-AB0D-ADB83A5E365E, name="EFI system partition"
/dev/sda3 : start=     1026066, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=2967A63F-3AA1-4409-BDA8-305B43B9513E, name="Microsoft reserved partition"
/dev/sda4 : start=     1058834, size=    64605696, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=18916FDB-D9D2-4F31-AD1F-1F574B24070A, name="Basic data partition"
/dev/sda5 : start=   246730258, size=     3338240, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=17DDD755-5CBF-4FBE-AAA4-C20CE93D52A8, name="attrs="RequiredPartition GUID:63"

I am trying to go from an HP x360 ee 11 128GB to an HP x360 ee 11 64GB. I have tried both resized image and an image where i shrunk the main partition to 33GB both ways gave the same error. Image deploys fine back to original laptop Any ideas? Running version 1.5.2

Second time I captured it the task completed still didn’t reboot but computer did boot properly after turning it off and on. Image moved to the proper spot with correct name too. First capture might have just been a fluke.

They are HP x360 ee 11
It doesn’t show an active task and shows end time in the imaging log
The interesting thing is that when i tried capturing the image the task still said active and it dint move the image from the dev folder to the properly named folder. Also that Machine wouldn’t boot again after capturing. Kept having startup problems that weren’t easily fixable so i just re-imaged it which even though it didn’t reboot it did boot fine after imaging.
bzimage is 4.15.2

I updated to 1.5.2 to fix a problem with windows 10 not resizing now when an image finishes capturing or deploying the machine throws an error when trying to reboot. I have attached a picture not sure what other info you need? I cant seem to find the srv version in this update but i just did the latest update today if that helps.

@Tom-Elliott
Hey Tom saw your post in the other thread earlier. Working now thanks!

@zclift15
Just seen it actually a few minutes ago. Thanks for the heads up.

Does seem like we are having pretty much the same issue. If i have any breakthroughs I’ll let you know.

Server

• FOG Version: 1.4.1 6071
• OS: Cent OS 7

Client

• Service Version:
• OS:

Description

Registered Host in web console and created a capture task. Boot of network everything works till it attempts to check in and fails. Things Ive done include changing cables, switching from stable to the newest trunk, verifing nfs is working with simple debug file transfer, verified services is are running (rpc bind nfs mysql not sure if there is more). Also I dont know if this is related just thought I’d mention it I can never get host registration to work from the network boot menu. Im kind of green with both linux and fog although I used to use it a while back. Anything else I need to do to help debug or check?
Thanks