Hide Forgot
Description of problem: After update 20110329, the boot messages are not gone. Version-Release number of selected component (if applicable): How reproducible: every time I boot the system Steps to Reproduce: 1. boot system 2.no messages, just fsck messages 3. Actual results: systemd-fsck[383]: /dev/sda2: clean, 475019/2883584 files, 3974230/11521280 blocks systemd-fsck[787]: /dev/sda5: clean, 351730/11845632 files, 31113725/47375616 blocks systemd-fsck[783]: /dev/sda1: clean, 93/102400 files, 109180/409600 blocks Expected results: A lot more information on what service has started, which has not Additional info: [bpm]$ sudo systemctl status plymouth-start.service plymouth-start.service - Show Plymouth Boot Screen Loaded: loaded (/lib/systemd/system/plymouth-start.service) Active: failed since Tue, 29 Mar 2011 08:17:03 -0500; 4h 59min ago CGroup: name=systemd:/system/plymouth-start.service
Found this in /var/log/messages Mar 29 07:48:54 dufus kernel: [ 13.873383] systemd-fsck[690]: /dev/sda1: clean, 93/102400 files, 109180/409600 blocks Mar 29 07:48:54 dufus kernel: [ 13.953798] systemd[1]: plymouth-start.service: control process exited, code=exited status=69 Mar 29 07:48:54 dufus kernel: [ 13.959061] systemd[1]: Unit plymouth-start.service entered failed state. Mar 29 07:48:54 dufus kernel: [ 14.077149] systemd-fsck[735]: /dev/sda5: clean, 351683/11845632 files, 31106844/47375616 blocks Mar 29 07:48:54 dufus kernel: [ 14.449639] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) Mar 29 07:48:54 dufus kernel: [ 14.727011] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: user_xattr Mar 29 07:48:54 dufus kernel: [ 17.041152] mcelog.setup[926]: read: No such device Ma
I aslo see these "plymouth-start.service: control process exited, code=exited status=69" maybe these ar ok, i really don't know. I am able to boot normally. # systemctl status plymouth-start.service plymouth-start.service - Show Plymouth Boot Screen Loaded: loaded (/lib/systemd/system/plymouth-start.service) Active: failed since Thu, 14 Apr 2011 18:01:13 -0300; 1h 39min ago Process: 818 ExecStart=/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid (code=exited, status=69) CGroup: name=systemd:/system/plymouth-start.service # uptime 19:40:58 up 1:39, 5 users, load average: 0.14, 0.11, 0.13 This is normal boot: Apr 14 18:01:16 xxxx kernel: [ 7.310607] microcode: AMD microcode update via /dev/cpu/microcode not supported Apr 14 18:01:16 xxxx kernel: [ 7.310928] microcode: AMD microcode update via /dev/cpu/microcode not supported Apr 14 18:01:16 xxxx kernel: [ 7.968136] mtp-probe[625]: checking bus 3, device 2: "/sys/devices/pci0000:00/0000:00:02.0/usb3/3-3" Apr 14 18:01:16 xxxx kernel: [ 7.968348] mtp-probe[642]: checking bus 4, device 2: "/sys/devices/pci0000:00/0000:00:04.0/usb4/4-3" Apr 14 18:01:16 xxxx kernel: [ 8.088590] mtp-probe[625]: bus: 3, device: 2 was not an MTP device Apr 14 18:01:16 xxxx kernel: [ 8.088600] mtp-probe[642]: bus: 4, device: 2 was not an MTP device Apr 14 18:01:16 xxxx kernel: [ 8.103753] md: bind<sdb2> Apr 14 18:01:16 xxxx kernel: [ 8.253635] Adding 8000332k swap on /dev/sda5. Priority:0 extents:1 across:8000332k Apr 14 18:01:16 xxxx kernel: [ 8.263377] ACPI: PCI Interrupt Link [LN0B] enabled at IRQ 18 Apr 14 18:01:16 xxxx kernel: [ 8.263384] HDA Intel 0000:02:00.1: PCI INT B -> Link[LN0B] -> GSI 18 (level, low) -> IRQ 18 Apr 14 18:01:16 xxxx kernel: [ 8.283738] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 17 Apr 14 18:01:16 xxxx kernel: [ 8.283745] CA0106 0000:01:09.0: PCI INT A -> Link[LNKB] -> GSI 17 (level, low) -> IRQ 17 Apr 14 18:01:16 xxxx kernel: [ 8.283774] snd-ca0106: Model 1006 Rev 00000000 Serial 10061102 Apr 14 18:01:16 xxxx kernel: [ 8.300203] md: bind<sda2> Apr 14 18:01:16 xxxx kernel: [ 8.324773] md: raid1 personality registered for level 1 Apr 14 18:01:16 xxxx kernel: [ 8.324917] bio: create slab <bio-1> at 1 Apr 14 18:01:16 xxxx kernel: [ 8.324997] md/raid1:md127: active with 2 out of 2 mirrors Apr 14 18:01:16 xxxx kernel: [ 8.325030] md127: detected capacity change from 0 to 35837444096 Apr 14 18:01:16 xxxx kernel: [ 8.344058] md127: unknown partition table Apr 14 18:01:16 xxxx kernel: [ 8.651217] systemd[1]: plymouth-start.service: control process exited, code=exited status=69 Apr 14 18:01:16 xxxx kernel: [ 8.662348] systemd[1]: Unit plymouth-start.service entered failed state. Apr 14 18:01:16 xxxx kernel: [ 8.688638] systemd-fsck[790]: Reiserfs super block in block 16 on 0x806 of format 3.6 with standard journal Apr 14 18:01:16 xxxx kernel: [ 8.688810] systemd-fsck[790]: Blocks (total/free): 204909056/12458212 by 4096 bytes Apr 14 18:01:16 xxxx kernel: [ 8.688819] systemd-fsck[790]: Filesystem is clean Apr 14 18:01:16 xxxx kernel: [ 8.690154] systemd-fsck[763]: Reiserfs super block in block 16 on 0x816 of format 3.6 with standard journal Apr 14 18:01:16 xxxx kernel: [ 8.690165] systemd-fsck[763]: Blocks (total/free): 200246192/102501814 by 4096 bytes Apr 14 18:01:16 xxxx kernel: [ 8.690187] systemd-fsck[763]: Filesystem is clean Apr 14 18:01:16 xxxx kernel: [ 8.866897] REISERFS (device sdb6): found reiserfs format "3.6" with standard journal Apr 14 18:01:16 xxxx kernel: [ 8.866911] REISERFS (device sdb6): using ordered data mode Apr 14 18:01:16 xxxx kernel: [ 8.867426] REISERFS (device sdb6): journal params: device sdb6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Apr 14 18:01:16 xxxx kernel: [ 8.867868] REISERFS (device sdb6): checking transaction log (sdb6) Apr 14 18:01:16 xxxx kernel: [ 8.868306] REISERFS (device sda6): found reiserfs format "3.6" with standard journal Apr 14 18:01:16 xxxx kernel: [ 8.868323] REISERFS (device sda6): using ordered data mode Apr 14 18:01:16 xxxx kernel: [ 8.869286] REISERFS (device sda6): journal params: device sda6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Apr 14 18:01:16 xxxx kernel: [ 8.869781] REISERFS (device sda6): checking transaction log (sda6) ------------------ dracut.noarch 009-5.fc15 @updates-testing kernel 2.6.38.2-9.fc15.x86_64 plymouth.x86_64 0.8.4-0.20110304.1.fc15 @fedora plymouth-core-libs.x86_64 0.8.4-0.20110304.1.fc15 @fedora plymouth-graphics-libs.x86_64 0.8.4-0.20110304.1.fc15 @fedora plymouth-plugin-label.x86_64 0.8.4-0.20110304.1.fc15 @fedora plymouth-plugin-two-step.x86_64 0.8.4-0.20110304.1.fc15 @fedora plymouth-scripts.x86_64 0.8.4-0.20110304.1.fc15 @fedora plymouth-system-theme.x86_64 0.8.4-0.20110304.1.fc15 @fedora plymouth-theme-charge.x86_64 0.8.4-0.20110304.1.fc15 @fedora
Is the issue still happening? Can this bug-report be closed?
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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