**Warning**: This lab represents a significantly broken environment and goes well beyond simple troubleshooting.
In this lab, you must resolve any issues preventing the content mounted at `/storage` from being accessed.
*This course is not approved or sponsored by Red Hat.*
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Verify the iSCSI target configuration and status.
On Server1 (10.0.1.10)
Verify the target service is running:
systemctl status targetStart and enable the target service:
systemctl start target && systemctl enable targetVerify the process is listening on port 3260:
ss -ltnp | grep 3260Check if the firewall is permitting traffic over 3260/tcp:
firewall-cmd --list-allPermit incoming traffic over port 3260/tcp:
firewall-cmd --permanent --add-port=3260/tcpReload the firewall:
firewall-cmd --reloadView the iSCSI target configuration:
targetcli/> ls- Verify the iSCSI initiator configuration and status.
On Server2 (10.0.1.11)
View any existing node entires:
iscsiadm -m nodeVerify the initiator name matches the ACL from the target:
cat /etc/iscsi/initiatorname.iscsiChange the name to match the target:
InitiatorName=iqn.1994-05.com.redhat:c1cd6e78d22Verify security settings match those of target:
less /etc/iscsi/iscsid.conf#node.session.auth.authmethod = CHAP ... #node.session.auth.username = username #node.session.auth.password = passwordRestart the
iscsidservice to pick up the change:systemctl restart iscsidDiscover iSCSI targets from 10.0.1.10:
iscsiadm -m discovery -t sendtargets -p 10.0.1.10Log in to target:
iscsiadm -m node -T iqn.2003-01.org.linux-iscsi.ip-10-0-1-10.x8664:sn.a3776832068c -lEnable the
iscsidservice to permit connection upon reboot:systemctl enable iscsid- Resolve disk encryption.
Review the contents of
/etc/crypttaband/etc/fstab:cat /etc/crypttabcat /etc/fstabAttempt to manually open the volume using the key referenced in
/etc/crypttab:cryptsetup luksOpen /dev/mapper/vg_1-lv_1 luks-vg_1-lv_1 --key-file /root/passphrase.keyView the volume key slots:
cryptsetup luksDump /dev/mapper/vg_1-lv_1Restore the LUKS header:
cryptsetup luksHeaderRestore /dev/mapper/vg_1-lv_1 --header-backup-file /root/vg_1-lv_1.headerOpen the volume manually:
cryptsetup luksOpen /dev/mapper/vg_1-lv_1 luks-vg_1-lv_1 --key-file /root/passphrase.keyView the entries in
/dev/mapper:ll /dev/mapperAttempt to mount
/storage:mount /storageView the file system label:
blkidThe volume appears to be a swap format, however the entry in
/etc/fstabsuggests it’s an XFS file system. Repair the file system:xfs_repair /dev/mapper/luks-vg_1-lv_1Mount
/storage:mount /storageView the contents of
/storage:ll /storage
