Bug 13151

Summary:	USB stick only unmountable as admin, after that system won't boot up: time out, dependencies failed
Product:	Mageia	Reporter:	Sascha Schroeder <sascha.schroeder>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	critical
Priority:	Normal	CC:	zen25000
Version:	4
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Sascha Schroeder 2014-04-05 13:49:58 CEST

Description of problem:

I use an USB stick which most of the time is constantly plugged in. Recently I wanted to unplug it because of an installation of an old scanner.

The system won't let me unmount it, I get a message that it was mounted by another user, which is just not true. However, I had to type in my admin password and were good to go.

The "magic" happened after this:

I wasn't able to reboot into my system after this operation:

[TIME] Timed out waiting for device dev-disk-by\<blah_id>\blah.device
[DEPEND] Dependency failed for /media/win_c2
[DEPEND] Dependency failed for Local File Systems
[DEPEND] Dependency failed for Relabel all filesystems, if necessary
netprofile is started [...]

Welcome to emergency mode! After logging in type [...]

I wasn't able to solve the problem from here. Seriously, what is the system trying to relabel??

The only thing which worked was to plug in my USB stick again and reboot. In this case it isn't unpluggable again, I have to leave the system that way.

Mageia 4: For me it is a nightmare. This has to be the fifth or sixth time I am not able to boot into the system correctly. What is going on with this release??

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

How reproducible:
see above

Steps to Reproduce:
1. try to unplug a USB device
2. system will ask for admin pw because you plugged in as another user (there is only one in my case)
3. type in pw
4. reboot
5. system won't boot up anymore
6. time outs, dependencies failed, etc., see desc

Reproducible:

Steps to Reproduce:

Comment 1 Barry Jackson 2014-04-05 14:12:11 CEST

1.Boot with the stick inserted.
2. Comment out the line which refers to your USB stick in /etc/fstab, (you will need to use a text editor as root)
3. Shut down
4. Remove the stick
5. Reboot

You should now be able to use the stick as normal.

CC: (none) => zen25000

Comment 2 Sascha Schroeder 2014-04-05 14:23:46 CEST

Prior to your comment deleting the lines will do the same job.

But thank you for the advice.

Is it normal that this entry is permanent in fstab? And what caused this?

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME

Comment 3 Barry Jackson 2014-04-05 18:33:26 CEST

(In reply to Sascha Schroeder from comment #2)

> Is it normal that this entry is permanent in fstab? 

No, removable media should not normally be in fstab

And what caused this?

Maybe you used diskdrake to mount the stick and allowed it to update fstab?

Or possibly this bug https://bugs.mageia.org/show_bug.cgi?id=12631

Hint: if you ever hit this issue again, you can run mc from the emergency mode and edit fstab with it's built-in editor, then re-boot. I had to do this a few days ago on a server after removing a hard drive which I had forgotten had a partition in fstab.

Comment 4 Sascha Schroeder 2014-04-06 12:52:12 CEST

I remember the fact you mention about removable media and was surprised about this behavior.

And I really didn't change anything, never used diskdrake. What I did prior to this was editing the xorg.conf. But this isn't related to fstab in a way, is it?

I read about the other bug but my installation was via the DVD.

I never encountered this error with USB media btw, I am using Mageia for two years now.

I was overwhelmed by this emergency mode, especially what was listed in journalctl -xb. I just had no use for this information. If I had known that fstab was affected I would have used MC and edited it directly, as you recommend.