> -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of Martha McConaghy > Sent: Thursday, December 28, 2006 1:52 PM > To: [email protected] > Subject: Stuck between a rock and a really hard place... (fwd) > > > We just got a z9 and I've been given a whole 2 weeks to move > all of our > production services from a z900 to the new machine. (I'm such a lucky > girl......blah!) > > I'm doing what testing I can during the holidays and found > that some of > our older Linux servers are having serious issues with the > z9. All are > running under z/VM 5.2.0 so I know that isn't the problem. They are > running kernel 2.4.17 and were "hand built" by a former > employee and haven't > had any patches put on them recently, so I know they are out of date. > > The system appears to be unable to read its disks. It knows that the > disks are there, but cannot get to the data. Here are some > of the messages > I see: > > Kernel command line: root=/dev/dasda1 ro initrd= noinitrd > dasd=195-19F > Highest subchannel number detected (hex) : 0018 > SPID - Device 0195 on Subchannel 000D became 'not operational' > SPID - Device 0191 on Subchannel 000E became 'not operational' > SPID - Device 0190 on Subchannel 0012 became 'not operational' > SPID - Device 019E on Subchannel 0013 became 'not operational' > SPID - Device 019D on Subchannel 0014 became 'not operational' > SPID - Device 019F on Subchannel 0015 became 'not operational' > > Finally, it gives up trying to boot: > > VFS: Cannot open root device "dasda1" or 5e:01 > Please append a correct "root=" boot option > Kernel panic: VFS: Unable to mount root fs on 5e:01 > HCPGIR450W CP entered; disabled wait PSW 000A0000 802741C0 > > I suspect that the drivers don't like something about the z9, > but don't know > what. Is there anything we can do besides build new servers for them? > Help! We go production next weekend, so I'm desperate! > > Martha
Looks like something about SPID is mentioned on: http://www-128.ibm.com/developerworks/linux/linux390/current2_4_17-may20 02.html It even matches your kernel level, 2.4.17, the May 2002 stream of maintenance. The page has a link to download the maintenance. <quote> Description: Common io layer: path grouping. Symptom: Linux detects an interface control check during SetPGID. Problem: The data address in the SPID ccw was incorrect, causing zero data to be sent. Solution: Make sure the data address is always correct. </quote> -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. ---------------------------------------------------------------------- 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
