@Sebastian-Roth @Wayne-Workman Just an update, making a folder for the image, switching the type, renaming image file to sys.img.000 and copying partition info into the new folder made the image work.
Best posts made by dustindizzle11
-
RE: Could Not Remove Old Partition?
-
RE: Grab Windows hostname during imaging??
@george1421 Thanks so much for your response. Just to share with anyone else who might use it, I just created a Powershell script that gets the hostname and emails me an alert about the system. Script below if you want it…(I am calling the script if certain criteria are not met (like missing drivers or something)…
$test=Test-Connection $env:COMPUTERNAME -count 1 | select Ipv4Address $IP=$test.IPV4Address.IPAddressToString $MAC=(gwmi -Class Win32_NetworkAdapterConfiguration | where { $_.IpAddress -eq $IP }).MACAddress $Hostname=Invoke-WebRequest http://192.168.64.14/fog/service/hostname.php?mac=$MAC $Hostname=$Hostname -split("\n") $Hostname=$Hostname[0] $Hostname=$Hostname.Replace("#!ok=", "") $Hostname=$Hostname.Trim() Send-MailMessage -To "YOURTOEMAIL" -From "FOG_WARNING@FOGALERTS.NET" -Subject "$Hostname Alert" -SmtpServer "YOUR SMTP SERVER" -Body "$Hostname had a problem... You need to fix this!!!!!"
Mod edited to use codebox.
-
RE: How to add live cd iso to Fog 1.2 on Ubuntu 12.04
@jbonilla Just in-case anyone else is trying to get this working, I had to add “union=overlay” after the “filesystem.squashfs” portion to get it working on my server.
:CLONEZILLA
kernel http://${fog-ip}/fog/service/ipxe/clonezilla/vmlinuz
initrd http://${fog-ip}/fog/service/ipxe/clonezilla/initrd.img
imgargs vmlinuz boot=live username=user fetch=http://${fog-ip}/fog/service/ipxe/clonezilla/filesystem.squashfs union=overlay locale=en_US.UTF-8 keyboard-layouts=NONE
boot || echo failed to boot
prompt
goto MENU``` -
RE: i219LM NIC, ASUS Q170M-C Motherboard
@Sebastian-Roth @Tom-Elliott @george1421
I took your advice and modified the init.xz to make a custom init, and all I did was just add “auto eth0” and “auto iface eth0 inet dhcp” to the interfaces file. It brings up eth0 and it images after adding this. So at this point it works. The fix is probably not the best fix in the world, but hey, it works!
-
RE: Fog Upgrade 0.31 to 1.2.0
I installed a fresh copy of 12.04 server with the same version of Fog that my current server had (0.31) and imported the database. After importing the database I installed the upgrade to 1.2.0. It was Friday evening and I was doing work on the Fog server through a VPN connection, so when I tried to upgrade the Schema it did it’s usual “hang”. I thought I would just figure it out on Tuesday when I came in for work. When I came in for work, to my surprise the test box had upgraded. My only theory is that it took some time to do, not sure why, but it ended up upgrading over the weekend.
This can be closed for now, but I am still unsure why the Schema would hang for such a long period of time to update the tables in the SQL database.
A quick note to anyone installing an older version (like 0.31) on ubuntu server 12.04, you will need to install SQL server BEFORE you run the install. I had to run “sudo rm -rf /var/lib/apt/lists/*” and “sudo apt-get update” before SQL server would install properly.
-
RE: Fog 1.2 replicating issue on master node
@Tom-Elliott Thanks Tom.
I upgraded all the nodes. What cleared the error is below.
The issue was that this was a “part-image” type of image that I updated and re-uploaded which converted it into a partclone image. The master node overwrote the old file when I uploaded the image. The other nodes though, which get the image updated from the master still had the old image on them which was a file, not a directory which partclone seems to use. Once I deleted the old image from the nodes, it replicated to the others without the error.
-
RE: Fog 1.2 "is a directory", "not a partclone image" download issue
I have just solved this issue. The problem is that the image was uploaded with the “vista” OS type. I think this must be broken in 1.2. I was able to recover my image by changing the name of the image file inside the folder to “sys.img.000” and changing the OS type of the image to “Windows 7”. To do this, simply browse on your master node, or where your images are stored and rename the largest file inside the image folder to the “sys.img.000”. I was able to fix two images I uploaded with the vista OS type.