RUnning the install to “working” resolved my issue. Thanks for the help!
C
Posts made by callcenter
-
RE: Unable to register host after upgrading to 1.50 /bin/fog.man.reg errorposted in FOG Problems
-
RE: Unable to register host after upgrading to 1.50 /bin/fog.man.reg errorposted in FOG Problems
@mfang I had the same issue after going from 1.4.0 to 1.5.0. I’m building images for a new rollout and thought this upgrade was not going to impact my workflow. Now I’m stuck! Any help from an admin would be appreciated…
-
RE: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) Kernel Offset: disabledposted in FOG Problems
It was the windows DHCP scopes having the old 67 option in them instead of the new undionly.kpxe program. updated all my scopes and tested-ok not using the main server options since my wifi and telco devices do not need PXE. I saw others make mention of doing that instead of every scope having the references. In my environment it just doesn’t make sense.
thanks for the help.
-
RE: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) Kernel Offset: disabledposted in FOG Problems
Dear All,
New user/taken over 1.3.8 project from coworker.
I am having the same issue after upgrading to 1.4.0 today. Not sure where to change pxelinux.0 reference. Using windows as DHCP with options set. Any help would be great!!
