Well, no I've tried that and it didn't work. Now /Boot and bootmgr reside in sda3 (Windows 7) apart from sda2 (RECOVERY).
update-grub discovers two "Windows 7 loader", the first on sda2 and the second on sda3. Second one works fine now and loads W7 but the first one which is supposed to start the recovery process, simply halts.
Any ideas of how I may improve the current situation to resolve the recovery option as well?
Bookmarks