Posts made by cammykool

I would like to be able to move my father’s server to a proper piece of server hardware instead of the optiplex 790 it’s running on right now. Problem I’m facing is the server requires raid to be configured. I’m really trying not to have to go through the fog configuration again because it took me like a week to get right last time. what would be a good way to hopefully this transfer my current installation on to this new box? Fog is contained on an SSD with a 1 TB hard drive set to a folder in fstab. Plan on creating an ext4 disk in the raid copying all of my images to it and pointing fstab there for that folder. made an external clone of the fog drive and tried to boot it on the server without going into the RAID controller and it would not let me the required I initialize it which of course wipes to drive. Am I just kind of stuck with having to do a full rebuild? Thanks.

I have the fog client as part of all of my images for active directory joining(something i am still working on getting to work) I am wondering what else it is capable of? Can we remotely do things on the machines? Rebooting/updating etc. im just kind of wondering what the fog client can do before i go looking at other remote management stuff.

Thanks!

I cant find a clear answer as to if i can get this to boot. is there a way to get it to boot a hyperv? I have EFI and BIOS booting working properly

Thank you!

@george1421 ill run and IM you that pcap

pointed it all to ipxe.efi and get that as a return followed article to a T

@george1421 when i had looked previosly it didnt show me the option for EFi PXE like his guide showed. Just regular PXE.

So one of our deplyed machines is UEFI PXE only. What is the process for configuring that separate to this?

@george1421 Thanks man. I appreciate it.

@george1421

https://drive.google.com/open?id=1j0MRC88x-0h-5iLnocLhEgvdKHj8CWgB

@george1421 no just DHCP on 10.1.0.1

DNS is 2 and 3

Still ARP timeout. now the DHCP IP is 10.1.0.3 before it was 10.1.0.2

user@fog:~$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 18:03:73:cf:ab:5a brd ff:ff:ff:ff:ff:ff
    inet 10.1.80.1/16 brd 10.1.255.255 scope global noprefixroute enp0s25
       valid_lft forever preferred_lft forever
    inet6 fe80::7298:8d49:d303:484d/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

there we go

Do you think subnet mask could be the issue?

image url)

This is the data he gave me to use LMAO

@george1421 huh my windows box is getting 255.255.0.0 too. He gave me the 255.0.0.0 to use. Ill Change it

im working on the guide i was sent initially. boss gave me direct access to the DHCP server

yes it is. Netowkr manager has always been correct.

@george1421 it looked to be /8 too before

pxe is still getting 255.255.0.0 at boot

@george1421 ip addr show is still showing 255.255.255 even after changing in network manager

user@fog:~$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 18:03:73:cf:ab:5a brd ff:ff:ff:ff:ff:ff
    inet 10.1.80.1/8 brd 10.255.255.255 scope global noprefixroute enp0s25
       valid_lft forever preferred_lft forever
    inet6 fe80::7298:8d49:d303:484d/64 scope link noprefixroute
       valid_lft forever preferred_lft forever