>Eric Siegerman schrieb:
>> On Mon, Feb 07, 2005 at 04:41:17PM -0500, Jon LaBadie wrote:
>>>Can on look at the device connectors, or better yet, the external
>>> connectors, and tell if a device is LVD or SE? Or does one have
>>> to check the HW doc?
>>
If you're lucky enough that the manufacture
On Tuesday 08 February 2005 11:34, Christoph Scheeder wrote:
>Hi all,
>if the scsi-connector is more then 50-pin's wide you'll have to look
> in the HW doc to determin that.
>If its only 50 pin wide, it's definitly a SE device.
>Christoph
I don't know as I'd carve that on the doorframe Christoph.
Hi all,
if the scsi-connector is more then 50-pin's wide you'll have to look in the
HW doc to determin that.
If its only 50 pin wide, it's definitly a SE device.
Christoph
Eric Siegerman schrieb:
On Mon, Feb 07, 2005 at 04:41:17PM -0500, Jon LaBadie wrote:
Can on look at the device connectors, or b
I have the new scsi card (an inexpensive LSILogic LSIU80ALVDB) that fixes the problems I was having. So, the Exabyte tech support was correct and the great advice I got herein this mailing list also said "get a separate scsi card" ! I am still using the older driver. I will be updating the d
On Mon, Feb 07, 2005 at 04:41:17PM -0500, Jon LaBadie wrote:
> Can on look at the device connectors, or better yet, the external connectors,
> and tell if a device is LVD or SE? Or does one have to check the HW doc?
I have no idea. Sorry.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont.
On Mon, Feb 07, 2005 at 03:55:36PM -0500, Eric Siegerman wrote:
> On Fri, Feb 04, 2005 at 07:21:59PM -0500, Gene Heskett wrote:
> > Aha, LVD! LVD is not compatible with the rest of the system unless
> > the rest of the system is also LVD. It is two, completely seperate
> > signalling methods th
I am near positive I did not fry anything since everything is working correctly except a sustained write to the tape. If anything were damages, I would expect nothing to work at all. I have ordered the new scsi card and I will report back in to this thread when I find the results. I am also
On Fri, Feb 04, 2005 at 07:21:59PM -0500, Gene Heskett wrote:
> Aha, LVD! LVD is not compatible with the rest of the system unless
> the rest of the system is also LVD. It is two, completely seperate
> signalling methods that just happen to use the same cabling.
Yes and no. From the SCSI FAQ:
On Friday 04 February 2005 14:58, James D. Freels wrote:
>On Fri, 2005-02-04 at 14:36 -0500, Gene Heskett wrote:
>
>The cable IS completely disconnected from the scsi card and the
> cd-rom IS the only
>device on that cable. This is what is so strange. I did this test
>thinking it might
>fix my pr
--On Friday, February 04, 2005 09:41 -0500 "James D. Freels"
<[EMAIL PROTECTED]> wrote:
When you say "cabling" issues, does this include a separate scsi card
specific for the
tape drive ? I think my cable connections are good.
This encompasses a whle list of issues. The two or three most c
On Fri, 2005-02-04 at 14:36 -0500, Gene Heskett wrote:
The cable IS completely disconnected from the scsi card and the cd-rom IS the only
device on that cable. This is what is so strange. I did this test thinking it might
fix my problem since I am down from 2-internal, 1-external on the sam
On Friday 04 February 2005 13:31, James D. Freels wrote:
>Interesting test. I powered down and disconnected the narrow 50-pin
>cable from card and unplugged
>the power cable from the CD-ROM on the other end. In this
>configuration, there is
>one wide 80-pin cable with 3 hard drives + 1 VXA-1 tape
Interesting test. I powered down and disconnected the narrow 50-pin cable from card and unplugged
the power cable from the CD-ROM on the other end. In this configuration, there is
one wide 80-pin cable with 3 hard drives + 1 VXA-1 tape drive on the internal connection
to the card. The new p
On Friday 04 February 2005 10:12, Geert Uytterhoeven wrote:
>On Fri, 4 Feb 2005, James D. Freels wrote:
>> The tape drive is within the VXA-2 Packet-Loader 1U rack mount.
>> It is connected via an external
>> scsi cable that came with the drive. the unit also came with it's
>> own terminator whic
On Fri, 4 Feb 2005, James D. Freels wrote:
> So, you think if I disconnected the CD-rom (as a test), this would
> resolve the problem ?
Probably (I hope so).
> Also, I just tried a kernel with the ncr53c8xx driver and ultra
> conservative settings (for example,
> setting to asynchronous I/O) and
So, you think if I disconnected the CD-rom (as a test), this would resolve the problem ?
The CD-rom is seldom used accept for emergency boots.
Also, I just tried a kernel with the ncr53c8xx driver and ultra conservative settings (for example,
setting to asynchronous I/O) and it behaves better.
On Friday 04 February 2005 09:41, James D. Freels wrote:
>I specifically pointed out to the Exabyte tech support that I
> thought the Linux tools
>provided with the tape drive were Intel-specific and because I had
> an Alpha, it would
>not execute properly. I knew this because I had already tried
On Fri, 4 Feb 2005, James D. Freels wrote:
> The tape drive is within the VXA-2 Packet-Loader 1U rack mount. It is
> connected via an external
> scsi cable that came with the drive. the unit also came with it's own
> terminator which is also plugged into the
> packet loader. The packet-loader i
The tape drive is within the VXA-2 Packet-Loader 1U rack mount. It is connected via an external
scsi cable that came with the drive. the unit also came with it's own terminator which is also plugged into the
packet loader. The packet-loader is the only device connected to the scsi card exte
On Fri, 4 Feb 2005, James D. Freels wrote:
> When you say "cabling" issues, does this include a separate scsi card
> specific for the
> tape drive ? I think my cable connections are good.
The cable may be too long, or not properly terminated.
> The scsi card I have is a "LSI Logic / Symbios Logi
I specifically pointed out to the Exabyte tech support that I thought the Linux tools
provided with the tape drive were Intel-specific and because I had an Alpha, it would
not execute properly. I knew this because I had already tried to use them prior to
calling Exabyte. I already had the l
--On Thursday, February 03, 2005 15:03 -0500 "James D. Freels"
<[EMAIL PROTECTED]> wrote:
I am getting scsi sense errors using the new drive about 1-2 minutes
after an amdump or amflush starts. Below are the reommendations from
Exabyte tech support to fix it.
I seem to remember doing FW upgrade
On Thursday 03 February 2005 17:49, James D. Freels wrote:
>No. It should be still Alpha compatible. The problem is that the
>firmware upgrade utilities
>for Linux are binary-only so I cannot compile them for the alpha nor
> run them on the alpha.
Are you saying its not a case of dd if=inputfile
No. It should be still Alpha compatible. The problem is that the firmware upgrade utilities
for Linux are binary-only so I cannot compile them for the alpha nor run them on the alpha.
On Thu, 2005-02-03 at 16:19 -0500, Eric Siegerman wrote:
On Thu, Feb 03, 2005 at 03:03:22PM -0500, James
On Thu, Feb 03, 2005 at 03:03:22PM -0500, James D. Freels wrote:
> Here is what [drive vendor's Tech Support said] is needed:
>
> 1) need a separate scsi chain; they said I already have too many scsi
> devices on this chain to make it reliable.
See recent threads re. SCSI cables, bus lengths, etc
I am getting scsi sense errors using the new drive about 1-2 minutes after an amdump or amflush starts. Below are the reommendations from Exabyte tech support to fix it.
Any comments ?
Forwarded Message
From: James D. Freels <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
26 matches
Mail list logo
