Direkt zum Inhalt

Problems creating Secure Zone, kernel panic after reboot ("kernel panic everywhere")

Thread needs solution

Computer: Sony VAIO VGN-AR51J (laptop)
O/S: Windows 7 Professional (64-bit)
HDD: Seagate Momentus 7200.5 500GB SATA 2.5" (16MB Cache / 7200RPM ) ST9500423AS
Product: Acronis True Image 2013 (Trail)
Partitions: System Reserved, C: and ASZ
Acronis Startup Recovery Manager = Enabled

Hi!

Trying to create an ASZ (Acronis Secure Zone) to put my future backup of my HDD on and when I get a prompt asking me to restart I of course do it.

But now comes the problem, the computer freezes when I see the Acronis logo and the white text.
The same problem (freezing) also occurs when I try to boot into the Acronis Startup Recovery Manager (ASRM?) after I click on "Acronis". It also happens when I try to use a bootable rescue disk created with Acronis, no matter if its USB or DVD.

I have tried to reproduce it but I can't seem to get the same error message as I used to.
Earlier I got something like "kernel panic, could not sync, kill init d" but now when I tried ASRM it "hangs" on:
c1312012 ? acpi_pci_slot_init+0x1b/0x1b

I have exchanged the HDD in my computer from a 200GB 4200RPM HDD to a 500GB 7200RPM HDD.
I have also installed Win 7 Pro 64-bit and the computer comes preinstalled with Win Vista HP 32-bit.
All drivers reports as being installed and working.

Think I got the same problem when trying the bootable rescue disk even when I still had the old HDD in the computer OR perhaps it was the new HDD but still using Vista, I'm unsure.

Would appreciate help :)

Another question:
If my trail runs out and I have a partition on the ASZ could I still boot via the ASRM and restore it to my HDD or will it simply say "trail expired"? If so will I be able to enter a license code to be able to use the program without doing anything else?

0 Users found this helpful

N/A

Sorry my mistake, didn't think it should have been an reply only wanted to subscribe to get email updates.

I advise against creating the Secure Zone. It's really meant as a sub-optimal method of backup for people who have no external target to which to backup. If your drive fails, you would lose your system, files, and your Secure Zone backups.

It's much better and safer to make backup images to an external hard drive.

Also, in the past there were occasonal reports of the Secure Zone causing problems to the system. When I installed Secure Zone on one PC, it corrupted the hard drive causing data loss and rendering the system unbootable. Perhaps the latest versions of Secure Zone are improved, but that experience coupled with its inherent insecurity and lack of reduncancy cause me to be wary of Secure Zone.

I also recommend against the associated Startup Recovery Manager. If activated, it modifies your system drive Master Boot Record (MBR), which can cause problems with multi-boot managers and other low-level disk utilities.