Aller au contenu principal

Can't boot recovery with Crucial M4 SSD

Thread needs solution

I've used most versions of TI over the years and never had a problem, and haven't had a problem backing up with current system either, but the other day I needed to recover some system files and after the reboot stage it looked like the bootloader was corrupt - screen showed:

Starting Acronis Loader ... (random ASCII characters) - see attached.

and the system was hung. I had to use the Win8 DVD and Bootrec to get the system bootable.

So then I tried booting the TI 2013 recovery CD - but that hung after the second splash screen if I chose TI. I tried another disc built from the TI tools menu then the one you can download from My Account / Get Updates. Both hang. I then tried booting from USB flash using GRUB4DOS and the TI recovery ISO - that fails with the common "unable to create initial RAMDRIVE" error.

Now the weird thing is, if I change my BIOS from AHCI to IDE, all three recoveries boot OK.

FWIW I'm using the latest TI 2013 (6514), the SSD is a Crucial M4 with the latest firmware (070H). mobo is a Gigabyte GA-P43-ES3G with 8GB RAM.

My recovery disks and flash drive all boot OK on another system here, also with a Crucial M4 SSD (but 040H firmware) and AHCI mode, so they aren't corrupt.

Fichier attaché Taille
acronisboot.jpg 210.4 Ko
0 Users found this helpful

The problem you are describing (the garbled text and boot issues) with build 6514 Rescue Media have been reported on this forum several times by other users. This problem does not exist on all systems (including my own - three separate systems).

This seems to be due to a different Linux kernel and/or drivers (or other program changes) being used in the 6514 build of 2013 Rescue Media as compared to earlier releases and builds of the recovery environment and Rescue Media (both use the same Linux kernel).

I would suggest that you open a support case with Acronis (no charge as this is recovery related). They can make available a newer build of the ISO (build 6528) that has several fixes implemented (GPT disk issues and mice/keyboard issues - possibly others?). This Rescue Media ISO MAY work properly on your system.

You should obtain this ISO (and create Rescue Media) and use it to perform ANY operations that normally would require a reboot into the recovery environment.

Until a new version is released that contains fixes that may help your situation, the Acronis Startup Recovery Manager, as well as a restore to a live/active OS partition and/or a clone operation from within windows should be avoided (because of the issues you described).

Thanks - I'd been searching on SSD problems but I just tried again with the SSD disconnected; recovery CDs still don't boot so it must be a BIOS or system hw issue.

I've requested 6528 from Support - I hadn't appreciated that recovery problems were FOC.

Meanwhile I tried downgrading to build 5551 and creating a rescue CD. That does boot the Linux kernel after the menu but it looks like there error messages that scroll too fast to read and I just end up at a "#" command prompt. Not sure what I can do from there - my knowledge of Linux commands ends with "ls".

Wish I could find (a legal source for) the original 2013 build - I'm pretty sure that worked.

Laurie,

If you have registered your serial number to your Acronis account, the 5551 build is available for you to download at all times.

See screenshot below.

Fichier attaché Taille
133664-108286.png 9.38 Ko

I already said that I tried 5551; it gives errors then drops into the Linux prompt "as-is", but does work with the boot parameters "quiet vga=ask acpi=off" that has been suggested elsewhere. Those parms don't help with 6514.

Meanwhile Support sent me the Recovery ISO for 6528 - but that also hangs after the second splash screen (the one that lists the patents).

Still I do now have a working boot CD should I need to do a recovery.