I can't boot

With RAID1 (mirroring) you definitely lose all data if all of the disks go bad at the same time.

@gregrocker, (@lehnerus2000)

I don't have a SysRepairDisk but I think this functionality is also available with the Install-DVD where you can choose the automatic repair what I did as first thing.
But it said that the partition table had been repaired wich wasn't destroyed since I could access both partitions from the Ubuntu Live DVD. Therefor I used the specific commands...
I'm not sure if HW-RAID1 is really a problem with win7, which doesn't realize at all that it deals with a RAID system. It justs uses a different driver as for a normal single disk drive. That's what I think at least.



@Hipster Doofus,

Thanks for the link, it looks interesting and I'll go through it in more detail.
I couldn't find any guide mentioning the detailed differencies between the normal Bios and EFI /UEFI which might be the point due to different booting methods.

I'm thinking of another way to save my installation.
I allready copied my system partition from the Ubuntu Live DVD on a USB drive twice, once with dd thus making an exact raw copy from the whole partition and additionally with the tar command thus having only all of the data from the system partition.
Next I'm going of installing win7 on my system partition (overwriting the old installation).
This way the booting environment should be healthy again.
Then I could copy all of the tar-copied data onto the system partition...
I think it should work. Any opinions on that? Or experiences?

The other possibility would be to copy back the exact raw copy (dd) of the partition...

@lehnerus2000,

that's true, RAID1 doesn't replace backups and one should keep making them.
What I wanted to say is, it's better then having just one disk and only for the time between backups of course,
if say one of the disks gets damaged.

Success - At last!

Thank God I could save my installation!

I think the key action was to set the boot flag at the system partition using the GParted LiveCD (graphic mode).

Next the normal boot said (a different error message!): "bootmanager missing".

Then I booted from the installation cd (this time it showed up the installed OS correctly)
and setup the command "bootrec /fixboot" which earlier said "element not found", but this time it said "...successful".

Next normal boot said again "bootmanager missing".

Again booting from the install CD and tried the "bootrec /rebuildbcd": failed! No OS was shown up, Hey???!!!
Also "bootrec /scanOS" couldn't find the OS - The "repair disk" program recognized the OS(!).

Next I tried automatic repair and this time it could repair the correct things! I don't know why and what exactly happened.

The next thing I'm going to do is create a Recovery CD!

The Problems lasted 1 week but it paid not installing the whole shit from scratch.

Thanks for your help!

Glad it got fixed.

I'm not sure why users insist on sticking with old XP-era bootrec and bootsect commands when Win7 Startup Repair automates these as well as many other repairs which may also be needed. Lehnerus and I posted this a day ago along with a specific question which was not answered.

The procedure to repair Win7 is to mark the System Reserved or Win7 partition Active, then run Startup Repair up to 3 separate times with reboots until Win7 starts on its own. This works in about 80% of cases, while another 20% require extra steps.

Partition - Mark as Active (Method Two)
Startup Repair - Run 3 Separate Times
Partition Wizard