Guest User!

You are not Sophos Staff.

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

Having difficulty encrypting an HP Elite 8200 w/ 5.60: "Invalid Slice" "No/ Boot Loader"

The poster in this thread had the same issue. This results in the machine becoming unbootable. I have used SGNRollback twice to remove the software. The MBR was cleaned and all other steps were followed.

How do I make use of the latest POA settings database file? I see that I can run the SGNHWInfo which dumps out the following:

<?xml version="1.0" encoding="utf-8" ?>
<Actions>

	<Action>
		<Version></Version>
		<Condition>
			<Machine Vendor="Hewlett-Packard" UseVendor="1" Model="HP Compaq 8200 Elite SFF PC" UseModel="1" Type="" UseType="0" />
			<BIOS Vendor="Hewlett-Packard" UseVendor="1" Version="HPQOEM - 1072009" UseVersion="0" />
			<HardDisk Model="ST3500413AS" UseModel="0" />
			<HD-Controller VID="8086" UseVID="1" PID="1C00" UsePID="1" />
			<USB-Controller VID="8086" UseVID="0" PID="1C2D" UsePID="0" />
			<GraphicController VID="8086" UseVID="0" PID="0102" UsePID="0" />
			<VideoControllerDriver Vendor="Intel Corporation" UseVendor="0" Version="6.14.10.5361" UseVersion="0" />
		</Condition>
		<Command></Command>
	</Action>

</Actions>

Can I somehow use this information to successfully install the encryption?

:16105


This thread was automatically locked due to age.
  • Hi heyheyash,

    we are currently working on this machine. Can you please be so kind and raise a support call so that we can internally forward the information.

    Thank you & Regards

    Dan

    :16187
  • I submitted this via the form submission and have incident #2913509 . I have not heard from anyone yet however.

    :16331
  • Hi,

    unfortunately I cannot make any comments on the progress of tickets as requests have to be requested via the ticketing system or by phone.

    If you answer to the initial case opening mail that you received from our system the mail will automatically be attached to the case and your engineer will get back to. If you are entitled to a Platinum Contract there is even an option to review the ticket status online as I have heard but I have no detailed information about but at hand - please contact your Sophos sales person if you need any info on that.

    Regards

    Dan

    :16339
  • The fix ended up being very simple... an upgrade from 5.60 to 5.60.1!

    Thanks again!

    :16375
  • trying to install safeguard version 6 on a HP Elite 8200...

    I'm also getting the message  'invalid slice no/ boot/ loader' after I reboot following the client install

    I load windows 7 recovery using  installation disk and run command 'bootrec /mbr

    this allows the windows OS to load but the initial one-off encryption does not kick in when I log in

    not getting the safeguard POA screen either..

    any ideas?

    :25347
  • I had issues with this PC in 5.6, 5.60.1 fixed a lot of issues but I had the best results when upgrading to 6.  We have several flavors of this same version and they all work, although on some there is a 1-2 minute delay during POA startup because of the fact HP has a bad habbit of calling several different board revisions the exact same board and some of those revisions have minor hardware defects in the onboard sata controller.

    Sometimes you may have issues with switching into ATA mode or N13 mode at startup as configured by your install on some models, what you need to to is try using SHIFT+F6 or SHIFT+F5 depending on what flavor you have when it says "Starting Sophos SafeGuard" to switch the mode.  When that works and switches it over make sure to do a repair on the install then reboot and you should be able to access the system normally again.  We are an HP shop so this is a common issue with us.

    :25369
  • tried hotkeys.. still no joy

    :25387
  • This soulds almost like a corrupt boot loader POA environment.  Would it be possible to try upgrading to 6.0, the issues I experienced with HP hardware in 5.6 were fixed in 6.0.

    Also after getting back into the system do a drive test just to be on the safe side.  I've had issues where one sector of the POA gets put on a bad block or cross-linked sector on the disk causing strange issues nobody had ever scene before and it turns out the drive was bad and should have failed SMART but didn't.  Remember that sector based encryption and especially POA are dependant on a correctly working drive, more so than other types of software.  If the drive is erroring out but reporting it did everything ok it'll do everything correctly.

    :25409
  • That sounds like it needs an escalation tech to look at seriously.  I haven't scene that problem even once.   I've scene a few wierd errors when I didn't put in alloc mode into the registry for the install but never that one.

    :25779