New
#11
have you tried this command?
bootsect.exe /nt60 C:
drive letters switched after changing motherboard
-
-
New #12
I wonder if you are getting hung up on the drive letter part. Don't worry about the letters at all. The truth is, whatever volume you boot from becomes C.
Once we get the boot issue figured out, if you still have trouble with the letters, we can work on it from Disk Management.
Now, maybe I'm a little confused too. When you said "it doesn't boot", what happened?
If you're sure the 100GB partition is active, and startup repair doesn't fix it, try these commands:
bootrec /fixboot
bootrec /fix mbr
bootrec /rebuildbcd
Then try a startup repair.
-
New #13
Sorry. I need to clarify. It's not so much drive letters. That's been sorted out (c is c again, d is d again). There's just no longer a system reserve which I had named z:. I used diskpart and deleted it. I found the article on bootrec after you had mentioned it in a previous article, and went through the steps of using all of the bootrec commands. And it looked like it had completed ok. I restarted, the system booted to the windows logon with the coloured balls...and subequently rebooted. Using Windows 7 repair disk, I used a command window and saw again. No 100mb partition of system reserve. For whatever reason, it appears 7 does not want to create that reserve partition even though it show it available for use. I'm stumped at this point.
Little edit - I tried running
bootrec /rebuildbcd
after running
bootrec /fixboot
bootrec /fix mbr
fixmbr and boot worked. Rebuildbcd gives a "successfully scanned Windows installations. Total identified Windows Installations: 0
The operation completed successfully".
Well. Shit. Windows is definitely installed. I can change from x:\windows\system32\ to c:\windows or root of c: etc. And windows is definitely installed. I wonder why it won't recognize the installation and rebuild the bcd. Damn this is frustrating. And no bootsect.exe /nt60 C: is a good idea, but didn't work. one of the first things I tried.
more edit.
bootrec /scanos does the same thing. Successfully scanned Windows installations. Total identified Windows installations: 0
The operation completed successfully.
I don't get it.Last edited by tercero; 02 Apr 2010 at 08:28.
-
New #14
Installing win7 onto a completely empty disk will automatically add the system reserved partition this is the only way I know to achieve this.
As you now have existing partitions this will no longer occur.
What you need to do now is to replace the windows 7 startup files onto the windows system drive as these were located on the system reserved partition that has been deleted, which is why this partition was marked as active.
You should be able to achieve this by running the startup repair several times without anything in between, from the install disk - sometimes a single run is not enough
-
New #15
Thanks Barman. I'm trying a variation on that very idea. I was lucky to have 4 other 1 tb disks available (removed from a DNS 321). I used one of the disk to do a fresh install of windows 7. Next, I tried doing a restore from a months old image of my original system. It reimaged c: and z:, with the predictable results that the system would halt on the windows logo. I rebooted, using the windows 7 repair disk, went to a command window, used diskpart, set the 100 gig partition (containing the os) to active. Next I ran startup repair, it found something, rebooted. And it halted and told me there was an error in the boot/bcd. To inset the install disk an choose repair. I did. And I'm back to where I was. It won't get past the swirling logo. It halts and reboots.I'm almost ready to admit defeat. And I'm a bit worried about causing surface errors on the disks everytime I do a hard reboot. I'll try a couple more things and then admit defeat. I'm disappointed that windows 7 does not allow for a repair install unless you actually have the os running and log in as admin. Seems pointless.
-
New #16
That is strange - I have done a few startup repairs to win7 systems over the last 18 months (Yes I'm and early adopter who like to test to destruction), every one has succeeded. This includes many where the system would not boot
Rather than go the BCDedit route after the first repair fails did you try to run the actual startup repair a second time - I have known systems where it has taken 3 or 4 runs to actually expedite the repair
-
New #17
If you have an installation DVD, you don't need the Z:\System Reserve partition anyway. That partition only contains the repair files, which you can access by booting from the DVD anyway. I haven't deleted mine, but I have the DVD, and don't really need it.
By the way, I had the same thing happen to me twice. Windows would halt at the logo at boot. I got so frustrated that I just went and started to watch a movie, and just let it sit. 20 minutes later, my desktop was up, and never had a problem again. For some reason it just took forever to get past the logo screen the first time.
-
New #18
I'm trying another install...again (arghh). This time I'll try writing over the files with files from the system that won't start...preserving the /boot only. I might as well mix and match and see what happens. I think Windows 7 hates me.
-
New #19
I thought it hated me too. For some reason it just took awhile to get past the logo screen on the first install. I have no idea why, but try a little patience next time, and see if that pays off. Can't hurt any. I know it worked for me.
-
New #20
Quote
Related Discussions