linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Jack Waterworth <jack@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] lvm2 conf on boot disk
Date: Fri, 11 Jul 2014 19:15:13 -0400	[thread overview]
Message-ID: <53C07001.2090700@redhat.com> (raw)
In-Reply-To: <CAAWpFTFehTVd2J7vq6w2Yo266fsh2anGGosv8PruBBbhmmQNdw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2459 bytes --]

The rebuild of the ramdisk should use the 'mkinitrd' command:

     # mkinitrd /boot/initrd-<version>.img <version>

grub install would be either 'grub' or 'grub-install'.

     # grub-install /dev/sda

If you have an active Red Hat subscription both procedures should be 
documented on the customer portal.

   Jack Waterworth, RHCE
   Senior Technical Support Engineer
   Red Hat Global Support Services
   919.610.2024 -- jack@redhat.com

On 07/11/2014 08:54 AM, Alfredo De Luca wrote:
> Hi Jack.
> Thanks for that. I did pretty much what you said but not sure how to
> re-create the initrd then install the grub.
> Do you have a specific procedure?
> I followed the procedure in attachment but it's slightly different
> from what I am looking for.
>
>
> On Thu, Jul 10, 2014 at 2:46 AM, Jack Waterworth <jack@redhat.com> wrote:
>> There is no way to do an in-place convert from a partitioned device to LVM
>> without losing data. I would recommend adding a new disk, reinstall the OS
>> on the new disk with LVM, and then moving over any data that was required
>> after installation.
>>
>> You may be able to do this in rescue mode within a chrooted environment, but
>> things could get messy. Add the new device, build the lvm stack, copy over
>> the data then chroot into the NEW lvm root. Mount everything appropriately,
>> recreate the initrd and re-install grub onto the new disk.  Go in with the
>> expectation that you may be fixing things after the reboot from rescue mode.
>>
>>    Jack Waterworth, RHCE
>>    Senior Technical Support Engineer
>>    Red Hat Global Support Services
>>    919.610.2024 -- jack@redhat.com
>>
>> On 07/08/2014 05:56 AM, Alfredo De Luca wrote:
>>> Hi all.
>>> I have red hat 5.7 with no lvm2 installed. Now I want to configure
>>> lvm2 on the root and swap partition then later on adding a couple of
>>> LUNs to create a VG
>>> What's the best practice/procedure to install lvm2 on the boot disk?
>>> Is it possible? I guess I have to run Linux CD in rescue mode
>>>
>>> Regards
>>>
>>>
>> _______________________________________________
>> linux-lvm mailing list
>> linux-lvm@redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-lvm
>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
>
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/


[-- Attachment #2: Type: text/html, Size: 4032 bytes --]

      reply	other threads:[~2014-07-11 23:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08  9:56 [linux-lvm] lvm2 conf on boot disk Alfredo De Luca
2014-07-09 16:46 ` Jack Waterworth
2014-07-11 12:54   ` Alfredo De Luca
2014-07-11 23:15     ` Jack Waterworth [this message]

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=53C07001.2090700@redhat.com \
    --to=jack@redhat.com \
    --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).