Hide Forgot
Description of problem: I have mdadm raids on my system as md0 / md1 / md2 Running fedup 0.8 from testing. Okay I upgraded everything else, but I have got two machines using mdadm and raid LVMs. The fedup --network 20 --nogpgcheck runs through no issues, apart from a few packages. However on reboot, it bombs out complaining it cant find the UUID of my arrays and drops into a dracut shell. Sure I checked in /dev/disk/by-uuid, all the md0 / md1 / md2 volumes are gone, only the 3 physical disks are still there. Seems dracut is not mounting my raid volumes making it impossible to upgrade. # Start End Size Type Name 1 2048 4095 1M BIOS boot parti 2 4096 1747599359 833.3G Linux RAID 3 1747599360 1931919359 87.9G Linux RAID 4 1931919360 1952497663 9.8G Linux RAID 5 1952497664 1953521663 500M Microsoft basic Disk /dev/sdc: 320.1 GB, 320071851520 bytes, 625140335 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x000c287e Device Boot Start End Blocks Id System /dev/sdc1 2048 625139711 312568832 83 Linux Disk /dev/md2: 10.5 GB, 10534969344 bytes, 20576112 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md0: 94.4 GB, 94370717696 bytes, 184317808 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md1: 894.8 GB, 894767587328 bytes, 1747592944 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes # # /etc/fstab # Created by anaconda on Sat Feb 18 02:44:59 2012 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # UUID=4804abbd-8f20-4c7f-a8ce-3033e5a56751 / ext4 defaults,usrquota 1 1 UUID=47d3652d-feda-4c8f-9bbb-b1bc6e10da4d /boot ext4 defaults 1 2 UUID=38ac7b70-2223-4dbd-9dd5-6c33d4e54085 /home ext4 defaults,usrquota 1 2 UUID=3367a211-bb54-4ff9-9031-9b17f7655b1d swap swap defaults 0 0 Clearly fedup is broken... And then..... yum --releasever=20 distro-sync Works! I had the same level of clean up as a fedup upgrade on the non mdadm machines. Clearly a bug in fedup unable to boot off existing mdadm raids - pretty stupid since you run raid for redundancy. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Might be related: bug 1097664
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Weird that apparently no developer is actively involved with this software yet Fedora ships it as 'supported'....
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora 'version' of '21'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.