GRUB

Hello everybody!
I am now facing a serious problem .
My CPU is AMD Athlon 64 3000+ 754 pin
HD1 is WD 250G SATA2 in three partition(for windows XP&storage)
HD2 is Maxtor 13G IDE(very old type) (for Linux distributions, but now
only SuSE Linux 10)
> After I install my XP SP1,
> I install my Linux SuSE 10.
> finally I found the boot loader doesn't work very well
> though it can boot SuSE 10
> it can't boot windows
> Whenever I select windows ,it shows that
> "
> chainloader (hd1,2) +1
>
> A disk read error occured.
> Please press Alt+Crtl +Del to restart .
> "
> **** it ,though I have try many times and go to Yast for many revision
> ,I just can't log in to windows

Thank for your solutions.

david750322@yahoo.com.tw adjusted his/her tinfoil beanie to post:

> Hello everybody!
> I am now facing a serious problem .
> My CPU is AMD Athlon 64 3000+ 754 pin
> HD1 is WD 250G SATA2 in three partition(for windows XP&storage)
> HD2 is Maxtor 13G IDE(very old type) (for Linux distributions, but
> now only SuSE Linux 10)
>> After I install my XP SP1,
>> I install my Linux SuSE 10.
>> finally I found the boot loader doesn't work very well
>> though it can boot SuSE 10
>> it can't boot windows
>> Whenever I select windows ,it shows that
>> "
>> chainloader (hd1,2) +1


Have a look in /boot/grub/menu.lst ( you will have to be root to do
this ) or in Yast>System>Bootloader and see if that is the right entry,
hd1 is for the slave drive on the primary IDE interface and if that is
in the windows section it should probably be sd1 for SATA, there was a
renaming for SATA drives in the kernel and probably the one on the
install disk used hd? but the installed kernel uses sd? so that might
be the problem.

just in case I am wrong post the contents of the menu.lst here first so
we can see it also post the contents of /etc/fstab so we can match the
2 up.

In the /var/log/boot.msg you might or might not see errors when the
kernel probes the drives so post them if possible, just the detection
bit not the whole file please to save on space, here is a snip from
mine showing the correct SATA detection:

<<snip>>

