Our last successful patching cycle was to level 3.0.42 with no issues with our zfcp devices. Since we experienced the /dev/urandom issue we upgraded only the kernel to level 3.0.58-0.6.6.1.5402.0.PTF to resolve the issue. Now we are going through a complete patch cycle with an upgrade to version 3.0.74 of kernel. We use smt and basically upgrade all the patches to a set date that we mirror from full to testing. Now after patching and reboot, the servers come up with no LUNs attached (we have the root file system on eckd, but program and data files are on LUNs). If I add them back in with zfcp_disk_configure that seems to resolve the issue and the servers reboot with no issues. Any ideas what may be causing this?
Chris Will The information contained in this communication is highly confidential and is intended solely for the use of the individual(s) to whom this communication is directed. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information is prohibited. Please notify the sender, by electronic mail or telephone, of any unintended receipt and delete the original message without making any copies. Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are nonprofit corporations and independent licensees of the Blue Cross and Blue Shield Association. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
