Hello all,

I'm new to Linux and today decided to finally install Suse 10 (from dvd) and this will probably also be the last time!

First I used partition magic (in windows xp) to resize the partition from my 2nd harddisk from 80GB to 50GB (NTFS).

After that I started installing Suse which suggested to use the left over space on the 2nd harddisk to make 2 linux partitions (swap+normal).

The installation didn't go as perfect as it could be. It gave an error message that it could not install the suse-build-key package. I ignored that error and everything else went fine.

After initial setup I decided to reboot the computer and the linux boot loader(?) from where I can choose to run Linux or Windows. All fine so far. I can start both Windows and Linux from there.

I ejected the DVD and restarted the pc again, which resulted in the following error: "NTLDR is missing. Press CTRL-ALT-DEL to restart"

I tried going into Windows safe mode, but it won't let me even get to the windows startup menu.

So now when I want to go anywhere, I always have to use the linux dvd.

Some specs:
harddisk1: 120GB (NTFS, Windows XP)
harddisk2: 80GB divided into NTFS partition/Linux swap/Linux

When I google on the NTLDR error people suggest to go into windows recovery mode and do a fixmbr. Will this solve my problem (and not screw things up completely?) or is there a better solution.

Thanks for your help! It's very much appreciated

Did you install grub to the mbr?
Post /boot/grub/grub.conf
or for Suse may be;
/boot/grub/menu.lst

Also, I forgot to mention that my first harddisk does have two partitions. The first one is very small and for recovery purposes from the manufacturer of the computer. I don't know if this has anything to do with the problem.

Anyways, here's the contents of /boot/grub/menu.lst
# Modified by YaST2. Last modification on zo okt 30 17:21:01 CET 2005

color white/blue black/light-gray
default 0
timeout 8
gfxmenu (hd1,2)/boot/message

###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows
chainloader (hd0,0)+1

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX 10.0
root (hd1,2)
kernel /boot/vmlinuz root=/dev/hdb3 vga=0x31a selinux=0 resume=/dev/hdb2 splash=silent showopts
initrd /boot/initrd

###Don't change this comment - YaST2 identifier: Original name: Vendor diagnostic###

title Vendor diagnostic
chainloader (hd0,1)+1

###Don't change this comment - YaST2 identifier: Original name: floppy###
title Diskette
chainloader (fd0)+1

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Veilige modus -- SUSE LINUX 10.0
root (hd1,2)
kernel /boot/vmlinuz root=/dev/hdb3 vga=normal showopts ide=nodma apm=off acpi=off noresume selinux=0 nosmp noapic maxcpus=0 edd=off 3
initrd /boot/initrd


And here's the contents of /boot/grub/device.map (both of these files were altered on the same date I installed Linux)
(hd1) /dev/hdb
(fd0) /dev/fd0
(hd0) /dev/hda


Oops, I just read in the manual which came with the pc that I can not install multiple operating systems. If I do, the restore function will not be available anymore. Could this be causing my NTLDR problem?

I don't think so! You simply can use the restore function. I have a similar situation on my PC and it runs just fine.

But the small partition could explain your troubles:
Your menu.lst tries to boot Windows from hd0,0 which is probably the small partition. Try to boot from hd0,1 (the 'Vendor diagnostic' item)

But the options listed in menu.lst are good, I think. This is the same list I get when I start the computer with the linux dvd in there. It starts from dvd, then I select "Boot from Harddisk". Then I get the exact options as they appear in menu.lst. When I select Windows at that time, Windows will start up without any problem. When I select the Vendor option, it will go to System Recovery.


Here's some more info...
In the YaST2 Configuration the partitioning menu reveals:
/dev/hda 114.4GB Maxtor-6Y120L0
/dev/hda1 111.9GB HPFS/NTFS /windows/C
/dev/hda2 2.5GB Vendor Diag

/dev/hdb 74.5GB ST380011A
/dev/hdb1 48.8GB HPFS/NTFS /windows/D
/dev/hdb2 1.0GB Linux swap swap
/dev/hdb3 24.6GB Linux native /

And in the bootloader configuration (via YaST2 Configuration) the location of the bootloader is set to "Master boot record of /dev/hda"

I also seem to have a /etc/grub.conf file which says:
setup --stage2=/boot/grub/stage2 (hd1,2) (hd1,2)
setup --stage2=/boot/grub/stage2 (hd0) (hd1,2)
quit

Again, any help is appreciated!

