Originally Posted by TheWoodchuck
And with your help i fixed it :-D .
Probably as I guessed a driver update that caused it to be able to see a partition that was previously not viewable under the previous driver for the Hard Drive controller. Only curious thing if this is the case is why it didn't break your linux installation as well. But everything seems to be working for now so it should be fine. It might be fedora fixed it's own configuration at the same time of compiling the driver into the kernel.
Originally Posted by syg00
Maybe change the title to something meaningful while you're at it.
I would say I agree with this, I myself do this just for normal installations but I go further with my hosted server where I work to make things a bit more obvious.
A typical kernel line would be like the following (please note this is from the domain-0 of a xen server)
title CentOS (2.6.18-164.11.1.el5xen)
I change this on my server to
title CentOS, Kernel: 2.6.18-164.11.1.el5xen (current)
on top of this I label previous Kernels as (old) and none Xen Kernels as (do not use) as Xen was installed post installation since the usage of the server changed and I did not reinstall it I still get none Xen Kernels but if Xen did develop a problem I still have the back-up of a none-xen kernel to fix things from, however these won't bring up my Virtual Machines so I label these as (do not use).