@Sebastian-Roth said in Updating FOG and Storages from 1.5.4 to lattest version:
ClusterSSH
thanks for the hints and sorry for the delay in answering! another question, running the install script would do the trick on an existing and running 1.5.4 server?
Hello everyone, hope you all are alright in this troubled times!
I’m planning on finally upgrading my FOG server from version 1.5.4 to lattest stable version available, but I have some concerns I must address first, maybe you can provide me some insight!
im running the server in version 1.5.4, and with it, about 160 remote locations running Storages. Will I have any serious issues if I update only the main server to lattest version, leaving the storages on older versions?
About the Storages, I know the best to do when updating main server is to update the Storages at the same time to ensure compatibility. BUT the large maiority of my remote storages dont have Internet access. Considering this, is there any way I could upload everything to my Storages via local network and then make then offline update? In this case, updating the main server first or the storages first? Ah, my storages are all running on CentOS7.
thanks in advance, and stay safe!
@Sebastian-Roth said in Help with GPT partitioning:
Why is you EFI boot partition (type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B) at the end of the disk? It’s quite strange. Did you do this install yourself?
I did not. Unfortunally I got a base image to work with from higher ranks of my organization to work with. If it was all my work from scratch, I would never do this nosense. Do you think is there any way to move the EFI boot partition to the beggining of the disk without compromising the entire system or I’m doomed to restart from scratch?
Sorry for bringing this back to life, but I guess this needs a disclosure: i fixed the issue incresing the max connections on my DB and by reducing the time that MySQL keeps the idle connections active. Sorry for not bringing this earlier.
Hello guys, and sorry if this is the wrong place for this kind of question. I’ve been working on a Windows 10 Golden Image on a VM with a 200Gb HD, one partition for the SO and another for Data. As soon I finished building it, I did the capture with FOG, version 1.5.5.
Now I’m in the phase of deploying and testing the image against our hardwares, and one of them has a hd of 120Gb, wich is presenting problem on deploy, some error in the moment of restoring the GPT table.
My guess the problem involes the GPT partition being in the end of the disk, but I would like an insight from you guys, and if there’s any ways of making this work without restart building my image from scratch. Here follows the infos on the capture files and the error screen.
d1.partitions:
label: gpt
label-id: 594FBEB8-B041-4144-93F7-E40896645CC8
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 419430366
/dev/sda1 : start= 2048, size= 218431488, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=CA86F564-26DF-4F24-892B-8D895CA56995, name="Basic data partition"
/dev/sda2 : start= 218433536, size= 200585216, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=734653A0-99BF-4CE4-B30C-B56E2C63F1BF, name="Basic data partition"
/dev/sda3 : start= 419018752, size= 409600, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=4B808A8E-70C8-4555-B027-31D0FAED65F8, name="EFI system partition", attrs="GUID:63"
d1.minimum.partitions
label: gpt
label-id: 594FBEB8-B041-4144-93F7-E40896645CC8
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 419430366
/dev/sda1 : start= 2048, size= 40209666, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=CA86F564-26DF-4F24-892B-8D895CA56995, name="Basic data partition"
/dev/sda2 : start= 218433536, size= 4442810, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=734653A0-99BF-4CE4-B30C-B56E2C63F1BF, name="Basic data partition"
/dev/sda3 : start= 419018752, size= 409600, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=4B808A8E-70C8-4555-B027-31D0FAED65F8, name="EFI system partition", attrs="GUID:63"
d1.fixed_size_partitions
:3
d1.original.fstypes
/dev/sda1 ntfs
/dev/sda2 ntfs
Any insights if my conjectures are right, and if theres any way to fix it, would be very welcome
Thanks again in advance
@Tom-Elliott
Organization Name: Tribunal Regional Eleitoral do Paraná
Location: Paraná - Brazil
Approximate Number of systems: about 2500 registered hosts and 158 different locations
How long: since early 2018
Tribunal Regional Eleitoral do Paraná, a.k.a. TRE-PR, is the government body responsible for the electoral process (election, electronic ballot box, tabulation of results, etc.)
We’re proud to post here because at this very date, we concluded our implementation of FOG in our entire state (Paraná), wich means:
So, hurray and thanks for all the efforts of the development team and your support!
@Sebastian-Roth said in Error trying to restore GPT partition deploying an Image to Smaller Disk:
it doesn’t make much sense to me to set fixed to “:2:3:4”
indeed it does not make sense, because i confused myself haha =D
i meant to set fixed to “:1:2:3”, intending to keep the 3 first partitions fixed and the last one resizable as need. that also did not work.
i really don’t mind changing the files to achieve the desired result, but if fixed_size_partitions works, it would be a LOT more easier 
@Sebastian-Roth yeah, we did… To solve the problem i did that HEX edition on the d1.mbr file you suggested and it fixed my issue. what still intrigues me is the fact that using d1.fixed_size_partitions, i.e. changing it to :2:3:4 is not ensuring those partitions to stay with fixed size as i needed. to make it happen, i had to make the sizes on both d1.partitions and d1.minium.partitions the same.
i’ll take a look on this other forum link you mentioned.
I noticed sometimes it happened because my database max connections were exceeded, leading to an error on loading the menu.
Is there a way to change this behavior of iPXE commanding a reboot?
Hello everyone! Here’s my scenario: I have my computer’s boot order set to:
1st boot: Lan with PXE
2nd boot: Hard Disk.
Lets say that, for any mysterious reasons, the iPXE booting fails to load the FOG Boot Menu, in this case I would expect that it would continue to booting on the 2nd boot configured, Hard Disk in my case. But it’s not happening, after the iPXE fails happens, seconds later the machine reboots and the machine gets stuck in a loop boot->ipxe fail->reboot .
Am I doing anything wrong? Is there any setting in FOG i’m missing?
@Sebastian-Roth I’ll be running your requests asap, but I can antecipate you that the only manual alteration I tried before posting here was to adjust the d1.minimim.partitions sizes to match the d1.partitions, because using the d1.fixed_size_partitions was not forcing my system partition to 60Gb (/dev/sda3 and i need it to never be resized.)
Maybe the capture process have anything to do with this? What I did: Prepare the image using UEFI Bios, then switch to Legacy for the FOG Capture, then reverting back to UEFI. Same deal on the deploy: change to legacy to Fog Deploy, then reverting back to UEFI.
@Sebastian-Roth thanks for answering, and sorry for my absense, i was travelling to remote sites to implement more fogstorages
Here’s the output of fdisk as you requested:
here’s a link all files except the big img ones:
https://drive.google.com/drive/folders/1LLdjb_OsqiFrrOTesQDlxvrb0RF3hDUC?usp=sharing
@Sebastian-Roth here is the test you asked me to run.
it seems the problem is what you mentioned about partition positioning and resizing. Is there any way to work around this?
@Quazz I’ll try your suggestion right now, be back in a minute! EDIT: i’m back, and the error persists…
P.S.: Sorry for taking so long to return the test results, busy day!
Hello guys, can you give some insight about this issue I’m having please?
We’re upgrading our park to Windows 10, so we prepared an Image using a Notebook with a disk of 250Gb. The image has 2 data partitions (one with 60Gb for the SO, and another for data with the rest of the disk).
The capture process was successful. The deploying in other hardwares with bigger disks went well too. The issue is when we try to deploy to a hardware with smaller disk, especificaly one with a 120GB SSD. We’re getting this error:
image url)
I’ll try to provide as much information as possible firsthand. Anything else you guys need, or tests you want me to run, just ask! Thank you very much for your time!
Scenario: Fog version 1.5.5
Details about image captured:
Contents of /images/W10_SEMSIS_MULTI_1.01
ls -al /images/W10_SEMSIS_MULTI_1.01/
total 23558836
drwxrwxrwx 2 root root 4096 May 2 17:12 .
drwxrwxrwx 47 fog root 4096 Apr 30 14:33 ..
-rwxr-xr-x 1 root root 3 May 2 14:56 d1.fixed_size_partitions
-rwxrwxrwx 1 root root 1048576 Apr 30 14:18 d1.mbr
-rwxrwxrwx 1 root root 738 May 2 14:51 d1.minimum.partitions
-rwxrwxrwx 1 root root 45 Apr 30 14:18 d1.original.fstypes
-rwxrwxrwx 1 root root 0 Apr 30 14:18 d1.original.swapuuids
-rwxrwxrwx 1 root root 311 Apr 30 14:18 d1.original.uuids
-rwxrwxrwx 1 root root 557796 Apr 30 14:18 d1p1.img
-rwxrwxrwx 1 root root 13404976 Apr 30 14:18 d1p2.img
-rwxrwxrwx 1 root root 19562007460 Apr 30 14:31 d1p3.img
-rwxrwxrwx 1 root root 4547186410 Apr 30 14:33 d1p4.img
-rwxrwxrwx 1 root root 738 May 2 14:49 d1.partitions
Content of d1.fixed_size_partitions
cat d1.fixed_size_partitions
:2
Content of d1.minimum.partitions
cat d1.minimum.partitions
label: gpt
label-id: CBDC4619-6786-11E9-97EA-F82201FA303B
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 500118158
/dev/sda1 : start= 2048, size= 751104, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=CBDC4615-6786-11E9-97EA-F82201FA303B, name="attrs=\x22RequiredPartition GUID:63"
/dev/sda2 : start= 753152, size= 202752, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=CBDC4616-6786-11E9-97EA-F82201FA303B, name="attrs=\x22GUID:63"
/dev/sda3 : start= 955904, size= 125829120, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=CBDC4617-6786-11E9-97EA-F82201FA303B
/dev/sda4 : start= 126785024, size= 13564664, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=CBDC4618-6786-11E9-97EA-F82201FA303B
content of d1.partitions
cat d1.partitions
label: gpt
label-id: CBDC4619-6786-11E9-97EA-F82201FA303B
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 500118158
/dev/sda1 : start= 2048, size= 751104, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=CBDC4615-6786-11E9-97EA-F82201FA303B, name="attrs=\x22RequiredPartition GUID:63"
/dev/sda2 : start= 753152, size= 202752, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=CBDC4616-6786-11E9-97EA-F82201FA303B, name="attrs=\x22GUID:63"
/dev/sda3 : start= 955904, size= 125829120, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=CBDC4617-6786-11E9-97EA-F82201FA303B
/dev/sda4 : start= 126785024, size= 251604480, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=CBDC4618-6786-11E9-97EA-F82201FA303B
content of d1.original.fstypes
cat d1.original.fstypes
/dev/sda1 ntfs
/dev/sda3 ntfs
/dev/sda4 ntfs
Hello there from Brazil. If you still need, here’s a translation to “pt-BR” (brazilian portuguese)
### SHUTDOWN PROMPT ###
{company} precisa realizar manutenção neste computador.
Por favor salve todos os documentos e feche todos os programas.
Cancelar
Hide
Adiar
Reiniciar Agora
Desligar Agora
Adiar por
X hora(s) Y minuto(s) Z segundo(s)
### NOTIFICATIONS ###
Desligamento abortado
Desligamento foi abortado
Desligamendo adiado
Desligamento foi adiado para {time}
Desligamento acontecerá em {time}
Você está prestes a ser desconectado
Você será desconectado se permanecer inativo
Instalando {snapin name}
Por favor não desligue até a instalação ser concluída
{snapin name} instalado
Instalação foi concluída e está pronta para uso```Hey, I don’t know if I can do it myself, but you guys can set this one to solved
@tom-elliott i completely understand, and cant thank you enough for the time and the effort you guys put on this awesome solution! now I understood the ideas and the concepts of the iPXE menus, so this topic can be marked as solved.
just to let you guys know, i’m implementing Fog on our company, it will be managing around 3000 hosts, distributed around 200 diferent locations, so I’ll try to get involved with the project as much as I can from now on.
keep up the good work, guys!
@tom-elliott and @Sebastian-Roth again, thanks a lot for your time and explanations! The code @Tom-Elliott suggested me to put under FOG_ADVANCED_PXE field did the trick, and also helped me understand a bit more about the logic behind the boot menus.
Can you help me understand where my interpretation was wrong in the first time?
I hope you can undersand my pavorous english
@sebastian-roth i’m looking into @Tom-Elliott hints, he asked me about from where that second “#!ipxe” is comming from, so I went to check the code from “advanced.php”, it looks like this:
*/
require '../../commons/base.inc.php';
header('Content-type: text/plain');
/**
* Parses the statements to print the advanced menu
*
* @param array $Send the data to be parsed
*
* @return void
*/
$parseMe = function ($Send) {
foreach ($Send as $ipxe => &$val) {
printf("%s\n", implode("\n", (array)$val));
unset($val);
}
};
$login = isset($_REQUEST['login']);
$user = trim($_REQUEST['username']);
$pass = trim($_REQUEST['password']);
if ($login) {
$Send['loginstuff'] = array(
'#!ipxe',
'clear username',
'clear password',
'login',
'params',
'param username ${username}',
'param password ${password}',
'chain ${boot-url}/service/ipxe/advanced.php##params',
);
$parseMe($Send);
unset($_REQUEST['login']);
}
if (!empty($user)) {
$tmp = FOGCore::attemptLogin($user, $pass);
if ($tmp) {
$Send['loginsuccess'] = array(
'#!ipxe',
'set userID ${username}',
'chain ${boot-url}/service/ipxe/advanced.php',
);
} else {
$Send['loginfail'] = array(
'#!ipxe',
'clear username',
'clear password',
'echo Invalid login!',
'sleep 3',
'chain -ar ${boot-url}/service/ipxe/advanced.php',
);
$parseMe($Send);
unset($user, $pass);
}
}
printf(
"#!ipxe\n%s",
FOGCore::getSetting('FOG_PXE_ADVANCED')
);
so Im guessing that extra piece of “#!ipxe” that @Tom-Elliott told is not meant to be there is that last 4 lines, am I right?
printf(
"#!ipxe\n%s",
FOGCore::getSetting('FOG_PXE_ADVANCED')
);
Im thinking on changing it to this one, so the extra unnecessary #!ipxe would be gone, what do you think?
printf(
"\n%s",
FOGCore::getSetting('FOG_PXE_ADVANCED')
);```Well? Anyone have insights about this? Should I try another version of FOG, perhaps one directly from GitHub?