[RESOLVED] NTLDR is missing
Ich habe mittlerweile 2x mein Betriebssystem komplett neu installiert weil ich Acronis 2013 ausgeführt habe. Das Backup hat auch hervorragend geklappt und ist ohne Fehler durchgelaufen. Okay, CD raus, Neustart!
Ab jetzt ist es nicht mehr möglich das Betriebssystem zu starten, es endet immer in "NTLDR is missing".
Kann mir jemand sagen woran das liegt?
Das System besteht aus folgenden Komponenten:
Gigabyte Z77X-UP4 TH (Uefi) - i7-3770K - 16GB Speicher - Samsung830 SSD 128GB
ich bin vollkommen ratlos...
Danke, Michael.
Issue resolved here.
- Accedi per poter commentare
Hi Pat L, sorry for my english, i try to explain.
Operating System was W7-Ultimate 64bit, ATI not installed, i make a backup from my System SSD C: to my second HDD Samsung 103SJ only with CD.
My second try was the same but with installed ATI2013 & ADD11, cause i thought maybe that was the problem but it was the same result.
I try a Windows repair with my W7 Disk but after some tests and some auto try to repair from windows i became a message that it is not possible to repair this System. So i give up and made my third installation but i dont try again if im not shure what happened after backup, im carefully now.
Is it possible that ATI changes some settings on the backup disk? I just can not imagine that...
Perhaps the fault lies in UEFI and gpt? or i did something wrong, i dont know.
Thanks, Micha.
- Accedi per poter commentare
Mika,
Did you change any of the following? BIOS to UEFI and/or MBR to GPT?
Was your system multi-boot? Did you upgrade from XP to Windows7 and left the XP installation on the other disk?
http://answers.microsoft.com/en-us/windows/forum/windows_7-system/error…
When you say you made a backup from the C:\ SSD to the Samsung disk, did you backup the entire disk (ATI in disk mode) or only the C:\partition? On a modern Win7 computer, there is often some hidden partition like System Reserved or some other OEM partition (RECOVERY, etc.)? Did you include all of these in your backup?
- Accedi per poter commentare
I installed in UEFI Modus a clean W7-Ultimate 64bit to the SSD, so the SSD is GPT, no upgrade or something like that.
No Multiboot, no upgrade from XP, no OEM.
I made my Backups allways complete, with hidden partitions.
- Accedi per poter commentare
Mika,
Is your BIOS set up to boot to the right disk?
If yes, then it is probably the case that your BIOS settings are not correct for the type of disk that was created.
Boot with the Windows installation DVD, choose install, repair, command prompt. Type diskpart.
Then type list disk
Is your SSD effectively setup as GPT?
- Accedi per poter commentare
Moin Pat L,
the SSD is listet as GPT, the HDD not.
- Accedi per poter commentare
Problem solved, i made a new installation with a testdisk and delete the HDD D: complete, then i change the HDD from MBR to GPT and make a new partition on it. On the old MBR partition was a Acronis Secure Zone and i think the Computer tried to boot from this partition, thats why "NTLDR is missing". I think all what i had to do was disconnecting the HDD for one boot and everything is okay, for that problem i need more than 10hours, im a stupid goofy...
I don´t try a new Secure Zone, i save tib´s only in Files, works perfect. Sorry for any inconvenience...
Thanks, Micha.
- Accedi per poter commentare
Glad you solved it. NTLDR was from XP, shouldn't show up in late MS OSs.
- Accedi per poter commentare
yes, the Secure Zone was from the older XP Installation, i really think about the priority cause i tried every possible bios starts but it dont work. The only thing i dont do is disconnect the HDD, but that was what i have to do, grrrr.
However, maybe there is another goofy like me and this thread could help him.
- Accedi per poter commentare
Did you have an OS installed on that D: disk earlier? I doubt the ASZ was the source of the issue...
- Accedi per poter commentare
The BIOS was going to a hdisk looking for the secondary bootstrap (ntldr) and couldn't find it. It was going to the wrong disk, most likely e.g., going to disk 1 instead of disk 0. When you removed the other hdisk, it could only try to boot from the "correct" disk.
- Accedi per poter commentare
Pat L wrote:Did you have an OS installed on that D: disk earlier? I doubt the ASZ was the source of the issue...
no, this was the data Disk for me and i cut something for the ASZ...
Scott Hieber wrote:The BIOS was going to a hdisk looking for the secondary bootstrap (ntldr) and couldn't find it. It was going to the wrong disk, most likely e.g., going to disk 1 instead of disk 0. When you removed the other hdisk, it could only try to boot from the "correct" disk.
yes, thats what i thought, but later, over 10 working hours and more than 24 thinking hours later, now i can not believe i fell for that cheap crap.
I work with computers since 15 years, okay not for business only for me, my small company and friends , i buy acronis since 8 years and i have this failures allready, in W2000 often in XP not so much but i know it and i´ve forgotten it...damn
You never stop learning - you never can be shure or secure - i would be glad if my brain works like a HDD, so i could not forget anything.
- Accedi per poter commentare