Date: Mon, 7 Jun 1999 16:10:32 -0400 (EDT) From: steven <stevensl@mindspring.net> To: scsi@freebsd.org Subject: Invalid Pack w/ CAM (SCSI) Message-ID: <Pine.BSF.4.05.9906071601300.806-100000@freelove.mindspring.net>
next in thread | raw e-mail | index | archive | help
I've seen the threads for awhile, i've experienced this since i went to 3.x, reguardless of version, except the pre-releases which didn't. It only happens with my secondary drive (seagate hawk 4.2 gig) and never my primary drive. I've been inclined to believe the source of the problem is the drives power requirements since it is a power hog. When i get the invalid pack error i can hear the drive spindown, then it usually recovers and spins back up but the os never seems to recover. Eventually it locks up. For a fluke i did some testing. I got the error twice in a row on a cold startup and then a warm reboot. Afterwards everything was fine for about a week. Cold startups, reboots etc. Nothing could shake it. Then it starts up again for no reason. I was running fsck on the drive after rebooting and saw this in the logs during the fsck... Jun 7 15:54:00 pangaea /kernel: (da1:ahc0:0:4:0): WRITE(06). CDB: a e 66 2b 2 0 Jun 7 15:54:00 pangaea /kernel: (da1:ahc0:0:4:0): WRITE(06). CDB: a e 66 2b 2 0 Jun 7 15:54:00 pangaea /kernel: (da1:ahc0:0:4:0): RECOVERED ERROR info:e662b asc:3,0 Jun 7 15:54:00 pangaea /kernel: (da1:ahc0:0:4:0): RECOVERED ERROR info:e662b asc:3,0 Jun 7 15:54:00 pangaea /kernel: (da1:ahc0:0:4:0): Peripheral device write fault field replaceable unit: 9 sks:80,1 Jun 7 15:54:00 pangaea /kernel: (da1:ahc0:0:4:0): Peripheral device write fault field replaceable unit: 9 sks:80,1 Jun 7 15:56:43 pangaea /kernel: (da1:ahc0:0:4:0): SCB 0x3d - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xc Jun 7 15:56:43 pangaea /kernel: (da1:ahc0:0:4:0): SCB 0x3d - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xc Jun 7 15:56:44 pangaea /kernel: (da1:ahc0:0:4:0): Queuing a BDR SCB Jun 7 15:56:44 pangaea /kernel: (da1:ahc0:0:4:0): Queuing a BDR SCB Jun 7 15:56:44 pangaea /kernel: (da1:ahc0:0:4:0): Bus Device Reset Message Sent Jun 7 15:56:44 pangaea /kernel: (da1:ahc0:0:4:0): Bus Device Reset Message Sent Jun 7 15:56:44 pangaea /kernel: (da1:ahc0:0:4:0): no longer in timeout, status = 353 Jun 7 15:56:44 pangaea /kernel: (da1:ahc0:0:4:0): no longer in timeout, status = 353 Jun 7 15:56:44 pangaea /kernel: Unexpected busfree. LASTPHASE == 0xa0 Jun 7 15:56:44 pangaea /kernel: Unexpected busfree. LASTPHASE == 0xa0 Jun 7 15:56:44 pangaea /kernel: SEQADDR == 0x151 Jun 7 15:56:44 pangaea /kernel: SEQADDR == 0x151 is this of any help? anyone got any ideas on how to fix this? I've gone thru 2 powersupplies thinking thats the culprit on the drive timing out. I've replaced the cables, the terminations etc. I've got 3 devices in the chain and this is in the middle. I might put another drive in the middle to see if it happens again. ~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~ Steven S. linux.com freebsd.org gnustep.org stevensl@mindspring.net 403forbidden.net ~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~'~ 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: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9906071601300.806-100000>