I'm taking the RHCE on Monday and I am still having issues with this lab. No matter what I do or how I configure this iscsi initiator, it hangs on rebot. I don't get it. If I login to the target and run mksf.xsf on the iscsi disk I can see it presented via #blkid. So, without mounting it or even putting anything in the fstab I reboot just to test. And every isingle time it hangs right after the message "Storage is finalized". I'm really worried about this happening on the exam and casuing me to fail. Any help would be greatly appreciated.
Since I don't seem to be able to copy and paste from the console, here is my target config:
Like I said, I can login to the target just fine and mount the disk. So everything seems ok with my configuration. It just locks up when shutting down. So if I hard power it off then power it back on it works fine.
I thought you had this solved, restart iscsid after you made all the changes. I will assume here that everything went well on client with iscsiadm -m discovery | node | seesion, all properly recognized, iqn name of client matches the iqn you listed on the server with ACL, portal direcitve matches client's IP and the only other possible problem is on the client, server is configured as it should be. Beside not restarting iscsid, another possible issue is erroneous entry in /etc/fstab if you mistyped the UUID, assuming/hoping you are using UUID to mount the remote block storage on local mount point.
I'll be sitting RHCE in less than two weeks, cold feet and all... :-(
Thanks for the quick reply! Yes I thought I had this resolved as well but I found that what happens is that after logging in and mounting the drive it ALWAYS hangs on first reboot. After that it works intermittently. I've found that when mounting the iscsi disk the iscsi service starts up as it should (evident by systemctl status iscsid). So, I restart the service just to make sure everything is connected and then reboot. But it doesn't seem to matter. The initiator will hang on shutdown 100% of the time on the first reboot after. So I then have to hard power it off and back on. It boots up fine and even mounts the disk appropriately. After that first reboot I can typically reboot freely w/o issue. I'm really at a loss here and all I can think of is that it's a bug.
I agree it is really intriguing. Is iscsiadm enabled? Firewall on client lets traffic on default iscsi port 3260 tcp go through? I know it is a set of dumb questions, but it seems the set of problems is unique...
Yup, firewall on the target is open on port 3260. The services iscsi and iscsid are enabled on the initiator. I flat out copy and paste the commands from the lab and it works but I still get the hang on shutdown. The only other dicrepency I can see is that in the video presented under "Accessing iSCSI Storage", the presenter creates the gdisk partition on the initiator after logging in whereas in the lab they have you create the partition on the target side. Not sure if that matters or not.
It's just odd that literally everything works fine except for the hang on shutdown. I can discover, login, mount, write files, etc... I just can't reboot cleanly.
I don't have access to those videos, but it is kind of surprising to see creating a partition on the initiator in order to mount remote block storage- it kind of beats the purpose of having remote block storage.
This lab just flat out does not work. I don't get it :/
I've tried everything. The system either hangs on shutdown or boots up complaining about failed dependencies and it loses it's iscsi config causing me to have to log back in. I really hope that this is just a big that has been addressed in the version of RHEL used in the exam.