@george1421 That did the trick. Now I need to dig into why its failing to capture an image. I’ll make a different post for that though if I need to.
Best posts made by TectonicLeader
-
RE: Tftp connection timed out 4c126092
Latest posts made by TectonicLeader
-
Unique Virtual Box Setup Network Issues
I am trying to setup FOG in a virtual box on an isolated network. This network cannot be connected to internet but the host computer can be. The problem is I do not see a way to have VB connected to both networks at once in a way that fog can use properly. Kind of lost here I see a lot of posts from 12 years ago about this stuff but it seems mostly outdated now.
-
RE: Image capture (Disk has bad sectors) SSD
@Tom-Elliott I’ve done that. I’ll try swapping the drive but I am fairly confident that’s not the issue.
-
Image capture (Disk has bad sectors) SSD
I am getting this error. The SSD is fine there are no issues with it as far as I can tell here is the error screen. The screen. Fog is running on Ubuntu on a custom machine and the computer being captured is also custom.
-
RE: Unable to capture: No route to Host
@youzersef It looks like that is for HDD I am using an SSD. I followed the steps anyway and it has changed the error but its freezing up in the same spot still. New Error
-
RE: Unable to capture: No route to Host
@youzersef Looks like it helped still have an issue though. The Next Issue
-
RE: Unable to capture: No route to Host
@youzersef I am trying to capture an image from a host. https://wiki.fogproject.org/wiki/index.php?title=Booting_into_FOG_and_Capturing_your_first_Image The server is 192.168.1.3 and the host is 192.168.1.7. Yes they are on the same network.
-
RE: Unable to capture: No route to Host
@youzersef I changed the router because it was causing a failure to boot via PXE.
-
RE: Unable to capture: No route to Host
@youzersef Its the IP the server used to be on before I switched to a different network.
-
RE: Unable to capture: No route to Host
Yea there is no device registered to that IP on the network currently.
-
RE: Unable to capture: No route to Host
@youzersef Do you mean 192.168.1.2 that’s the machine the fog server used to be running on… Huh