[1.3.0-RC-8] 'Virus Scan - Quarantine' does not boot

  • Server
    • Version: 1.3.0-RC-8
    • OS: Ubuntu 14.04 LTS
    • Version: 0.11.5
    • OS: Windows 7

    The ‘Virus Scan - Quarantine’ task fails shortly after loading iPXE. Here is an image of the error (sorry about the blurriness):


    I have not found any other tasks that have this issue.

    EDIT: Fixed image.

  • Senior Developer

    This should be fixed in RC9, please test and let us know.

  • Senior Developer

    This should be fixed in RC9, please test and let us know.

  • IMO, the virus stuff should just be removed from FOG. IF your AV has a bootable ISO, you can make this into a menu item via the web interface and some Linux-doings.

    I’m with Tom - both in theory and practice. We’ve had viruses. NEVER once did we want to repair the machine. All technicians always opt to image. Because it’s just that fast, and it fixes the issue every time. (another great reason to NOT isolate your fog server.)

  • @george1421 Mostly Avast (either Pro Antivirus or Internet Security), although we are in the process if switching to Webroot. Funny enough, the reason I wanted to try the virus scan is because Avast recently sent out an update that seems to have caused the boot-time scan to behave very strangely: it will start scanning and then will boot straight into Windows after only checking 1 or 2 percent of the files. As a result, I wanted to check out the ClamAV scan and see what it might bring up.

    @Tom-Elliott I’ll see if I can get those logs for you.

  • Moderator

    I would have to ask, what is your primary antivirus tool that is on these windows 7 targets?

  • Senior Developer

    I don’t know if I can fix this. The idea of init bootable antivirus was, at one point, a good idea, but typically it’s just faster to reimage a machine that to have it scanned or quarantined of virus’s. I’d recommend using your main av setup for this. I will try to see what’s causing the error of which you may be able to help as well. If you can setup another quarantine task and boot a system, then get us you Apache error logs it can probably point us towards what’s breaking it to begin with.

Log in to reply