Description of problem: Fedup-dracut hangs around the time where it is supposed to mount the raid volume I updated fedora, rebooted, installed fedup, ran fedup-cli --network 18 rebooted my machine Version-Release number of selected component (if applicable): fedup 0.7.2-1.fc17 How reproducible: Very I did a clean isntall of F17 to test it (the F18 usb did not run Anaconda) Steps to Reproduce: 1. Update, reboot, install fedup 2. fedup-cli --network 18 3. reboot 4. Watch fedora logo never progress, the harddrive light never blinks Actual results: Nothing Expected results: Some progress to happen (maybe a blinking harddrive light) Additional info:
Can you boot F17 and attach /etc/fstab and /proc/cmdline?
Created attachment 689467 [details] The fstab that doesn'T let fedUp 18 properly boot
Created attachment 689468 [details] The cmdline that doesn'T let fedUp 18 properly boot
Good, your system is properly using UUIDs, so it's not bug 895805. You said you did a fresh install of F17 - what version of systemd is installed? (rpm -q systemd)
I'm using: systemd-44-23.fc17.x86_64 I should probably say, that I followed the recommendations in this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=879327 And that when I tried to isntall F18 from a liveUSB/dvd: 1. The first time I think the install was faulty because it didn't even drop me into "first boot" to add my first user. 2. When I tried to resintall with the same liveUSB/different dvd, anaconda would crash before even opening up. I gave up and reinstalled F17. I would file a bug report for those two, but I wouldn't know what to say :S
Created attachment 692951 [details] "Screenshot" of where it hangs in the boot process I'm sorry if it is really blurry, my hand is not really steady and my camera phone has a large shutter time.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 to Fedora 17's end of life. 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.
I'm closing this bug because I decided to move away from Raid 1 and therefore no longer have a system to check if this is still an issue.
Changing resolution for record-keeping purposes.