schachinger
Mission Specialist
Mission Specialist
  • 4,741 Views

Client system shutdown hangs at "A stop job is running for /iscsidisk"?

Jump to solution

So I'm studying for the RHCE (EX300) and i'm on the iscsi lab in the rh254 course. Everything works as expected but after I mount the iscsi disk on the client and reboot to check persistence it just hangs indefinitely on shutdown saying 'a stop job is running on /iscsidisk" (the mount point). How do I prevent this?

FWIW here is my fstab entry

UUID=######   /iscsidisk   xfs   _netdev   0 2

 

Thanks!

Labels (1)
0 Kudos
1 Solution

Accepted Solutions
varelov
Flight Engineer Flight Engineer
Flight Engineer
  • 4,721 Views

So I went back to lab iSCSI and the hang happened to me too, on the client. I didn't restart iscsid on the client. I forgot to:

systemctl restart iscsid

... which was probably the reason I was presented the dracut screen at shutdown time.

I've labbed iSCSI few times and it was all going well, this time it didn't and that was the only thing I failed to do, so I'm thinking that'd be the cause of your problem too.

View solution in original post

2 Replies
varelov
Flight Engineer Flight Engineer
Flight Engineer
  • 4,728 Views

As an RHCE candidate myself, that is preparing on my own, I don't know what is in that particular lab and how much of an access does one have to the iSCSI target in that lab, as I don't have access to the official training material and associated online labs but have you tried mounting the remote resource via the mount command instead of going straight for /etc/fstab first? Any error messages during mount or umount?

What do you mean by "indefinite"? It may be a mandatory timeout of some service before shutdown too. You may have to poke /sys/block/sdx/device for the timeout setting for that remote block storage device, usually it is set to 30 seconds. Or the timeout of the iscsi service on the initiator.

0 Kudos
varelov
Flight Engineer Flight Engineer
Flight Engineer
  • 4,722 Views

So I went back to lab iSCSI and the hang happened to me too, on the client. I didn't restart iscsid on the client. I forgot to:

systemctl restart iscsid

... which was probably the reason I was presented the dracut screen at shutdown time.

I've labbed iSCSI few times and it was all going well, this time it didn't and that was the only thing I failed to do, so I'm thinking that'd be the cause of your problem too.

Join the discussion
You must log in to join this conversation.