Hallo Peter
as mentioned in the previous mail I have installed a (fresh) F8T1, shot
some photos when I configured the
partition and where to write the boot sector.
results:
device.map:
# this device map was generated by anaconda
(hd2) /dev/sdc
grub.conf:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd2,2)
# kernel /boot/vmlinuz-version ro root=/dev/sdc3
# initrd /boot/initrd-version.img
#boot=/dev/sdc3
default=0
timeout=5
splashimage=(hd2,2)/boot/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.23-0.61.rc1.git9.fc8)
root (hd2,2)
kernel /boot/vmlinuz-2.6.23-0.61.rc1.git9.fc8 ro root=LABEL=/1
initrd /boot/initrd-2.6.23-0.61.rc1.git9.fc8.img
disks layout under F8T1:
Device Boot Start End Blocks Id System
/dev/sda1 * 63 12016619 6008278+ 7 HPFS/NTFS
/dev/sda2 12016620 32981444 10482412+ c W95 FAT32 (LBA)
/dev/sda3 32981445 53962334 10490445 83 Linux
Device Boot Start End Blocks Id System
/dev/sdb1 * 63 15647309 7823623+ 83 Linux
/dev/sdb2 15647310 31294619 7823655 83 Linux
/dev/sdb3 31294620 226628954 97667167+ 8e Linux LVM
/dev/sdb4 226628955 625137344 199254195 5 Extended
/dev/sdb5 226629018 242276264 7823623+ 83 Linux
/dev/sdb6 242276328 257923574 7823623+ 83 Linux
/dev/sdb7 257923638 268414019 5245191 83 Linux
Device Boot Start End Blocks Id System
/dev/sdc1 * 63 292977404 146488671 83 Linux
/dev/sdc2 292977405 296897264 1959930 82 Linux swap / Solaris
some curiosities:
1.
F8T1 installs a boots sector [*] to /dev/sdc (configured was sdc3) and
toggles the boot flag on that disk.
- after my previous mail I toggled it to "not boot able" -
[*] or better -cause I'm not a experienced boot-sector-reader -
the dd if=sd[bc] of=... bs=446 ... and a diff on it shows "0".
So you have been (nearly) correct/right (?) with that MBR statement.
2.
Next I tried to update the kernel.
to boot F8T1 I copied the above grub lines to my F7-grub.conf and had to
change root (hd2,2) to root (hd1,2).
rpm -ivh kernel... -vvv 2>&1 |tee kernel-install.
turns out:
grubby fatal error: unable to find a suitable template.
should be clear.
grubby searches the template on a *none existing* /dev/sdc3 !!!
currently I haven't realized where that sdc3 setting is configured....
and some more question's will left...
should this be bugzilla'ed or do I have made a error in reasoning ?
I'm not sure if it is healthy when a installer or whatsoever writes to
disks even when it wasn't allowed to, esp. when it's a data disk !
and I believe it's not very helpful if a disk is sometimes sda and
sometimes sdc.
for comparison:
disk layout seen from F7:
Device Boot Start End Blocks Id System
/dev/sda1 * 1 974 7823623+ 83 Linux =>F7
/dev/sda2 975 1948 7823655 83 Linux
/dev/sda3 1949 14107 97667167+ 8e Linux LVM
/dev/sda4 14108 38913 199254195 5 Extended
/dev/sda5 14108 15081 7823623+ 83 Linux
/dev/sda6 15082 16055 7823623+ 83 Linux
/dev/sda7 16056 16708 5245191 83 Linux
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 18237 146488671 83 Linux
/dev/sdb2 18238 18481 1959930 82 Linux swap /
Solaris
Device Boot Start End Blocks Id System
/dev/sdc1 1 748 6008278+ 7 HPFS/NTFS
/dev/sdc2 749 2053 10482412+ c W95 FAT32 (LBA)
/dev/sdc3 * 2054 3359 10490445 83 Linux => F8
--
Ronald
(me and my English
:-|
)
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
