Re: scsi errors, how dangerous could it be?
On Sunday 01 December 2002 06:34 am, Alexey Chetroi wrote: Hello All, I have some messages in /var/log/syslog which attracted my attention. it about scsi errors which I don't fully understand: Dec 1 07:40:30 ial kernel: scsi0: PCI error Interrupt at seqaddr = 0x9 Dec 1 07:40:30 ial kernel: scsi0: Data Parity Error Detected during address or write data phase These message appear time to time. I've tried to google for this problem, but haven't figured anything, beside that: 1) problem exists :( 2) it also happens to bsd folks. snip Is this a problem? Bios setting disables IRQ for USB, but usb-uhci still uses it. Could USB be disabled without recompiling kernel? Motherboard is dual-pentium ready, but only one processor is installed. Should I use kernel-image-*-smp or not? Any help is apreciated. Thank you in advance. There is an issue with the MPS version setting in the BIOS. I had to change the default to get error free performance on mine. Its been awhile so I don't remember which MPS version to use now but a google on MPS SCSI will get you more info. If you never plan on getting that second processor you don't need an smp kernel, but the board rocks with 2 :) -- Greg Madden -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SCSI errors in xmcd (more info)
Oliver Elphick wrote: I am running xmcd with a Yamaha CD writer connected to an Adaptec 2940UW SCSI card. About twice a second throughout playing a CD I get these errors in the xterm from which I started xmcd: CD audio: SCSI command error on /dev/cdrom: Opcode=0x42 Status=0x1 Msg=0x0 Host=0x0 Driver=0x28 Key=0x5 Code=0x24 Qual=0x0 One crucial bit of information I missed is that xmcd cannot update the current track/position; presumably its request for this data is the command that is causing the error. -- Vote against SPAM: http://www.politik-digital.de/spam/ Oliver Elphick[EMAIL PROTECTED] Isle of Wight http://www.lfix.co.uk/oliver PGP key from public servers; key ID 32B8FAA1 Watch ye therefore, and pray always, that ye may be accounted worthy to escape all these things that shall come to pass, and to stand before the Son of man. Luke 21:36
Re: SCSI errors on Install
On Tue, 16 Feb 1999, Kent West wrote: At 04:02 PM 2/16/1999 -0500, Raymond A. Ingles wrote: On Tue, 16 Feb 1999, Kent West wrote: This is my first experience with SCSI, so I don't know where to begin. First things first: what's the exact model name and number of the SCSI card? You need to make sure it's properly supported by Linux. [...] Oh well, according to the Ctrl-A setup screen, it's an Adaptec AHA-2940 Ultra/Ultra W. Fair enough. Those should be supported, but the driver you're using was made without any support from Adaptec and had to be reverse-engineered. It may have some bugs. That being said, have you used these SCSI disks with this adapter before, with DOS or Windows? Adaptecs have a reputation for being very sensitive to cabling issues. If the cables aren't set up just right, they can get flaky. Especially if you're doing Ultra SCSI, you have to make sure that you've got active termination, and it's terminated in the right places. The SCSI-HOWTO is currently unmaintained (something I'm hoping will be remdied soon) but still useful. Take a look at: ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/unmaintained/SCSI-HOWTO This will give you enough information to make sure that the cables are set up right. After that, you need to look at how the card is set up in its BIOS (the Ctrl-A setup screen) and see if maybe you have an unsupported option enabled or something. Sincerely, Ray Ingles (248) 377-7735[EMAIL PROTECTED] Suffering is good for the soul, but it is usually best to wait until the body has no choice in the matter. - Stephen Donaldson
Re: SCSI errors on Install
On Tue, 16 Feb 1999, Kent West wrote: In trying to run INSTALL.BAT off the Cheapbytes hamm CD, it gets to a point where it tries to scan the SCSI bus and it goes into a loop containing the following: [...] This is my first experience with SCSI, so I don't know where to begin. First things first: what's the exact model name and number of the SCSI card? You need to make sure it's properly supported by Linux. Sincerely, Ray Ingles (248) 377-7735 [EMAIL PROTECTED] Una saus victus nullam sperare salutem. - The one hope of the damned is not to hope for safety.
Re: SCSI errors on Install
At 04:02 PM 2/16/1999 -0500, Raymond A. Ingles wrote: On Tue, 16 Feb 1999, Kent West wrote: In trying to run INSTALL.BAT off the Cheapbytes hamm CD, it gets to a point where it tries to scan the SCSI bus and it goes into a loop containing the following: [...] This is my first experience with SCSI, so I don't know where to begin. First things first: what's the exact model name and number of the SCSI card? You need to make sure it's properly supported by Linux. Sincerely, Ray Ingles (248) 377-7735 [EMAIL PROTECTED] Is there any particular reason I was too stupid to write that down when I had the case open? I wrote down everything else Oh well, according to the Ctrl-A setup screen, it's an Adaptec AHA-2940 Ultra/Ultra W.
Re: scsi-errors: wrong free-blocks -count, need help, please
On Wed, Dec 23, 1998 at 11:21:40PM +0100, Peter Berlau wrote: Hi, [..] - I partition the disk before making the filesystem: mkfs -V /dev/sdc5 for example the scsi timed out and the sytem hangs, there where no change to reboot so I hard-reset the box. slow down the datatransfer rate rom 10m to 08m in the scsi-apapter-config for id3 == /dev/sdc and restart, became some messages /dev/sda11 needs check ,,, (/var) /dev/sdb5 needs check (/usr) error messages: Dec 23 22:35:09 pmurmel kernel: EXT2-fs error (device 08:15): ext2_check_blocks_bitmap: Wrong free blocks count for group 222, stored = 6301, counted = 6297 Dec 23 22:35:09 pmurmel kernel: EXT2-fs error (device 08:15): ext2_check_inodes_bitmap: Wrong free inodes count in group 194, stored = 451, counted = 443 Dec 23 22:35:09 pmurmel kernel: EXT2-fs error (device 08:15): ext2_check_inodes_bitmap: Wrong free inodes count in super block, stored = 471542, counted = 471534 Dec 23 22:35:09 pmurmel kernel: EXT2-fs error (device 08:0a): ext2_check_blocks_bitmap: Wrong free blocks count for group 70, stored = 7479, counted = 7471 Dec 23 22:35:09 pmurmel kernel: EXT2-fs error (device 08:0a): ext2_check_blocks_bitmap: Wrong free blocks count for group 91, stored = 7260, counted = 7252 [..] Can I repair the filesystem, or will it repair itself during several reboots with fsck or what must I do, ??? Please help, thank You very much Good X-mas Good 1999 an other question I actually have, is it sure that the drive only runs if needed and if not needed is in , let say , sleep-mode. The drive is for sound- and harddisk-recording and I don't use it very often, but if I use it i mean it does make a start-run noise -- Peter
Re: SCSI Errors and Resetting
Probably this does not apply to you or it won't solve your problems (because your SCSI controller is different than mine) but I was getting SCSI timeouts with 2.0.30 and an Adaptec AHA-2940U with two hard disks and one DAT tape unit. I was unable to make it work but all the problem went away when I upgraded to 2.0.32. It was just like that: magic. Why don't you try going to 2.0.32? It culd happen to you as well... Good luck, E.- P.S. The timeouts only ocurred while trying to backup to tape. During normal disk operation (no tape activity) everything was just fine. William D. Rendahl [EMAIL PROTECTED] wrote: : Hi, : First off: _very_ cool list! Lurking here has been exceedingly helpful. : We're running Debian 1.3.1 (bo, kernel 2.0.30) on an Intel Premier : PCI II motherboard, with a 90MHz Penti, 32MB, BusLogic BT-948, and : Quantum Fireball Drive. Several times a day we get messages on the : console describing a SCSI error, the system is momentarily frozen, : and then everything is fine . . . : On bootup it looks like this: : Dec 1 13:40:35 mail kernel: scsi: * BusLogic SCSI Driver Version : 2.0.9 of 29 March 1997 * : Dec 1 13:40:35 mail kernel: scsi: Copyright 1995 by Leonard N. Zubkoff : [EMAIL PROTECTED] : Dec 1 13:40:35 mail kernel: scsi0: Configuring BusLogic Model BT-948 : PCI Ultra SCSI Host Adapter : Dec 1 13:40:35 mail kernel: scsi0: Firmware Version: 5.06I, I/O : Address: 0xFCFC, IRQ Channel: 11/Level : Dec 1 13:40:35 mail kernel: scsi0: PCI Bus: 0, Device: 6, Address: : 0xFFBFF000, Host Adapter SCSI ID: 7 : Dec 1 13:40:35 mail kernel: scsi0: Parity Checking: Enabled, Extended : Translation: Enabled : Dec 1 13:40:35 mail kernel: scsi0: Synchronous Negotiation: UUF#, : Wide Negotiation: Disabled : Dec 1 13:40:35 mail kernel: scsi0: Disconnect/Reconnect: Enabled, : Tagged Queuing: Enabled : Dec 1 13:40:35 mail kernel: scsi0: Scatter/Gather Limit: 128 of 8192 : segments, Mailboxes: 255 : Dec 1 13:40:35 mail kernel: scsi0: Driver Queue Depth: 255, Host : Adapter Queue Depth: 192 : Dec 1 13:40:35 mail kernel: scsi0: Tagged Queue Depth: Automatic, : Untagged Queue Depth: 3 : Dec 1 13:40:35 mail kernel: scsi0: Error Recovery Strategy: Default, : SCSI Bus Reset: Enabled : Dec 1 13:40:35 mail kernel: scsi0: SCSI Bus Termination: Enabled, : SCAM: Disabled : Dec 1 13:40:35 mail kernel: scsi0: *** BusLogic BT-948 Initialized : Successfully *** : Dec 1 13:40:35 mail kernel: scsi0: Target 0: Synchronous at 20.0 : mega-transfers/second, offset 15 : Dec 1 13:40:35 mail kernel: scsi0: Target 2: Synchronous at 10.0 : mega-transfers/second, offset 15 : Dec 1 13:40:35 mail kernel: Failed initialization of WD-7000 SCSI card! : Dec 1 13:40:35 mail kernel: PPA: unable to initialise controller at : 0x378, error 1 : Dec 1 13:40:35 mail kernel: scsi0 : BusLogic BT-948 : Dec 1 13:40:35 mail kernel: scsi : 1 host. : Dec 1 13:40:35 mail kernel: Vendor: QUANTUM Model: FIREBALL : ST2.1S Rev: 0F0C : Dec 1 13:40:35 mail kernel: Type: : Direct-Access ANSI SCSI revision: 02 : Dec 1 13:40:35 mail kernel: Detected scsi disk sda at scsi0, channel 0, : id 0, lun 0 : Dec 1 13:40:35 mail kernel: Vendor: NEC Model: CD-ROM : DRIVE:462 Rev: 1.13 : Dec 1 13:40:35 mail kernel: Type: : CD-ROM ANSI SCSI revision: 02 : Dec 1 13:40:35 mail kernel: Detected scsi CD-ROM sr0 at scsi0, channel : 0, id 2, lun 0 : Dec 1 13:40:35 mail kernel: scsi : detected 1 SCSI cdrom 1 SCSI disk : total. : Dec 1 13:40:35 mail kernel: SCSI device sda: hdwr sector= 512 bytes. : Sectors= 4235629 [2068 MB] [2.1 GB] : Dec 1 13:40:35 mail kernel: Partition check: : Dec 1 13:40:35 mail kernel: sda: sda1 sda2 : Dec 1 13:40:35 mail kernel: VFS: Mounted root (ext2 filesystem) : readonly. : Dec 1 13:40:35 mail kernel: scsi0: Tagged Queuing now active for Target : 0 : And the error messages are: : Dec 1 14:26:57 mail kernel: scsi : aborting command due to timeout : : pid 38105, scsi0, channel 0, id 0, lun 0 Write (6) 17 02 59 02 00 : Dec 1 14:26:57 mail kernel: scsi0: Aborting CCB #38128 to Target 0 : Dec 1 14:26:57 mail kernel: scsi : aborting command due to timeout : : pid 38106, scsi0, channel 0, id 0, lun 0 4scsi0: CCB #38128 to Target : 0 Aborted : Dec 1 14:26:57 mail kernel: Write (6) 17 40 53 02 00 : Dec 1 14:26:57 mail kernel: scsi0: Aborting CCB #38129 to Target 0 : Dec 1 14:26:57 mail kernel: scsi : aborting command due to timeout : : pid 38107, scsi0, channel 0, id 0, lun 0 4scsi0: CCB #38129 to Target : 0 Aborted : Dec 1 14:26:57 mail kernel: Write (6) 17 45 13 0c 00 : Dec 1 14:26:57 mail kernel: scsi0: Aborting CCB #38130 to Target 0 : Dec 1 14:26:57 mail kernel: scsi : aborting command due to timeout : : pid 38108, scsi0, channel 0, id 0, lun 0 4scsi0: CCB #38130 to Target : 0 Aborted : Dec 1 14:26:57 mail kernel: Write (6) 17 45 33 02 00 : Dec 1 14:26:57
Re: SCSI Errors and Resetting
Hi, First off: _very_ cool list! Lurking here has been exceedingly helpful. Hi. Thanks, we'll keep up :) We're running Debian 1.3.1 (bo, kernel 2.0.30) on an Intel Premier PCI II motherboard, with a 90MHz Penti, 32MB, BusLogic BT-948, and Quantum Fireball Drive. Several times a day we get messages on the console describing a SCSI error, the system is momentarily frozen, and then everything is fine . . . I had exactly the same kind of errors with my SyJet drive. I found it defective and exchanged for another one - no errors now. Meanwhile I think I found the reason of it - disk just can't keep the pace of negotiated synchronous transfer. The cure might be to disable synchronous mode in your adapter with this drive or to replace the drive ;( Oh, yeah, and check your cables ... Alex Y. -- _ _( )_ ( (o___ +---+ | _ 7 |Alexander Yukhimets| \()| http://pages.nyu.edu/~aqy6633/ | / \ \ +---+ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: SCSI Errors and Resetting
Probably this does not apply to you or it won't solve your problems (because your SCSI controller is different than mine) but I was getting SCSI timeouts with 2.0.30 and an Adaptec AHA-2940U with two hard disks and one DAT tape unit. I was unable to make it work but all the problem went away when I upgraded to 2.0.32. It was just like that: magic. Why don't you try going to 2.0.32? It culd happen to you as well... Good luck, E.- P.S. The timeouts only ocurred while trying to backup to tape. During normal disk operation (no tape activity) everything was just fine. William D. Rendahl [EMAIL PROTECTED] wrote: : Hi, : First off: _very_ cool list! Lurking here has been exceedingly helpful. : We're running Debian 1.3.1 (bo, kernel 2.0.30) on an Intel Premier : PCI II motherboard, with a 90MHz Penti, 32MB, BusLogic BT-948, and : Quantum Fireball Drive. Several times a day we get messages on the : console describing a SCSI error, the system is momentarily frozen, : and then everything is fine . . . : On bootup it looks like this: : Dec 1 13:40:35 mail kernel: scsi: * BusLogic SCSI Driver Version : 2.0.9 of 29 March 1997 * : Dec 1 13:40:35 mail kernel: scsi: Copyright 1995 by Leonard N. Zubkoff : [EMAIL PROTECTED] : Dec 1 13:40:35 mail kernel: scsi0: Configuring BusLogic Model BT-948 : PCI Ultra SCSI Host Adapter : Dec 1 13:40:35 mail kernel: scsi0: Firmware Version: 5.06I, I/O : Address: 0xFCFC, IRQ Channel: 11/Level : Dec 1 13:40:35 mail kernel: scsi0: PCI Bus: 0, Device: 6, Address: : 0xFFBFF000, Host Adapter SCSI ID: 7 : Dec 1 13:40:35 mail kernel: scsi0: Parity Checking: Enabled, Extended : Translation: Enabled : Dec 1 13:40:35 mail kernel: scsi0: Synchronous Negotiation: UUF#, : Wide Negotiation: Disabled : Dec 1 13:40:35 mail kernel: scsi0: Disconnect/Reconnect: Enabled, : Tagged Queuing: Enabled : Dec 1 13:40:35 mail kernel: scsi0: Scatter/Gather Limit: 128 of 8192 : segments, Mailboxes: 255 : Dec 1 13:40:35 mail kernel: scsi0: Driver Queue Depth: 255, Host : Adapter Queue Depth: 192 : Dec 1 13:40:35 mail kernel: scsi0: Tagged Queue Depth: Automatic, : Untagged Queue Depth: 3 : Dec 1 13:40:35 mail kernel: scsi0: Error Recovery Strategy: Default, : SCSI Bus Reset: Enabled : Dec 1 13:40:35 mail kernel: scsi0: SCSI Bus Termination: Enabled, : SCAM: Disabled : Dec 1 13:40:35 mail kernel: scsi0: *** BusLogic BT-948 Initialized : Successfully *** : Dec 1 13:40:35 mail kernel: scsi0: Target 0: Synchronous at 20.0 : mega-transfers/second, offset 15 : Dec 1 13:40:35 mail kernel: scsi0: Target 2: Synchronous at 10.0 : mega-transfers/second, offset 15 : Dec 1 13:40:35 mail kernel: Failed initialization of WD-7000 SCSI card! : Dec 1 13:40:35 mail kernel: PPA: unable to initialise controller at : 0x378, error 1 : Dec 1 13:40:35 mail kernel: scsi0 : BusLogic BT-948 : Dec 1 13:40:35 mail kernel: scsi : 1 host. : Dec 1 13:40:35 mail kernel: Vendor: QUANTUM Model: FIREBALL : ST2.1S Rev: 0F0C : Dec 1 13:40:35 mail kernel: Type: : Direct-Access ANSI SCSI revision: 02 : Dec 1 13:40:35 mail kernel: Detected scsi disk sda at scsi0, channel 0, : id 0, lun 0 : Dec 1 13:40:35 mail kernel: Vendor: NEC Model: CD-ROM : DRIVE:462 Rev: 1.13 : Dec 1 13:40:35 mail kernel: Type: : CD-ROM ANSI SCSI revision: 02 : Dec 1 13:40:35 mail kernel: Detected scsi CD-ROM sr0 at scsi0, channel : 0, id 2, lun 0 : Dec 1 13:40:35 mail kernel: scsi : detected 1 SCSI cdrom 1 SCSI disk : total. : Dec 1 13:40:35 mail kernel: SCSI device sda: hdwr sector= 512 bytes. : Sectors= 4235629 [2068 MB] [2.1 GB] : Dec 1 13:40:35 mail kernel: Partition check: : Dec 1 13:40:35 mail kernel: sda: sda1 sda2 : Dec 1 13:40:35 mail kernel: VFS: Mounted root (ext2 filesystem) : readonly. : Dec 1 13:40:35 mail kernel: scsi0: Tagged Queuing now active for Target : 0 : And the error messages are: : Dec 1 14:26:57 mail kernel: scsi : aborting command due to timeout : : pid 38105, scsi0, channel 0, id 0, lun 0 Write (6) 17 02 59 02 00 : Dec 1 14:26:57 mail kernel: scsi0: Aborting CCB #38128 to Target 0 : Dec 1 14:26:57 mail kernel: scsi : aborting command due to timeout : : pid 38106, scsi0, channel 0, id 0, lun 0 4scsi0: CCB #38128 to Target : 0 Aborted : Dec 1 14:26:57 mail kernel: Write (6) 17 40 53 02 00 : Dec 1 14:26:57 mail kernel: scsi0: Aborting CCB #38129 to Target 0 : Dec 1 14:26:57 mail kernel: scsi : aborting command due to timeout : : pid 38107, scsi0, channel 0, id 0, lun 0 4scsi0: CCB #38129 to Target : 0 Aborted : Dec 1 14:26:57 mail kernel: Write (6) 17 45 13 0c 00 : Dec 1 14:26:57 mail kernel: scsi0: Aborting CCB #38130 to Target 0 : Dec 1 14:26:57 mail kernel: scsi : aborting command due to timeout : : pid 38108, scsi0, channel 0, id 0, lun 0 4scsi0: CCB #38130 to Target : 0 Aborted : Dec 1 14:26:57 mail kernel: Write (6) 17 45 33 02 00 : Dec 1 14:26:57
Re: SCSI Errors and Resetting
William D. Rendahl wrote: Hi, First off: _very_ cool list! Lurking here has been exceedingly helpful. We're running Debian 1.3.1 (bo, kernel 2.0.30) on an Intel Premier PCI II motherboard, with a 90MHz Penti, 32MB, BusLogic BT-948, and Quantum Fireball Drive. Several times a day we get messages on the console describing a SCSI error, the system is momentarily frozen, and then everything is fine . . . Whoa.. deja vu.. this is the exact sort of error messages we recieve here at work... WD-7000 initialization failed... And other assorted error messages. For the most part I think they're harmless (We've never had any problems with our Micropolis SCSI drive..) however, it's truly strange.. and I'm the sort that just doesn't like miscellaneous errors popping up, even if they are harmless. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: SCSI Errors and Resetting
On Thu, 4 Dec 1997, Wintermute wrote: William D. Rendahl wrote: We're running Debian 1.3.1 (bo, kernel 2.0.30) on an Intel Premier PCI II motherboard, with a 90MHz Penti, 32MB, BusLogic BT-948, and Quantum Fireball Drive. Several times a day we get messages on the console describing a SCSI error, the system is momentarily frozen, and then everything is fine . . . Whoa.. deja vu.. this is the exact sort of error messages we recieve here at work... WD-7000 initialization failed... And other assorted error messages. For the most part I think they're harmless (We've never had any problems with our Micropolis SCSI drive..) however, it's truly strange.. and I'm the sort that just doesn't like miscellaneous errors popping up, even if they are harmless. Well, let's sort out which error messages you mean. Anybody running an installation kernel is going to see the WD-7000 one (unless they have a WD-7000, I suppose!), and the next line comes from having parallel-port SCSI support but (e.g. a zip drive) not present. (Though I get error 2, not 1.) But these were in the boot up section and are harmless. The others looked more serious, but I'm no expert. Some people have had cabling problems, others have had to switch off a feature like ultra speed. Perhaps the latter is why upgrading the kernel could make a difference - you get the support for the newer feature in the newer kernel. -- David Wright, Open University, Earth Science Department, Milton Keynes MK7 6AA U.K. email: [EMAIL PROTECTED] tel: +44 1908 653 739 fax: +44 1908 655 151 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: SCSI Errors and Resetting
William D. Rendahl [EMAIL PROTECTED] writes: Hi, First off: _very_ cool list! Lurking here has been exceedingly helpful. We're running Debian 1.3.1 (bo, kernel 2.0.30) on an Intel Premier PCI II motherboard, with a 90MHz Penti, 32MB, BusLogic BT-948, and Quantum Fireball Drive. Several times a day we get messages on the console describing a SCSI error, the system is momentarily frozen, and then everything is fine . . . I recently had this identical problem with the same BusLogic controller, and eventually tracked it down to incorrect SCSI termination (a new drive was inserted in the middle of the SCSI chain but the clown^H^H^H^H^Hinstaller left the termination on). Errors and freezes occured only when the system tried to access devices beyond the termination. Check and make sure only the *last* SCSI drive is terminated and see if this helps. --Norris -- Norris Preyer (541) 962-3310 (office) Physics Program (541) 962-3873 (fax) Eastern Oregon University [EMAIL PROTECTED] La Grande, OR 97850http://physics.eou.edu/npreyer.html finger [EMAIL PROTECTED] for PGP key -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: SCSI Errors and Resetting
William D. Rendahl [EMAIL PROTECTED] writes: Hi, First off: _very_ cool list! Lurking here has been exceedingly helpful. We're running Debian 1.3.1 (bo, kernel 2.0.30) on an Intel Premier PCI II motherboard, with a 90MHz Penti, 32MB, BusLogic BT-948, and Quantum Fireball Drive. Several times a day we get messages on the console describing a SCSI error, the system is momentarily frozen, and then everything is fine . . . I recently had this identical problem with the same BusLogic controller, and eventually tracked it down to incorrect SCSI termination (a new drive was inserted in the middle of the SCSI chain but the clown^H^H^H^H^Hinstaller left the termination on). Errors and freezes occured only when the system tried to access devices beyond the termination. Check and make sure only the *last* SCSI drive is terminated and see if this helps. --Norris -- Norris Preyer (541) 962-3310 (office) Physics Program (541) 962-3873 (fax) Eastern Oregon University [EMAIL PROTECTED] La Grande, OR 97850http://physics.eou.edu/npreyer.html finger [EMAIL PROTECTED] for PGP key -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: SCSI Errors and Resetting
Eloy A. Paris [EMAIL PROTECTED] writes: Probably this does not apply to you or it won't solve your problems (because your SCSI controller is different than mine) but I was getting SCSI timeouts with 2.0.30 and an Adaptec AHA-2940U with two hard disks and one DAT tape unit. I was unable to make it work but all the problem went away when I upgraded to 2.0.32. It was just like that: magic. Why don't you try going to 2.0.32? It culd happen to you as well... I have a Buslogic BT-958 and a Buslogic BT-948, and three drives connected. I saw the same thing running 2.0.31-pre9. Haven't seen it yet with 2.0.32, although I've only had it up 3 days. But, maybe it was a general problem with SCSI in those kernels. Later, Dale -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: scsi errors
Hi Mike -- You asked: Is there any way of testing a block device in linux? The test program is fsck. Every time you boot, fsck is run if there's a problem with the file system. So this may be some help, but not consolation. Cheers? Susan Kleinmann
Re: Scsi errors
In your email to me, [EMAIL PROTECTED], you wrote: It's down to 3.3... Any other settings to jack with?? Make sure you have the shortest cable possible, and good termination. Other than that, try another scsi cable. Tim Thanks to all who have replied, but nothing has helped. I've got a 4 inch cable hooked up between the drive and the card now, but that didn't do it. The drive is a SCSI-III so I believe its a self-terminating device, but I don't know... Are there any terminators that would go on the end of a 50 pin ribbon? Anyway, I don't think the cabling is a problem. I ran a media verify from the onboard bios and it went through the whole drive with no problems, except for the usual media defects. I also did a dma transfer test from the bios and it came up clean. Are there any kernels that are known to work _for_sure_ with an AHA-1542CF?? Maybe that's my problem... Mike
Re: Scsi errors
At 07:55 PM 9/25/96 -0500, you wrote: Are there any kernels that are known to work _for_sure_ with an AHA-1542CF?? Maybe that's my problem... Mike I've been running a AHA-1542CF since the 1.x kernel series with no trouble at all. I know have two systems with them in there running 2.0.15 and 1.2.10. I did have a problem before with the scsi cable which I posted to here - basically what it kept doing was writing to the hard drive in wrong places, corrupting things when accessing the cdrom I have connected. Turned out that it was the cable and I've never had any trouble since then. Perhaps it could be the hard drive, but then again, I wouldn't know about that - both my scsi disks are SCSI-2 and yours is a SCSI-3, perhaps it doesn't like them for some reason? Regards ...Karl -- Karl Ferguson, Tower Networking Pty Ltd (ACN: 072 322 760)[EMAIL PROTECTED] t/a STAR Online Services [EMAIL PROTECTED] Tel: +61-9-455-3446 Fax: +61-9-455-2776 http://www.star.net.au/
Re: Scsi errors
[EMAIL PROTECTED] writes: device, but I don't know... Are there any terminators that would go on the end of a 50 pin ribbon? Normally, there's a switch, or jumper you have to set that terminates the drive. If the drive's not terminated, and is at the end of a scsi chain. You'll most likely have problems. I didn't think SCSI-III was special in that respect. -- Rob
Re: Scsi errors
On Wed, 25 Sep 1996 [EMAIL PROTECTED] wrote: In your email to me, [EMAIL PROTECTED], you wrote: It's down to 3.3... Any other settings to jack with?? Make sure you have the shortest cable possible, and good termination. Other than that, try another scsi cable. Tim Thanks to all who have replied, but nothing has helped. I've got a 4 inch cable hooked up between the drive and the card now, but that didn't do it. The drive is a SCSI-III so I believe its a self-terminating device, but I don't know... Are there any terminators that would go on the end of a 50 pin ribbon? Anyway, I don't think the cabling is a problem. I ran a media verify from the onboard bios and it went through the whole drive with no problems, except for the usual media defects. I also did a dma transfer test from the bios and it came up clean. Are there any kernels that are known to work _for_sure_ with an AHA-1542CF?? Maybe that's my problem... I've been using the standard aha1542 driver as a module with 2.0.14 with no problems, but I had a lot of problems initially. My problem was termination and the symptoms sound similar to yours. My one external device is a ZIP drive. If your hard drive has resisters installed (usually near the ribbon connector area on the component side of a SCSI drive, then its got internal terminators, but they may not be enabled, or termination power to the BUS may not be set properly. You really need to get some decent documentation for the drive. I hope the SCSI driver developers or kernel developers can implement a way for things like this to have less of an impact, 1.2 never complained (neither did DOS, etc.). Apparently the driver is only able to sense what's going on on the bus when its loaded, so it can't gracefully fail to load when such a problem occurs. I'd rather see it able to run despite such a problem :-) Anyway, good luck. Richard G. Roberto [EMAIL PROTECTED] 011-81-3-3437-7967 - Tokyo, Japan -- *** Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. ***
Re: Scsi errors
In reply to [EMAIL PROTECTED]'s message of Tue, 24 Sep 1996 I'll just repeat what others have already stated: it is very likely your cables and termination. I was having very similar problems which got worse with the newer kernels. I finally bought new high quality cables and active terminators (expansive), which improved the problems considerably, but did not cure them. More recently I upgraded to a new motherboard, so I bought a cheap 53c810 controller, which has now completely eliminated all problems and dramatically increased performance as well. So if you have PCI slots on your board, then you should upgrade to a $60 PCI 53c810 (or 53c815) card and sell your Adaptec card to some DOS user. Otherwise you will probably just have to check your termination and cables, but you may not be able to do much about it. On the other hand I just noticed your messages are also reporting unexpected interrupts. Have you checked to make sure that nothing else is using that interrupt? You probably should try removing all unnecessary card and see if the problem goes away. Can anyone help me here? I've got an AHA1542 with a quantum XP32150W as the only device on the chain. I keep getting errors like the following: scsi : aborting command due to timeout : pid 198, scsi0, channel 0, id 0, lun 0 Write (10) 00 00 27 88 b0 00 00 76 00 scsi : aborting command due to timeout : pid 198, scsi0, channel 0, id 0, lun 0 Write (10) 00 00 27 88 b0 00 00 76 00 SCSI host 0 abort (pid 198) timed out - resetting SCSI bus is being reset for host 0 channel 0. Sent BUS DEVICE RESET to target 0 Sending DID_RESET for target 0 aha1542_intr_handle: Unexpected interrupt tarstat=0, hastat=0 idlun=10 ccb#=5 Are there any settings I need to tweak in order to rid myself of these timeout errors? Mike
Re: Scsi errors
Make sure you have the shortest cable possible, and good termination. Other than that, try another scsi cable. Tim The SCSI spec for SCSI-III (Specifically, bus rates up to 20 Mhz) state that the total length of the SCSI bus should not exceed 3 metres when using four or less devices, and not exceed 1.5 metres with five to eight devices. (More devices, less distance on the cable to the farthest device) In all cases, no devices should be closer than .3 metres apart. Thanks to all who have replied, but nothing has helped. a 4 inch cable hooked up between the drive and the card now, but that didn't do it. The drive is a SCSI-III so I believe its a self-terminating device, but I don't know... Are there any terminators that would go on the end of a 50 pin ribbon? .3 metres is over 8 inches. It never hurts to plug in a terminator on the end of a 50 pin ribbon connector to make sure the bus is terminated, but the self-terminating drives make life much easier. Anyway, I don't think the cabling is a problem. I ran a media verify from the onboard bios and it went through the whole drive with no problems, except for the usual media defects. I also did a dma transfer test from the bios and it came up clean. Does it work under a different OS or on a different controller card? It seems that the drive is seeing the commands if you're able to send down commands to the drive in your media test. Hopefully you can get it working under one case to eliminate termination and cable problems. Usually it's the software drivers, because most people set up the SCSI bus correctly and it is forgiving in many instances. Are there any kernels that are known to work _for_sure_ with an AHA-1542CF?? Maybe that's my problem... This, I do not know. Good luck in finding someone with specific experience, perhaps there is someone at the company who makes the card using Linux. Charles
RE: Scsi errors
Can anyone help me here? I've got an AHA1542 with a quantum XP32150W as the only device on the chain. I keep getting errors like the following: scsi : aborting command due to timeout : pid 198, scsi0, channel 0, id 0, lun 0 Write (10) 00 00 27 88 b0 00 00 76 00 scsi : aborting command due to timeout : pid 198, scsi0, channel 0, id 0, lun 0 Write (10) 00 00 27 88 b0 00 00 76 00 It looks like your drive failed to respond to a write request within the Linux disk IO timeout period. SCSI host 0 abort (pid 198) timed out - resetting SCSI bus is being reset for host 0 channel 0. Sent BUS DEVICE RESET to target 0 Sending DID_RESET for target 0 Sending DID_RESET for target 0 Sending DID_RESET for target 0 Sending DID_RESET for target 0 It looks likes Linux is resetting the SCSI bus and the SCSI disk. aha1542_intr_handle: Unexpected interrupt tarstat=0, hastat=0 idlun=10 ccb#=5 aha1542_intr_handle: Unexpected interrupt tarstat=0, hastat=0 idlun=10 ccb#=7 It looks like the the Adaptec SCSI card finally tried to return the disk requests, it said the target status (the disk) and the host adapter status (the Adaptec) were ok. Although I wouldn't always trust what an Adaptec controller was telling me. Too bad your logs don't give timing information. From the data given (and my limited knowledge of how Linux disk drivers work) I'd say that Linux's timeout on IO requests may be too short, causing a race condition between when the status of the async disk IO is is returned and when Linux goes in to reset mode. (Linux times out, sends the bus and device reset (which should cause this disk to forget about any IOs) but after all of that's over, the Adaptec tries to say the IOs completed successfully). Last time I was writing SCSI disk drivers (about 1992) newer disks were capable of queuing 64 commands. That number could be up substantially now. If an average IO takes 10ms to process, 256 queued IOs could take 2.5 seconds to process; may be bumping into Linux's SCSI device driver timeout. Just a theory... Then again this whole problem may be as simple as a bad SCSI cable or termination (very common problem and usually intermittent) or disk controller or host adapter brains going south. I don't have the source for the SCSI disk controller, If I get a chance I'll download some source and try to look through it to see what the timeouts are and if they're easily configured. Good Luck, Al Youngwerth [EMAIL PROTECTED]
