Bug 1026730

Summary:	openSUSE Tumbleweed doesn't boot when Windows 10 ssd is plugged in
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Forgotten User BIZIQc76wK <forgotten_BIZIQc76wK>
Component:	Basesystem	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P5 - None
Version:	Current
Target Milestone:	---
Hardware:	x86-64
OS:	SUSE Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User BIZIQc76wK 2017-02-23 21:09:27 UTC

After the upgrade to systemd 232 my openSUSE Tumbleweed system was not booting anymore. In the last weeks, I tried to fix the issue by reinstalling the whole system. openSUSE Leap worked without any issue, but Tumbleweed didn't. I tried several kernels. The only error message on boot was:

“dracut-initqueue[398]: Failed to connect to bus: No such file or directory”

By chance, I removed the windows 10 sdd from the pc and Tumbleweed was booting without any issue. I plugged it back in and it wasn't booting.

My ssd with Tumbleweed is encrypted, but I tried an installation without encryption and it was still not working.

Please tell me, which further information you need.

Comment 1 Tomáš Chvátal 2018-06-19 14:36:52 UTC

Unfortunately this bug was overlooked.

Please if you are still having the issue open a new ticket as it is highly probable we already fixed it in meanwhile.

This time also include the exact partition layout, also yast logs could be helpful about the installation.