From owner-freebsd-alpha@FreeBSD.ORG Mon Apr 26 04:37:52 2004 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80E3B16A4CE for ; Mon, 26 Apr 2004 04:37:52 -0700 (PDT) Received: from sassie.net (mail.sassie.net [64.56.122.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD9A243D2D for ; Mon, 26 Apr 2004 04:37:51 -0700 (PDT) (envelope-from mike@sassie.net) Received: from mike ([192.168.10.106]) by sassie.net with MailEnable ESMTP; Mon, 26 Apr 2004 07:37:50 -0400 From: "M Gollihue" To: Date: Mon, 26 Apr 2004 07:37:49 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <5EEBE9C3C61D1142994C6B620C51E8470CC842@ip-64-32-234-4.dsl.iad.megapath.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal Subject: RE: odd 4.9 scsi problem X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Apr 2004 11:37:52 -0000 Hello! I am a newbie on the list, and have only just recently started playing with Alphas and BSD. To me, this sounds like it could be a termination problem. Make sure that you are using the proper terminators ... active terminators with termpower turned on somewhere. Just a thunk, since your HDD channels seem to work fine. Are you sure the firmware on the DAT has not been corrupted? The changing caps is just a bit too wierd! Could be that it isn't corrupt ... just that it needs updated to be compatible with the system. This is reminicient of waaaayyyyy back in the day, the old Macintosh IIfx. I remember I worked with a few ... the external scsi chain had to have passive terminators at the beginning or in the middle for it to work right. Putting them at the end was like running with none (Sometimes having none worked ... with NO drive terminators turned on!!). Bizarre problems like this popped up. Of course, with today's active termination stuff like that should be a thing of the past. Anyhow, just my two cents. Michael Gollihue -----Original Message----- From: owner-freebsd-alpha@freebsd.org [mailto:owner-freebsd-alpha@freebsd.org]On Behalf Of Richard J. Valenta Sent: Monday, 26 April 2004 1:35 am To: freebsd-alpha@freebsd.org; freebsd-questions@freebsd.org Subject: odd 4.9 scsi problem I have an odd scsi problem - this is a DS20 with 3 Qlogic scsi cards, 0 has only the external TZ89 DLT drive, 1 has the hard drives, 2 has the internal DAT (TLZ,T1Z10)and the cdrom. If I power down all devices completely including the server (not just reboot) and then power everything up, this is the result: worx# camcontrol devlist at scbus0 target 3 lun 0 (pass0,sa0) at scbus1 target 0 lun 0 (pass1,da0) at scbus1 target 1 lun 0 (pass2,da1) at scbus1 target 2 lun 0 (pass3,da2) at scbus2 target 4 lun 0 (pass4,sa1) at scbus2 target 5 lun 0 (pass5,cd0) But an odd thing happens to the DAT after I manually reset and rescan - it changes names, worx# camcontrol reset 2 Reset of bus 2 was successful worx# camcontrol rescan 2 Re-scan of bus 2 was successful worx# camcontrol devlist at scbus0 target 3 lun 0 (pass0,sa0) at scbus1 target 0 lun 0 (pass1,da0) at scbus1 target 1 lun 0 (pass2,da1) at scbus1 target 2 lun 0 (pass3,da2) at scbus2 target 4 lun 0 (sa1,pass4) at scbus2 target 5 lun 0 (pass5,cd0) But this isn't the main problem - I just discovered this playing around after the main problem - when I try to use sa0 (the DLT), I often get an error like below: archive/backup/images/Videos/rich.mov tar (child): /dev/sa0: Wrote only 0 of 10240 bytes tar (child): Error is not recoverable: exiting now Broken pipe worx# when I try to perform the backup again it hangs and the tail of /var/log/messages shows: Apr 25 18:07:11 worx /kernel: (sa0:isp0:0:3:0): failed to write terminating filemark(s) Apr 25 18:07:11 worx /kernel: (sa0:isp0:0:3:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM command to clear this state. And when I try to do so: worx# mt -f /dev/sa0 rewind mt: /dev/sa0: Device not configured and when I reboot... worx# camcontrol devlist at scbus1 target 0 lun 0 (pass0,da0) at scbus1 target 1 lun 0 (pass1,da1) at scbus1 target 2 lun 0 (pass2,da2) at scbus2 target 4 lun 0 (pass3,sa0) at scbus2 target 5 lun 0 (pass4,cd0) Odd change of CAPS for the DAT, and the DLT has disappeared... System info: single 500mhz alpha processor DS20, with 3 Qlogic scsi cards and a brand new kernel, which only includes Qlogic cards in its config, and all scsi device types as well. I had 5.0 on this machine and ran backups fine. Then changed to 4.9 trying to get sound to work, that was unsuccessful, and now I have this tape problem, I don't know if they are related. At times, if I simply let the machine sit, the DLT will just fall off the chain and a rescan/reset will not bring it back. At the same time the other tape gets renamed. I'd like to blame a card to the tape drive, but I've moved things around and had the same problems, and would think that if the DLT was fried it just wouldn't work - not work some of the time. Love to hear anyone's opinions or thoughts on repairing this. Richard _______________________________________________ freebsd-alpha@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-alpha To unsubscribe, send any mail to "freebsd-alpha-unsubscribe@freebsd.org"