Best posts made by Scott B

@tprice said:

2. What is the best combination for installing FOG i.e. is Ubuntu better than Centos?

Just my personal preference, but I’ve always been happy with FOG on Ubuntu and formerly Fedora.

@Pascal-Gazaille said:

Hi,
I’m on Ubuntu 14.04.2 LTS with Fog 1.2.0. I’m trying to update to latest svn but during the fog installation I get :

• Addubg needed repository…Failed!

and everything stops

What can I do?

I had this issue and finally found my filter was blocking launchpad.net. After allow access to that page it updated like a charm.

Do you mean to make it so the image file(s) can’t be overwritten? There is a checkbox under the properties of the image in FOG for “protected” that makes it so this isn’t possible if so.

@THEMCV

I’d buy one.

@Wayne-Workman said:

@Scott-B Just get rid of those…

Backup your DB first. FOG Configuration -> Configuration Save -> Export

For an individual:

update inventory set iOtherTag='' where iID=1972;

For everything:

update inventory set iOtherTag='' where iOtherTag like '%\\\\\\\\\\\\\\%';

Thank you, that cleaned up the list very well.

What do the logs on the server suggest the issue could be?

Please provide some details of the server. Ubuntu? Fedora? Versions? Do the log files on the server point to anything?

@Tom-Elliott said:

@Scott-B Is it possible that the links are causing weird things?

Can you delete all webroot paths for fog?

rm -rf /var/www/fog
rm -rf /var/www/html/fog

Then rerun the fog installer?

Thanks Tom, that did the trick.

@Sebastian-Roth said:

Marking this solved for now as we didn’t hear back from anyone. If you have printer issues please follow the link Wayne posted below. If you still think there is an issue within FOG please let us know!

I apologize for the delay, been swamped. It does seem the issue has been resolved. I have not seen it after the past several SVNs. Thank you very much for your help.

With a lot of help from @Sebastian-Roth we did track down the issue. Someone must have been in our DHCP server and changed the case of the undionly.kpxe to all caps… thus not finding the file. Sometimes is those simple things you just don’t think to look for. Thanks again for your help Sebastian!

@Wayne-Workman said in Target partition is smaller than source:

@Scott-B Can you try a resizable image? If for no other purpose than to see the result?
@Scott-B Remember after changing that on the image you need to re-upload. Or just create a new image.

I made new images and made them realizable. They all seem to be working just fine that way so I’ll go with it.

@Sebastian-Roth said in Target partition is smaller than source:

Now that I have done some testing I don’t think this is the same issue than @robza has. He’s got a totally different partition layout (which I mentioned already) which we don’t do a very good detection on yet. His problem will never be fixed by re-trying I am sure! Will get to this later.

Now back to @Scott-B’s issue. Your partition layout is very simple and should not cause any trouble. Don’t get me wrong. Not saying that I don’t believe you but I need to kindly ask you to give us some more information. The picture you posted is Roger Saffle’s. While I don’t mind reusing anyones pictures we really need your information here to figure out what’s going wrong (with your image/partition layout).

So can you please to me a favor: Create a new image definition (so you don’t need to mess with your working ones) and make it Single disk - non-resizable. Upload from the same client you have before (so we have the same information in d1.partitions). Then deploy this new image in debug mode to one of your clients. If you get an error, please take a picture and run the following command when you get back to the command shell: sfdisk -d /dev/sda (again take a picture). If it does not fail could you please try over and over till you see the error.

I can, but won’t be able to get to it till Monday. @Roger-Saffle and I work together. Same machines in question.

@Scott-B said in chainloading failed advanced menu:

I think we are good. I was able to add DBAN back to the menu list.

For anyone who may find this thread down the road below is the quick advanced menu I wrote for this thread.

#!ipxe
menu
item --gap – ---------------- iPXE boot menu ----------------
item DBAN Boot and Nuke
item DBANAUTO Boot and Nuke Autowipe
item HIRENSCD Hirens Boot CD (Most Features Outdated)
item GPARTED GParted Partition Editor 
item SRCD System Rescue CD
item SHELL iPXE Shell
item RETURN Return to previous menu
choose --default RETURN --timeout 10000 target && goto ${target}

:DBAN
kernel ${boot_url}/dban/dban.bzi nuke="dwipe" silent vga=785
boot
goto MENU

:DBANAUTO
kernel ${boot_url}/dban/dban.bzi nuke="dwipe --autonuke" silent nousb vga=785
boot
goto MENU

:HIRENSCD
sanboot http://${fog-ip}/hirenscd/HirensBootCD152.iso
chain memdisk iso raw ||
goto MENU

:GPARTED
kernel http://${fog-ip}/gparted/live/vmlinuz vmlinuz boot=live config components union=overlay username=user noswap noeject ip= vga=788 fetch=${fog-ip}/gparted/live/filesystem.squashfs
initrd http://${fog-ip}/gparted/live/initrd.img
boot

:SRCD
kernel http://${fog-ip}/srcd/rescue64 netboot=http://${fog-ip}/srcd/sysrcd.dat
initrd http://${fog-ip}/srcd/initram.igz
boot
boot

:SHELL
shell ||
goto MENU

:RETURN
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
prompt
goto MENU

autoboot```

@george1421 said in New Image Upload - Stuck on Updating Database:

I have an image going up now. I’ll see what it does.