LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   NTLDR missing after slack install ? (https://www.linuxquestions.org/questions/slackware-14/ntldr-missing-after-slack-install-235205/)

e1000 09-25-2004 07:14 PM

NTLDR missing after slack install ?
 
I just installed slackware 10 on my 200gb hard drive (/dev/hdb) partitioned as fallows

hdb1: 50gb windows (NTFS)
hdb2: 100gb windows (NTFS)
hdb3: 45gb Slackware (reiser)
hdb4: 3gb swap

I wrote lilo to the MBR and told it that windows was on partition 1.

/dev/hda is a 10 gigabyte drive formated with fat so that i can share files between the 2 OS's. because its so old, i cant find the jumper guide so it must be the master. (to compensate, i'v told my motherboard to look at my slave hard drive for booting instead of my master)

now my problem;
after installing slackware, i was able to boot into slack, but when i selected windows, it would give me this error;
"NTLDR is missing"

PS; there can be no reformating of windows of any sort because i dont feel like loosing all the data on my windows partition, i need to fix this w/o corrupting windows and i would prefer not to loose slackware as well.

Samsara 09-25-2004 07:25 PM

NTLDR is the NT Loader.

shilo 09-25-2004 07:32 PM

These two links should help you:

Restore your MBR: (I think it's one of the last two commands. The backup is in /boot for sure.)
http://www-user.tu-chemnitz.de/~mibe...d4hnode70.html


Get things working:
http://www.wlug.org.nz/HowToLinuxNTLoader

Never had to deal with any of this, so I hope those are helpful.

Good luck,

AC0H 09-25-2004 11:28 PM

To fix this boot off of your windows CD and open the recovery console.
At the prompt type fixmbr and hit enter.
This will re-install the NTLDR to the MBR of the drive. You will temporarily lose the ablitity to boot Linux.
Boot Linux off of the emergency boot disk you made and check out /etc/lilo.conf for a messed up or missing windows stanza. Edit the file to add or fix the windows stanza save it and at the prompt type /sbin/lilo -v to re-install LILO on the MBR.

e1000 09-26-2004 03:03 PM

after doing fixmbr nothing at all worked.

so my solution was to reformat my insignificant 10gb disk and install windows on it (no way Im gona use linux when doing backups to & from NTFS) . from there I backuped all my inportant files onto my data partition.

what I'm going to have to do is make the 10gb disk a slave and remove it during the install procedure of windows and linux, then I can plug it back in and hopefully everything will work.
but at least im not losing any data in this whole thing.

shilo 09-26-2004 04:35 PM

That's too bad. Did you read the links I posted? No mention of fixmbr. You have a copy of a working MBR right there in /boot, just waiting for you to copy it onto the MBR. Then, follow the other link to get things booting properly. Don't write LILO to the MBR when dual-booting WindowsNT. I think that was what all the articles I've seen are saying.

e1000 09-27-2004 12:06 AM

Quote:

Originally posted by shilo
That's too bad. Did you read the links I posted? No mention of fixmbr. You have a copy of a working MBR right there in /boot, just waiting for you to copy it onto the MBR. Then, follow the other link to get things booting properly. Don't write LILO to the MBR when dual-booting WindowsNT. I think that was what all the articles I've seen are saying.
Yea i read those links and tried the lilo -u thing, and on boot it said "loading Nvidia boot agent" then it gave an error about an invalid boot sector and kept repeating.

so i tried the fixmbr and it also failed to make my computer boot into any OS. (i even tried fixboot and fixmbr)

so finally as a last resort i installed windows for the sake of not losing all my data.

Im gona install slackware again but this time im going to see if i can make my larger Hard drive the master (even if it involves removing the 10 gig one) cause i think that this was the root of the problem, seing as how iv done this sucessfully many times before and the hard drive configuration was the only difference.


All times are GMT -5. The time now is 12:01 PM.