I just noticed a couple of really nasty things about the open-iscsi initiator.. If both systems is running, everything is fine. BUT... If the target goes down, or there's a cable/connection disruption, the initiator system hangs dead hard. Nothing except a hardware reset will wake it up.. No matter if the connection is restored, the system is still dead in the water. Then, if I set the open-iscsi initiator client to automatically connect to the target at system startup, I have an entry in fstab as well, the boot process is kindof out of sync, the file system check is made before the session to the target is established, and of course it fails. Also, the session didn't auto-connect, I had to login to the target manually, mount the volume, dismount it and then run xfs_check, and lastly mount it again.. To me, the natural way would be to establish the session early, then check the file system and lastly mount it as part of the boot process. Anders Norrbring Norrbring Consulting