Ahh, I see! In your case the diagnostic partition is on the other end (on my system it's hda1).
We've had a similar thread recently with the same phenomenon, but we couldn't resolve it. But maybe you want to have a look: http://www.linuxquestions.org/questi...hreadid=376609


BTW: What I wanted to say in the above post is that you "can't" use the restore funtion anymore.

This is weird. When I go into windows and start partition magic, the first partition on my first harddisk is indeed the recovery partition. The second partition is the NTFS partition.

But in Linux partititioning it says hda1 is my NTFS partition and hda2 is my recovery partition ?!

Weird indeed! Then you should try to boot from HDD and select the 'Diagnostic' option. Maybe this'll take you to Windows...

BTW: What's the active partition? Maybe you need to activate 'the other'.

I already tried going into the Diagnostic menu option, but that will get me into that one. Just like I can get into Windows by selecting the windows menu option.

So linux says partition 1 = Windows and partition 2 = System Restore
And this works!
While windows says partition 1 = System Restore and partition 2 = Windows

In Windows partiton magic's PartitionInfo I can see that:
Disk 1:
Partition Information:
Partition1 = Utility, Pri, 2643.5MB, startsector 63
Partition2 = NTFS, Pri,Boot, 114596.5MB, startsector 5,413,905

Disk Geometry Information:
1st line says startsector 5,413,905
1nd line says startsector 63

Also, it says partition 2 (Volume C) has the following error:
"Info: MBR Partition Table not in sequential order."


Disk 2:
Partition 1 = NTFS, Pri,Boot, 49999.1MB, startsector 63
Partition 2 = Linux Swap, Pri, 1027.6MB, startsector 102,398,310
Partition 3 = Linux Ext2, Pri, 25289.8MB, startsector 104,502,825

Disk Geometry Information for disk 2:
1st line says startsector 63
2nd line says startsector 102,398,310
3rd line says startsector 104,502,825

No errors here.


So I guess something is messed up in disk 1, but what? And why did this happen when installing Linux?

About active partitions:
On disk 1, the NTFS partition is active
On disk 2, the NTFS partition is active

Ok, I decided to make things worse.....

In Partition Magic I made the Linux partition the active one. Which means my Windows partition on the 2nd harddisk is not anymore.

I booted and it gave me the following message:
"GRUB loading stage 1.5.
GRUB loading, please wait...
graphics file "(hd1,2)/boot/message" missing, press a key to continue...

Then it comes up with the bootmenu from Linux! Looks good so far!
I choose Windows, and then it comes up with:
"Booting 'Windows'
chainloader (hd0,0) +1
NTLDR missing...
Press CTRL-ALT-DEL to restart"

So, still not solved. I decided to boot back into windows using the linux dvd to boot from. This still worked without any problems. But when I got back into windows, my D drive was gone (the windows partiton on the 2nd harddisk).
In partition magic it says it's still there, but it's hidden!!! Luckily there's an option to unhide a partition. So that's what I did. Restarted again with the linux dvd. But still the same problem.
So I decided (in partition magic) to make my windows partition active again by first unhiding, then make it active.

But after restarting, nothing is changed. My linux partition is still active and my D drive is still gone.

What's going on here????

What options do you have set in the BIOS for the two HDs ????.
Probably AUTO, maybe LBA, hopefully not anything else.

Both harddisks used to be AUTO, but I have set them to LBA cause I read somewhere AUTO can give problems. So, they're currently set to LBA.

Ok, I don't know what's up with this, but I tried making my D drive active again, and now it worked.

But the boot problem with NTLDR missing still exists....

There is another thread with a similar problem:
http://www.linuxquestions.org/questi...5&pagenumber=2

19syzerman19 solved the problem by swapping the drives in /boot/grub/device.map. I can't imagine if it's going to help in your case, but one never knows...

Let me teach you,
if u r using suse 10.0, just boot with a DOS/Windows 98 bootdisk, enter Fdisk /MBR to delete grub first.
then , boot with CD rom your XP or Windows 2000 CD,
choose rescue,
go to C:,
type attrib -h -r -s *.*
then, copy NTRDL and NTDETECT.com from /i386 from your CD to c:
reboot,
you should be able to run your windows again.

To get back your Grub, boot with suse 10.0 CD or DVD, choose installation,
after a few steps, choose "others" when asked about type of installation, you can see the REPAIR option,
click next, choose AutoRepair,
follow on will get back your Grub to Dual Boot with windows.