From: Dennis Schridde <devurandom@gmx.net>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Check of pool ernie/cache failed (status:1). Manual repair required!
Date: Sat, 12 May 2018 13:30:36 +0200 [thread overview]
Message-ID: <2496144.kxeQXG1iRO@monk> (raw)
In-Reply-To: <1973783.dFIIZJkBNM@monk>
[-- Attachment #1: Type: text/plain, Size: 2258 bytes --]
On Friday, 11 May 2018 19:34:42 CEST Dennis Schridde wrote:
> Hello!
>
> I have an issue re-gaining access to my data. The error messages are:
> # lvchange -ay ernie/system
> Check of pool ernie/cache failed (status:1). Manual repair required!
> # lvconvert --repair ernie/system
> bad checksum in superblock
> Repair of cache metadata volume of cache ernie/system failed (status:1).
> Manual repair required!
>
> How do I recover from this situation and repair the volume group?
>
> For a full log, including the output of pvdisplay, vgdisplay and lvdisplay
> -a, please see attached log file. If more information is necessary, please
> ask.
>
> What led to this situation:
> I am using one of the infamous AMD Ryzen 2400G with an AMD B350 chipset,
> which suffers from random lockups related to CPU C-states [1]. With the
> recent AGESA 1.0.0.2a firmware update and the introduction of the "Power
> Supply Idle Control = Typical Current Idle" setting, the system is stable,
> if it boots at all. But it often takes several attempts to boot -- the
> failed attempts ending in weird firmware / EFI or CPU / idle related Linux
> kernel stack traces, which sometimes even require a hard reset, since
> soft-reboot (ctrl+alt +del) sometimes has no effect, because init dies.
> This was such a situation, where I had to reboot (ctrl+alt+del) and reset
> (hard) the system several times, at the end of which everything seemed
> fine, except that dracut was timing out when activating the disks.
> Debugging the situation using a Fedora 28 live system resulted in the
> attached log file.
>
> --Dennis
>
> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=196683
P.S. I already found older posts [2,3] describing a similar scenario. At the
time a recovery was impossible for the user, but it seems that the situation
improved somewhat since then. However, I am still stick, with `lvconvert --
repair` asking me to repair "manually" (whatever that means), `cache_dump --
repair` not being able to operate on non-active LVs and LVM refusing to
activate the LV as long as it has not been repaired.
[2]: https://www.redhat.com/archives/linux-lvm/2016-December/msg00013.html
[3]: https://www.redhat.com/archives/linux-lvm/2015-August/msg00008.html
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2018-05-12 11:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 17:34 [linux-lvm] Check of pool ernie/cache failed (status:1). Manual repair required! Dennis Schridde
2018-05-12 11:30 ` Dennis Schridde [this message]
2018-05-15 8:11 ` Dennis Schridde
2018-05-15 11:15 ` Zdenek Kabelac
2018-05-16 18:31 ` Dennis Schridde
2018-05-23 19:39 ` Dennis Schridde
2018-05-26 10:15 ` Dennis Schridde
2018-06-04 11:50 ` Dennis Schridde
2018-06-05 8:14 ` Marian Csontos
2018-06-05 10:08 ` Dennis Schridde
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=2496144.kxeQXG1iRO@monk \
--to=devurandom@gmx.net \
--cc=linux-lvm@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).