Hi, I have mounted the volume using the ISCSI target. After restarting the server, the ISCSI volume was not mounted.

I have done the below steps.

1. "iscsiadm -m discovery" - Able to see the IQN targets.
2. "iscsiadm -m node --target name - login" - it is connected and log in.
3. Then I can see the volume in the fdisk-l command, but I am not able to see the PV, VG, & LV.

Need support to fix this issue,

Fine. Now what does "lsblk -f" report for that device, and does "pvscan --cache" see the LVM volume?

Hi Rknichols

Thanks for your email. I will explain this in detail below.

* We are using StoreTrends storage with SAN "16 Volumes".

* All those volumes are mounted through the ISCSI initiator in the Dell Physical server "Centos 5.11."

* Out of 16 Volumes, 2 Volumes are not able to mount. I can see the disk in fdisk-l. But in PVS VGS & LVS it is not showing.

Also, I tried the commands "lsblk -f" & "pvscan --cache" this command is not available in the "Centos 5.11."

CAN I TRY TO MOUNT THE PROBLEM STORAGE VOLUME TO ANOTHER LINUX CENTOS 7.9 SERVER?.

Need your further support.

Regards
Vasanth Sherly

I did a test install of CentOS 5 in a VM, and indeed that ancient system (nearly 10 years past EOL) lacks an "lsblk" command. You can try the "blkid" command as a substitute. But, there should certainly be a "pvscan" command in /sbin. Perhaps you were not trying that as root. A missing "pvscan" command would explain why you are not seeing any of your LVM volumes.

I would certainly expect a CentOS 7.9 system to recognize those volumes.

Hi Rknichols,

This is to inform you that we have fixed the issue. Please find the details below.

The problematic volume is 11TB. Initially, we created the partition through the GDISK command.

Now, we have checked the disk with the GDISK command and found the error "GPT: damaged".

Then, we ran the GDISK recovery option and fixed the issue. Finally, the state changed from "GPT: damaged" to "GPT: Present."

===============================================================================
gdisk /dev/sdw
GPT fdisk (gdisk) version 0.6.10

Caution! After loading partitions, the CRC doesn't check out!
Warning! Main partition table CRC mismatch! Loaded backup partition table
instead of main partition table!

Warning! One or more CRCs don't match. You should repair the disk!

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged

****************************************************************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
****************************************************************************
=================================================================================

Regards
Vasanth Sherly

Good to hear that. Please mark the thread as solved.