F17 destroyed my F16

[sea]

Heyas

After getting some feedback on my homepage, i decided to install F17, in order to test my scripts in a live environment.
Its not that i have no clue how to do it, i've done so at least 200 times (if not more) during the last 12 months, without issues.

Anyway, i rebooted from my F16 install, and booted of the dvd install media from my usb (could/should have used netinstall), as the dvd media forced me to plug in the wire for internet.

So the F17 installer booted properly without any issues, but "could not insert floppy" and "rpcbind -w"

Before F17 install the partitions looked like:
* bios_boot 1mb
* /home 200gb
* / 16 gb (f16 root)
* swap 1 gb
* /boot 768 mb
* /arch
* /debian

/home, /boot and swap i did choose to reuse for both, F16 and f17, created a new partition at the end, sized 8 gb for F17 minimal installation root.
* bios_boot 1mb
* /home 200gb (NOT formatted)
* / 16 gb (f16 root)
* swap 1 gb (NOT formatted)
* /boot 768 mb (NOT formatted)
/arch
/debian
* / 8gb (f17 root)

Installation went well, and after it, i ctrl+alt+f2, chrooted /mnt/sysimage and ran my script to setup GUI from minimal installation. After it was successfully done, i rebooted.
Here the errors started..
F17 hangs on kernel panic, with no lower kernel available to boot from.
And Arch, Debian and F16 squeeze hang either on kernel panic or runaway loop modprobe.
GRUB 2.0.0~beta4

Trying to change the boot comand of Grub, causes to free grub
So i cant even enter runlevel 1, without a livedisk.

Question:
Any ideas how to fix?
Or Would reinstalling F17, with formatting /boot be the fastest/ easiest way?

[bigflopper2]

Originally Posted by sea

[...]
Or Would reinstalling F17, with formatting /boot be the fastest/ easiest way?

yeah, think so.

[sea]

Weird, it just worked. (it didnt the last 2 tries, but those were in the middle of the night )
I did run st tweak grub2 from chroot /mnt/sysimage, but my f16 was not recognized anymore
Even after successfully starting F17 minimal console, and running my tweak grub2 script, it reports to have found f16, but on grub-screen at boot, i just see f17..

EDIT
After running grub2-mkconfig -o /boot/grub2/grub.cfg several times, it is finaly showing 2 Fedora entries on boot.
However, both lead to gpt5, but f16 would be on gpt3, when i try to change that line in grub menu, grub freezes.

[mmix]

grub problem.. where did all other bootloaders go.. lilo

[sea]

There must be a way to get grub running as one expect it.
Oh well, time to increase capabilities of my grub2 script


EDIT:
Regardless the fact that i cant boot my 'old wolrking' f16 installation, i cant install upon the minimal installation of f17

ifconfig p3p1 up
dhclient -B p3p1
ping -c 1 fedoraproject.org
sent 1, recieved in 28ms, total 100% success

yum install XY..
Could not resolve fedora host adress

wtf?
But the greatest drawback is the fact that it even destroyed my 'working' F16 installation... at least i couldnt boot to it allthough i havent touched its root.

[dswaner]

I thought my F17 install killed my "production" F16 instance also. However, what was happening was that the grub2-mkconfig and/or os-prober dropped the kernel parms when it generated the F16 linux line in the grub.cfg. So I copied the old F16 grub.cfg section into the 40_custom file, reran grub2-mkconfig, and my F16 now works, if I invoke it from the 40_custom code with the proper kernel parms. My F16 instance is on a partition on another drive than the F17 instance, and it comes after a Windows partition - may or may not have something to do with it not generating the proper kernel parms. An F15 instance on the same hard drive as F17 has the proper linux kernel parms generated and works fine.