Hide Forgot
Created attachment 549140 [details] dmesg file Description of problem: Attempting to upgrade from Fedora 15 to Fedora 16 via preupgrade or booting from USB live disk causes the error message: "Disks sda, sdb contain BIOS RAID metadata, but are not part of any recognized BIOS RAID sets. Ignoring disks sda, sdb" Because of this I am unable to upgrade an existing Fedora installation. Using the following anaconda version: [liveuser@hayden-fedora ~]$ rpm -qa | grep anaconda anaconda-16.25-1.fc16.x86_64 anaconda-yum-plugins-1.0-6.fc15.noarch [liveuser@hayden-fedora ~]$ Currently sda and sdb are setup in a hardware RAID-1 mirroring configuration with a previous installation of Fedora 15 running on there now. The motherboard is Gigabyte GA-H67MA-UD2H-B3, which appears to have an Intel SATA controller that has the hardware RAID functionality. 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
Created attachment 549141 [details] lspci output
Created attachment 549143 [details] /var/log/messages file This contains some information about the RAID that it appears that anaconda logs.
Same issue with preupgrade from FC16 to FC17 as well as Net Install Cd. If I boot into rescue mode with the FC17 Net Install CD I can access the partitions via: lvm vgchange -ay Then mount the resultant dm device under /mnt/sysimage.
(In reply to comment #3) > Same issue with preupgrade from FC16 to FC17 as well as Net Install Cd. > > If I boot into rescue mode with the FC17 Net Install CD I can access the > partitions via: > > lvm vgchange -ay > > Then mount the resultant dm device under /mnt/sysimage. That probably means you have old, spurious RAID metadata on your disks. You should remove it using the wipefs utility. See 'man wipefs' for details.
Output of wipefs: [root@ears ~]# wipefs /dev/sda wipefs: WARNING: /dev/sda: appears to contain 'gpt' partition table offset type ---------------------------------------------------------------- 0xe8e0db5c00 isw_raid_member [raid] [root@ears ~]# wipefs /dev/sdb wipefs: WARNING: /dev/sdb: appears to contain 'gpt' partition table offset type ---------------------------------------------------------------- 0xe8e0db5c00 isw_raid_member [raid] Output of blkid: [root@ears ~]# blkid /dev/md126p3: UUID="b1uCrb-0Jqq-KGiY-TUxL-Tezn-BAOb-TmC3ix" TYPE="LVM2_member" /dev/md126p2: UUID="18ab3ab5-ee65-49c2-b92b-e61806d4a775" TYPE="ext4" /dev/sda: TYPE="isw_raid_member" /dev/sdb: TYPE="isw_raid_member" /dev/mapper/vg_ears-lv_swap: UUID="cc9c0678-eba6-4b14-8f00-b30ecc6e0621" TYPE="swap" /dev/mapper/vg_ears-lv_root: UUID="e08378fb-c33c-4fd2-b8ed-116b089cb13d" TYPE="ext4" /dev/sdc1: LABEL="My Book" UUID="5f772048-d6a4-43ec-9c63-70acb6edf15d" TYPE="xfs" /dev/mapper/vg_ears-lv_tmp: UUID="1573db74-b39d-40a6-8575-12146d1313c4" TYPE="ext4" /dev/mapper/vg_ears-lv_home: UUID="785a599d-0613-480d-a6b0-673079cd7543" TYPE="ext4" /dev/mapper/vg_ears-lv_local: UUID="2c8c96b9-5058-4fbb-89b4-b801f463ce42" TYPE="ext4" @David -- System is currently running fine under FC16? Are you suggesting to run wipefs -a?
Not if you have an operational array there, no. How about attaching the following log files (collected from the shell on tty2 right after you see the error during install) so I can see what is happening: /tmp/storage.log /tmp/anaconda.log /tmp/program.log /tmp/syslog Please attach them one at a time, as type text/plain -- no archives. Thanks.
Created attachment 595396 [details] FC16 to FC17 preupgrade /tmp/storage.log
Created attachment 595397 [details] FC16 to FC17 preupgrade /tmp/anaconda.log
Created attachment 595398 [details] FC16 to FC17 preupgrade /tmp/program.log
Created attachment 595399 [details] FC16 to FC17 preupgrade /tmp/syslog
@David -- request files have been uploaded.
Dan, parted seems to think there is something wrong with the partition table on your raid device. Preupgrade ignores devices that appear unusable. I'd be curious what the output of the following command looks like when run from tty2 in the installer while the error message is on the screen: parted /dev/md126 print
# parted /dev/md126 print Error: The backup GPT table is corrupt, but the primary appears OK, so that will be used. OK/Cancel? OK Model: Linux Software RAID Array (md) Disk /dev/md126: 1000GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 1 1049kB 2097kB 1049kB bios_grub 2 2097kB 526MB 524MB ext4 ext4 boot 3 526MB 1000GB 1000GB lvm
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.