Categories

  • 13k Topics
    115k Posts
    T

    unnamed (1).jpg

  • Get the latest news on what's happening.
    184 Topics
    825 Posts
    A

    @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

  • View tutorials or talk about FOG in general.
    2k Topics
    19k Posts
    V

    Re: Wiping HD

    It was mentioned in an earlier post:

    @george1421 said in Wiping HD:

    @lostitguy We you will need to make up your own fog ipxe menu to specifically call the wipe function.

    I am not 100% sure I have the stanza right but it should look like this

    Menu Item: fog.wipeit
    Description: FOG builtin Disk Eraser Tool
    Parameters:
    kernel tftp://${fog-ip}/bzImage
    initrd tftp://${fog-ip}/init.xz
    imagargs bzImage initrd=init.xz root=/dev/ram0 rw ramdisk_size=256000 ip=dhcp web=${fog-ip}/fog/ consoleblank=0 loglevel=4 mode=wipe wipemode=full
    imgfetch init.xz
    boot ||
    goto MENU
    Menu Show with: All Hosts

    I was trying this today. As things likely changed since this was posted I found that I needed to change:

    kernel tftp://${fog-ip}/bzImage
    initrd tftp://${fog-ip}/init.xz

    With :

    kernel http://${fog-ip}/fog/service/ipxe/bzImage
    initrd http://${fog-ip}/fog/service/ipxe/init.xz

    Also there was a ram error so needed to increase size of the ramdisk to something larger such as 512000

    I also omitted imgfetch init.xz and it still worked to my understandimg. Can someone please confirm that this line is redundant?

    I get a database failed to update after the wipe. I am assuming this is because the wipe was initiated without being tasked?

    Also I was surprised that the full wipe on the nvme SSD took less than a minute. Shouldn’t it take much long to write zeros or does FOG wipe perform some other type of erasure? If so what kind of erase method does FOG use for wipemode=full ?

  • Report bugs, request features, or get the latest progress.
    2k Topics
    21k Posts
    Tom ElliottT

    @Valer Thanks for the report and the writeup, that’s a good catch. You’re right about the cause. Debian 13 dropped the sysv-rc-conf package since it’s fully on systemd now, so the installer chokes trying to apt-get it. We never actually use that tool on a systemd system anyway, it only ever got called on the old non-systemd paths, so it was just dead weight on Trixie.

    I pushed a fix to working-1.6. It leaves the package off the list on Debian 13 and up, and it also strips it out of a cached .fogsettings so an in-place upgrade doesn’t drag it back in. Older Debian keeps installing it like before so nothing changes there.

    If you want to get moving before you pull the update, you can either grab the latest working-1.6 and rerun the installer, or just open /opt/fog/.fogsettings and delete sysv-rc-conf from the packages line, then run the installer again. Either one gets you past it.

    Let me know if you hit anything else on Trixie.

51

Online

12.7k

Users

17.6k

Topics

156.8k

Posts