Unable to upgrade from FC10
First of all, thanks for your attention. Second: I've a "bit" problem upgrading Fedora. This aventure starts on FC11 and stays unsolved. I've posted the problem on the Bugzilla page, 'cause this issue appears even all on another distributions, like Ubuntu.
I'll try to explain briefly: Some years ago, I installed FC10 on my computer (Packard Bell imedia 6050), and no problem appeared. Even all, packagekit upgrades the kernel 'till version 2.6.27.41 with no problem.
Some months later, appeared FC11, and a bit later, FC12, so I decided to upgrade to FC12 ASAP to keep the system updated. So, I download the DVD, reboot the system, Anaconda prepares the installation, and here becomes the problem: No HD to install to!
Then, I waited for a while (some versions more) to see if the problem gets solved, (I'm not a linux expert) and I see that this issue remains on the rest of the versions, so I report the problem to Bugzilla, telling that the problem appears on FC11, stills active on FC14, and so on.
When I discover the way to complete the info that the guys from redhat needs to improve Fedora, I add them to the bugzilla report, and wait for any help. (https://bugzilla.redhat.com/show_bug.cgi?id=755554 for further information)
Some time later, redhat lauches kernel 3.3.0.4 for FC16, so I wait to FC17 to be sure that the kernel installed is OK: No HD to install to
Currently, I don't know what to do (logically, I can't to buy a new computer, and I can't stay many more time on FC10!), nor if this issue is well known, is a Kernel problem or if can be solved with an specific driver (none found for the motherboard/SCSI/SATA/RAID for this machine for linux/fedora specific).
Thanks for your patiente and attention.
PD: This is the Hardware identified by Hardware Lister:
description: Desktop Computer
product: IMEDIA 6050
vendor: Packard Bell BV
version: PB80142604
serial: xxxxxxxxx
width: 64 bits
capabilities: smbios-2.5 dmi-2.5 vsyscall64 vsyscall32
configuration: boot=normal chassis=desktop uuid=400EE97C-F26F-DD11-BBBF-83AB48E575DE
*-core
description: Motherboard
vendor: Packard Bell BV
physical id: 0
version: 1.0
*-firmware
description: BIOS
vendor: American Megatrends Inc.
physical id: 0
version: PBCBR00.P23 (05/01/2008)
size: 64KiB
capacity: 960KiB
capabilities: isa pci pnp apm upgrade shadowing escd cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer int10video acpi usb ls120boot zipboot biosbootspecification
*-cpu
description: CPU
product: AMD Athlon(tm) 64 X2 Dual Core Processor 5000+
vendor: Advanced Micro Devices [AMD]
physical id: 3
bus info: cpu@0
version: AMD Athlon(tm) 64 X2 Dual Core Processor 5000+
serial: To Be Filled By O.E.M.
slot: CPU 1
size: 2600MHz
capacity: 2600MHz
width: 64 bits
clock: 200MHz
capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ...
I think this issue can be resolved by updating your BIOS,i had the same with f15 solved after updating the BIOS...try it...
For support use this plattform!
You are going to need to follow up on the bug report you filed. It apperars your hard drive is recognized "state=mounted", and even mounted, so I am going to guess this is a problem with anaconda ? Could be a problem with the kernel, and in your output it shows what kernel modules you need. "driver=ahci" ect, so you need to identify which drive is not working, and sort out if it is a kernel problem or not. ie can you mount the hard drive(s) with the live CD ? If so, then my guess is a problem with anaconda.
@TarracoServer, what is your current status? Have you tried anything newer? Are you still watching this request or your bug report?