Re: Welcome to emergency mode!

On Thu 11 Feb 2016 at 10:28:34 (-0800), Rick Thomas wrote: > > On Feb 10, 2016, at 12:42 PM, David Wright wrote: > > > I hope you eventually get to study the journal even if you don't have > > /var/log/journal. You might post the output from: > > The systemd journal

Re: Welcome to emergency mode!

On Feb 10, 2016, at 12:42 PM, David Wright wrote: > I hope you eventually get to study the journal even if you don't have > /var/log/journal. You might post the output from: The systemd journal is, by default, kept in the directory, /run/log/journal. Because it is

Re: Welcome to emergency mode!

On Tue, Feb 09, 2016 at 04:01:12PM -0600, Dutch Ingraham wrote: > On Tue, Feb 09, 2016 at 02:49:20PM -0700, Bob Holtzman wrote: > > > > > > > >As root journalctl produces a long list, tail journalctl produces > > > > > > > >"tail: cannot open ‘journalctl’ for reading: No such file or directory". >

Re: Welcome to emergency mode!

On Tue, Feb 09, 2016 at 04:28:16PM -0600, John Hasler wrote: > Bob Holtzman writes: > > Read the first line of my post. > > You wrote: > > As root journalctl produces a long list > > Which we, of course, read as "When I run the command journalctl as root > it produces a long list". > > Then

Re: Welcome to emergency mode!

On Tue, Feb 09, 2016 at 10:54:30PM +, Brian wrote: > On Tue 09 Feb 2016 at 14:50:40 -0700, Bob Holtzman wrote: > > > On Mon, Feb 08, 2016 at 05:52:27PM -0600, John Hasler wrote: > > > Bob Holtzman writes: > > > > As root journalctl produces a long list, tail journalctl produces > > > > > >

Re: Welcome to emergency mode!

On Wed 10 Feb 2016 at 12:41:21 (-0700), Bob Holtzman wrote: > On Tue, Feb 09, 2016 at 10:54:30PM +, Brian wrote: > > On Tue 09 Feb 2016 at 14:50:40 -0700, Bob Holtzman wrote: > > > > > On Mon, Feb 08, 2016 at 05:52:27PM -0600, John Hasler wrote: > > > > Bob Holtzman writes: > > > > > As root

Re: Welcome to emergency mode!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Feb 08, 2016 at 04:27:47PM -0700, Bob Holtzman wrote: [...] > As root journalctl produces a long list, tail journalctl produces > > "tail: cannot open ‘journalctl’ for reading: No such file or directory". > > Now I'm really confused. Any

Re: Welcome to emergency mode!

Bob Holtzman writes: > Read the first line of my post. You wrote: > As root journalctl produces a long list Which we, of course, read as "When I run the command journalctl as root it produces a long list". Then you wrote: > tail journalctl produces "tail: cannot open ‘journalctl’ for reading:

Re: Welcome to emergency mode!

On Mon, Feb 08, 2016 at 05:56:33PM -0600, Dutch Ingraham wrote: > > > > > >As root journalctl produces a long list, tail journalctl produces > > > > > >"tail: cannot open ‘journalctl’ for reading: No such file or directory". > > > > > >Now I'm really confused. Any explanation? > > > > > > > I

Re: Welcome to emergency mode!

On Tue, Feb 09, 2016 at 02:49:20PM -0700, Bob Holtzman wrote: > > > > > >As root journalctl produces a long list, tail journalctl produces > > > > > >"tail: cannot open ‘journalctl’ for reading: No such file or directory". > > > > > >Now I'm really confused. Any explanation? > > > > > > > I

Re: Welcome to emergency mode!

On Mon, Feb 08, 2016 at 05:52:27PM -0600, John Hasler wrote: > Bob Holtzman writes: > > As root journalctl produces a long list, tail journalctl produces > > > "tail: cannot open ‘journalctl’ for reading: No such file or directory". > > > Now I'm really confused. Any explanation? > >

Re: Welcome to emergency mode!

On Mon, Feb 08, 2016 at 06:35:27PM -0500, Frank McCormick wrote: > On 08/02/16 06:27 PM, Bob Holtzman wrote: > >On Mon, Jan 11, 2016 at 10:32:43AM +, Brian wrote: > >>On Mon 11 Jan 2016 at 00:51:24 -0500, Steve Matzura wrote: > >> > >>>On Sun, 10 Jan 2016 23:40:28 -0500, Gary wrote: > >>> >

Re: Welcome to emergency mode!

On Tue 09 Feb 2016 at 14:50:40 -0700, Bob Holtzman wrote: > On Mon, Feb 08, 2016 at 05:52:27PM -0600, John Hasler wrote: > > Bob Holtzman writes: > > > As root journalctl produces a long list, tail journalctl produces > > > > > "tail: cannot open ‘journalctl’ for reading: No such file or

Re: Welcome to emergency mode!

Dutch Ingraham composed on 2016-02-08 17:56 (UTC-0600): >> >"tail: cannot open ‘journalctl’ for reading: No such file or directory". >> >Now I'm really confused. Any explanation? >> I belive tail is designed for use with text files...which systemd journal >> isn't. > journalctl has a

Re: Welcome to emergency mode!

On 08/02/16 06:27 PM, Bob Holtzman wrote: On Mon, Jan 11, 2016 at 10:32:43AM +, Brian wrote: On Mon 11 Jan 2016 at 00:51:24 -0500, Steve Matzura wrote: On Sun, 10 Jan 2016 23:40:28 -0500, Gary wrote: On 10/01/16 07:15 PM, Steve Matzura wrote: After solving all my mount problems and

