Recovery boot screen replacing grub2

[Elementality]

Alright, I've searched high and low for a solution.

I'm dual booting Ubuntu and Windows 7. On my 7 partition I have Paragon Backup and Recovery Suite installed. This program has a boot screen, "press F6 to enter recovery console." Well, I have a boot disk for that console, rendering the boot screen useless to me. In addition to that, it replaces Grub2, so every time I want to boot Ubuntu I have to boot the livecd and reinstall grub. Is there any way to remove this boot screen?

Any advice would be great.

Thanks,
Elementality

[devils casper]

Hi and Welcome !

Does Ubuntu GRUB give an option to boot up Windows OS? Post the contents of /boot/grub/grub.cfg file here.

You should check Paragon Suite's Manual to disable its boot screen.

[Elementality]

Yes, there is a Windows 7 option which takes me to the Windows boot loader, except after this last install of grub the Windows 7 option command must be wrong, it takes me to an error screen. Is there anything I can do to let grub take precedence over any other boot screen?

Thanks,
Elementality

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s /boot/grub/grubenv ]; then
have_grubenv=true
load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
saved_entry=${prev_saved_entry}
save_env saved_entry
prev_saved_entry=
save_env prev_saved_entry
fi
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/white
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Ubuntu, Linux 2.6.31-20-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
linux /boot/vmlinuz-2.6.31-20-generic root=/dev/sda5 ro quiet splash
initrd /boot/initrd.img-2.6.31-20-generic
}
menuentry "Ubuntu, Linux 2.6.31-20-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
linux /boot/vmlinuz-2.6.31-20-generic root=/dev/sda5 ro single
initrd /boot/initrd.img-2.6.31-20-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda5 ro quiet splash
initrd /boot/initrd.img-2.6.31-14-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda5 ro single
initrd /boot/initrd.img-2.6.31-14-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Windows 7 (loader) (on /dev/sda1)" {
chainloader +1
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

[devils casper]

GRUB is chainloading Windows OS directly. Execute sudo update-grub command again to generate new GRUB Menu. In case it doesn't work, post the output of these commands :

sudo fdisk -l
sudo blkid

[Elementality]

So I did the update-grub and it didnt change the grub.cfg entry for windows 7. So I edited grub.cfg and added set root=(hd0,1) a line above chainloader +1, which will only hold up until my next update-grub and it will more than likely set it back to chainloader +1. But in the meantime that brought back my Windows boot loader. Then I booted windows and uninstalled paragon backup, and reinstalled to see if there was an option to not install the boot recovery console, it's all or nothing with that program.

Here's my current fdisk and blkid
tuck@Elementality-laptop:~$ sudo fdisk -l
[sudo] password for tuck:

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb4d3762b

Device Boot Start End Blocks Id System
/dev/sda1 * 1 7500 60242726 7 HPFS/NTFS
/dev/sda2 7501 8766 10169145 7 HPFS/NTFS
/dev/sda3 8767 18145 75336817+ 7 HPFS/NTFS
/dev/sda4 18146 19457 10538640 5 Extended
/dev/sda5 18146 19395 10040593+ 83 Linux
/dev/sda6 19396 19457 497983+ 82 Linux swap / Solaris
tuck@Elementality-laptop:~$ sudo blkid
/dev/sda1: UUID="405E1EAA5E1E992C" TYPE="ntfs"
/dev/sda2: UUID="E2E2220FE221E88D" TYPE="ntfs"
/dev/sda3: UUID="0D07D04643DD77A5" TYPE="ntfs"
/dev/sda5: UUID="9f5b7072-6cff-4e36-bc9d-439cd168c211" TYPE="ext4"
/dev/sda6: UUID="b15da10d-47a7-437c-aa5d-db3d24e4baf3" TYPE="swap"
tuck@Elementality-laptop:~$


Now I will run update-grub and see if it changes the windows 7 entry in grub.cfg
Yea, just as I thought. Changed the entry back to chainloader +1 without set root=(hd0,1)

here's my new fdisk and blkid
tuck@Elementality-laptop:~$ sudo fdisk -l

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb4d3762b

Device Boot Start End Blocks Id System
/dev/sda1 * 1 7500 60242726 7 HPFS/NTFS
/dev/sda2 7501 8766 10169145 7 HPFS/NTFS
/dev/sda3 8767 18145 75336817+ 7 HPFS/NTFS
/dev/sda4 18146 19457 10538640 5 Extended
/dev/sda5 18146 19395 10040593+ 83 Linux
/dev/sda6 19396 19457 497983+ 82 Linux swap / Solaris
tuck@Elementality-laptop:~$ sudo blkid
/dev/sda1: UUID="405E1EAA5E1E992C" TYPE="ntfs"
/dev/sda2: UUID="E2E2220FE221E88D" TYPE="ntfs"
/dev/sda3: UUID="0D07D04643DD77A5" TYPE="ntfs"
/dev/sda5: UUID="9f5b7072-6cff-4e36-bc9d-439cd168c211" TYPE="ext4"
/dev/sda6: UUID="b15da10d-47a7-437c-aa5d-db3d24e4baf3" TYPE="swap"
tuck@Elementality-laptop:~$

same as before

I suppose I could create a custom menu entry, I don't believe those get overwritten after an update.

[Elementality]

Update:

Alright, so I opened /ect/grub.d and edited 30_os-prober. it was missing "set root=(hd0,1)", saved it. Checked grub.cfg, still missing. ran update-grub and it looks like we're in business, it included "set root=(hd0,1)" and Windows is bootable. Now if I could only find a way get around this recovery console boot screen (it hasnt shown up since i havent ran a backup since i've reinstalled it.)

[devils casper]

I am glad that you have sorted out problem. GRUB2 is really smart boot loader but it has a few drawbacks too.
Well Done !