Bug 664325
| Summary: | Installation failure - Preupgrade fails after restart | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gary Meerschaert <gary.meerschaert> |
| Component: | preupgrade | Assignee: | Richard Hughes <richard> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 14 | CC: | richard |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-12-20 01:34:14 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
*** This bug has been marked as a duplicate of bug 664327 *** |
Description of problem: Using preupgrade from Fedora 13, the installation fails after the reboot as indicated in the attached bug report. The installation seems to fail upon encountering my large RAID array, which works properly in Fedora 13. /etc/mdadm.conf contains # mdadm.conf written out by anaconda MAILADDR root@localhost AUTO +imsm +1.x -all ARRAY /dev/md/0_0 metadata=0.90 UUID=53654485:40f422c8:19f0a6b8:f896c017 ARRAY /dev/md0 metadata=1.2 name=:md1 UUID=07b8cb07:1dd824e4:1a20d1d0:f7cff60d mdadm --detail /dev/md127 reports /dev/md127: Version : 0.90 Creation Time : Mon Feb 16 06:56:03 2009 Raid Level : raid5 Array Size : 1465127616 (1397.25 GiB 1500.29 GB) Used Dev Size : 488375872 (465.75 GiB 500.10 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 127 Persistence : Superblock is persistent Update Time : Sun Dec 19 15:31:16 2010 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 4K UUID : 53654485:40f422c8:19f0a6b8:f896c017 Events : 0.316754 Number Major Minor RaidDevice State 0 8 2 0 active sync /dev/sda2 1 8 49 1 active sync /dev/sdd1 2 8 65 2 active sync /dev/sde1 3 8 33 3 active sync /dev/sdc1 dmesg (patrial) reports raid6: sse2x1 3640 MB/s raid6: sse2x2 4546 MB/s raid6: using algorithm sse2x2 (4546 MB/s) md: raid6 personality registered for level 6 md: raid5 personality registered for level 5 md: raid4 personality registered for level 4 raid5: device sda2 operational as raid disk 0 raid5: device sdc1 operational as raid disk 3 raid5: device sdd1 operational as raid disk 1 raid5: device sde1 operational as raid disk 2 raid5: allocated 4222kB for md127 0: w=1 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0 3: w=2 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0 1: w=3 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0 2: w=4 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0 raid5: raid level 5 set md127 active with 4 out of 4 devices, algorithm 2 RAID5 conf printout: --- rd:4 wd:4 disk 0, o:1, dev:sda2 disk 1, o:1, dev:sdd1 disk 2, o:1, dev:sde1 disk 3, o:1, dev:sdc1 md127: detected capacity change from 0 to 1500290678784 md: bind<sda3> md127: unknown partition table md: bind<sdb3> md: raid1 personality registered for level 1 raid1: raid set md0 active with 2 out of 2 mirrors md0: detected capacity change from 0 to 223315164160 md0: unknown partition table EXT4-fs (sda1): mounted filesystem with ordered data mode EXT4-fs (dm-7): mounted filesystem with ordered data mode EXT4-fs (dm-6): mounted filesystem with ordered data mode EXT4-fs (dm-0): mounted filesystem with ordered data mode EXT4-fs (dm-1): mounted filesystem with ordered data mode EXT4-fs (dm-3): mounted filesystem with ordered data mode EXT4-fs (dm-2): mounted filesystem with ordered data mode EXT4-fs (dm-4): mounted filesystem with ordered data mode EXT4-fs (dm-5): mounted filesystem with ordered data mode EXT4-fs (md127): mounted filesystem with ordered data mode Adding 16777212k swap on /dev/sdb2. Priority:-1 extents:1 across:16777212k df -h reports Filesystem Size Used Avail Use% Mounted on /dev/sdb1 238G 561M 236G 1% / tmpfs 1.6G 1.3M 1.6G 1% /dev/shm /dev/sda1 485M 245M 215M 54% /boot /dev/mapper/VG0-Logical_Volume_07 45G 24G 19G 57% /data /dev/mapper/VG0-Logical_Volume_06 30G 3.8G 25G 14% /home /dev/mapper/VG0-Logical_Volume_00 6.8G 234M 6.3G 4% /opt /dev/mapper/VG0-Logical_Volume_01 30G 5.5G 23G 20% /usr /dev/mapper/VG0-Logical_Volume_03 6.8G 4.3G 2.3G 66% /var /dev/mapper/VG0-Logical_Volume_02 30G 2.6G 26G 10% /usr/local /dev/mapper/VG0-Logical_Volume_04 30G 285M 28G 1% /var/log /dev/mapper/VG0-Logical_Volume_05 30G 178M 28G 1% /var/spool /dev/md127 1.4T 626G 680G 48% /backup Version-Release number of selected component (if applicable): How reproducible: completely. Happens every time. Steps to Reproduce: 1. run preupgrade 2. system reboots 3. error reported. Bug report saved Actual results: Installation failed Expected results: System upgraded to Fedora 14 Additional info: