@tom-elliott thanks Tom! ok it’s working now, I forgot to change from dev branch to working one since my latest trouble. Everything is fine now! keep on good work!
Latest posts made by stormbyte
-
RE: Wrong registered client association since 1.5.0 RC9 upgrade
-
Wrong registered client association since 1.5.0 RC9 upgrade
Hi!
Using FOG since years without any trouble. Upgrade was done 2 days ago from 1.5.0 RC4 upto RC9.
First I had the isbitlockedpartition error and I solve it using your thread https://forums.fogproject.org/topic/11017/isbitlockedpartition-error
But now the main remains: all client are considered as the same! I can’t capture/deploy because PXE is not recognizing the active tasks for the computer.
Example:
launching a capture for computer TRAINING5
on TRAINING5 pxe is not recognizing the task (MAC is correct) and launching standard disk OS
then going on TRAINING5 PXE FOG menu and I see ‘Host is registered as TRAINING1’ !!! (and not TRAINING5!)
-> MAC adresses are different between TRAINING1 / 5 and correctly configured under FOGI’ve made many tests with 10 workstations/client, it’s the same FOG is not identifying correctly the computers.
FOG environment is working since years now, everything was checked (DHCP, FW, etc.) and nothing was moved since FOG 1.5.0 RC4 -> RC9 upgradeIn order to test again I then launched a task for TRAINING1, and it was correctly launched. So FOG is considered all my network as TRAINING1 hostname despite MAC?? (never had trouble before! each computer is technically the same, SHUTTLE mini PCs)
Then I delete all my 12 clients under FOG.
Having an emmpyt inventory, I then put only the TRAINING6 computer. I was able to launch taks, capture, etc.
I then put another client TRAINING2 in the inventory. I try to launch tasks, and it was not working again.
Again, PXE menu on TRAINING2 is whosing ‘Host registered as TRAINING6’ (and not TRAINING2!)How to solve this?:
- Downgrade?
- Purge database (I’ve checked database maintenance script but it’s not mentionned under 1.5.0 https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL)
Thanks for your expertise and feedback!
-
RE: Error trying to restore GTP partition tables (restorePartitionsTablesAndBootLoaders)
@Tom-Elliott Error message is: "Attempting to expand/fill partitions…awk: /usr/share/fog/lib/procsfdisk.awk:280: fatal: cannot open file ‘1:’ for reading (No such file or directory)
By the way the d1.fixed_siez_partitions already have a 1: inside… I just added a new one that created the error message above and it’s working fine
Here is the d1.fixe_size_partitions used:
0_1455648147461_d1.fixed_size_partitions -
RE: Error trying to restore GTP partition tables (restorePartitionsTablesAndBootLoaders)
@Tom-Elliott You’re the boss Tom I’ve added a :1 at the end of the d1.fixed_size_partitions and it’s working! Installation is OK, no problem for partition anymore.
BUT your solution is throwing an error just before the partclone (I didn’t catch it, it’s really fast on screen - if you need it I can record a video). Due to :1 … any chance to include this into a future FOG release or do I need to manually change my file for each capture?
Also, this solution is working for both resizable / not resizable captures ???
-
RE: Error trying to restore GTP partition tables (restorePartitionsTablesAndBootLoaders)
@Tom-Elliott Tom, I’ve updated but the problem is exactly the same … I’m ready to try your other suggestion!
-
RE: Error trying to restore GTP partition tables (restorePartitionsTablesAndBootLoaders)
@Tom-Elliott no problem Tom, there’s a life outside FOG world! please just tell me when you will deliver a new release to solve this problem, and thanks again for your time. I’m ready to make new tests if you need. Kind regards
-
RE: Error trying to restore GTP partition tables (restorePartitionsTablesAndBootLoaders)
@Tom-Elliott of course Tom, I’ve launched the station with debug mode. What command I should enter then on the workstation?
-
RE: Error trying to restore GTP partition tables (restorePartitionsTablesAndBootLoaders)
@Tom-Elliott unfortunately, same problem same error during partclone… what’s the next step?!?