Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.sys.ibm.ps2.hardware    |    Discussing IBM PS/2 hardware    |    42,985 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 41,600 of 42,985    |
|    Pertti Helander to All    |
|    Re: Decoding SCSI error [got me a re-edj    |
|    30 Mar 23 07:18:16    |
      From: pertti.helander@pp.nic.fi              maanantai 27. maaliskuuta 2023 klo 17.07.06 UTC+3 Louis Ohland kirjoitti:       > Since we're past the frantic part, I wendt back to rightly dividing one       > of your SCSI errors.       >       > RDDDPL QEET       > 0208600U 5A6J       >       > Leading zero, "208" Unknown device type [not a good sign!], "6" SCSI ID       > 6, "0" LUN 0 [duh!], "U" unknown capacity [not good].       >       > QEET - Q = 0-8 SCSI POST codes, Q = 9 Adv Diags HD error code       >       > 5A6J       >       > Error codes (EE) with Q = 4 or 5 may be reported that are not listed       > here or can actually have a definition other than that given, depending       > on the device. So, not finding "A6" is quite possumble.       >       > So, if I understand, "5" does refer to the additional sense byte, but       > "A6" is not listed, so what that is, dunno. The Test code is given       >       > 5 - Additional sense byte (byte 12) of sense information from device       > A6 - Not listed       > J - Device not ready (initial unit attention clearing)       >       > So... the system DOES see the drive at ID6, but it can't tell what it       > is, it is throwing a "Device not ready".       >       > My furtive efforts would be to jumper it to start up as soon as power is       > applied. But autospin might not fix "initial unit attention clearing"       >       > Pertti Helander wrote:       > > 0208600U 5A6J       I jumpered my IBM DCAS-32160 2100MB as SCSI ID 6 and termination enabled.       Booting with refdisk in FDD after some CPs fdd stars to read refdisk but stops       and I got error I9990010 and 9557 starts boot again and same chain happens       over and over.       Because my hdd was formatted when I bought it there was no IML partition       and 9557 tries to load IML from FDD but fails and gives this I9990010 error.       No other error messages I got now.       Whal shall I do?              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca