Hello Peter, As requested, I issued a cat /proc/s390dbf/cip_msg/sprintf > cio_msg.txt (/tmp doesn't exist (yet)).
When I cat cio_msg.txt | more, I see the following: 00 01163006499:983853 0 - 00 00263b0e Detected device 0CF0 on subchannel 03AE - PIM = FF, PAM = FF, POM = FF 0CF0 - 0CFF are mi DASD drives. This is a good sign. Later in the file, I find: 00 01163006499:996152 0 - 00 0026b7ae ccw_device_path_notoper(03ae) - path(s) 8 0 are not operational 00 01163006499:996156 2 - 00 0026ab14 SenseID : path 80 for device 0cf0 on subc hannel 03ae is 'not operational' This is not a good sign. The rest of the cio_msg.txt file is basically various versions of the above two messages for different paths for all the DASD. Thanks, Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 [EMAIL PROTECTED] >>> [EMAIL PROTECTED] 11/8/2006 9:27 AM >>> David Stuart <[EMAIL PROTECTED]> wrote on 08.11.2006 17:38:56: > When I issue the ls command you suggested, all I see are the addresses > of my OSA card, and a couple CTC's that are defined in the IOCP. > > No DASD... > > And I can't find any problems in my IOCP configuration. The fact that the DASD device numbers don't show up in the /sys directory indicates that Linux does not know about them at all. Unless you explicitly told Linux to leave those devices alone by specifying the 'cio_ignore=' parameter on the kernel command line (can be checked by issuing 'cat /proc/cmdline'), this is a strong indication of a configuration mismatch outside of Linux (LPAR, storage server, etc). Unfortunately my experience with IOCP/IOCDS and storage server configuration is rather limited. Maybe someone on the list with more knowledge in these areas can help you out. Regards, Peter Oberparleiter P.S.: There's one more approach to gathering information about the source of the problem you are seeing via Linux: please perform the following command and send me the resulting file /tmp/cio_msg.txt off-list. cat /proc/s390dbf/cio_msg/sprintf > /tmp/cio_msg.txt -- Peter Oberparleiter Linux on zSeries Development IBM Development Lab, Boeblingen/Germany ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
