Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I recently installed SuSE 9.1 Professional
onto my 80GB hard disk to dual boot with
Windows XP. Since then Windows cannot boot,
and the error message below is displayed
after Windows is selected from Grub's
startup menu:
(hd 0,0)
Filesystem type unknown, partition type
0x7
chainloader +1
I've read about problems with installing
Linux on partitions > 8GB, and I followed
the article below to try and fix it. I have
also read other articles about this, but my
question is not answered.
http://portal.suse.com/sdb/de/2004/05/fhassel_windows_not_booting91.html
I managed to copy the driver update to
floppy and install it as directed, but the
problem occurs when I press "Back", the CD
starts 'Loading data into ramdisk ...' as
if I were installing the OS from scratch.
What I'm trying to do is finish the
remaining tasks below to repair the broken
partition table and thus resolve the
problem.
How can I do this without the installation
process beginning?
QUOTEAfter completing the driver update, press
"Back".
The following dialog for repairing the
partition table displays your hard disk
(usually /dev/hda) and the status of the
partition table (broken). Select the hard
disk and click "OK" in order to repair the
partition table.
After repairing the partition table, exit
the menu with "Back". Press the key
combination CTRL-ALT-DEL in order to reboot
the computer and remove all media from the
drives.
Now you should be able to boot both
Windows and Linux.
QUOTE
NB: I can see all the files stored on the
Windows partition through Linux in My
Computer. I also have the 5 CD distro.
I hope someone can help?
Thanks in advance.

Newer versions of GNU/Linux should have no problems installing on partitions larger than 8Gb. You problem is more likely to be your grub config. Post up your /boot/grub/grub.conf. You will want to use rootnoverify, make sure the entry for windoze looks something like:
title XP
rootnoverify (hd0,0)
makeactive
chainloader +1

# Modified by YaST2. Last modification on
Mon Jul 19 22:34:27 2004
color white/blue black/light-gray
default 0
timeout 8
gfxmenu (hd0,2)/boot/message
###Don't change this comment - YaST2
identifier: Original name: linux###
title Linux
kernel (hd0,2)/boot/vmlinuz
root=/dev/hda3 vga=0x314 splash=silent
desktop resume=/dev/hda2 showopts
initrd (hd0,2)/boot/initrd
###Don't change this comment - YaST2
identifier: Original name: windows###
title Windows
root (hd0,0)
chainloader +1
###Don't change this comment - YaST2
identifier: Original name: floppy###
title Floppy
root (fd0)
chainloader +1
###Don't change this comment - YaST2
identifier: Original name: failsafe###
title Failsafe
kernel (hd0,2)/boot/vmlinuz
root=/dev/hda3 showopts ide=nodma apm=off
acpi=off vga=normal noresume nosmp noapic
maxcpus=0 3
initrd (hd0,2)/boot/initrd

Try changing:
###Don't change this comment - YaST2
identifier: Original name: windows###
title Windows
root (hd0,0)
chainloader +1for
###Don't change this comment - YaST2
identifier: Original name: windows###
title Windows
rootnoverify (hd0,0)
chainloader +1
NB: With grub all you usually need to do is modify the config file. With lilo you have to run the lilo command to write the changes to your boot record.

![]() |
need help with error 27
|
Creating ISO image questi...
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |