SCSI disk errors in dmesg

Madhusudan Katti yellowdog-general@lists.terrasoftsolutions.com
Thu Jun 19 01:34:01 2003


Hi Bruce,

OK. I have set the appropriate jumper pin to Force Single Ended Mode, as
far as I can tell. I also notice that the Drive already had two other
jumpers set: Auto Start on; and Disable Sync Negotiation. I did not
touch these for this test.

Drive boots up ok, and here's what the tail end of dmesg has to say
after I log in:

SCSI disk error : host 1 channel 0 id 0 lun 0 return code = 8000000
Current sd08:06: sense key Aborted Command
 I/O error: dev 08:06, sector 27588576
SCSI disk error : host 1 channel 0 id 0 lun 0 return code = 8000002
Current sd08:06: sense key None
 I/O error: dev 08:06, sector 9735104
i2c-core.o: i2c core module
dmasound_pmac: Awacs/Screamer Codec Mfct: 1 Rev 2
PowerMac AWACS rev 2  DMA sound driver rev 016 installed
Core driver edition 01.06 : PowerMac Built-in Sound driver edition 00.07
Write will use    4 fragments of   32768 bytes as default
Read  will use    4 fragments of   32768 bytes as default
SCSI disk error : host 1 channel 0 id 0 lun 0 return code = 8000002
Current sd08:06: sense key None
 I/O error: dev 08:06, sector 6960872
SCSI disk error : host 1 channel 0 id 0 lun 0 return code = 8000000
Current sd08:06: sense key Aborted Command
 I/O error: dev 08:06, sector 5904832

So that sense key error is apparently still there. Any other ideas?
Before I start playing with other jumper settings on a trial and error
basis?

thanks,

Madhu

On Wed, 2003-06-18 at 12:22, bruce woller wrote:
> Madhu:
> 
> I can not find an IBM drive with DXHS model type on the net.  There is
> an Ultrastar 18XP listed at http://www.hgst.com/hdd/prod/9lp18xp.htm
> that could be your drive.  The ANSI revision level:03 implies that
> this 
> drive is capable of Low Voltage Differential (LVD) interface
> operation. 
>   The hgst web site indicates that this drive can run in either LVD or
> SIngle Ended mode.  The 8500 SCSI controller is probably a Single
> Ended 
> (SCSI Rev:02) controller.  Try checking the jumper settings for your 
> drive model to insure that "force Single Ended" operation jumper is
> set.
> 
> Regards,
> Bruce
> On Wednesday, June 18, 2003, at 10:52  AM, Madhusudan Katti wrote:
> 
> > (I'm reposting this to the list - didn't notice yesterday
> > that the reply-to was set to sender, not the list)
> >
> > Here's what's in /proc/scsi/scsi
> >
> > Attached devices:
> > Host: scsi1 Channel: 00 Id: 00 Lun: 00
> >   Vendor: IBM      Model: DXHS             Rev: 0430
> >   Type:   Direct-Access                    ANSI SCSI revision: 03
> > Host: scsi1 Channel: 00 Id: 02 Lun: 00
> >   Vendor: QUANTUM  Model: FIREBALL SE4.3S  Rev: PJ0A
> >   Type:   Direct-Access                    ANSI SCSI revision: 02
> > Host: scsi1 Channel: 00 Id: 03 Lun: 00
> >   Vendor: MATSHITA Model: CD-ROM CR-8005A  Rev: 4.0i
> >   Type:   CD-ROM                           ANSI SCSI revision: 02
> >
> > A minor error in my previous message - the smaller of my two hard 
> > drives
> > is 4.3 GB not 5.4. Since the errors in dmesg all point to ID 0, with
> > different sector numbers, I'm wondering if there is a problem with
> some
> > sectors on that drive.
> >
> > The SCSI controller is whatever is on the 8500 logic board. I don't
> see
> > any id conflicts, and am pretty sure the internal scsi chain is
> > terminated.
> >
> > Let me know if you need any other info, although I won't be at this
> > machine for the rest of the day.
> >
> > thanks,
> > Madhu
> >
> > On Tue, 2003-06-17 at 09:00, Brian Waite wrote:
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> What does /proc/scsi/scsi look like?
> >> What devices are on your bus(es)
> >> What SCSI controller do you have.
> >> Are you sure you are terminated corectly?
> >> It is hard to say right now but a little more infomation could
> help.
> >> Thanks
> >> Brian
> >> On Tuesday 17 June 2003 11:49 am, Madhusudan Katti wrote:
> >>> Hi,
> >>>
> >>> I just noticed several SCSI error messages during the boot
> process,
> >>> although everything seems to work fine otherwise. dmesg shows
> about
> >> half
> >>> a dozen entries like the following, at several points during the
> >> boot
> >>> process:
> >>>
> >>> SCSI disk error : host 1 channel 0 id 0 lun 0 return code =
> 8000000
> >>> Current sd08:06: sense key Aborted Command
> >>>  I/O error: dev 08:06, sector 5620744
> >>>
> >>> Every instance is identical to the above except for the sector
> >> number,
> >>> and in one case it says "sense key none" instead of "aborded
> >> command".
> >>> They all refer to the same dev, one of two internal ones in this
> >> system.
> >>>
> >>> Any ideas what this means? How worried should I be about the hard
> >> drive?
> >>>
> >>> BTW, my system is a G3 upgraded PMac 8500, 360 MB RAM, with two
> >> internal
> >>> scsi drives, 18GB and 5.4GB.
> >>>
> >>> thanks,
> >>> Madhu
> >>>
> >>> _______________________________________________
> >>> yellowdog-general mailing list
> >>> yellowdog-general@lists.terrasoftsolutions.com
> >>>
> >>
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
> >> -----BEGIN PGP SIGNATURE-----
> >> Version: GnuPG v1.0.7 (GNU/Linux)
> >>
> >> iD8DBQE+7zsDmxLCz0u+Ko8RAu75AKC2Vva7Zd9Ip5o6aVPXYwzh2iL9XwCgkDmu
> >> B6JUcYEvxLvU61d4UHdnXCQ=
> >> =/HLJ
> >> -----END PGP SIGNATURE-----
> >>
> >
> > _______________________________________________
> > yellowdog-general mailing list
> > yellowdog-general@lists.terrasoftsolutions.com
> >
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
> >
> 
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general@lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
>