From: Georges Giralt <georges.giralt@free.fr>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] Sorry to ask here ...
Date: Thu, 23 Feb 2017 20:25:26 +0100 [thread overview]
Message-ID: <b55d9679-db08-7e72-ff0f-ec471fc8f514@free.fr> (raw)
Hello !
I'm sorry to ask for help here, but I'm lost in the middle of nowhere ...
The context :
A PC hardware with an UEFI "BIOS" set to legacy boot only.
3 disks with 2 partitions each. The 3 first partitions are set in
software mirror (md0) and used for /boot (Ext4) .The second 3 partitions
are used as a software mirror and the resulting md1 is the sole PV of a
vg0 group onto which 8 logical volumes are set. This is used to run
Ubuntu 16.04.2 software (after many upgrades...). *
This setup has worked for years and seen changes in disk sizes, main
board, etc...
Lastly, I bet the cause is an upgrade of some packages, the machine
refuses to boot. It drops onto initramfs shell because the vg0 volume
group is not activated. Launching lvm and doing a vgchange -a y does the
trick and the system boots fine afterwards.
I've searched everything I can (but maybe the setup was so rock solid I
became lazy or unconscious) and tried to make again the initramfs with
no luck.
So every leads or advice would be greatly appreciated. Please, refrain
to hit me hard on the face. I'm already mourning....
Many thanks in advance for your help !
* : The 3 disks are here because at one time, long ago, I used mirroring
in the LVM software. ... I switched to software raid and kept the 3
disks as I had them into the box.
--
"If a man empties his purse into his head, no man can take it away from him.
An investment in knowledge always pays the best interest"
Benjamin Franklin.
next reply other threads:[~2017-02-23 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 19:25 Georges Giralt [this message]
2017-02-23 20:23 ` [linux-lvm] Sorry to ask here Xen
2017-02-24 17:00 ` Georges Giralt
2017-03-02 5:44 ` Eric Ren
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=b55d9679-db08-7e72-ff0f-ec471fc8f514@free.fr \
--to=georges.giralt@free.fr \
--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).