Bug 955172

Summary:	systemd-fstab-generator: Failed to create mount unit file /run/systemd/generator/sysroot.mount
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Ludwig Nussel <lnussel>
Component:	Basesystem	Assignee:	Thomas Blume <thomas.blume>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	fvogt, lnussel, okurz, thomas.blume, trenn
Version:	Current
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Ludwig Nussel 2015-11-16 12:08:24 UTC

Fresh minimal TW install on lvm has this in dmesg:

[    1.770439] systemd-fstab-generator[123]: Failed to create mount unit file /run/systemd/generator/sysroot.mount, as it already exists. Duplicate entry in /etc/fstab?
[    1.770749] systemd[120]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with error code 1.
[    3.310458] systemd-fstab-generator[590]: Failed to create mount unit file /run/systemd/generator/sysroot.mount, as it already exists. Duplicate entry in /etc/fstab?

Comment 1 Dr. Werner Fink 2015-11-16 12:41:30 UTC

(In reply to Ludwig Nussel from comment #0)

I'm missing your /etc/fstab from both hard disk as well as from initrd if any. Also the complete content of etc/cmdline.d/ from initrd and the used /proc/cmdline.

Comment 2 Thomas Blume 2015-11-16 12:47:29 UTC

Reason for the message is that the initrd now contains an /etc/fstab with the root mount entry.
In addition, root= is given as boot parameter.
systemd-fstab-generator is reading both and would create a sysroot.mount unit for each. The second attempt to create a sysroot.mount unit fails, as it already exists.
Thomas, Fabian, in order to suppress this error, I guess we need to add the /etc/fstab entry into the initrd only if there is not root= boot parameter.

Comment 3 Fabian Vogt 2015-11-16 13:04:13 UTC

There's some more discussion in the other bug about this.

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

Comment 4 Thomas Blume 2015-11-16 13:09:38 UTC

ok, thanks

Comment 5 Oliver Kurz 2015-11-22 21:03:26 UTC

adjust resolution state to "duplicate" instead of "fixed" as of comment #3

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