Arch Linux

sardina

Member

Registered: 2013-02-23

Posts: 152

[SOLVED] emergency mode after latest filesystem upgrade

After reading the directives on the front page, I successfully updated my system.

But when I rebooted, system went into emergency mode, giving me root login and suggesting to run "journalctl -xb".

Browsing the forum, I saw Scimmia's fix guide at post #265 here, I followed it, reinstalling filesystem, but nothing changed. I also tried unlinking bin, sbin and usr/sbin first, with no luck.

Here's my "journalctl -xb": http://pastebin.com/nw577hSD

Note: The FAT32 lines refers a pen drive, which was mounted at that boot.

Even by (trying) reading it I don't understand how to fix this, could someone help me, please?

TIA

Last edited by sardina (2013-06-11 20:46:11)

---

alter-destiny | wired sound | copycats

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,727

Re: [SOLVED] emergency mode after latest filesystem upgrade

I'm guessing you're automounting with this: https://wiki.archlinux.org/index.php/US … _with_udev ?

If so, make sure /usr/lib/udev/domount is executable.

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: [SOLVED] emergency mode after latest filesystem upgrade

Also, there are a nuber of references to the filesystem being fat32 in your journalctl output.  Around these Linux parts, we refer to those filesystems as vfat. 

An just FYI, typically udev is not intended to be used for things like automounting.  Most of the time the biggest abuse you will see is people having a direct /usr/bin/mount command in their udev rule.  I guess at least what you are doing is calling a script. But I still think that using one of the more traditional automounting methods like udisks, udisks2, or udevil/devmon would be a better way to go.  Just my 2 cents.

u8sand

Member

Registered: 2012-08-15

Posts: 24

Re: [SOLVED] emergency mode after latest filesystem upgrade

I am having what I thought was a very similar issue, my computer was working even after successfully applying the latest update (merging the bins). I noticed that the kernel was updated but when running mkinitcpio--I got lots of 'ERROR: module not found' errors. I noticed it was trying to build a different kernel than the one I had but it still failed to compile when i specified. I'm looking for a solution now.

After reviewing the posts I may have a completely different problem in which I apologize for maybe hijacking.

Like I said, I'm sorry guys... I started writing this post a while ago and should have checked before posting. I just noticed "emergency mode ..." which is what I'm experiencing..

Last edited by u8sand (2013-06-11 15:11:01)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,727

Re: [SOLVED] emergency mode after latest filesystem upgrade

u8sand, completely different issue, that is being discussed in this thread: https://bbs.archlinux.org/viewtopic.php?id=164948

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: [SOLVED] emergency mode after latest filesystem upgrade

@u8sand, your issue is absolutely nothing like that of the OP's.  Please don't try to hijack threads.  If you want help with your issue, then start a thread.  Or better yet, search for issues that relate to your issue or even match your issue and participate in those.  If you can't find any, post a new thread.  If you find something that is only somewhat related, but you think is relevant, post a new thread and link to that thread.

sardina

Member

Registered: 2013-02-23

Posts: 152

Re: [SOLVED] emergency mode after latest filesystem upgrade

Also, there are a nuber of references to the filesystem being fat32 in your journalctl output.  Around these Linux parts, we refer to those filesystems as vfat. 

An just FYI, typically udev is not intended to be used for things like automounting.  Most of the time the biggest abuse you will see is people having a direct /usr/bin/mount command in their udev rule.  I guess at least what you are doing is calling a script. But I still think that using one of the more traditional automounting methods like udisks, udisks2, or udevil/devmon would be a better way to go.  Just my 2 cents.

You're right, I too don't like this kind of things, and I don't remember when I wrote that rule. Just a remnant from when I was a bigger noob, I guess.

Anyway I removed it, but still the problem persists.

Latest "journalctl -xb": http://pastebin.com/Sb6BNk6v

---

alter-destiny | wired sound | copycats

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,727

Re: [SOLVED] emergency mode after latest filesystem upgrade

It's failing for /dev/sdb1, is that still the flash drive?

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,459

Website

Re: [SOLVED] emergency mode after latest filesystem upgrade

Why does it have /dev/sdb1 at /media/usb as a requirement for local filesystem?  What's in your fstab?

EDIT: cross posted with the above.

Last edited by Trilby (2013-06-11 18:48:37)

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

sardina

Member

Registered: 2013-02-23

Posts: 152

Re: [SOLVED] emergency mode after latest filesystem upgrade

Oh my God, this is so embarassing...

Yeah, it was fstab settings fault.

I should have understood by myself, even if it's late here and I'm tired, sorry.

Really thanks to Trilby and the very helpful Scimmia. ('Monkey' in my language )

Closing.

---

alter-destiny | wired sound | copycats