This is something new. I've been able to rip from this drive before. I
can still play cd audio from that drive (with cdplay, for example).
Trying to run cdparanoia I get the following errors (as either a normal
use or as root).
$ cdparanoia 1-2
cdparanoia III release 9.8 (March 23, 2001)
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
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
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
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
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
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:
SCSI host 0 abort (pid 0) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
SCSI host 0 channel 0 reset (pid 0) timed
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
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
Hi,
to X-mas I got me a new ibm-scsi-drive :)
therefore I have a Adaptec 2940 AU Controller
and, unfortanelety, the drives for this
(65 pin) ? are outsold.
So I buy a IBM 4,5 GB UW
trapezoid connector looks
()
\---/
is smaller, than the Drive - Connectors i usualy have,
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
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
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
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
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
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
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 Drive. Several
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
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
Thanks again to all who have replied. Apparently the problems
I was seeing were from the kernel version I was running. When I upgraded
to 2.0.15 all the errors went away. Although the reported errors went
away, almost none of the data I've put on the drive comes back off like
it's
: Re: Scsi errors
Author: debian-user@lists.debian.org at cclink
Date:26.09.96 14:54
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
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
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
Stupid me... another symptom I've noticed is when I try
and make a file system on the drive in question, when it stalls
I checked another terminal and init was dead and every process
that ended was zombieing. Does this point to the kernel at all??
Mike
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
[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
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
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
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
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
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
32 matches
Mail list logo
