Description of problem: The order of volumes in /etc/fstab affect the availability of shell in case of problems with the availability of one of the volumes. Version-Release number of selected component (if applicable): initscripts-8.95-1.i586 How reproducible: 100% Steps to Reproduce: 1. change label on last volume (as example /home) 2. reboot system 3. try to type root password and have access. Actual results: after every symbol of password system put new line. It is not possible to login to damaged system and repair it Expected results: login into damaged system. Additional info: This order work OK. All pseudo FS are placed after root volume and before any other. ---- UUID=808be4f5-829e-48bc-8ff1-14cf3a37cc1b / ext3 defaults 1 1 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts defaults 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 UUID=fe2ec445-2fd6-4cec-9bb4-9eafd0477e53 /var ext4 defaults 1 2 UUID=31431d4e-6d56-48b8-afa8-4f7431d67ac4 /tmp ext4 defaults 1 2 UUID=c79d1cfc-4ec7-4b9c-b8dd-a77cafcba8d3 /usr ext4 defaults 1 2 UUID=55e112c6-3bf2-4ba4-8930-ac81c53be71d /home ext4 defaults 1 2 UUID=7fea1f7d-8ea8-488b-aa9e-67b1946a3e53 /opt ext4 defaults 1 2 UUID=b48051ba-9c21-435f-9acc-190f09ef2d5f /ABulk ext4 defaults 1 2 UUID=c19f898a-307c-4d13-a87b-5323f128263f /ASpace ext4 defaults 1 2 UUID=fb284549-c0b5-4679-8364-ed3cddec8813 swap swap defaults 0 0 This order cause problem. --- UUID=808be4f5-829e-48bc-8ff1-14cf3a37cc1b / ext3 UUID=fe2ec445-2fd6-4cec-9bb4-9eafd0477e53 /var ext4 defaults 1 2 UUID=31431d4e-6d56-48b8-afa8-4f7431d67ac4 /tmp ext4 defaults 1 2 UUID=c79d1cfc-4ec7-4b9c-b8dd-a77cafcba8d3 /usr ext4 defaults 1 2 UUID=55e112c6-3bf2-4ba4-8930-ac81c53be71d /home ext4 defaults 1 2 UUID=7fea1f7d-8ea8-488b-aa9e-67b1946a3e53 /opt ext4 defaults 1 2 UUID=b48051ba-9c21-435f-9acc-190f09ef2d5f /ABulk ext4 defaults 1 2 UUID=c19f898a-307c-4d13-a87b-5323f128263f /ASpace ext4 defaults 1 2 UUID=fb284549-c0b5-4679-8364-ed3cddec8813 swap swap defaults 0 0 defaults 1 1 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts defaults 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0
Sorry, bug is reffered to Fedora-11. Maybe Fedora-12 have the same problem, but I can not confirm it right now
(In reply to comment #0) > Steps to Reproduce: > 1. change label on last volume (as example /home) > 2. reboot system > 3. try to type root password and have access. > > Actual results: > after every symbol of password system put new line. It is not possible to login > to damaged system and repair it > > Expected results: > login into damaged system. Seems like a plymouth issue where it's not quitting properly.
*** Bug 530224 has been marked as a duplicate of this bug. ***
just to transfer the note from the dupe: with 'rhgb' removed from kernel command line (I thought this disabled plymouth, but apparently that's not what it does exactly) this works OK. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This should be fixed as of 0.2009.29.09.11
This is filed against f11, so we can't close it as fixed until an f11 update is shipped (if you can't fix in f11, must close as CANTFIX or WONTFIX). but will drop from f12 blocker list. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. 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 '11'. 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 11'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 11 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.