Quote:
Originally posted by bill1850
I have just one seagate hd installed. I am very sure it was formated by XP to be NTFS. I did not run defrag or any type of partition software. I did change the bios to LBA after I installed Suse but it did not help.
When I try to boot to xp in grub it comes up with the fore mentioned error and then goes to a screen as if the computer had been shut off with the power switch not by the OS. It gives me a few different options to boot to xp but none of them work. It goes to the XP splash screen for about 3 seconds, then it goes to a screen with a blue box that says something but I it doen't stay on the screen long enough to read it. Then it goes to the grub editor.
|
bill1850: You have only one hard disk in the system. You do not need the map command.
The above post confuses me considerably. (It is recommended to defrag an ntfs partition (from Windows) before shrinking it. That aside for the moment...) It sounds like the Windows boot loader is getting loaded, and recognizes that Windows did not start properly the previous time. A blue box? If the whole screen were blue that would be one thing (reminiscent of a 'stop error', aka BSOD). But a box? What color is the rest of the screen around the box? Do you have a digital camera available to capture it with? How in the world would it get from there back to grub? When you say "grub editor" do you mean the menu, the prompt, or something different. It is possible for grub to still be in memory at that point, but there is no excusable reason that I can find for windows to jump to that spot in memory (without loading it's stuff there first). Does the system reboot at the blue box?
Keeping my confusion in mind, I think your ntfs partition was damaged when it was resized (this doesn't explain the problems with your partition type). If this is the case, then you may be able to read some of what is left from Linux.
Better yet, see if you can select boot logging from that menu. If you can't, then push F8 repeatedly just before that and select logging. Now if you can read the partition from Linux, find the windows/system32/ntbtlog.txt file (It think it's in unicode or something, by the way). If you can get a copy of this file from your system, it may help in understanding your problem.
You might try running "chkdsk /p" from the recovery console on the Windows installation CD.
From Linux, you can change the partition type using "cfdisk /dev/hda1". I have seen one instance where a system would not boot Windows 98 because the partition type was wrong, but it was a weird set up in the first place (third party boot loader). I don't think Windows cares about the type, but maybe it does (still wouldn't explain your other behavior, though).
lloydie:
Sure. Grub labels the disks/partitions differently than Linux does. This can be a source of confusion. Basically, you start counting at zero instead of one.
(fd0) - floppy disk drive
(hd0) - primary master drive
(hd1) - primary slave drive
(hd2) - secondary master drive
(hd3) - secondary slave drive
(hd0,0) - primary master, first partition
(hd1,0) - secondary master, first partition
(hd0,2) - primary master, third partition
(hd2,4) - secondary master, first logical volume (/dev/hdc5)
You should be able to compare these to your /boot/grub/device.map file.
"Chainloader" means to grab and load the first block of the root device and run it. I believe it got this name as you would chain boot loading code together (bios-> mbr-> grub-> something else-> etc.).
The map command logically swaps two drives. It does not fool Windows for very long, just long enough to get Windows to boot. You must use map anytime you install Windows to a master drive, and then switch that drive to slave. To avoid confusion, the "root" device should still be the true drive. Don't go loading (hd0) in an attempt to load (hd1)
.
