Bug 708489

Summary:	Fedora 15 boot fails after upgrade
Product:	[Fedora] Fedora	Reporter:	Vytas <vytautas1987>
Component:	systemd	Assignee:	Lennart Poettering <lpoetter>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	15	CC:	dennis, harald, johannbg, lpoetter, maurizio.antillon, metherid, mschmidt, notting, plautrba, tooru.oguri
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-06-10 18:57:57 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vytas 2011-05-27 19:31:43 UTC

Description of problem:
Fedora 15 boot fails after upgrade
Welcome to emergency mode
..
And Then I can login as root into terminal.

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


How reproducible:
100%

Steps to Reproduce:
1. turn PC on

  
Actual results:
boot failure

Expected results:
boot into kdm

Additional info:
Can provide it after login just ask what you need.

Comment 1 Vytas 2011-05-28 05:59:06 UTC

I dmesg and found in last line that Unit *.mount entered failed state.
It was my manual mount in /etc/fstab so I commented it out then dmesg shows:
Unit emergency.service entered failed state.

Comment 2 Vytas 2011-05-28 06:08:34 UTC

I booted into it finally. :D

Here "bad" lines of /etc/fstab:
#/dev/sda1		/home/vytautas/Downloads/	ext4	defaults	0 0
#/dev/sdb1		/mnt/sdb1		vfat	users,uid=500,gid=500	0 0

I still need to figure out how to re add those mounts.

Comment 3 Harald Hoyer 2011-05-30 08:01:26 UTC

(In reply to comment #2)
> I booted into it finally. :D
> 
> Here "bad" lines of /etc/fstab:
> #/dev/sda1  /home/vytautas/Downloads/ ext4 defaults 0 0
> #/dev/sdb1  /mnt/sdb1  vfat users,uid=500,gid=500 0 0
> 

are these not valid? you might want to use UUID or LABEL... and if you want to mount them manuallly add "noauto" to the options.

For automount, you might want to add also "comment=systemd.automount" to the options.

Comment 4 Michal Schmidt 2011-05-30 10:48:53 UTC

Do not ever use /dev/sd?? names in fstab. The order in which the kernel discovers the disks is more or less random. Definitely use stable names instead (e.g. UUID, LABEL).

Comment 5 Michal Schmidt 2011-06-06 17:35:02 UTC

Does it work with stable device names in fstab?

Comment 6 Vytas 2011-06-10 18:29:22 UTC

UUID=13768150-5ce8-4d22-8bb9-52f2f163f7a4 /home/vytautas/Downloads/	ext4	defaults	0 0
Does not work.

$ su -c 'blkid'
Password: 
/dev/sda2: UUID="7382592E06EB46E2" TYPE="ntfs" 
/dev/root: LABEL="Fedora-12-x86_64" UUID="94f87b1c-7df0-40f8-a55d-5f2a777b51b3" TYPE="ext4" 
/dev/sda3: UUID="48105aa5-9232-4c4c-bd1a-8dae7f6e16da" TYPE="ext4" 
/dev/sda1: UUID="13768150-5ce8-4d22-8bb9-52f2f163f7a4" TYPE="ext4" 
/dev/sda5: UUID="SDDceU-QvMu-81ep-GjEQ-wsjH-oWvf-vdarva" TYPE="LVM2_member" 
/dev/mapper/vg_vyto-lv_swap: UUID="89886854-3954-4435-b4b4-ed85cb1dde28" TYPE="swap"

Comment 7 Michal Schmidt 2011-06-10 18:49:55 UTC

(In reply to comment #6)
> UUID=13768150-5ce8-4d22-8bb9-52f2f163f7a4 /home/vytautas/Downloads/ ext4
> defaults 0 0
> Does not work.

Oh, this is almost certainly bug 709681.
See if removing the trailing '/' helps.

Comment 8 Vytas 2011-06-10 18:57:30 UTC

Yes, it helps.

Comment 9 Vytas 2011-06-10 18:57:57 UTC


*** This bug has been marked as a duplicate of bug 709681 ***