Skip to main content

How to create Storage array for iscsi disk on a linux machine

 Use Case:

I have to create a KVM cluster using GFS Datastore.


#Create a Ubuntu Linux to act as storage server array:

# Make sure the system have enough resources(Storage,MEM&CPU)

#Install TargetCLI tool:  

     apt install targetcli-fb -y

#Create LUN:

 mkdir -p /iscsi_disks

 fallocate -l 600G /iscsi_disks/disk01.img

 targetcli 

     /backstores/fileio create disk01 /iscsi_disks/disk01.img 600G

     /iscsi create iqn.2025-01.com.example:storage1

     /iscsi/iqn.2025-01.com.example:storage1/tpg1/luns create /backstores/fileio/disk01

     /iscsi/iqn.2025-01.com.example:storage1/tpg1/acls create iqn.2025-01.com.example:client1

     /iscsi/iqn.2025-01.com.example:storage1/tpg1/acls create iqn.2025-01.com.example:client2

    /iscsi/iqn.2025-01.com.example:storage1/tpg1/acls create iqn.2025-01.com.example:client3


#Allow all network to access this LUN:

    cd /iscsi/iqn.2025-01.com.example:storage1/tpg1/portals

    create 0.0.0.0

#enable target service:

    systemctl enable --now target


#on host1:

    echo "InitiatorName=iqn.2025-01.com.example:client1" | sudo tee /etc/iscsi/initiatorname.iscsi

    systemctl restart open-iscsi

#on host2:

    echo "InitiatorName=iqn.2025-01.com.example:client2" | sudo tee /etc/iscsi/initiatorname.iscsi

    systemctl restart open-iscsi

#on host 3:

    echo "InitiatorName=iqn.2025-01.com.example:client3" | sudo tee /etc/iscsi/initiatorname.iscsi

    systemctl restart open-iscsi


#scan target lun on each hosts:

    iscsiadm -m discovery -t sendtargets -p <Storage_IP>

  #login from each hosts

   iscsiadm -m node -p <storage_IP> --login

    #verify new lun:

     lsblk

#To make the iscsi login permanent after reboots: on all hosts:

iscsiadm -m node -T iqn.2025-01.com.example:storage1 -p <Storage_IP>--op update -n node.startup -v automatic

Comments

Popular posts from this blog

Deploy OVF fails Issues detected with selected template. Details: VALUE_ILLEGAL: No supported hardware versions among [virtualbox-2.2]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19].

 Error: While deploy using OVF file ,getting error as : Issues detected with selected template. Details: - -1:-1:VALUE_ILLEGAL: No supported hardware versions among [virtualbox-2.2]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19]. Solution: Open .OVF file and edit       <Info>Virtual hardware requirements for a virtual machine</Info>       <System>         <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>         <vssd:InstanceID>0</vssd:InstanceID>         <vssd:VirtualSystemIdentifier>zabbix_appliance-6.2.7</vssd:VirtualSystemIdentifier>         <vssd:VirtualSystemType> virtualbox-2.2 </vssd:VirtualSystemType>       </System> to  vmx-19       <Info>Virtual hardware requireme...

Change ESXi acceptane level of VIBs to community Supported

-When you install VIB bundles you may see issue like:               'Could not find a trusted signer: self signed certificate  For resolving this issue, we have to convert the ESXi to community supported acceptance level. -To do that: if  ESXI is a VM :      Edit settings ->boot option ->disable secure boot. if Physical ESXi:      Edit  UEFI Now ssh to ESXi: - Move the ESX machine to community-support esxcli software acceptance set --level=CommunitySupported - Install the bundle with no-sign-check esxcli software vib install -d  VMware_bootbank_vmware-fdm_7.0.1-16478307.vib --no-sig-check -  Set back PartnerSupported esxcli software acceptance set --level=PartnerSupported