From: Kai Krakow <hurikhan77@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: F21 fails to mount root part, btrfs check: Couldn't open file system
Date: Wed, 01 Apr 2015 01:38:35 +0200 [thread overview]
Message-ID: <ronrub-mln.ln1@hurikhan77.spdns.de> (raw)
In-Reply-To: CAJCQCtRZuUvmYnZh1_UV7nEkT4rFZprzhs3qfFx1yQCJYBOJ0w@mail.gmail.com
Chris Murphy <lists@colorremedies.com> schrieb:
> On Tue, Mar 31, 2015 at 4:15 PM, Chris Murphy <lists@colorremedies.com>
> wrote:
>
>> The i915 regression right now is really annoying. With a Samsung 840
>> EVO I've had inexplicable and non-deterministic boot failures.
>
> Clarification: the boot failures happen following the i915 panic and
> subsequent forced power off.
Yeah I thought that, too, because after hitting "reset" it looked like one
hard disk didn't appear in dmesg and thus btrfs didn't mount (btrfs-raid).
So I turned the machine off completely because I had similar issues with
i915 freezes and strange boot issues during the following boot before. It
looks like the GPU is not necessarily completely reset when hitting the
reset button. But that's another story.
In my case the hard disk was there - I didn't just scan hard enough through
the huge pile of logs. I had to btrfs-zero-log, wrote "reboot" into the
rescue shell, kernel came back, mount still locking up and sitting there
until systemd decided to throw me to emergency after 5 minutes of waiting or
so. I've rebooted again, machine came up. This was a few reboots after the
machine was powered off, so I'd rule any GPU freeze artifacts out here. I
just needed multiple reboots to arrange myself with my dracut/systemd combo
super hero voodoo abilities (read: I cumbersome tried everything until one
thing worked while swearing at my innocent monitor, well sort of, it's
powered by the GPU).
On every reboot it felt like bcache was replaying cache transactions - but I
think this is by design (read: bcache is always dirty, even after a clean
shutdown, if using write-back mode) and not part of the problem.
--
Replies to list only preferred.
next prev parent reply other threads:[~2015-03-31 23:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 18:55 F21 fails to mount root part, btrfs check: Couldn't open file system Martin Langhoff
2015-03-31 20:09 ` Chris Murphy
2015-03-31 20:11 ` Chris Murphy
2015-03-31 21:45 ` Kai Krakow
2015-03-31 21:48 ` Kai Krakow
2015-03-31 22:15 ` Chris Murphy
2015-03-31 22:17 ` Chris Murphy
2015-03-31 23:38 ` Kai Krakow [this message]
2015-03-31 23:56 ` Martin Langhoff
[not found] ` <HK2PR01MB0308B3759FC1AED779C219869AF40@HK2PR01MB0308.apcprd01.prod.exchangelabs.com>
2015-03-31 22:11 ` Chris Murphy
2015-03-31 23:54 ` Martin Langhoff
2015-04-01 1:33 ` Chris Murphy
2015-04-01 15:42 ` Martin Langhoff
2015-04-01 16:15 ` Martin Langhoff
2015-04-01 16:26 ` Martin Langhoff
2015-04-01 17:09 ` Chris Murphy
2015-04-01 17:03 ` Chris Murphy
2015-04-01 17:26 ` Martin Langhoff
2015-04-01 18:04 ` Chris Murphy
2015-04-01 18:16 ` Martin Langhoff
2015-04-01 18:20 ` Chris Murphy
2015-04-01 18:29 ` Martin Langhoff
2015-04-01 18:54 ` Chris Murphy
2015-04-01 19:23 ` Martin Langhoff
2015-04-01 20:14 ` Chris Murphy
2015-04-01 20:21 ` Chris Murphy
2015-04-02 3:29 ` Chris Murphy
2015-04-01 15:47 ` Martin Langhoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ronrub-mln.ln1@hurikhan77.spdns.de \
--to=hurikhan77@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox