Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Can't get Win7 to boot, drive letters changed


  • Please log in to reply

#16
dmccoy

dmccoy

    GeekU Sophomore

  • GeekU Sophomore
  • PipPipPip
  • 693 posts
Okay that should work. The,first command was a duplicate anyway. Try to restart and see what happens. I don’t understand why you cannot access your drives in command prompt though?
  • 0

Advertisements


#17
dmccoy

dmccoy

    GeekU Sophomore

  • GeekU Sophomore
  • PipPipPip
  • 693 posts
If it doesnt work. Then perform the following and provide the output

diskpart
list disk

Edited by dmccoy, 28 January 2018 - 04:24 PM.

  • 0

#18
mailalan

mailalan

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts

Still can't reboot. This is the result of the listDisk command:

 

listdisk.jpg


  • 0

#19
dmccoy

dmccoy

    GeekU Sophomore

  • GeekU Sophomore
  • PipPipPip
  • 693 posts
Did you change the boot order in the bios to the correct C: drive? Run the bcdedit again and provide a picture.
  • 0

#20
mailalan

mailalan

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts

I'm not sure what you mean by "correct C: drive". I havent changed anything in the BIOS. I removed the Win 7 installation disk and rebooted. The screen showed "Starting Windows" with multicolored dots that swirl in to form the Windows logo. However it freezes on that screen and then reboots itself and then gives the message saying "Windows did not start correctly......"

 

What bcdedit command do you want me to run?


  • 0

#21
dmccoy

dmccoy

    GeekU Sophomore

  • GeekU Sophomore
  • PipPipPip
  • 693 posts
Okay. I mean when you at command prompt you should be able to access your c: drive by typing C: for example

Please run the this command bcdedit > 0 & notepad 0 and provide the output file or picture again.
  • 0

#22
mailalan

mailalan

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts

Here's the result of that command:

 

bcdedit.jpg


  • 0

#23
dmccoy

dmccoy

    GeekU Sophomore

  • GeekU Sophomore
  • PipPipPip
  • 693 posts
It didnt change anything. Are you sure these last commands ran successfully? Run them again and check that it changed the bootloader location by using bcdedit command again

bcdedit /set {default} device partition=C:
bcdedit /set {default} osdevice partition=C:

Option 2. Manually reassign drive letters and make correct C: drive active
diskpart
list disk
select disk 0
list volume
select volume 1 (or correct letter of C:)
remove letter=C
exit

diskpart
list disk
select disk 0
list volume
select volume 2 (or correct letter of E:)
assign letter=C
exit

diskpart
list disk
select disk 0
list volume
select volume 2 (or correct letter of C:)
active
exit

Then you may have to rebuild the boot file once C drive is working and active.

bootrec /RebuildBcd
bootrec /fixMbr
bootrec /fixboot

Edited by dmccoy, 28 January 2018 - 05:32 PM.

  • 0

#24
mailalan

mailalan

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts

I ran the commands again and again they ran successfully. I then ran the bcdedit > 0 & notepad 0 command again and verified that it changed the bootloader location. However when I reboot the system does not save the changes, it fails to boot and when I run the bcdedit command again the bootloader location reverts back to the E: drive.

I had already tried using diskpart to manually assign the drive letters before I made this forum post. Just like above, it will show me that it has manually reassigned the drive letters to what I need them to be while I am in the Win 7 Recovery Environment but as soon as I reboot the system reassigns the incorrect drive letters. It seems any changes made in the recovery environment don't stick.

When I recovered the RAID array composed of the 4 spinning drives I ran a live system rescue disk to do that. I used the TestDisk software and it rebuilt the partition successfully. That did stick. I believe I can delete the partition which is now labeled C: using TestDisk. Should I try that?


  • 0

#25
dmccoy

dmccoy

    GeekU Sophomore

  • GeekU Sophomore
  • PipPipPip
  • 693 posts
I think it is all regarding your raid array which is causing the difficulty. You don’t want to remove the system Reserve partition it is required and should be the first partition. I am not familiar enough with raid to feel I can offer you the best assistance. However, my last idea would be to use a disk partition program such as minitool or other and see if you can assign the correct drive letters and move the partitions to the correct locations. Maybe someone else with have some other ideas as well.
  • 0

Advertisements


#26
mailalan

mailalan

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts

Okay thank you very much for your help!


  • 0

#27
dmccoy

dmccoy

    GeekU Sophomore

  • GeekU Sophomore
  • PipPipPip
  • 693 posts
You’re welcome sorry you didn’t have better results. Let us know if you figure it out or can do anything else.
  • 0

#28
dmccoy

dmccoy

    GeekU Sophomore

  • GeekU Sophomore
  • PipPipPip
  • 693 posts
I was thinking about this again today and I think i was looking at it wrong last night. We want to move or create your boot files on your drive listed as E since it has Windows installed. Have you tried that option? If not run the following command to change and see if it will boot.

bcdboot c:\windows /s c:

Next option, if you haven’t tried already. Only connect the two raid drives and make sure the hard drive listed as E is on Sata 0 so it is the default and should be listed as C: then see if it will boot or you can at least access from command line.
  • 0

#29
mailalan

mailalan

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts

I don't think running that command will do any good since nothing I do in the recovery environment command prompt seems to stick when I reboot. Someone else also suggested to me to connect only the two SSD RAID drives so I will try that and let you know. Thank you for perservering!


  • 0

#30
dmccoy

dmccoy

    GeekU Sophomore

  • GeekU Sophomore
  • PipPipPip
  • 693 posts
Yeah until we can get One of your drives to show with command prompt it probably useless. Let me know what you find out with the other option.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP