Hello from Gregg C Levine normally with Jedi Knight Computers I am inclined to agree with Scott on that problem, except for one issue. The system does have a sense of humor. After all take into account the different architecture types found inside the kernel sources? The humor idea that he is thinking of, is that of slapstick. Given the environment where penguins live, well most of them, this is an appropriate stance. But when it comes to distribution types, I chose an oddball variant which has one thing going for it. It is almost foolproof to install. Slackware is that one. ------------------- Gregg C Levine [EMAIL PROTECTED] ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke."� Obi-Wan Kenobi (This company dedicates this E-Mail to General Obi-Wan Kenobi ) (This company dedicates this E-Mail to Master Yoda )
> -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED]] On Behalf Of > Ledbetter, Scott E > Sent: Friday, December 21, 2001 11:17 AM > To: [EMAIL PROTECTED] > Subject: Re: Dasd error with Suse 7.0 > > Bytes 22 and 23 have X'6709', which from an SVA or RVA translates to this: > > Subsystem time-of-day offload; used to correlate the host's > time-stamp on error log entries, and the subsystem's > time-stamp on failure report log entries. The sense data > was > reported on Cluster 0, Chan J (Chan 9, Chan 0x9). > > > > Bytes 22 and 23 of sense data have what STK labels the FSC or fault symptom > code. You could see anywhere from 6700->672F in bytes 22 and 23 for this > environmental offload. > > As an exception class 6, the driver needs to accept this as environmental > data. > > I believe on OS/390 this just causes a LOGREC entry to be made. However, > the S390 Linux DASD driver has no sense of humor about this. > > Scott Ledbetter > StorageTek > > > > > > -----Original Message----- > From: Steve Bui [mailto:[EMAIL PROTECTED]] > Sent: December 20, 2001 5:10 PM > To: [EMAIL PROTECTED] > Subject: Dasd error with Suse 7.0 > > > We're running Suse linux 7.0 on a 7060-H70 lpar and every day at midnight, > cron runs a command (installation default) and caused i/o error on our disk > pack: > "/USR/SBIN/CRON[1194]: (root) CMD ( rm -f > /var/spool/cron/lastrun/cron.daily)" > "/USR/SBIN/CRON[1197]: (root) CMD ( test -x > /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh > daily &)" > "kernel: dasd(eckd):device 40F0 on irq 2876: I/O status report:" > "kernel: dasd(eckd):in req: 07e78430 CS: 0x00 DS: 0x02" > "kernel: dasd(eckd):Failing CCW: 07e784c8" > "kernel: dasd(eckd):Sense: 0:0x00 1:0x00 2:0x06 3:0x00 4:0xf0 5:0x60 > 6:0x41 7:0x00" > "kernel: dasd(eckd):Sense: 8:0x00 9:0x00 10:0x00 11:0x01 12:0x59 13:0x77 > 14:0x00 15:0x10" > "kernel: dasd(eckd):Sense: 16:0x42 17:0x00 18:0x08 19:0x14 20:0x00 21:0x15 > 22:0x67 23:0x09" > "kernel: dasd(eckd):Sense: 24:0x04 25:0x10 26:0x4e 27:0x00 28:0x00 29:0x00 > 30:0x00 31:0x00" > "kernel: dasd(eckd):32 Byte: Format: 1 Exception class 6" > "kernel: dasd: devno 0x40F0 on subchannel 2876 = /dev/dasdb (94:4) > postprocessing successful error recovery action using 00072fb0" > We use 2 3390-3 disks on a SVA 9393 and the packs were formatted with > DASDFMT. The SVA itself does not report any error. Could someone help with > the error? Thanks much. > > ____________ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > Steve Bui , IRIS - IBM Systems Support Mgr. > Phone(480) 965-3070 / fax(480) 965-6317 >
