Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 24 replies
  • Subscribers 1 subscriber
  • Views 21021 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Error Message: Rootkit scan cancelled due to a corrupt disk

sophos-icated

We are seeing the rootkit scan fail on multiple systems due to a "corrupt disk".  Specifically the error is:

Code: a01e0004

Description: Rootkit scan cancelled due to a corrupt disk

Have checked systems experiencing this error and there is no problem with the disk (scans are negative).  Any idea what corrupt disk this might refer to.  Also interesting is clicking on the link back to sophos knowledgebase comes up with nothing.  That is there is no entry for error code a01e0004.

We are running enterprise console 4.0.0.2362. 

System experiencing the error is running Windows Vista service pack 2.

Anyone have ideas on what might be causing this?

Thanks in advance.

:1514


This thread was automatically locked due to age.
  • 0

    I've seen this one a handful of machines now running version 9.5

    Has there been any updates on what causes this or how to fix it?

    :4532
  • 0

    Hi

    We have upgraded to 9.5 and i still have 2 machines with this error.

    James

    :4877
  • 0

    I am also seeing this on a few machines at a client site. Would be nice to know the cause and if it's an issue.

    :4887
  • 0

     I have this message.  The scan didn't actually shut down - it just hung up.

    Windows Defender also fails to finish the scan - it slows to a crawl.

    I think my system is infected, but I don't know what to do about it.

    Details.

    ***************** Sophos Anti-Virus Log - 24/10/2010 14:06:22 **************
    ...
    20101024 111309    Scan 'Scan my computer' started.
    20101024 120135    Rootkit scan has been cancelled due to a corrupt disk.
    20101024 120237    Using detection data version 4.58G (detection engine 3.12.1). This version can detect 2032840 items.
    20101024 120238    User (NT AUTHORITY\LOCAL SERVICE) has started on-access scanning for this machine.

     
     
     
    Sophos Anti-Virus9.0.5
    Release statusFull
    On-access statusEnabled
    Detection engine3.12.1
    Detection data4.58G
    Virus data date04/10/2010
    Items detected2032840
    Detection identities230
    HIPS rules version3.2.0
    HIPS configuration version1.0.4
    Last updated24/10/2010 10:41:07
     
     
     
     

    *

    :5588
  • 0

    We are seeing the error on several PC.  Some running 7.5 and others running 9.5.  Code is a01e0004 but does not return anything from the Sophos site.

    :6249
  • 0

    this is still going on. I'm really not impressed with the response from Sophos on this issue.

    I have 234 machines managed and I'm now into the double digits with the number of machines now getting this error.

    Please fix this!

    :7527
  • 0

    Hi cvaisey,

    This is generally caused by a timeout by the scanner, so the message you receive is quite generic.

    Can you message me your case reference please?

    How many machines are actually showing this error ?

    Can you replicate it on demand by doing a scan ?

    Is it specific machines/OS's?

    Is there a specific spec of the machines giving the error ?

    Thanks,

    OD

    :7537
  • 0

    I am getting this error as well, on multiple Windows XP SP3 and Windows Vista SP1 machines. Sophos version 9.5.4 VDL4.61G, Enterprise Console version 4.5.1.0. Error happens every day during a daily Full Scan that includes a "Scan for Suspicious Files"

    :8327
  • 0

    I would like to add that since upgrading to SAV v9.5 and console 4.5.1, hopeful that it would resolve the issue as promised by Sophos support, we are still experiencing the above error. For us it is all exclusively related to laptops, Windows 7 for the most part in our case.  We have been promised a fix to this for some time now, please step up Sophos and resolve the issue.

    :8607
  • 0

    Hello,

    We have recently identified issue where the corrupt disk message could be sent when a timeout occuers during the scan.

    The team is currently looking into this and i hope to have an update soon.

    Regards,

    Shai Gelbaum

    Product Manager

    :8701