Posts made by BedCruncher

@Wayne-Workman
I’ve just downloaded, extracted, uploaded and successfully booted from the most current release of SRCD.
That is version 4.8.1 with absolutely NO MODIFICATIONS to the posted boot menu. So the above works flawlessly.

@EAHarvey
One thing you might could try. I know in the past I’ve used a bootable usb that helped to boot into FOG. I am not sure if it would allow you to automate some of the things you were wanting to do to bypass that or not.

GPXE Bootable USB

Just kinda throwing that out there.

It’s a nice collection of utilities I’ve used in the past to do many things I can’t do. It’s a fairly lightweight OS too all told weighing in at around 364MB. For what it allows it’s really powerful. I will try to update this with the latest one, but it does work perfectly fine otherwise.

@Wayne-Workman
It’s version 2.4.1

https://www.system-rescue-cd.org/SystemRescueCd_Homepage

Here is the description of what it is/does.

About SystemRescueCd
Description: SystemRescueCd is a Linux system rescue disk available as a bootable CD-ROM or USB stick for administrating or repairing your system and data after a crash. It aims to provide an easy way to carry out admin tasks on your computer, such as creating and editing the hard disk partitions. It comes with a lot of linux software such as system tools (parted, partimage, fstools, …) and basic tools (editors, midnight commander, network tools). It can be used for both Linux and windows computers, and on desktops as well as servers. This rescue system requires no installation as it can be booted from a CD/DVD drive or USB stick, but it can be installed on the hard disk if you wish. The kernel supports all important file systems (ext2/ext3/ext4, reiserfs, btrfs, xfs, jfs, vfat, ntfs), as well as network filesystems (samba and nfs)

I’ve recently got this working on my server figured I would share. For informational purposes I’ve extracted the following files to /var/www/html/srcd

initram.igz
rescue64
sysrcd.dat
sysrcd.md5

My menu entry is as follows

@Joe-Gill
I would suggest setting network boot as first priority and then setting a timeout of 5 seconds on the menu so that if there is no task, then at most your boot time is impacted maybe 40 seconds.

@Towndrunk
There is a setting under the header Multicast Settings that is called FOG_UDPCAST_MAXWAIT you might look there to see if that is where you set the 10 minute timeout.

@Towndrunk
Try this…

systemctl stop FOGMulticastManager
killall udp-sender
killall udp-sender
killall udp-sender
mysql -u root fog
TRUNCATE TABLE multicastSessionsAssoc;
TRUNCATE TABLE multicastSessions;
TRUNCATE TABLE tasks;
quit;
systemctl start FOGMulticastManager

I would suggest doing that as it’s what I do on my images.
Deleting Hiberfile.sys
I have a first logon script that reenables it so that I don’t have to waste space storing a file that might or might not be the same size on any machines I deploy my image to.

@cnewman402
Check out what I have done in my server with this iPXE boot menu. I’ve got quite a few ISO’s booting on my setup using memdisk.

:dban
menu DBAN Nuke Menu
item autonuke AutoNuke DoD 3-Pass
item zero AutoNuke 1-Pass Zero Wipe
item choose-disk Single Disk Selection
item return Back to top menu...
item
choose --default return --timeout 10000 target && goto ${target}
:autonuke
kernel http://${fog-ip}/dban/dban.bzi nuke="dwipe --autonuke" silent vga=785
boot || goto failed
:zero
kernel http://${fog-ip}/dban/dban.bzi nuke="dwipe --autonuke --method zero" silent vga=785
boot || goto failed
:choose-disk
kernel http://${fog-ip}/dban/dban.bzi nuke="dwipe" silent vga=785
boot || goto failed
:return
chain ${boot-url}/service/ipxe/boot.php?mac=${net0/mac} || prompt goto MENU
:WHDD
kernel http://${fog-ip}/whdd/whdd.bzi
initrd http://${fog-ip}/whdd/initramfs
boot
:HDT
initrd http://${fog-ip}/hdt/hdt.iso
chain http://${fog-ip}/hdt/memdisk iso raw
boot
:AVG
initrd http://${fog-ip}/avg/avg.iso
chain http://${fog-ip}/avg/memdisk iso raw
boot
:BreakIn
initrd http://${fog-ip}/breakin/breakin.iso
chain http://${fog-ip}/breakin/memdisk iso raw
boot

