Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 18 Jan 1999 20:04:58 +0100
From:      Bernd Walter <ticso@cicely.de>
To:        "Jeroen C. van Gelderen" <gelderen@mediaport.org>, freebsd-scsi@FreeBSD.ORG
Subject:   Re: Disk dying (Conner CFP and Tagged Queueing Probs)
Message-ID:  <19990118200458.29368@cicely.de>
In-Reply-To: <000301be4279$667e93c0$0d79eb0a@deskfix.local>; from Jeroen C. van Gelderen on Mon, Jan 18, 1999 at 01:27:58AM +0100
References:  <000301be4279$667e93c0$0d79eb0a@deskfix.local>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Mon, Jan 18, 1999 at 01:27:58AM +0100, Jeroen C. van Gelderen wrote:
> Hello,
> 
> Today I saw these messages scrolling over my screen. The last line worries
> me a bit. Is this likely an indicator of a failing disk? Or is there
> something else wrong?
> 
> Cheers,
> Jeroen
> 
> Jan 18 00:03:20 wit395301 /kernel: (da0:ahc0:0:0:0): tagged openings now 31
> Jan 18 00:05:19 wit395301 /kernel: (da0:ahc0:0:0:0): SCB 0xe - timed out
> while idle, LASTPHASE == 0x1, SEQADDR == 0x9
> Jan 18 00:05:20 wit395301 /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB
> Jan 18 00:05:20 wit395301 /kernel: (da0:ahc0:0:0:0): Bus Device Reset
> Message Sent
> Jan 18 00:05:20 wit395301 /kernel: (da0:ahc0:0:0:0): no longer in timeout,
> status = 353
> Jan 18 00:05:20 wit395301 /kernel: Unexpected busfree.  LASTPHASE == 0xa0
> Jan 18 00:05:20 wit395301 /kernel: SEQADDR == 0x14f
> Jan 18 00:06:17 wit395301 /kernel: (da0:ahc0:0:0:0): SCB 0x12 - timed out
> while idle, LASTPHASE == 0x1, SEQADDR == 0x9
> Jan 18 00:06:17 wit395301 /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB
> Jan 18 00:06:17 wit395301 /kernel: (da0:ahc0:0:0:0): Bus Device Reset
> Message Sent
> Jan 18 00:06:17 wit395301 /kernel: (da0:ahc0:0:0:0): no longer in timeout,
> status = 353
[...]
> Jan 18 00:14:17 wit395301 /kernel: Unexpected busfree.  LASTPHASE == 0xa0
> Jan 18 00:14:17 wit395301 /kernel: SEQADDR == 0x14f
> Jan 18 00:15:17 wit395301 /kernel: (da0:ahc0:0:0:0): SCB 0xc - timed out in
> message in phase, SEQADDR == 0x101
> Jan 18 00:15:17 wit395301 /kernel: (da0:ahc0:0:0:0): BDR message in message
> buffer
> Jan 18 00:15:18 wit395301 /kernel: (da0:ahc0:0:0:0): no longer in timeout,
> status = 34b
> Jan 18 00:15:18 wit395301 /kernel: ahc0: Bus Device Reset on A:0. 31 SCBs
> aborted
> Jan 18 00:15:18 wit395301 /kernel: /: got error 0 while accessing filesystem
> -------------
[...]
> pass1 at ahc0 bus 0 target 3 lun 0
> pass1: <MATSHITA CD-ROM CR-503 1.0f> Removable CD-ROM SCSI-2 device
> pass1: 3.300MB/s transfers
> da0 at ahc0 bus 0 target 0 lun 0
> da0: <CONNER CFP4207S  4.28GB 1524> Fixed Direct Access SCSI-2 device
> da0: 5.0MB/s transfers (5.0MHz, offset 15), Tagged Queueing Enabled
> da0: 4096MB (8388608 512 byte sectors: 255H 63S/T 522C)
> WARNING: / was not properly dismounted
> ffs_mountfs: superblock updated for soft updates
> ffs_mountfs: superblock updated for soft updates
> (da0:ahc0:0:0:0): tagged openings now 31
> 
Looks exactly the same like on my <CONNER CFP1080S 3939> I had mentioned in this list
earlier.
You should be very carefully with this problem it damaged me sometimes the fs on it.

With a quirk entry disabling tagged command queueing the drive is running without
any problems for several days.

Sound like there are more than just my drive broken.
Can someone please check and commit an entry?

I use the following in sys/cam/cam_xpt.c:
        {
                /* Broken tagged queuing drive */ 
                { T_DIRECT, SIP_MEDIA_FIXED, "CONNER", "CFP*", "*" },
                /*quirks*/0, /*mintags*/0, /*maxtags*/0
        },

Interestingly the following is already there:
        {
                /* Broken tagged queuing drive */ 
                { T_DIRECT, SIP_MEDIA_REMOVABLE, "CONNER", "CFP2107*", "*" },
                /*quirks*/0, /*mintags*/0, /*maxtags*/0
        },

Is his realy a removeable drive?
If yes it sounds as there might be some conflicts using both.

> --
> Jeroen C. van Gelderen -- gelderen@mediaport.org -- &[8-D}~<=
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-scsi" in the body of the message

-- 
  B.Walter


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?19990118200458.29368>