On Sat, 2014-06-07 at 23:24 +0200, Ralf Mardorf wrote:
> On Sat, 2014-06-07 at 17:13 -0400, Leonid Isaev wrote:
> > I'd remove the fsck hook to let systemd check the filesystems and see
> > if that helps.
>
> Done, but I won't reboot now. I will report back next time I (re)boot
> Arch Linux.
fsck
On Sat, 2014-06-07 at 15:26 -0700, Thilina Mallawa Arachchi wrote:
> Today I upgraded the kernel from a fresh install of 3.14 to 3.4
Hi, downgrading the kernel doesn't cause the issue.
Install the packages
# pacman -Q systemd libsystemd systemd-sysvcompat
syst
I just tried to upgrade three packages, including core/filesystem, and
saw these errors:
filesystem-2014.05-... 8.7 KiB 4.23M/s 00:00 [##] 100%
e2fsprogs-1.42.10-1... 691.8 KiB 1305K/s 00:01 [##] 100%
cups-filters-1.0.54... 648.6 KiB 2033K/s 00
Hi Arch Community,
Today I upgraded the kernel from a fresh install of 3.14 to 3.4 via the
yaourt install of linux-lts34 from AUR.
Booting results logging into the recovery console as root. My / partition
is being booted but my /var and /home are not.
Very similar to this post https://bugs.archl
On Sat, 2014-06-07 at 17:13 -0400, Leonid Isaev wrote:
> I'd remove the fsck hook to let systemd check the filesystems and see
> if that helps.
Done, but I won't reboot now. I will report back next time I (re)boot
Arch Linux.
> > Off-topic PS:
> I meant "running", not "tunning". Also, I can only
On Sat, Jun 07, 2014 at 10:34:12PM +0200, Ralf Mardorf wrote:
> Date: Sat, 07 Jun 2014 22:34:12 +0200
> From: Ralf Mardorf
> To: arch-general@archlinux.org
> Subject: Re: [arch-general] Unwanted forced fsck at each startup - Was: How
> do I _really_ fix the superblock?
> X-Mailer: Evolution 3.12.
On Sat, 2014-06-07 at 19:46 +0200, Alessandro Doro wrote:
> The fsck issue comes (AFAICT) from
> https://bugs.freedesktop.org/show_bug.cgi?id=79576
>
> Systemd 213-6 is now in testing with a patch to remove the recently
> added "-l" option to fsck in systemd-fsck.
> Did you try that?
Yes, it does
On Sat, 2014-06-07 at 13:23 -0400, Leonid Isaev wrote:
> That's actually interesting. Whether / will be fsck'ed or not depends
> on your mkinitcpio hooks (fsck) and kernel cmdline. What are them? Do
> you have "ro" in the cmdline?
The GRUB lines for my kernels all include 'ro'.
[rocketmouse@archl
On Sat, Jun 07, 2014 at 06:44:21PM +0200, Ralf Mardorf wrote:
> On Sat, 2014-06-07 at 18:36 +0200, Alessandro Doro wrote:
> > It's not a new "issue", maybe you're seeing it for the first time
> > (localtime here), in coincidence with the forced fsck bug.
>
> Oops, sorry, not closed, I indeed misse
On Sat, Jun 07, 2014 at 06:49:58PM +0200, Ralf Mardorf wrote:
> Date: Sat, 07 Jun 2014 18:49:58 +0200
> From: Ralf Mardorf
> To: arch-general@archlinux.org
> Subject: Re: [arch-general] How do I _really_ fix the superblock?
> X-Mailer: Evolution 3.12.2
>
> On Sat, 2014-06-07 at 12:43 -0400, Leoni
On Sat, 2014-06-07 at 12:43 -0400, Leonid Isaev wrote:
> Just out of curiosity, when exactly do you see the fsck warning: at
> each reboot, or when booting after some downtime? Also, how do you
> syncronize time: ntpd/chrony/timesyncd?
I see the warning with each startup, it doesn't matter if I re
On Sat, 2014-06-07 at 18:36 +0200, Alessandro Doro wrote:
> It's not a new "issue", maybe you're seeing it for the first time
> (localtime here), in coincidence with the forced fsck bug.
Oops, sorry, not closed, I indeed missed something.
My impression was, that the superblock issue does cause th
On Sat, Jun 07, 2014 at 06:23:49PM +0200, Ralf Mardorf wrote:
> Date: Sat, 07 Jun 2014 18:23:49 +0200
> From: Ralf Mardorf
> To: arch-general@archlinux.org
> Subject: Re: [arch-general] How do I _really_ fix the superblock?
> X-Mailer: Evolution 3.12.2
>
> On Sat, 2014-06-07 at 12:12 -0400, Leoni
On Sat, 2014-06-07 at 18:34 +0200, Ralf Mardorf wrote:
> On Sat, 2014-06-07 at 11:14 -0500, Doug Newgard wrote:
> > On 2014-06-07 11:05, Ralf Mardorf wrote:
> > > On Sat, 2014-06-07 at 17:54 +0200, Bardur Arantsson wrote:
> > >> On 2014-06-07 17:46, Ralf Mardorf wrote:
> > >> [--snip--]
> > >> >
>
On Sat, Jun 07, 2014 at 05:46:48PM +0200, Ralf Mardorf wrote:
> "systemd, libsystemd and systemd-sysvcompat 213-6 from testing only
> solve the fstab issue, but they don't solve the superblock issue." -
> https://bugs.archlinux.org/task/40706
>
> I never run into trouble before, because I use the
On Sat, 2014-06-07 at 11:14 -0500, Doug Newgard wrote:
> On 2014-06-07 11:05, Ralf Mardorf wrote:
> > On Sat, 2014-06-07 at 17:54 +0200, Bardur Arantsson wrote:
> >> On 2014-06-07 17:46, Ralf Mardorf wrote:
> >> [--snip--]
> >> >
> >> > I suspect it's just the evil policy of those systemd folks, wh
On Sat, 2014-06-07 at 12:12 -0400, Leonid Isaev wrote:
> your clock is not correct apparently.
The clock provides the correct localtime. There's no issue caused by the
clock. The issue only appears for Arch Linux with systemd from the
repositories > version 212-3. It worked before:
[rocketmouse@a
On 2014-06-07 11:05, Ralf Mardorf wrote:
On Sat, 2014-06-07 at 17:54 +0200, Bardur Arantsson wrote:
On 2014-06-07 17:46, Ralf Mardorf wrote:
[--snip--]
>
> I suspect it's just the evil policy of those systemd folks, who want to
> teach everybody to follow there ways, as the only right ways.
>
P
On Sat, Jun 07, 2014 at 05:46:48PM +0200, Ralf Mardorf wrote:
> Date: Sat, 07 Jun 2014 17:46:48 +0200
> From: Ralf Mardorf
> To: arch-general@archlinux.org
> Subject: Re: [arch-general] How do I _really_ fix the superblock?
> X-Mailer: Evolution 3.12.2
>
> On Sat, 2014-06-07 at 09:59 -0500, Doug
On Sat, 2014-06-07 at 17:54 +0200, Bardur Arantsson wrote:
> On 2014-06-07 17:46, Ralf Mardorf wrote:
> [--snip--]
> >
> > I suspect it's just the evil policy of those systemd folks, who want to
> > teach everybody to follow there ways, as the only right ways.
> >
>
> Please don't insinuate cons
On 2014-06-07 17:46, Ralf Mardorf wrote:
[--snip--]
>
> I suspect it's just the evil policy of those systemd folks, who want to
> teach everybody to follow there ways, as the only right ways.
>
Please don't insinuate conspiracies without good evidence.
> IMO there's no valid reason not to chose
On Sat, 2014-06-07 at 09:59 -0500, Doug Newgard wrote:
> The Beginner's Guide says: Warning: Using localtime may lead to several
> known and unfixable bugs.
>
> If you're going to do something non-standard that's known to cause
> problems, you have to expect things like this from time to time.
On 2014-06-07 06:57, Ralf Mardorf wrote:
On Sat, 2014-06-07 at 13:50 +0200, Jens Adam wrote:
Sat, 07 Jun 2014 13:36:08 +0200
Ralf Mardorf :
> Could systemd be the culprit?
Yes.
https://bugs.archlinux.org/task/40706
Thank you
and my apologize that I didn't check the bugs myself.
"I had the
On Sat, 2014-06-07 at 13:50 +0200, Jens Adam wrote:
> Sat, 07 Jun 2014 13:36:08 +0200
> Ralf Mardorf :
>
> > Could systemd be the culprit?
>
> Yes.
> https://bugs.archlinux.org/task/40706
Thank you
and my apologize that I didn't check the bugs myself.
"I had the same problem. Simply reverting
Sat, 07 Jun 2014 13:36:08 +0200
Ralf Mardorf :
> Could systemd be the culprit?
Yes.
https://bugs.archlinux.org/task/40706
--byte
signature.asc
Description: PGP signature
Hi,
I still need to comment out everything in fstab, excepted of / (it does
include home) to boot Arch Linux, so at least I'm able to boot. Anyway,
each time I boot, I get a message that the superblock's last write time
was in the future, it always gets fixed and than always the / partition
is che
26 matches
Mail list logo
