Windows/Linux dual-boot imaging using Macrium

Hi,

Here they are.

ANG0.txt has the following at the end:
find --set-root --ignore-floppies /boot/grub/core.img
kernel /boot/grub/core.img
boot
# All your boot are belong to NeoSmart!
find --set-root --ignore-floppies /grub/core.img
kernel /grub/core.img
boot
# All your boot are belong to NeoSmart!
find --set-root --ignore-floppies /boot/grub2/core.img
kernel /boot/grub2/core.img
boot
# All your boot are belong to NeoSmart!
find --set-root --ignore-floppies /grub2/core.img
kernel /grub2/core.img
boot
# All your boot are belong to NeoSmart!
===============
It scans all drives (except floppies) for /boot/grub/core.img. If found then boot from that partition.
Not found... then it tries /grub/core.img
then /boot/grub2/core.img then /grub2/core.img

Because you restored the linux partition and it worked prior to restore.. file should still be there. Adding linux again to win7 bootmanager using easybcd.... linux still doesn't boot. Problem is most likely in linux itself

In the linux rescue prompt that you get type:

Code:

 
find --set-root --ignore-floppies /boot/grub/core.img
find --set-root --ignore-floppies /grub/core.img
find --set-root --ignore-floppies /boot/grub2/core.img
find --set-root --ignore-floppies /grub2/core.img

Does it find something?

Mmm. OK. I guess Linux just doesn't behave "nicely" when restored from a Macrium image.....that really all I wanted to determine. I thought it wouldn't have a problem, but.........

Unless I'm imaging incorrectly or restoring the image incorrectly, but I don't see how. Oh well.

EDIT: trying your suggestion now..........

At the grub rescue> prompt

Code:

find --set-root --ignore-floppies /boot/grub/core.img

Unknown command 'find'

In grub rescue:

Code:

 
ls (hd0,0)/
ls (hd0,1)/
ls (hd0,2)/
and more

What is your linux partition?
Even try

Code:

 
ls (hd0,msdos7)/

Even try msdos6, msdos8 or msdos1

From grub rescue> ls

(hd0) (hd0,msdos1) (hd1) (hd1,msdos7) (hd1,msdos6) (hd1,msdos5) (hd1,msdos2) (hd1,msdos1)

in linux rescue:

Code:

ls

you most likely see (hd0) and (fd0). But what else?

Golden said:

From grub rescue> ls

(hd0) (hd0,msdos1) (hd1) (hd1,msdos7) (hd1,msdos6) (hd1,msdos5) (hd1,msdos2) (hd1,msdos1)

Code:

 
ls (hd0,msdos7)/
ls (hd0,msdos7)/boot

Is that your linux partition?

OK. I tried several combinations of ls (hd0,msdos1)/ etc., each one returned unknown filesystem until I did this:

Code:

ls (hd1,msdos2)/

Code:

./ ../ lost+found. etc/ media/ bin /boot/ dev /home /lib /lib64 /mnt /opt/ proc/ root/ run/ sbin/ selinux/ srv/ sys/ tmp/ usr/ var/ vmlinuz initrd.img

Thus, (hd1, msdos2) is the Linux partition, correct?

Kaktussoft said:

Golden said:

From grub rescue> ls

(hd0) (hd0,msdos1) (hd1) (hd1,msdos7) (hd1,msdos6) (hd1,msdos5) (hd1,msdos2) (hd1,msdos1)

Code:

 
ls (hd0,msdos7)/
ls (hd0,msdos7)/boot

Is that your linux partition?

I meant hd0 instead of hd1!! Was typo