I noticed a couple recent issues about the iscsi initiator hanging on boot when a target is not accessible. In the past these test cases were heavily covered and should still be performed on a normal basis unless things have changed.
In the past problems had been discover in this area. If you are running older versions of Solaris 10, like Update 1, make sure you get the latest Sun solve patches. A number of fixes occured in this area post update 1. (The next largest cause of slow iscsi boots when devices are gone is due to stale /dev links. If your adding and removing devices you don't expect to return its a good idea to run devfsadm -C to clean up those old device links. This will speed up lots of aspects of solaris boot process.) If all else fails you can try the below workaround to get your system to boot. (Someone might have to verify this syntax as I don't have a Solaris system right now.) boot -m milestone=none - This should get Solaris to boot and the iscsi initiator will not be loaded. The problem is the local /etc file system is still read only so you can't do to much yet. svcs -a | grep file svcadm enable <service> - This should report a number of SMF file system services. You need to enable minimal, local, and utils/bin (can't remember this last one for sure.) - At this point you can play with /etc cd /etc/iscsi append .bad to all the files in this directory. reboot - at this point the system will reboot with the iscsi initiator reset. If you ever need you can rename iscsi...bad files back to their normal name and reboot to reproduce the problem. This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
