Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 5 subscribers
  • Views 8091 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

SGM400 Kernel Load Failure

RJ_Shane

Hello.

Has anyone seen the SGM400 error before and, if so, has there been any success in fixing it?

Thanks!

PS: I should add that the product is SafeGuard Enterprise 5.50.8. Thanks, again!

:26595


This thread was automatically locked due to age.
  • 0

    Yea I had the error on some newer HP desktop hardware that wasn't support correctly until SG 5.60.1 with POA config file because HP likes to change their board revisions in several places in the world all at once and call it the same thing.  The sata controller was reporting it was one thing but it was another.  Fixed in SG 6.0 without POA config though you should deploy the latest as a matter of good practice.

    :26611
  • 0

    Hi RJ_Shane,

    if your installation was not a new install, this error can arise when the SafeGuard kernel has been corrupted. Possibly due to a hard disk failure or physical dmadge to the harddiks.

    To resolve this you will need to rebuild the kernel.


    This can be done by using the SafeGuard recovery environment CD, (WinPE), which can be downloaded from the link below

    SafeGuard Device Encryption: Recovering data from a volume-based encrypted SafeGuard Device Encryption Client

    The Download Recovery Guide pdf will guide you through accessing the encrypted drive, which is essential to perform the fix.


    After unlocking the drive, you should be able to see the encrypted files on the local disk. At that point, click on BE_restore from the quick launch bar near the bottom of the screen. Click repair to completely repair the kernel and re-write the MBR.

    The repair process can take up to 30 minutes to complete.

    Hope that helps,

    Chris

    :26675
  • 0

    I unlocked the drive and attempted the repair according to the instructions, but received a response that the kernel couldn't be found. All HDD diagnostics came back without finding a problem so, in the end, I had to reimage the machine. It's been running fine ever since.

    :27775
Unfiltered HTML