Bug 704053

Summary: Computer does not boot - relabel issue
Product: [Fedora] Fedora Reporter: rossirafael
Component: systemdAssignee: Lennart Poettering <lpoetter>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 15CC: esandeen, johannbg, 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-05-14 03:36:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
screen dump of last lines of the the boot process where failure occurs
none
same as before but with better formatting none

Description rossirafael 2011-05-12 01:21:20 UTC
Created attachment 498418 [details]
screen dump of last lines of the the boot process where failure occurs

Description of problem: computer does not boot - relabel issue (see boot_output.txt attached). Boot process stops before graphic interface is enabled and asks for Ctrl-D for maintenance or boot login


Version-Release number of selected component (if applicable): Fedora 15 Beta


How reproducible: every attempt boot


Steps to Reproduce:
1. boot computer
2.
3.
  
Actual results: computer does not boot


Expected results:normal boot process


Additional info: occured after yum update to a new kernel. booting with older kernels *does not* help.

Comment 1 rossirafael 2011-05-12 01:35:10 UTC
Created attachment 498419 [details]
same as before but with better formatting

after the line

Started Initialize storage subsystems (RAID, LVM, etc.).

the computer halts for a couple of seconds before continuing.

Comment 2 Eric Sandeen 2011-05-12 03:16:30 UTC
fs_mark is a benchmark, I do not think it will cause any boot problems.  :)

Looks more systemd related to me, but I can't parse the error messages:

> Starting Mark the need to relabel after reboot aborted because a dependency
> failed.
> Starting Relabel all filesystems, if necessary aborted because a dependency 
> failed.
> Welcome to emergency mode. Use "systemctl default" or ^D to activate default > mode.

Maybe it's some other package invoked by systemd, but I don't know how to triage this one.

-Eric

Comment 3 Michal Schmidt 2011-05-12 08:01:17 UTC
Please attach /etc/fstab

Comment 4 Lennart Poettering 2011-05-12 11:06:55 UTC
You seem to mention /dev/sdd1 in your fstab which doesn't exist, which causes systemd to timeout waiting for it.

Consider adding "nofail" to the respective fstab entry in order to make this fs if it is missing non-fatal.

Comment 5 rossirafael 2011-05-14 03:35:51 UTC
(In reply to comment #4)
> You seem to mention /dev/sdd1 in your fstab which doesn't exist, which causes
> systemd to timeout waiting for it.
> 
> Consider adding "nofail" to the respective fstab entry in order to make this fs
> if it is missing non-fatal.

You've got it. I have one external HD always plugged in and hence it is in the fstab (/dev/sdd). The power cable of this HD was off and I didn't expect Fedora not to boot because of that. I have added "nofail" and boot is ok.

Thanks