Hello,

Can anyone show me how to access my FC4?Here it goes,I have 4 HD's,2 SATA and 2 IDE.First IDE is winxp,second IDE NTFS(no OS).the other 2 SATA's:120G FC4_64 and on the other drive ,SUSE 10.0_64.

Boot's with the Bootloader interface of SUSE.I can get WinDoze + Suse,but not FC4.When I try to boot with Fedora,gives me this:

Chainloader
(HD2,0)+1
Grub

I tried to fix it with UBCD,in< boot.ini >but my keyboard stops working ;(

I am no big expert when come times with the boot loader..

Can anyone help me please?

Many thanks in advance,

Mart.

OK lets say your FC4 is in the first partition of the 3rd disk. As Grub counts from 0 so (hd2,0) would be the right address for its root partition

The syntax in Suse's /boot/grub/menu.lst for booting FC4 should be

title This is my FC4 @ sda1
root (hd2,0)
chainloader +1

Newer versions of Grub permits the last two lines combined but the about works for all Grub versions.

You will not be able to boot FC4 with the above Unless you have arranged FC4's boot loader inside sda1 (which could be named as hde1 too in Suse).

These are the instructions for arranging FC4's standard boot loader, which is Grub, in its root partition if you haven't done it previously.

(1) Boot up Suse, log in as root (need admin privilege), click terminal
(2) Make a temporary directory in /mnt called /mnt/sda1
(3) Mount FC4 partition on /mnt/sda1
(4) Change root to /mnt/sda1
(5) At this point your are inside FC4 so replicate its Grub in raw device sda1
(6) Exit FC4, Exit Suse and reboot

mkdir /mnt/sda1
mount /dev/sda1 /mnt/sda1
chroot /mnt/sda1
grub-install /dev/sda1
exit
reboot

I use also 2 IDE and 2 Sata but there are over 120 partitions with 50+ bootable systems managed by one Grub. You need to try harder.

If you have specified Lilo as boot loader in FC4 the just replace grub-install /dev/sda1 with

lilo -b /dev/sda1

-----------------------------------------------

In chainloading you boot the boot loader of another system! It is the easiest thing to learn but the most powerful.

Try to show us where is what !
What you tell us means your dive is on your 3-disk
and if you use frup you have to tell grub
grub > setup (hd0)
there is your bootloader installed

guignol has got a workable Grub from Suse booting both Sue and Windoze just fine, as he reported.

Setup (hd0) means installing a Grub in (hd0) but that isn't what is needed here.

This post asks for tribooting Suse, Windoze and FC4 and the guy is stuck not knowing how to proceed after chainloader +1.

He is always half way there.

You are right, Baut I ask too where is what ............................
where is your windows (HD2) where SUSE etc.
how many disks you ae using
HD2 ....
grub
mean it doesn't find something there

The way I read it is he has arranged the BIOS to both IDE first and has possibly

hda1 for a Windoze system
hdb1 for NTFS partition storing own data
Sda1 for FC4 or any partition that holds the root
sdb1 for Suse or any partition that holds the root

The word chainloader +1 is only used by Grub, which is the standard boot loader for both Fedora and Suse.

hda, hdb, sda and sdb are Linux notations for IDE and Sata disk. Grub only count the order as it receives from the BIOS. Thus the same disks are known (hd0), (hd1), (hd2) and (hd3) in Grub notation.

The boot loader has to be in the first IDE or hda and the guy has indicated FC4 was in Sata and before Suse in the last. Since he already asking root (hd2,0)+1 then FC4 is confirmed independently in sda.

His disks and partitions can be revealed fully if he list the content of

fdisk -l

Also the way Grub calls his 4 disks is documented in a text file stored as /boot/grub/device.map which he can also list here.

Thanks for the help guy's...here is my Grub in FC4 & Dev map of Suse...I will now reboot after changing sda1 to hda1 in SUSE...Hope it works!Thx again.
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd1,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup01/LogVol00
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
#hiddenmenu
title Fedora Core (2.6.13-1.1526_FC4)
root (hd2,0)
kernel /vmlinuz-2.6.13-1.1526_FC4 ro root=/dev/VolGroup01/LogVol00 rhgb quiet
initrd /initrd-2.6.13-1.1526_FC4.img
title Fedora Core (2.6.13-1.1526_FC4smp)
root (hd2,0)
kernel /vmlinuz-2.6.13-1.1526_FC4smp ro root=/dev/VolGroup01/LogVol00 rhgb quiet
initrd /initrd-2.6.13-1.1526_FC4smp.img
title Fedora Core (2.6.12-1.1447_FC4smp)
root (hd2,0)
kernel /vmlinuz-2.6.12-1.1447_FC4smp ro root=/dev/VolGroup01/LogVol00 rhgb quiet
initrd /initrd-2.6.12-1.1447_FC4smp.img
title Fedora Core (2.6.12-1.1456_FC4)
root (hd2,0)
kernel /vmlinuz-2.6.12-1.1456_FC4 ro root=/dev/VolGroup01/LogVol00 rhgb quiet
initrd /initrd-2.6.12-1.1456_FC4.img
title Fedora Core (2.6.11-1.1369_FC4)
root (hd2,0)
kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=/dev/VolGroup01/LogVol00 rhgb quiet
initrd /initrd-2.6.11-1.1369_FC4.img
title Windows XP
map (hd0) (hd1)
map (hd1) (hd0)

DEV MAP-------------------------------
(fd0) /dev/fd0
(hd2) /dev/sda
(hd0) /dev/hdc
(hd3) /dev/sdb
(hd1) /dev/hdd
rootnoverify (hd1,0)
makeactive
chainloader +1

rest of ...fdisk -l:

Disk /dev/sda: 120.0 GB, 120060444672 bytes
255 heads, 63 sectors/track, 14596 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 14596 117137947+ 8e Linux LVM

Disk /dev/sdb: 80.0 GB, 80032038912 bytes
255 heads, 63 sectors/track, 9730 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 1 131 1052226 82 Linux swap / Solaris
/dev/sdb2 132 9730 77103967+ 83 Linux

Disk /dev/hdc: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdc1 * 1 14592 117210208+ 7 HPFS/NTFS

Disk /dev/hdd: 40.0 GB, 40016019456 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdd1 * 1 4864 39070048+ 7 HPFS/NTFS

This is killing me! 4 hours passed...ouff...I will get this.I read the post's at least 20 times.This is what I dig:

E.g.

(hd0) /dev/hda
(hd1) /dev/hdb
(hd2) /dev/hdc

hda->sda1, hdb->sda2 , hdc , etc...

But still no results.. argggggg.........I will get tru this!!!

Mart.

I presume that error messgae in the initial post was typed by hand - can't see that coming from grub.

Put everything back the way it was initially. Let's see your Suse grub.conf and map file - separate, not intermixed. Put each in separate code tags to make it much more readable.

Did that FC system ever boot successfully ???. Try commenting the out that (FC) splashimage line and see what happens.

guignol,

You are doing something silly if you are trying to alter the hard disk designations artificially.

The hda, hdb, hdc and hdd are named by the Linux according to the position you hooked up the hardware. Some of them may not exist. There are reserved raw devices. You could still have hda but it could be a CD or DVD drives!

Your new drive designations can only be effective if you exchange the CD/DVD ribbon cable with that of the two IDE disks. The price you paid is Suse will get into trouble as the as-installed hard disk names are no longer valid.

So what has happen?

You know if your system doesn't work you haven't told me what was the error.

We still have no clue of what's wrong with your system.

My suggestion to you now is to get into any unbootable Linux by boot up one that works, ideally from the installed Suse. If Suse has gone then use a Live CD instead.

Once inside the distressed Linux by change root, replicate its boot loader onto a floppy and try to boot it via a floppy first.

In my previous instructions of

mkdir /mnt/sda1
mount /dev/sda1 /mnt/sda1
chroot /mnt/sda1
grub-install /dev/sda1
exit
reboot

you change sda1 with fd0 and the Grub will go to the floppy. Once you got it bootable with a floppy then you can put Grub back into sda1 any time.

Report what error you get if any.

Hi,

God knows I am trying!Maybe this info could ring the bell...I can mount all my drives except SDA

My SUSE grub:
# Modified by YaST2. Last modification on Wed Nov 9 13:33:28 EST 2005

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

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

###Don't change this comment - YaST2 identifier: Original name: windows 1###

title XP
chainloader (hd0,0)+1

###Don't change this comment - YaST2 identifier: Original name: windows 2###

title windows 2
chainloader (hd1,0)+1

###Don't change this comment - YaST2 identifier: Original name: Linux other###****************************************

title Fedora
root (hd2,0)
kernel /boot/vmlinuz-2.6.13-1.1526_FC4 root=/dev/VolGroup01/LogVol00 ro rhgb quiet
chainloader +1

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

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE LINUX 10.0
root (hd3,1)
kernel /boot/vmlinuz root=/dev/sdb2 vga=normal showopts ide=nodma apm=off acpi=off noresume selinux=0 edd=off 3
initrd /boot/initrd
----------------------------------------------------------------------------------------------------

FC4 Grub.conf:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd1,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup01/LogVol00
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=5
splashimage=(hd2,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.11-1.1369_FC4)
root (hd2,0)
kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=/dev/VolGroup01/LogVol00 rhgb quiet
initrd /initrd-2.6.11-1.1369_FC4.img
title Other
rootnoverify (hd0,0)
chainloader +1
--------------------------------------------------------------------------
FC4 DEvice map:
# this device map was generated by anaconda
(hd2) /dev/hdc
(hd1) /dev/hda
------------------------------------------------------------------------------
SUSE Dev Map:
(fd0) /dev/fd0
(hd2) /dev/sda
(hd0) /dev/hdc
(hd3) /dev/sdb
(hd1) /dev/hdd

-------------------------------------------------------------------------------
& last ....:
Disk /dev/sda: 120.0 GB, 120060444672 bytes
255 heads, 63 sectors/track, 14596 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 14596 117137947+ 8e Linux LVM

Disk /dev/sdb: 80.0 GB, 80032038912 bytes
255 heads, 63 sectors/track, 9730 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 1 131 1052226 82 Linux swap / Solaris
/dev/sdb2 132 9730 77103967+ 83 Linux

Disk /dev/hdc: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdc1 * 1 14592 117210208+ 7 HPFS/NTFS

Disk /dev/hdd: 40.0 GB, 40016019456 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdd1 * 1 4864 39070048+ 7 HPFS/NTFS

-----------------------------------------------------------------
No problem booting with XP and SUSE...

Thx again !

OK your device.map from FC4 doesn't show up the two Sata but instead showing hda and hdc. There is no (hd0) either, so something may be seriously wrong with your FC or you must have installed FC not in the same current 4 disks enviroment.

The original hda and hdc now change to hdc and hdd would indicate that you might have swapped the ribbon cables for the IDE disk

I am also uncomfortable with the FC4 kernel is 2.6.13 in Suse's Grub but changes to 2.6.11 in FC4 Grub.conf.

Something has happened and you have not told us the truth.

I am not sure if your FC will boot or not if there are incompatibility hidden from us.

To move the matter forward I would suggest

(1) Overwrite FC's /boot/grub/device.map with Suse's version

(2) Try to see if you can mount sda1

(3) Use Suse's Grub to boot FC4 but you may need to add

initrd /boot/initrd-2.6.13-1.1526_FC4.img

after the kernal line in the boot option starting with "title Fedora"

(4) Check FC4's /boot and make sure the 2.6.13 kernel and initrd file names match up with the FC4 boot option description in Suse.

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!SUCCESS!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

it was so simple thanks to you guy's!!!!!! I did like you said Saikee,I just edited both Grubs the same!then,I had to remove "chainloader(hd2,0)+1" and thats it!

Like this in both my OS's grubs:

###Don't change this comment - YaST2 identifier: Original name: Linux other###

title Fedora

root (hd2,0)
kernel /vmlinuz-2.6.13-1.1526_FC4 ro root=/dev/VolGroup01/LogVol00
initrd /initrd-2.6.13-1.1526_FC4.img


Voila!!!!!! FC4 works great!!!

Now I know how grub works!To bad I do not have more space in my machine for a 5th HD eh he eh!! Could have installed another Distrib know that I know how to....GRUBBBBBBBBBBBBBB

Thx again!!!!!!!!!


Martin.

Don't laugh yet. The best trick in the business is to use chainloader +1 because you don't have to know the name of the kernal and initrd, plus you boot Windows in the same way as you boot another Linux, another Windows, a DOS, a BSD or a Solaris. I cry if I were you!

You can increase you Linux collection by allocating a smaller partition to a distro. The majority of the distros are between 2 to 3 Gb large after installation. I use 5Gb typically but have 10 and 20Gb partitions in Sata for a totally different reason.

Linux allows a maximum of 63 partition in an IDE disk (I only manage 60!) and 15 for a Sata. Therefore I was forced to be generous with Linux in my 200Gb Sata.

But you gave 120Gb to a Suse! My Suse 9.3 Pro occupies 2.83Gb and Suse 10 foorprint is 1.88 Gb inside 5Gb partitions.

You don't need another disk to install Linux. Just try not over-generous with disk space will do.

---------------------------------

If the above gives you an idea to repartition the disk then create a new thread of asking how to move a LInux from one partition to anther (without re-installation).

Don't want to make this too long here.