Lelio Michele Lattari
asked on
Linux LVM - LVM logical volume from group on raid1 partition not available (not active) at startup
Hi experts!
I have a physical lvm2 volume over raid1 partition. Logical volume from this group is inactive at startup and the respective fs /home cannot be mounted, althouht I have previously activated the group with vgchange -a y. On startup I land in emergency mode from where I can activate the group and continue normally. I use Scientific Linux 7. Why the lvm logical volume is not active at startup? Thanks for any help!
I have a physical lvm2 volume over raid1 partition. Logical volume from this group is inactive at startup and the respective fs /home cannot be mounted, althouht I have previously activated the group with vgchange -a y. On startup I land in emergency mode from where I can activate the group and continue normally. I use Scientific Linux 7. Why the lvm logical volume is not active at startup? Thanks for any help!
Last Comment
ASKER
Hi!
There are absolutely no errors on boot, until I try to mount the volume through /etc/fstab. The volume, althought I activate the group using vgchange, is inactive after every reboot.
[root@filemon1 ~]# pvdisplay
--- Physical volume ---
PV Name /dev/md2
VG Name mirrored-raid1-devices
PV Size 869.08 GiB / not usable 2.81 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 222483
Free PE 94483
Allocated PE 128000
PV UUID 0lo3jy-qixg-tWPl-nQqv-6dtA
[root@filemon1 ~]# vgdisplay
--- Volume group ---
VG Name mirrored-raid1-devices
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 869.07 GiB
PE Size 4.00 MiB
Total PE 222483
Alloc PE / Size 128000 / 500.00 GiB
Free PE / Size 94483 / 369.07 GiB
VG UUID gTdMqy-yfDt-dgQr-LqN1-mkpD
[root@filemon1 ~]# lvdisplay
--- Logical volume ---
LV Path /dev/mirrored-raid1-device
LV Name lv_home
VG Name mirrored-raid1-devices
LV UUID 0cttq2-x5DN-I4I3-7sZK-h9zb
LV Write Access read/write
LV Creation host, time filemon1, 2014-11-17 22:09:01 +0100
LV Status NOT available
LV Size 500.00 GiB
Current LE 128000
Segments 1
Allocation inherit
Read ahead sectors auto
[root@filemon1 ~]# vgchange -aay
1 logical volume(s) in volume group "mirrored-raid1-devices" now active
[root@filemon1 ~]# lvdisplay
--- Logical volume ---
LV Path /dev/mirrored-raid1-device
LV Name lv_home
VG Name mirrored-raid1-devices
LV UUID 0cttq2-x5DN-I4I3-7sZK-h9zb
LV Write Access read/write
LV Creation host, time filemon1, 2014-11-17 22:09:01 +0100
LV Status available
# open 0
LV Size 500.00 GiB
Current LE 128000
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
[root@filemon1 ~]# fdisk -l
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes, 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 * 2048 1026047 512000 fd Linux raid autodetect
/dev/sdb2 1026048 25815039 12394496 82 Linux swap / Solaris
/dev/sdb3 25815040 130672639 52428800 fd Linux raid autodetect
/dev/sdb4 130672640 1953525167 911426264 5 Extended
/dev/sdb5 130674688 1953523711 911424512 fd Linux raid autodetect
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes, 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x000bb947
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 1026047 512000 83 Linux
/dev/sda2 1026048 25815039 12394496 82 Linux swap / Solaris
/dev/sda3 25815040 130672639 52428800 83 Linux
/dev/sda4 130672640 1953525167 911426264 5 Extended
/dev/sda5 130674688 1953523711 911424512 83 Linux
Disk /dev/md1: 53.7 GB, 53653405696 bytes, 104791808 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/md0: 524 MB, 524222464 bytes, 1023872 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/md2: 933.2 GB, 933164285952 bytes, 1822586496 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/mirrored--raid
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
[root@filemon1 ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 500M 0 part
│ └─md0 9:0 0 500M 0 raid1 /boot
├─sda2 8:2 0 11.8G 0 part [SWAP]
├─sda3 8:3 0 50G 0 part
│ └─md1 9:1 0 50G 0 raid1 /
├─sda4 8:4 0 1K 0 part
└─sda5 8:5 0 869.2G 0 part
└─md2 9:2 0 869.1G 0 raid1
└─mirrored--raid1--devices
sdb 8:16 0 931.5G 0 disk
├─sdb1 8:17 0 500M 0 part
│ └─md0 9:0 0 500M 0 raid1 /boot
├─sdb2 8:18 0 11.8G 0 part [SWAP]
├─sdb3 8:19 0 50G 0 part
│ └─md1 9:1 0 50G 0 raid1 /
├─sdb4 8:20 0 1K 0 part
└─sdb5 8:21 0 869.2G 0 part
└─md2 9:2 0 869.1G 0 raid1
└─mirrored--raid1--devices
sr0 11:0 1 1024M 0 rom
[root@filemon1 ~]# blkid
/dev/sdb1: UUID="d94999a4-4d70-6676-e
/dev/sdb2: UUID="86d0f300-bc51-4f5f-a
/dev/sdb3: UUID="a9189950-e3ce-0155-c
/dev/sdb5: UUID="a444c20b-a067-3616-f
/dev/sda1: UUID="d94999a4-4d70-6676-e
/dev/sda2: UUID="262de8fc-67c1-4b29-a
/dev/sda3: UUID="a9189950-e3ce-0155-c
/dev/sda5: UUID="a444c20b-a067-3616-f
/dev/md1: UUID="a0c1f14f-f88c-4a95-9
/dev/md0: UUID="fa43cdb6-5bdd-40c3-b
/dev/md2: UUID="0lo3jy-qixg-tWPl-nQq
/dev/mapper/mirrored--raid
[root@filemon1 ~]# mdadm --examine --scan
ARRAY /dev/md0 UUID=d94999a4:4d706676:ea0
ARRAY /dev/md/1 metadata=1.2 UUID=a9189950:e3ce0155:ca5
ARRAY /dev/md/2 metadata=1.2 UUID=a444c20b:a0673616:f94
[root@filemon1 ~]# cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 sda5[2] sdb5[0]
911293248 blocks super 1.2 [2/2] [UU]
md0 : active raid1 sda1[1] sdb1[0]
511936 blocks [2/2] [UU]
md1 : active raid1 sda3[2] sdb3[0]
52395904 blocks super 1.2 [2/2] [UU]
unused devices: <none>
The main problem is that the logical volume lv_home is not being ACTIVATED during the startup process.
There are absolutely no errors on boot, until I try to mount the volume through /etc/fstab. The volume, althought I activate the group using vgchange, is inactive after every reboot.
[root@filemon1 ~]# pvdisplay
--- Physical volume ---
PV Name /dev/md2
VG Name mirrored-raid1-devices
PV Size 869.08 GiB / not usable 2.81 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 222483
Free PE 94483
Allocated PE 128000
PV UUID 0lo3jy-qixg-tWPl-nQqv-6dtA
[root@filemon1 ~]# vgdisplay
--- Volume group ---
VG Name mirrored-raid1-devices
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 869.07 GiB
PE Size 4.00 MiB
Total PE 222483
Alloc PE / Size 128000 / 500.00 GiB
Free PE / Size 94483 / 369.07 GiB
VG UUID gTdMqy-yfDt-dgQr-LqN1-mkpD
[root@filemon1 ~]# lvdisplay
--- Logical volume ---
LV Path /dev/mirrored-raid1-device
LV Name lv_home
VG Name mirrored-raid1-devices
LV UUID 0cttq2-x5DN-I4I3-7sZK-h9zb
LV Write Access read/write
LV Creation host, time filemon1, 2014-11-17 22:09:01 +0100
LV Status NOT available
LV Size 500.00 GiB
Current LE 128000
Segments 1
Allocation inherit
Read ahead sectors auto
[root@filemon1 ~]# vgchange -aay
1 logical volume(s) in volume group "mirrored-raid1-devices" now active
[root@filemon1 ~]# lvdisplay
--- Logical volume ---
LV Path /dev/mirrored-raid1-device
LV Name lv_home
VG Name mirrored-raid1-devices
LV UUID 0cttq2-x5DN-I4I3-7sZK-h9zb
LV Write Access read/write
LV Creation host, time filemon1, 2014-11-17 22:09:01 +0100
LV Status available
# open 0
LV Size 500.00 GiB
Current LE 128000
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
[root@filemon1 ~]# fdisk -l
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes, 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 * 2048 1026047 512000 fd Linux raid autodetect
/dev/sdb2 1026048 25815039 12394496 82 Linux swap / Solaris
/dev/sdb3 25815040 130672639 52428800 fd Linux raid autodetect
/dev/sdb4 130672640 1953525167 911426264 5 Extended
/dev/sdb5 130674688 1953523711 911424512 fd Linux raid autodetect
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes, 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x000bb947
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 1026047 512000 83 Linux
/dev/sda2 1026048 25815039 12394496 82 Linux swap / Solaris
/dev/sda3 25815040 130672639 52428800 83 Linux
/dev/sda4 130672640 1953525167 911426264 5 Extended
/dev/sda5 130674688 1953523711 911424512 83 Linux
Disk /dev/md1: 53.7 GB, 53653405696 bytes, 104791808 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/md0: 524 MB, 524222464 bytes, 1023872 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/md2: 933.2 GB, 933164285952 bytes, 1822586496 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/mirrored--raid
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
[root@filemon1 ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 500M 0 part
│ └─md0 9:0 0 500M 0 raid1 /boot
├─sda2 8:2 0 11.8G 0 part [SWAP]
├─sda3 8:3 0 50G 0 part
│ └─md1 9:1 0 50G 0 raid1 /
├─sda4 8:4 0 1K 0 part
└─sda5 8:5 0 869.2G 0 part
└─md2 9:2 0 869.1G 0 raid1
└─mirrored--raid1--devices
sdb 8:16 0 931.5G 0 disk
├─sdb1 8:17 0 500M 0 part
│ └─md0 9:0 0 500M 0 raid1 /boot
├─sdb2 8:18 0 11.8G 0 part [SWAP]
├─sdb3 8:19 0 50G 0 part
│ └─md1 9:1 0 50G 0 raid1 /
├─sdb4 8:20 0 1K 0 part
└─sdb5 8:21 0 869.2G 0 part
└─md2 9:2 0 869.1G 0 raid1
└─mirrored--raid1--devices
sr0 11:0 1 1024M 0 rom
[root@filemon1 ~]# blkid
/dev/sdb1: UUID="d94999a4-4d70-6676-e
/dev/sdb2: UUID="86d0f300-bc51-4f5f-a
/dev/sdb3: UUID="a9189950-e3ce-0155-c
/dev/sdb5: UUID="a444c20b-a067-3616-f
/dev/sda1: UUID="d94999a4-4d70-6676-e
/dev/sda2: UUID="262de8fc-67c1-4b29-a
/dev/sda3: UUID="a9189950-e3ce-0155-c
/dev/sda5: UUID="a444c20b-a067-3616-f
/dev/md1: UUID="a0c1f14f-f88c-4a95-9
/dev/md0: UUID="fa43cdb6-5bdd-40c3-b
/dev/md2: UUID="0lo3jy-qixg-tWPl-nQq
/dev/mapper/mirrored--raid
[root@filemon1 ~]# mdadm --examine --scan
ARRAY /dev/md0 UUID=d94999a4:4d706676:ea0
ARRAY /dev/md/1 metadata=1.2 UUID=a9189950:e3ce0155:ca5
ARRAY /dev/md/2 metadata=1.2 UUID=a444c20b:a0673616:f94
[root@filemon1 ~]# cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 sda5[2] sdb5[0]
911293248 blocks super 1.2 [2/2] [UU]
md0 : active raid1 sda1[1] sdb1[0]
511936 blocks [2/2] [UU]
md1 : active raid1 sda3[2] sdb3[0]
52395904 blocks super 1.2 [2/2] [UU]
unused devices: <none>
The main problem is that the logical volume lv_home is not being ACTIVATED during the startup process.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
The reason is that NOBODY could help me to solve the problem and I have found the solution inspecting the system. My question is: WHERE ARE THE EXPERTS? :-)))
Linux
Linux is a UNIX-like open source operating system with hundreds of distinct distributions, including: Fedora, openSUSE, Ubuntu, Debian, Slackware, Gentoo, CentOS, and Arch Linux. Linux is generally associated with web and database servers, but has become popular in many niche industries and applications.
71K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
Can you post some output back here to help diagnose
the following commands run as root might prove useful...
fdisk -l
vgs
lvs
(if using software raid)
mdadm --examine --scan
cat /proc/mdstat
Usually vgscan would find all the volumes and activate them, for rhel 7 though they use systemd so something might have gone awry, check the boot logs for more information (this would be in /var/log/boot.log but I dont know off the top of my head if this has changed as I've not had a chance to play with 7 yet)