My friend asked me to help him dual boot Linux on his computer, so I used the device manager to shrink his Windows partition and installed Ubuntu in the free space. He has a Lenovo Y580, which features RapidDrive technology. As I understood it, this technology was like ReadyBoost, but with an mSATA Solid State Drive. I was wrong. RapidDrive operates at a filesystem level, effectively spanning the data across the solid state drive and the hard disk drive. This configuration isn't readable by anything but the host installation of Windows and Lenovo's One Key Recovery (OKR) factory-defaults restoration software.
For some reason probably related to RapidDrive, the Ubuntu install failed. After the installation completed, GRUB2 (the GRand Unified Bootloader, version 2) didn't appear. After some troubleshooting, I decided that I wanted to boot into Windows, and found that I couldn't. The (broken) copy of GRUB had overwritten Microsoft's bootloader.
I tried to use Super Grub Disk to boot the Windows partition manually, but it wouldn't work. So I decided to use the Windows Recovery Disc to repair the startup process. It worked, but it made things worse. Instead of repairing the boot for my Windows installation, it "repaired" it for Lenovo's hidden OKR partitions. As I understand it, the bootsector points to one of the recovery partitions which has the Boot Manager installed in it. Unfortunately, there isn't a BCD store on that partition, so the boot fails, and I can't boot the recovery partition. There is, apparently, a store on the other recovery partition, because when I try to boot it manually, it says that it can't access the device it needs (0xc000000e).
Running startup repair again produces the same result every time: an error about a corrupted filesystem. Unfortunately, a "corrupted" filesystem (one on the SSD that's bigger than the drive, and one on the HDD that's missing data) is normal for a RapidDrive system.
Is there a way to manually configure the Windows 7 bootloader to point to the partition I need it to, without access to the destination Windows partition?
Also, is there a way that I can restore the ability to boot my recovery partition?