Uncaught Anaconda traceback with AIC-7xxx and SCSI CD upgrade RH 7.2 gold CD's Adaptec PCI controller, relatively recent SCSI Read/burner Will attach traceback in a moment
Created attachment 37604 [details] anaconda traceback of uncaught exception
If you need further details (lspci, bios versions, etc), please remind me that this was from my old ws6
Are you sure the cd is good? Anaconda is just trying to import a Python module that it needs, but it can't find it.
After filing this, I used the same physical CD set for three other installs ... part of my install procedure is run my audit files, which run a rpm -Va and no errors exist in those systems ... dunno. The reason I mentioned the AIC-7xxx/SCSI CD combo is that the retry logic on that SCSI driver was a bit of an issue late in the RH 7.2 Beta cycle
There are lots of sense errors in the log - is it possible the CD drive in this system is having problems with the install media?
Possible but quite unlikey -- it is a recently bought new Mashshusita <sp?> SCSI CD - RW ...Irrespective of the drive issue, should not all return codes be tested and directed to a handler ('caught', as the saying goes)?
Perhaps, although if read errors keep python 'import' statements from working you're already in bad shape. I have not seen this particular failure mode before, but based on other similar exceptions it is almost always due to a problem reading a CD. Can you try a NFS install from another machine, for example?
Any information on if this machine can install via other methods?
Sorry about delay -- have been briefly unavailable. ------------------ there are ZARRO media errors or retries during my testing sesions -- It looks as though the AIC-7xxx SCSI driver has too many pending requests to the CD, and it is locking up there. -- Attachment in a moment.
Created attachment 54045 [details] dmesg-scsi-HD-freeze.txt - last line -- is this showing SCSI command overflow?
ugh, this is an original Pentium? These are the SCSI errors we're talking about: <4>scsi0: ERROR on channel 0, id 5, lun 0, CDB: 0x28 00 00 04 5a 85 00 00 06 00 <4>Info fld=0x45a85, Current sd0b:00: sns = f0 3 <4>ASC= 2 ASCQ= 0 <4>Raw sense data:0xf0 0x00 0x03 0x00 0x04 0x5a 0x85 0x0a 0x00 0x00 0x00 0x00 0x02 0x00 0x00 0x00 0x00 0x00 <4> I/O error: dev 0b:00, sector 1141268 <4>scsi0: ERROR on channel 0, id 5, lun 0, CDB: 0x28 00 00 04 5a 86 00 00 05 00 <4>Info fld=0x45a86, Current sd0b:00: sns = f0 3 <4>ASC= 2 ASCQ= 0 <4>Raw sense data:0xf0 0x00 0x03 0x00 0x04 0x5a 0x86 0x0a 0x00 0x00 0x00 0x00 0x02 0x00 0x00 0x00 0x00 0x00 <4> I/O error: dev 0b:00, sector 1141272 <4>Error -3 while decompressing! <4>c0441860(-1944672)->c688d000(4096) <4>Error -3 while decompressing! <4>c04410f4(-1942762)->c7e53000(4096) <4>Error -3 while decompressing! <4>c0266c0a(-10)->c7e5b000(4096)
Unit is a dual processor, matched lot (consequetive serial numbers) P-150, on a Tyan D-1563 -- the D indicates dual processors I have new SCSI errors trying to burn a CD -- will attach in a moment This is a long time testing unit which shows aic-7xxx SCSI driver errors well, it seems
Created attachment 54085 [details] SCSI errors trying to burn CD - dmesg, lspci and more
My unit: oldpokey updates for lilo.conf produced a file which will not boot for either SMP or UP I will try to hook up a serial cable to trach the errors and file separately.
device 0:0:0 is the hard drive, on the internal UW channel; CD drive 0:5:0 is on the SCSI-II channel, with active termination after it on the chain, and the CD drive strapped for external termination.
These are the SCSI errors we're talking about: <4>scsi0: ERROR on channel 0, id 5, lun 0, CDB: 0x28 00 00 04 5a 85 00 00 06 00 <4>Info fld=0x45a85, Current sd0b:00: sns = f0 3 <4>ASC= 2 ASCQ= 0 <4>Raw sense data:0xf0 0x00 0x03 0x00 0x04 0x5a 0x85 0x0a 0x00 0x00 0x00 0x00 0x02 0x00 0x00 0x00 0x00 0x00 <4> I/O error: dev 0b:00, sector 1141268 These aren't driver problems. These are the CD drive telling the machine that it can't read the CD. That simple, media issue (the media may be fine on other machines, but for some reason this particular drive can't read this media). I'll look at the errors during burning next....
The cd writing errors are also valid device errors. In general, any time you have an error that reports a CHECK_CONDITION or REQUEST_SENSE return value, it means that the driver and the device are sucessfully talking (which is the limit of the driver's responsibility BTW), but that the device is having problems of it's own for whatever reason. In the case of the burning, I saw two device reported errors of concern. One was a complaint that it could write track 0 of the media, so a burning error. The second was a complaint that it didn't like the raw SCSI command that cdrecord sent to it (the invalid command sense code). Both of those indicate that the driver is working fine and that the problem lies elsewhere (either in media or an imcompatibility between the particular internal raw SCSI command driver in cdrecord and the Matshita device firmware). Closing as NOTABUG.