6>NFORCE3-250: IDE controller at PCI slot 0000:00:08.0
<6>NFORCE3-250: chipset revision 162
<6>NFORCE3-250: not 100% native mode: will probe irqs later
<6>NFORCE3-250: 0000:00:08.0 (rev a2) UDMA133 controller
<6> ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hdaMA, hdbio
<6> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdcMA, hddio
<7>Probing IDE interface ide0...
<4>hda: HL-DT-STDVD-ROM GDR8160B, ATAPI CD/DVD-ROM drive
<4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
<7>Probing IDE interface ide1...
<4>hdc: _NEC DVD_RW ND-3500AG, ATAPI CD/DVD-ROM drive
<4>ide1 at 0x170-0x177,0x376 on irq 15
<7>libata version 1.12 loaded.
<7>sata_nv version 0.6
<4> ACPI-0212: *** Warning: Device is not power manageable
<4>ACPI: PCI Interrupt Link [LTID] BIOS reported IRQ 0, using IRQ 22
<4>ACPI: PCI Interrupt Link [LTID] enabled at IRQ 22
<6>ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LTID] -> GSI 22 (level,
low) -> IRQ 177
<6>hda: ATAPI 48X DVD-ROM drive, 512kB Cache, UDMA(33)
<6>Uniform CD-ROM driver Revision: 3.20
<7>PCI: Setting latency timer of device 0000:00:0a.0 to 64
<6>ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xC800 irq 177
<6>ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xC808 irq 177
<6>hdc: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
<6>ata1: no device found (phy stat 00000000)
<6>scsi0 : sata_nv
<6>ata2: no device found (phy stat 00000000)
<6>scsi1 : sata_nv
<7>sata_sil version 0.9
<4>ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 19
<6>ACPI: PCI Interrupt 0000:02:0c.0[A] -> Link [LNKC] -> GSI 19 (level,
low) -> IRQ 185
<6>ata3: SATA max UDMA/100 cmd 0xFFFFC20000020880 ctl 0xFFFFC2000002088A
bmdma 0xFFFFC20000020800 irq 185
<7>Losing some ticks... checking if CPU frequency changed.
<6>ata4: SATA max UDMA/100 cmd 0xFFFFC200000208C0 ctl 0xFFFFC200000208CA
bmdma 0xFFFFC20000020808 irq 185
<6>ata5: SATA max UDMA/100 cmd 0xFFFFC20000020A80 ctl 0xFFFFC20000020A8A
bmdma 0xFFFFC20000020A00 irq 185
<6>ata6: SATA max UDMA/100 cmd 0xFFFFC20000020AC0 ctl 0xFFFFC20000020ACA
bmdma 0xFFFFC20000020A08 irq 185
<7>ata3: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01
87:4003 88:207f
<6>ata3: dev 0 ATA, max UDMA/133, 320173056 sectors: lba48
<6>ata3: dev 0 configured for UDMA/100
<6>scsi2 : sata_sil
<7>ata4: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01
87:4003 88:207f
<6>ata4: dev 0 ATA, max UDMA/133, 160086528 sectors:
<6>ata4: dev 0 configured for UDMA/100
<6>scsi3 : sata_sil
<7>ata5: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01
87:4003 88:207f
<6>ata5: dev 0 ATA, max UDMA/133, 160086528 sectors:
<6>ata5: dev 0 configured for UDMA/100
<6>scsi4 : sata_sil
<6>ata6: no device found (phy stat 00000000)
<6>scsi5 : sata_sil
<5> Vendor: ATA Model: Maxtor 6Y160M0 Rev: YAR5
<5> Type: Direct-Access ANSI SCSI revision: 05
<5>SCSI device sda: 320173056 512-byte hdwr sectors (163929 MB)
<5>SCSI device sda: drive cache: write back
<5>SCSI device sda: 320173056 512-byte hdwr sectors (163929 MB)
<5>SCSI device sda: drive cache: write back
<6> sda: sda1 sda2
<5>Attached scsi disk sda at scsi2, channel 0, id 0, lun 0
<5> Vendor: ATA Model: Maxtor 6Y080M0 Rev: YAR5
<5> Type: Direct-Access ANSI SCSI revision: 05
<5>SCSI device sdb: 160086528 512-byte hdwr sectors (81964 MB)
<5>Attached scsi generic sg0 at scsi2, channel 0, id 0, lun 0, type 0
<5>SCSI device sdb: drive cache: write back
<5>SCSI device sdb: 160086528 512-byte hdwr sectors (81964 MB)
<5>SCSI device sdb: drive cache: write back
<6> sdb: sdb1 sdb2 sdb3
<5>Attached scsi disk sdb at scsi3, channel 0, id 0, lun 0
<5>Attached scsi generic sg1 at scsi3, channel 0, id 0, lun 0, type 0
<5> Vendor: ATA Model: Maxtor 6Y080M0 Rev: YAR5
<5> Type: Direct-Access ANSI SCSI revision: 05
<5>SCSI device sdc: 160086528 512-byte hdwr sectors (81964 MB)
<5>SCSI device sdc: drive cache: write back
<5>SCSI device sdc: 160086528 512-byte hdwr sectors (81964 MB)
<5>SCSI device sdc: drive cache: write back
<6> sdc: sdc1 sdc2 sdc3 sdc4 < sdc5 sdc6 >
<5>Attached scsi disk sdc at scsi4, channel 0, id 0, lun 0
<5>Attached scsi generic sg2 at scsi4, channel 0, id 0, lun 0, type 0
<6>ACPI: CPU0 (power states: C1[C1])
<4>Attempting manual resume
<3>swsusp: Suspend partition has wrong signature?
<5>ReiserFS: sdb3: found reiserfs format "3.6" with standard journal
<5>ReiserFS: sdb3: using ordered data mode
<5>ReiserFS: sdb3: journal params: device sdb3, size 8192, journal first
block 18, max trans len 1024, max batch 900, max commit age 30, max
trans age 30
<5>ReiserFS: sdb3: checking transaction log (sdb3)
<5>ReiserFS: sdb3: Using r5 hash to sort names
<6>bootsplash: status on console 0 changed to off
<6>md: Autodetecting RAID arrays.
<6>md: autorun ...
<6>md: ... autorun DONE.
<6>device-mapper: 4.4.0-ioctl (2005-01-12) initialised:
dm-devel@redhat.com
<5>ReiserFS: sda2: found reiserfs format "3.6" with standard journal
<5>ReiserFS: sda2: using ordered data mode
<5>ReiserFS: sda2: journal params: device sda2, size 8192, journal first
block 18, max trans len 1024, max batch 900, max commit age 30, max
trans age 30
<5>ReiserFS: sda2: checking transaction log (sda2)
<5>ReiserFS: sda2: Using r5 hash to sort names
<6>NTFS driver 2.1.23 [Flags: R/W MODULE].
<6>NTFS volume version 3.1.

<<pims>>


Glad I looked there I forgot I have an NTFS partition, that can go now
as I don`t have windows anymore been meaning to reclaim that space for
ages, it can go towards my extra space for recordings :-)

HTH
--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp

> Hello everybody!
> I am now facing a serious problem .
> My CPU is AMD Athlon 64 3000+ 754 pin
> HD1 is WD 250G SATA2 in three partition(for windows XP&storage)
> HD2 is Maxtor 13G IDE(very old type) (for Linux distributions, but now
> only SuSE Linux 10)
> > After I install my XP SP1,
> > I install my Linux SuSE 10.
> > finally I found the boot loader doesn't work very well
> > though it can boot SuSE 10
> > it can't boot windows
> > Whenever I select windows ,it shows that
> > "
> > chainloader (hd1,2) +1
> >

You have probably to check your /boot/grub/menu.lst and change
the windows partition position of the first hd( for example
depending from your partition on hda (hd0,1) or (hd0,2) etc...)
Look at "man grub" or "info grub" and the menu.lst examples.