@Wayne-Workman
This just occured to me, but it seems exactly like the problem that I was having before with the custom rules that I had in my server. This is something that you had suggested that I do and it very well could solve the issue that is happening here…
https://forums.fogproject.org/topic/7245/multicast-issues-on-centos-7/51

@Wayne-Workman
Ok… so once I made some tweaks on this… I ran into a small issue getting the DBAN working properly while doing the timeout config. Ultimately here is where I stand with my current menu. This includes a new choice for disk selection as well as a default timeout of 10 seconds. It will then kick back to the main menu if it times out. I reverted back to using ${fog-ip} as well. After looking back at it as my ${boot-url} is http://${fog-ip}/${fog-webroot}. but all of my ISO’s whether mounted or chained using memdisk are mounted or stored in a directory off of webserver root instead of buried under the fog subdirectory.

:dban
menu DBAN Nuke Menu
item autonuke AutoNuke DoD 3-Pass
item zero AutoNuke 1-Pass Zero Wipe
item choose-disk Single Disk Selection
item return Back to top menu...
item
choose --default return --timeout 10000 target && goto ${target}
:autonuke
kernel http://${fog-ip}/dban/dban.bzi nuke="dwipe --autonuke" silent vga=785
boot || goto failed
:zero
kernel http://${fog-ip}/dban/dban.bzi nuke="dwipe --autonuke --method zero" silent vga=785
boot || goto failed
:choose-disk
kernel http://${fog-ip}/dban/dban.bzi nuke="dwipe" silent vga=785
boot || goto failed
:return
chain ${boot-url}/service/ipxe/boot.php?mac=${net0/mac} || prompt goto MENU

@Wayne-Workman
Thanks Wayne. So far it seems to be working flawlessly. The few times I tried navigating around the menus it didn’t seem to be an issue. The only thing I might consider doing different is adding a timer and default selection to return to the main menu.

Want to make sure I am doing this right… what I have seems to work, but I just want to make sure that I am not doing anything weird.

menu DBAN Nuke Menu
item autonuke AutoNuke DoD 3-Pass
item zero AutoNuke 1-Pass Zero Wipe
item return Back to top menu...
item
choose selected && goto ${selected} || goto failed
:autonuke
kernel ${boot_url}/dban/dban.bzi nuke="dwipe --autonuke" silent vga=785
boot || goto failed
:zero
kernel ${boot_url}/dban/dban.bzi nuke="dwipe --autonuke --method zero" silent vga=785
boot || goto failed
:return
chain ${boot_url}/service/ipxe/boot.php?mac=${net0/mac} || prompt goto MENU

EDIT:
changed
http://${fog-ip}/${fog-webroot}
to
${boot_url}
as they are functionally the same and to keep it consistent.

@Quazz
OK!!! Houston we have liftoff…

I was able to get this working by completely ignoring mounting the iso at all and instead doing what I had found in another forum with directly using memdisk and the raw iso. My working config for this is as follows

@Quazz
the folder hdt is simply the mount point for the iso. It houses only the subfolder isolinux which contains the folder contents listed above. I will delve into the isolinux.cfg file to see where I can tweak it.Will report back with anything I can find.

@Quazz
Tried both, menu.c32 gives same blinking cursor. isolinux.bin provides the following.

@Tom-Elliott
set fog-ip 192.168.240.10
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}

@Quazz
Just changed. Will have to wait a bit before I can test that. I’m also upgrading that laptop to W10 to beat the deadline. Will post back once I can try again.

EDIT:
After modifying the menu entry as you wanted me to do, I simply get a black screen with blinking cursor.