Grub.cnf with additional IF-LSE-THEN construction and CLZ-program on MBR or GPT??
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
Section 1:
On my desktop computer, motherboard ASUS P7P55D, I have installed an OEM W7-Ult-64bits O.S. (on /dev/sda1 in Dutch language and on /dev/sda2 the same for English.
After the installation (2012) of the W7 I have created an image for restoring in case of accidents. On a second HDD I did install Ubuntu-12.04 and made room (NTFS) for the repository of the “Clone images” on /dev/sdb5. All was fixed successfully, in 2012, with help of Clonezilla-live-20100318-karmic.iso.
At the moment I will replace the first HDD (WD 320GB) by a SSD (Samsung 256 GB).
In the mine time the W7 occupies ~60GB on /dev/sda2 and I have created a second image located at /dev/sdb5 for recovery by means of (the latest) Clonezilla-live-20140331-saucy-amd64.iso.
Moreover, I did restore this W7, to an external disk, connected to the same Desktop PC (so the new SSD is not burden SSD to much). In this trial the target location became /dev/sdg2.
After that I have installed Ubuntu 14.04 behind this W7 partition on an Extended partition /dev/sdg5. (CLZ warned for to change fstab and the grub configuration file, afterwards).
All these actions proceeded well and after restarting the computer a well-known screen (Grub2) appeared, with the possibility to choose for Ubuntu or W7. The first one started without any problem, but not W7: black window with blinking dash symbol.
That means W7 would NOT boot!
After this I repeated the same Restore, but now to the SSD: /dev/sda2, exactly the same error
of a not booting W7!
What may be the reason?
The different grub.cfg files below will help to find the reason?
I don’t understand the parameters in the additional “if else then” construction, but more important what has “/etc/grub/30_os-prober” found by writing some hints about EFI?
Or is it a question of choosing a wrong Clz iso file?
I did install the CLZ-2014 on an USB2.0-flash disk by means of Tuxboot.
I did also use Tuxboot for Installing (the latest) gparted on an USB drive: that was a disaster! Are these latest ISO files only intended for GTP instead of the MBR in the applied PC type?
Sub_Section 1
Attachment:
7-7-2014 Differences in Grub.cnf between versions 2012 and 2014 for the menuentry's of Windows 7 (loader):
2012:
menuentry "Windows 7 (loader) (on /dev/sda2)" --class windows --class os {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set=root 781C1DFC1C1DB65A
chainloader +1
2014:
BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 7 (loader) (on /dev/sdg2)' --class windows --class os $menuentry_id_option 'osprober-chain-781C1DFC1C1DB65A' {
insmod part_msdos
insmod ntfs
set root='hd6,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd6,msdos2 --hint-efi=hd6,msdos2 --hint-baremetal=ahci6,msdos2 781C1DFC1C1DB65A
else
search --no-floppy --fs-uuid --set=root 781C1DFC1C1DB65A
fi
parttool ${root} hidden-
chainloader +1
}
set timeout_style=menu
if [ "${timeout}" = 0 ]; then
set timeout=10
fi
END /etc/grub.d/30_os-prober ###
Sorry for the too long text. Next time I shall apply "Add attachments" (found below).
That is just the problem: my PC is NOT an uEFI machine!
So i did apply the wrong Clozilla iso file?
Therefore my question to you: is the latest Clonezilla-live-20140331-saucy-amd64.iso applicable for a machine with an old partition table ms-dos? Or just forbidden to use on my machine?
Did you try to use Clonezilla live on flash drive to save your uEFI machine then restore the image?
If so, does the restored OS boot?
If it works, then you can start to put that on hard drive for adding such as restoring mechanism.
Steven.