Bug 669951

Summary: no logs exists
Product: [Fedora] Fedora Reporter: Ahmed Abdou <mail>
Component: systemdAssignee: Lennart Poettering <lpoetter>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: lpoetter, metherid, mschmidt, notting, plautrba
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-18 10:59:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Ahmed Abdou 2011-01-16 02:57:09 UTC
Description of problem:
1 - The boot logs I see are truncated, just as
=====================================
                Welcome to Fedora 
Starting udev: 	[  OK  ]
Setting hostname ahmed.fedrawi.com:  	[  OK  ]
Setting up Logical Volume Management:   3 logical volume(s) in volume group "centos5" now active
  2 logical volume(s) in volume group "vg_sins" now active
	[  OK  ]
Checking filesystems
/dev/mapper/vg_sins-LV00_Sys: clean, 447399/2101232 files, 4432930/8394752 blocks
BigData2: recovering journal
/dev/sdb1: recovering journal
BigData2: clean, 104124/12558336 files, 38560311/50225214 blocks
/dev/sdb1: clean, 87/128016 files, 86400/512000 blocks
/home: recovering journal
/home: clean, 80473/575952 files, 1645285/2302976 blocks
BigData: recovering journal
BigData: clean, 302092/7061504 files, 18883136/28245162 blocks
	[  OK  ]
Remounting root filesystem in read-write mode:  	[  OK  ]
Mounting local filesystems:  	[  OK  ]
Enabling local filesystem quotas:  	[  OK  ]
Enabling /etc/fstab swaps:  	[  OK  ]
==================================

2-There's alert that there's a boot problem but I don't know see it , all processes boot-up correctly

Version-Release number of selected component (if applicable):
systemd-10-2.fc14.1.x86_64

How reproducible:
Power on ur machine, install systemd, then add it as default init as kernel parameter , then start


Expected results:
-boot logs should be complete
-the boot errors should not trigger false alarm

Additional info:
dmesg | fpaste > http://fpaste.org/ZdKT/

Comment 1 Lennart Poettering 2011-01-18 10:59:11 UTC
Please use rawhide if you want to test systemd, we do not really support systemd on F14. Sorry.