Created attachment 681981 [details] Picture I took of my boot text. Description of problem: I'm upgrading from Fedora 18 Beta to Fedora 18 and the System Upgrade option doesn't appear to be working. The progress bar just pauses and when I press escape it shows me an error: "dracut-pre-pivot[368]: mkdir: cannot create directory '/sysroot/lib/modules/3.6.10-4.fc18.x86_64': Read-only file system" and then proceeds to show the same things but for 'mount' and 'failed to bind', obviously due to its inability to create the directory in the first place. In /etc/fstab all of my filesystems are type 'defaults', which /should/ imply not being read-only, yes? Version-Release number of selected component (if applicable): fedup-0.7.1-1.fc18.noarch How reproducible: Every time I select the System Upgrade item Steps to Reproduce: 0. Possess my particular FStable 1. Reboot computer 2. Select "System Upgrade" from GRUB menu 3. Fail to write to filesystem Actual results: Fails to write to filesystem, claiming it's read-only when fstab begs to differ. Expected results: System actually upgrades Additional info: See attached text (my /etc/fstab)
Created attachment 681982 [details] /etc/fstab
Unable to solve by changing the 'ro' text in the 'linux' line of the System Upgrade boot commands to either 'defaults' or 'rw'. Previous message does not show when I see the boot text, but all that is displayed is "Reached Plymouth Boot Screen", something else related to boot, and "Welcome to Fedora 18 (Spherical Cow)." In the time I've spent sitting there, nothing happens. Graphical progress bar stops as usual.
Created attachment 685142 [details] Most recent boot text
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 18'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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.