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
"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 Statu
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
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 exper
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 thin
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
"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
"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
"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 Dr
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
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
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
> 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
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
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
> > 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
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
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.
[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 lik
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 system
>
> 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 n
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
22 matches
Mail list logo
