Bug 855576

Summary:	Booting with a missing partition renders the system impossible to rescue
Product:	[openSUSE] openSUSE 13.1	Reporter:	Forgotten User 5jFyFBvk-I <forgotten_5jFyFBvk-I>
Component:	Other	Assignee:	Stanislav Brabec <sbrabec>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P5 - None	CC:	seroton10
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 13.1
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User 5jFyFBvk-I 2013-12-16 08:51:26 UTC

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:25.0) Gecko/20100101 Firefox/25.0

Hi,

I have changed the secondary disk. Resulting in the id to change. I did this without removing the line in fstab.
Now when trying to boot I get failure message saying that cifs timed out etc.
I was expecting a login (in rescue mode) and it also tells me what to do when I login. BUT the login never appears, so I cannot login and remove the line from fstab

Reproducible: Always

Steps to Reproduce:
1.Remove/Change a partition without removing it from fstab
2.Reboot into failsafe mode
3.Wait for rescue login
4.Wait for a looong time (I waited for about 10 minutes)
Actual Results:  
Repeats prompt about disk failure and telling you what to do after logging in. But no login prompt appears.

Expected Results:  
A login prompt should appear to enable me to login and remove the line from fstab

Comment 1 Stanislav Brabec 2013-12-17 16:37:43 UTC

I guess that it can be the same issue as bug 849863. If you switch to text mode (F2 or Esc), do you see the same?

Comment 2 Forgotten User 5jFyFBvk-I 2013-12-17 19:49:24 UTC

Well, it looks very much like it, except that it does not do the fsck.

Other than that, yes

Comment 3 Olav Reinert 2014-04-13 16:04:23 UTC

I have also experienced this (highly annoying!) issue. It is perhaps easier to reproduce by adding a line for a bogus device to /etc fstab (e.g., /dev/sda44).

The only workaround to the never-appearing rescue mode I have found is to boot into emergency mode:
1. Add "systemd.unit=emergency.target" to the kernel options before booting.
2. Log in as root when prompted.
3. Remount root folder to make it writable: "mount -o rw,remount /"
4. Edit /etc/fstab to fix the problem.

Comment 4 Felix Miata 2014-07-14 06:15:49 UTC

This looks to me like yet another bug 832220 duplicate.

Comment 5 Tomáš Chvátal 2015-03-10 12:57:43 UTC

Yep this is another dupe of systemd zealous behaviour for fstab parsing.

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