Rename Linux Volume Groups and Logical Volumes

-
If you are decided to rename your Linux LVM Volume Groups or Logical Volumes then here is how:

Rename a volume group:

# vgrename /dev/vg_old /dev/vgnewname 

Rename a logical volume:

# lvrename /dev/vg_name/lv_old /dev/vg_name/lv_newname 

Make sure to modify the respective entries in fstab as well:

# vi /etc/fstab

 /dev/mapper/vg_old-lv_old       /var         ext4    defaults        1 1

to

/dev/mapper/vgnewname-lv_newname       /var         ext4    defaults        1 1

And if you are renaming your root partition VG or LV, then grub menu file also needs to be modified in order for server to find your vmlinuz kernel image under root directory during boot process:

# vi /boot/grub/menu.lst

kernel /vmlinuz-2.6.32-431.el6.x86_64 ro root=/dev/mapper/vg_old-lv_root rd_NO_LUKS rd_LVM_LV=vg_old/lv_root LANG=en_US.UTF-8 rd_LVM_LV=vg_old/lv_swap

to 

kernel /vmlinuz-2.6.32-431.el6.x86_64 ro root=/dev/mapper/vgnewname-lv_root rd_NO_LUKS rd_LVM_LV=vg_old/lv_root LANG=en_US.UTF-8 rd_LVM_LV=vgnewname/lv_swap


Note: If you forgot to modify these 2 mentioned files menu.list and fstab like me for the first time, you probably receive following kernel panic after reboot your system:

Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init tainted 2.6.32-431.el6.x86_64
Call Trace

After amended those files, you should be able to get rid of that kernel panic error and your system will be booted with new VG or LV names mounted. 







Comments

  1. Unknown5 September 2018 at 21:16

    Thanks!
    I changed the VG without restarting the system. After a year i did not know the reason for the kernel panic.

    ReplyDelete

Post a comment

Popular posts from this blog

Running Docker Wildfly/JBoss Application Server in Debug mode via Eclipse

-
I have recently built the whole Development Environment of Java Enterprise Edition (J2EE) project on multiple Docker containers. It has saved the hassle of setting up a dev env for new developers. All it takes to setup the environment is to clone our github repositories and run the Docker images.

I will explain the setup in a future post.

Build Wildfly Docker Image with Debugging Enabled
So basically in order to run the Wildfly in debug mode, we need to add --debug flag to the Wildfly standalone.sh startup script.

Also we need to expose port 8787 in our image as it's the default port for Wildfly JVM debug mode.

1. Create or change your Wildfly Dockerfile as follows:
$ cat Dockerfile FROM jboss/wildfly:10.0.0.Final EXPOSE8787CMD["/opt/jboss/wildfly/bin/standalone.sh", "-b", "0.0.0.0", "-bmanagement", "0.0.0.0", "--debug"] 2. Build and tag the image:
$ docker build -t wildfly-debug . 3. Run the image either via  docker run:
$ …
Read more

Foreman fresh installation issue on Foreman proxy

-
After a fresh  installation of Foreman, I got another weird error while try to add a host to foreman:

# puppet agent --test
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed when searching for node node.example.com: Failed to find node.example.com via exec: Execution of '/etc/puppet/node.rb node.example.com' returned 1:
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run


It turns out that issue is because of foreman proxy that it has not been created during installation.
So need to create it manually. In foreman GUI:
Infrastructure > Smart proxies > add new proxy
or if there is any exist edit it and correct the entry of your proxy FQDN. It's something like https://node.example.com:8443

And again, after try to add new proxy, yet another bug:  Unable to communicate with the proxy: ERF12-2530 [ProxyAPI::ProxyException]: Unable to detect features ([RestClient::RequestTimeout]: Request Timeout for proxy Plea…
Read more

Building RPM OpenSSH 7.1p1 on RHEL/CentOS 6.5

-
After I've implemented the OpenVAS vulnerability assessment system, I've made a complete vulnerability testing on the environment for both Linux and Wintel servers.

The result for the all Linux servers were Red :) Severity 10.0(High). The reason was the OpenSSH version 5.

Test result:

High (CVSS: 8.5)
NVT: OpenSSH Multiple Vulnerabilities (OID: 1.3.6.1.4.1.25623.1.0.806052) Product detection result: cpe:/a:openbsd:openssh:5.3 by SSH Server type and version (OID: 1.3.6.1.4.1.25623.1.0.10267) SummaryThis host is running OpenSSH and is prone to multiple vulnerabilities. Vulnerability Detection Result
Installed version: 5.3 Fixed version: 7.0 ImpactSuccessful exploitation will allow an attacker to gain privileges, to conduct impersonation attacks, to conduct brute-force attacks or cause a denial of service.
Impact Level: Application SolutionUpgrade to OpenSSH 7.0 or later. For updates refer to http://www.openssh.com Affected Software/OSOpenSSH versions before 7.0 Vulnerability InsightMu…
Read more