Re: Welcome to emergency mode!

> > > >As root journalctl produces a long list, tail journalctl produces > > > >"tail: cannot open ‘journalctl’ for reading: No such file or directory". > > > >Now I'm really confused. Any explanation? > > > > I belive tail is designed for use with text files...which systemd journal > isn't. >

Re: Welcome to emergency mode!

On Mon, Jan 11, 2016 at 10:32:43AM +, Brian wrote: > On Mon 11 Jan 2016 at 00:51:24 -0500, Steve Matzura wrote: > > > On Sun, 10 Jan 2016 23:40:28 -0500, Gary wrote: > > > > >On 10/01/16 07:15 PM, Steve Matzura wrote: > > >> After solving all my mount problems and changing from dynamic to >

Re: Welcome to emergency mode!

Bob Holtzman writes: > As root journalctl produces a long list, tail journalctl produces > "tail: cannot open ‘journalctl’ for reading: No such file or directory". > Now I'm really confused. Any explanation? journalctl is a program for querying the systemd journal. tail is a tool to output

Re: Welcome to emergency mode!

On Mon 08 Feb 2016 at 16:27:47 -0700, Bob Holtzman wrote: > On Mon, Jan 11, 2016 at 10:32:43AM +, Brian wrote: > > On Mon 11 Jan 2016 at 00:51:24 -0500, Steve Matzura wrote: > > > > > On Sun, 10 Jan 2016 23:40:28 -0500, Gary wrote: > > > > > > >On 10/01/16 07:15 PM, Steve Matzura wrote: > >

Re: Welcome to emergency mode!

On Mon, 11 Jan 2016 00:51:24 -0500 Steve Matzura wrote: > On Sun, 10 Jan 2016 23:40:28 -0500, Gary wrote: > > >On 10/01/16 07:15 PM, Steve Matzura wrote: > >> After solving all my mount problems and changing from dynamic to > >There are lots of things that can go

Re: Welcome to emergency mode!

On Mon 11 Jan 2016 at 00:51:24 -0500, Steve Matzura wrote: > On Sun, 10 Jan 2016 23:40:28 -0500, Gary wrote: > > >On 10/01/16 07:15 PM, Steve Matzura wrote: > >> After solving all my mount problems and changing from dynamic to > >There are lots of things that can go wrong, but if you had been

Re: Welcome to emergency mode!

On Mon, 2016-01-11 at 08:23 +, Joe wrote: > My best guess is a typo in fstab, as you said that was the next thing > to modify. The very first time I ran a systemd-enabled Debian, I got > that rather cheerful message, as I had removable drives there that > were > suddenly a problem. There

Re: Welcome to emergency mode!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jan 11, 2016 at 06:32:54AM -0500, Steve Matzura wrote: [...] > Ya know, I must really learn to be more careful and fastidious, and > for someone who's been doing this stuff for as long as I have, I > should rightfully be drummed out of the

Re: Welcome to emergency mode!

On Mon, 11 Jan 2016 11:35:22 +0100, Sven wrote: >There seems to be quite a few bug reports about problems with fstab and >dropping into emergency mode, so worth a shot. > >(Always make a backup before changing stuff in /etc!) Oh, I did; I simply forgot about that change, mostly because with all

Re: Welcome to emergency mode!

Joe: On Mon, 11 Jan 2016 08:23:27 +, you wrote: >My best guess is a typo in fstab, as you said that was the next thing >to modify. The very first time I ran a systemd-enabled Debian, I got >that rather cheerful message, as I had removable drives there that were >suddenly a problem. Ya know,

Re: Welcome to emergency mode!

Tim, On Sun, 10 Jan 2016 22:33:03 -0600, you wrote: >If you are using Debian Jessie a static IP address is set using >/etc/dhcpcd.conf and the much debated "systemd". I just worked my way >through this on a Raspberry Pi which uses "Raspian" Jessie, a port of >Debian. The details can be found

Re: Welcome to emergency mode!

Gary: On Sun, 10 Jan 2016 23:40:28 -0500, you wrote: >What messages are you seeing in dmesg or syslog (or the new SystemD >versions)? What do you see on the screen before you get the emergency >mode messages? dmesg shows no errors. /var/log/syslog's last message has a time stamp of just

Re: Welcome to emergency mode!

On 10/01/16 07:15 PM, Steve Matzura wrote: After solving all my mount problems and changing from dynamic to static addressing by editing /etc/network/interfaces, I reboot the system and was greeted with: Welcome to emergency mode. "systemctl default", "systemctl reboot" to

Re: Welcome to emergency mode!

On 1/10/2016 6:15 PM, Steve Matzura wrote: After solving all my mount problems and changing from dynamic to static addressing by editing /etc/network/interfaces, I reboot the system and was greeted with: Welcome to emergency mode. "systemctl default", "systemctl reboot" to

Re: Welcome to emergency mode!

On Sun, 10 Jan 2016 23:40:28 -0500, Gary wrote: >On 10/01/16 07:15 PM, Steve Matzura wrote: >> After solving all my mount problems and changing from dynamic to >There are lots of things that can go wrong, but if you had been booting >normally, it's likely something you've done since the initial

Welcome to emergency mode!

After solving all my mount problems and changing from dynamic to static addressing by editing /etc/network/interfaces, I reboot the system and was greeted with: Welcome to emergency mode. "systemctl default", "systemctl reboot" to try again, or press Control-D to cont