@mparlette @george1421 Thanks. I’m not sure what the issue was, but I believe it to have been network related. I didn’t realize it initially when I posted but the pings I was doing, showed dropped packets galore (even while some were successful). I’m working my way through the install guide after creating a new VM, and so far it’s looking alright. No packet loss on an initial test ping. We’ll see what happens when I start the FOG installer!
EDIT:
SUCCESS!
@george1421 I was following the guide here:
https://wiki.fogproject.org/wiki/index.php?title=CentOS_7
@george1421 I’m able to ping google by URL, but not fogproject. However, I am able to ping it by the IP listed.
[root@localhost ~]# ping google.com
PING google.com (172.217.8.174) 56(84) bytes of data.
64 bytes from ord37s08-in-f14.1e100.net (172.217.8.174): icmp_seq=5 ttl=56 time=8.09 ms
64 bytes from ord37s08-in-f14.1e100.net (172.217.8.174): icmp_seq=6 ttl=56 time=8.18 ms
64 bytes from ord37s08-in-f14.1e100.net (172.217.8.174): icmp_seq=7 ttl=56 time=8.13 ms
64 bytes from ord37s08-in-f14.1e100.net (172.217.8.174): icmp_seq=8 ttl=56 time=8.20 ms
^X64 bytes from ord37s08-in-f14.1e100.net (172.217.8.174): icmp_seq=9 ttl=56 time=8.13 ms
^C
--- google.com ping statistics ---
9 packets transmitted, 5 received, 44% packet loss, time 8019ms
rtt min/avg/max/mdev = 8.099/8.152/8.204/0.120 ms
[root@localhost ~]# ping google.com
PING google.com (172.217.8.174) 56(84) bytes of data.
64 bytes from ord37s08-in-f14.1e100.net (172.217.8.174): icmp_seq=4 ttl=56 time=8.15 ms
64 bytes from ord37s08-in-f14.1e100.net (172.217.8.174): icmp_seq=5 ttl=56 time=8.20 ms
64 bytes from ord37s08-in-f14.1e100.net (172.217.8.174): icmp_seq=6 ttl=56 time=8.16 ms
^X64 bytes from ord37s08-in-f14.1e100.net (172.217.8.174): icmp_seq=7 ttl=56 time=8.20 ms
^C
[root@localhost ~]# ping www.fogproject.org
PING fogproject.org (162.213.199.177) 56(84) bytes of data.
^C
--- fogproject.org ping statistics ---
49 packets transmitted, 0 received, 100% packet loss, time 48010ms
[root@localhost git]# ping 172.217.8.174
PING 172.217.8.174 (172.217.8.174) 56(84) bytes of data.
64 bytes from 172.217.8.174: icmp_seq=3 ttl=56 time=8.26 ms
64 bytes from 172.217.8.174: icmp_seq=4 ttl=56 time=8.13 ms
64 bytes from 172.217.8.174: icmp_seq=5 ttl=56 time=8.13 ms
^C
--- 172.217.8.174 ping statistics ---
5 packets transmitted, 3 received, 40% packet loss, time 4002ms
rtt min/avg/max/mdev = 8.136/8.178/8.262/0.119 ms
@george1421 So this is interesting… I’m able to ping machines on our local network, but I cannot ping www.fogproject.org.
That said, the machine definitely has internet access (as I am currently posting this from said machine).
@george1421 Thanks for the reply, it has direct access.
After not being able to get the install to complete on Ubuntu 18 or 16 due to inability to download binaries, I decided to give the CentOS install a shot. While it went better in terms of not having to deal with sourcing some of the required packages that are deprecated, the install is still failing at the
* Downloading binaries needed.................................Failed!
I’ve included the error log for the attempted CentOS install.
0_1530198049150_fog_error_1.5.4.log
Is there a way that I can download the binaries manually?
@george1421 I’ll attempt to. Not sure if this is coincidence, or not, but for some reason the (ISA) network card isn’t working on my Windows install now. Like it doesn’t even show in my network adapters list anymore. Attempted to go through the “Add New Hardware” prompts, won’t recognize on hardware scan. When I try to add it manually by selecting from list, it’s present but there is an error message next to it, saying the device failed to start. Tried ignoring it and re-installing the drivers anyways, but was unsuccessful.
@george1421 Burned to CD-R, it’s booting from it now, but it seems like it’s only seeing the onboard (non-functioning) network card.
EDIT:
I disabled both ports via BIOS configuration, and it still fails.
I take back my previous statement, I think that it’s at least recognizing the ISA card. If I have a cable plugged in the MAC shows up as 94:94:94:… but if it’s not plugged in, it’s all 0’s
@george1421 Upon further inspection, I don’t think the disk-drive is capable of reading from the disk I used, or something. I attempted to browse the disk in Explorer and I get an error saying the disk may be corrupt.
@george1421 Well I wasn’t actually able to boot from the image… or at least it seems that way. I set my boot order accordingly; on startup it went through the normal stuff, then "Boot from CD: " was displayed, the cursor blinked for 20 to 30 seconds, and it proceeded to boot from the HDD.
@george1421 I’m not seeing where the IP is applicable on rom-o-matic. I’m probably overlooking something, attempting to create a different boot image. I didn’t have any luck with the image you provided.
@george1421 Thanks. This is greatly appreciated, I’ve got it on a disk. I’ll have to wait until our production hours are over to test, but I’ll get back to you.
@george1421 Oh sorry, (duhhh moment), 192.168.30.11 is the IP address I use internally.
@george1421 Unfortunately no, because it’s on a hidden sub-net, kept in the dark from the outside world.
Prior to having FOG set up ransom-ware got to the current machine in question, along with 2 other identical machines. Put our production team down for two days thanks to one of our electrical eng’s downloading some printer drivers from a shady website. Crawled nearly our entire network.
@george1421 Yeah, there’s no USB port on the board to speak of, I was insinuating I’d need to buy a (non-existent) card to go that route.
Also, this network card appears to have a socket with no chip.
However, I’m inclined to believe what you said about the firmware being built in if the socket isn’t present because the links you provided to the Intel boot utility specifies it’s compatible with Pro/100… but I don’t think I have one it’s compatible with, per the empty socket. I’ll have to try, unfortunately that will have to wait until the machine isn’t being used.
@george1421 No, there’s nothing in the socket, that coupled with the fact that I don’t think ISA-to-USB cards even exist is why I was thinking I needed to find a new wireless card, unless there is a way I could use that boot image on a CD or floppy disk. Plan on diving into all that today to see where I can get.
Yes, indeed it is!
The intel links provided look familiar, I may have attempted this already some time ago. I seem to remember lack of support for the ISA cards. However, I could be mistaken, I’ll give it a shot.
<edit> First stop: Find a boot rom or a new card, I guess.
So I have a bit of a particular situation here.
I have a dated machine that I’ve previously used FOG to backup, however since then the network card has died. Since I need network connectivity on the machine otherwise, I have installed an ISA Intel EtherExpress Pro/100 which allows me access while using WinXP. However, I cannot figure out what I can do to continue using FOG via this off-board network card.
I cannot replace the motherboard, proprietary BIOS.
If there is another imaging solution that would allow me to backup over my network using this ISA card, feel free to recommend. I’m not opposed to using another product, I just already have fog configured for this machine and others.
@Wayne-Workman I killed subversion. Nothing, still showed up as an unformated repo, (repos still on the vm were still available too, via browser). Uninstalled subversion. Nada, repos still accessible via browser across our network. Uninstalled, purged apache2, renamed /etc/apache2/ which held some files used by subversion. Reinstalled apache2, fresh /etc/apache2 dir, but now: this.