Is there a supported way to attach a Tape Drive to OpenVMS 9.2-2

Post Reply

Topic author
pocketprobe
Valued Contributor
Posts: 68
Joined: Sat Apr 15, 2023 11:53 pm
Reputation: 0
Status: Offline

Is there a supported way to attach a Tape Drive to OpenVMS 9.2-2

Post by pocketprobe » Wed Mar 20, 2024 1:26 pm

Are there presently any supported ways to attach a(n LTO) tape drive to a system running 9.2-2?
Ideally via SAS/SCSI
Last edited by pocketprobe on Wed Mar 20, 2024 2:17 pm, edited 1 time in total.
Top

sms
Master
Posts: 349
Joined: Fri Aug 21, 2020 5:18 pm
Reputation: 0
Status: Offline

Re: Is there a supported way to attach a Tape Drive to OpenVMS 9.2-2

Post by sms » Thu Mar 21, 2024 12:29 am

Code: Select all

> Are there presently any supported ways to attach a(n LTO) tape drive
> to a system running 9.2-2?

   A physical (not virtual) tape drive?  I know nothing, but I doubt it. 
But I wouldn't be amazed if the answer depended on the exact type of
system on which VMS V9.2-2 was running.

   If you had such a tape drive, what would you do with it?  BACKUP can
deal with a save set on disk storage, too, for example.
Top

Topic author
pocketprobe
Valued Contributor
Posts: 68
Joined: Sat Apr 15, 2023 11:53 pm
Reputation: 0
Status: Offline

Re: Is there a supported way to attach a Tape Drive to OpenVMS 9.2-2

Post by pocketprobe » Thu Mar 21, 2024 10:25 am

sms wrote: ↑
Thu Mar 21, 2024 12:29 am

Code: Select all

> If you had such a tape drive, what would you do with it?  BACKUP can
> deal with a save set on disk storage, too, for example.
Your assumption is correct, it is for backups. As to why LTO Tape? It's reasonably priced, especially for generations that fit within the current volume size limit for OpenVMS... and I've inherited a dozen or so tapes. Ultimately, it's for the same reason as to why I'm collecting VTs; I just think they're neat.
sms wrote: ↑
Thu Mar 21, 2024 12:29 am

Code: Select all

> A physical (not virtual) tape drive?  I know nothing, but I doubt it. 
> But I wouldn't be amazed if the answer depended on the exact type of
> system on which VMS V9.2-2 was running.
I've since moved my bare metal machine to a(n) HP(E) ML150 Gen9 which is very close to being a(n) HP(E) DL380 Gen9, and the question about supported configurations comes up, as asking sysman to configure the tape drive for use crashes the machine. If it's something to be explored I can post more information.
Top

roberbrooks
VSI Expert
Contributor
Posts: 20
Joined: Thu Jun 20, 2019 11:48 am
Reputation: 0
Status: Offline

Re: Is there a supported way to attach a Tape Drive to OpenVMS 9.2-2

Post by roberbrooks » Thu Mar 21, 2024 11:12 am

Please post the first page of the output from

$ analyze/crash
SDA> CLUE CRASH

You are traveling a path we have not yet tried, so I'm curious to see where things went off the rails.

-- Rob
Top

Topic author
pocketprobe
Valued Contributor
Posts: 68
Joined: Sat Apr 15, 2023 11:53 pm
Reputation: 0
Status: Offline

Re: Is there a supported way to attach a Tape Drive to OpenVMS 9.2-2

Post by pocketprobe » Thu Mar 21, 2024 11:45 am

Unfortunately on this machine it crashes so hard, that we're unable to make a crash dump. I'd question if it's a driver bug for the gen9 smart array controllers; In my post about running on bare metal, I was advised that it wasn't fully validated and was only really tested with one specific controller. With some cable trickery (and purchase of an cable adapter) I could probably see if the tape drive works on the P440 rather than an H240. I should also see if it behaves with the 1068e that I used in my other machine (Though that controller also stops working if there's more than 32gb of ram in the machine.)

I'm not sure if this except from the install media will help but here it is.

Code: Select all

$$$ show dev

Device                  Device           Error   Volume          Free  Trans Mnt
 Name                   Status           Count    Label         Blocks Count Cnt
DMM0:                   Offline              0
DMM1:                   Mounted wrtlck       0 X860922OE         97836    13   1
LDM0:                   Online               0
LDM9476:                Mounted wrtlck       0 MD233417AA5A      25625    13   1
DKA0:                   Online               0
DKA1:                   Online               0
DKA2:                   Online               0

Device                  Device           Error
 Name                   Status           Count
OPA0:                   Online               0
FTA0:                   Offline              0

Device                  Device           Error
 Name                   Status           Count
SRA0:                   Online               0
MPA0:                   Online               0
EIA0:                   Online               0
EIB0:                   Online               0
PKA0:                   Online               0
PKB0:                   Online               0
$$$ mc sysman io
_IO function: find

%SYSMAN-I-OUTPUT, command execution on node 
On port _PKB0:, the following tape WWIDs and their proposed device
names have been found but not yet configured:
 
[Device $2$MGA0]
WWID=02000008:5001-4380-00AA-5984
 
Run SYSMAN IO AUTO to configure the above device(s).
 
$$$ mc sysman io auto

MMG$PAGEFAULT IPLHI:


VSI Dump Kernel SYSBOOT Nov  9 2023 12:17:04
%SYSBOOT-F-MEMTOOSMALL, find_best_memory: could not find enough memory to boot.
     Consider reducing the values in SYSGEN parameters BOOT_BITMAP1 and/or BOOT_BITMAP2.
%SYSBOOT-F-NOBEST, No memory large enough could be found
%SYSBOOT-F-NOINITMMMG, Unable to initialize SYSBOOT memory managment, status = 00000124
 
**************************************************************
* Exception taken before exception handler has been loaded!  *
* Unable to take crashdump.                                  *
**************************************************************
 
* Exception Frame Display: *
 
Exception taken at RIP 00000000.0087304B from Kernel mode
Exception Frame at 00000000.7888B680
X86 Vector  E (Page Fault)
 
* = Value read directly from the register rather than the frame
 
Control Registers:
CR0    System Control Flags                 * 00000000.80010013
       PE = 1   MP = 1   EM = 0   TS = 0   ET = 1   NE = 0
       WP = 1   AM = 0   NW = 0   CD = 0   PG = 1
CR2    Page-Fault Linear Address            * FFFF8300.AA394E80
CR3    Paging Control                       * 00000000.6B4C2000
       PWT= 0   PCD= 0  PGDB= 00000000.6B4C2000
CR4    Architectural Extension Flags        * 00000000.00070668
       VME= 0   PVI= 0   TSD= 0   DE = 1   PSE= 0   PAE= 1
       MCE= 1   PGE= 0   PCE= 0  FXSR= 1 XMMXC= 1  UMIP= 0
      LA57= 0  VMXE= 0  SMXE= 0  FSGS= 1 PCIDE= 1 XSAVE= 1
      SMEP= 0  SMAP= 0   PKE= 0
CR8    Task Priority Register (TPR)           * 00000000.0000000F
GSBASE GS Segment Base (SWIS data)            * 00000000.00A18000
 
RFLAGS Processor Flags                        00000000.00010206
       CF = 0   PF = 1   AF = 0   ZF = 0   SF = 0   TF = 0
       IF = 1   DF = 0   OF = 0  IOPL= 0   NT = 0   RF = 1   VM = 0
       AC = 0   VIF= 0   VIP= 0   ID = 0
 
Miscellaneous Registers:
Interrupt Priority Level (IPL)                1f
Stack Align                                   5e0
PPrev Mode                                    0
Previous Mode                                 0
Interrupt Depth                               0
 
General Registers:
RAX  00000000.00000400     RBX  00000000.00838E90     RCX  00000000.00000000
RDX  00000000.00000000     RSI  80000000.00000001     RDI  00000000.00000000
RSP  00000000.7888B860     RBP  00000000.7888BC40
R8   00000000.00000000     R9   FFFF8300.AA394E18     R10  00000000.00000000
R11  00000000.00000000     R12  00000000.00020000     R13  00000000.00962500
R14  00000000.00962550     R15  00000000.00962528
 
 
******************************************
* Using INIBRK to get help from Xdelta!  *
******************************************
 
**************************************************************
* Exception taken before exception handler has been loaded!  *
* Unable to take crashdump.                                  *
**************************************************************
 
* Exception Frame Display: *
 
Exception taken at RIP 00000000.008DA0C1 from Kernel mode
Exception Frame at 00000000.7888B380
X86 Vector  3 (Breakpoint)
 
* = Value read directly from the register rather than the frame
 
Control Registers:
CR0    System Control Flags                 * 00000000.80010013
       PE = 1   MP = 1   EM = 0   TS = 0   ET = 1   NE = 0
       WP = 1   AM = 0   NW = 0   CD = 0   PG = 1
CR2    Page-Fault Linear Address            * FFFF8300.AA394E80
CR3    Paging Control                       * 00000000.6B4C2000
       PWT= 0   PCD= 0  PGDB= 00000000.6B4C2000
CR4    Architectural Extension Flags        * 00000000.00070668
       VME= 0   PVI= 0   TSD= 0   DE = 1   PSE= 0   PAE= 1
       MCE= 1   PGE= 0   PCE= 0  FXSR= 1 XMMXC= 1  UMIP= 0
      LA57= 0  VMXE= 0  SMXE= 0  FSGS= 1 PCIDE= 1 XSAVE= 1
      SMEP= 0  SMAP= 0   PKE= 0
CR8    Task Priority Register (TPR)           * 00000000.0000000F
GSBASE GS Segment Base (SWIS data)            * 00000000.00A18000
 
RFLAGS Processor Flags                        00000000.00000006
       CF = 0   PF = 1   AF = 0   ZF = 0   SF = 0   TF = 0
       IF = 0   DF = 0   OF = 0  IOPL= 0   NT = 0   RF = 0   VM = 0
       AC = 0   VIF= 0   VIP= 0   ID = 0
 
Miscellaneous Registers:
Interrupt Priority Level (IPL)                1f
Stack Align                                   1e0
PPrev Mode                                    0
Previous Mode                                 0
Interrupt Depth                               0
 
General Registers:
RAX  00000000.00000000     RBX  00000000.00838E90     RCX  00000000.00838E08
RDX  00000000.788D3C18     RSI  00000000.00000000     RDI  00000000.00000300
RSP  00000000.7888B568     RBP  00000000.7888B5E0
R8   00000000.00FFFFFF     R9   00000000.00000006     R10  00000000.FFFFFFFF
R11  00000000.00000300     R12  00000000.00020000     R13  00000000.00962500
R14  00000000.00962550     R15  00000000.00962528
 
 
******************************************
* Using INIBRK to get help from Xdelta!  *
******************************************
 
**************************************************************
* Exception taken before exception handler has been loaded!  *
* Unable to take crashdump.                                  *
**************************************************************
 
* Exception Frame Display: *
 
Exception taken at RIP 00000000.008DA0C1 from Kernel mode
Exception Frame at 00000000.7888B080
X86 Vector  3 (Breakpoint)
 
* = Value read directly from the register rather than the frame
 
Control Registers:
CR0    System Control Flags                 * 00000000.80010013
       PE = 1   MP = 1   EM = 0   TS = 0   ET = 1   NE = 0
       WP = 1   AM = 0   NW = 0   CD = 0   PG = 1
CR2    Page-Fault Linear Address            * FFFF8300.AA394E80
CR3    Paging Control                       * 00000000.6B4C2000
       PWT= 0   PCD= 0  PGDB= 00000000.6B4C2000
CR4    Architectural Extension Flags        * 00000000.00070668
       VME= 0   PVI= 0   TSD= 0   DE = 1   PSE= 0   PAE= 1
       MCE= 1   PGE= 0   PCE= 0  FXSR= 1 XMMXC= 1  UMIP= 0
      LA57= 0  VMXE= 0  SMXE= 0  FSGS= 1 PCIDE= 1 XSAVE= 1
      SMEP= 0  SMAP= 0   PKE= 0
CR8    Task Priority Register (TPR)           * 00000000.0000000F
GSBASE GS Segment Base (SWIS data)            * 00000000.00A18000
 
RFLAGS Processor Flags                        00000000.00000006
       CF = 0   PF = 1   AF = 0   ZF = 0   SF = 0   TF = 0
       IF = 0   DF = 0   OF = 0  IOPL= 0   NT = 0   RF = 0   VM = 0
       AC = 0   VIF= 0   VIP= 0   ID = 0
 
Miscellaneous Registers:
Interrupt Priority Level (IPL)                1f
Stack Align                                   1e0
PPrev Mode                                    0
Previous Mode                                 0
Interrupt Depth                               0
 
General Registers:
RAX  00000000.00000000     RBX  00000000.00838E90     RCX  00000000.00838E08
RDX  00000000.788D3C18     RSI  00000000.00000000     RDI  00000000.00000300
RSP  00000000.7888B268     RBP  00000000.7888B2E0
R8   00000000.00FFFFFF     R9   00000000.00000006     R10  00000000.FFFFFFFF
R11  00000000.00000300     R12  00000000.00020000     R13  00000000.00962500
R14  00000000.00962550     R15  00000000.00962528
 
 
******************************************
* Using INIBRK to get help from Xdelta!  *
******************************************
 
**************************************************************
* Exception taken before exception handler has been loaded!  *
* Unable to take crashdump.                                  *
**************************************************************
 
* Exception Frame Display: *
 
Exception taken at RIP 00000000.008DA0C1 from Kernel mode
Exception Frame at 00000000.7888AD80
X86 Vector  3 (Breakpoint)
 
* = Value read directly from the register rather than the frame
 
Control Registers:
CR0    System Control Flags                 * 00000000.80010013
       PE = 1   MP = 1   EM = 0   TS = 0   ET = 1   NE = 0
       WP = 1   AM = 0   NW = 0   CD = 0   PG = 1
CR2    Page-Fault Linear Address            * FFFF8300.AA394E80
CR3    Paging Control                       * 00000000.6B4C2000
       PWT= 0   PCD= 0  PGDB= 00000000.6B4C2000
CR4    Architectural Extension Flags        * 00000000.00070668
       VME= 0   PVI= 0   TSD= 0   DE = 1   PSE= 0   PAE= 1
       MCE= 1   PGE= 0   PCE= 0  FXSR= 1 XMMXC= 1  UMIP= 0
      LA57= 0  VMXE= 0  SMXE= 0  FSGS= 1 PCIDE= 1 XSAVE= 1
      SMEP= 0  SMAP= 0   PKE= 0
CR8    Task Priority Register (TPR)           * 00000000.0000000F
GSBASE GS Segment Base (SWIS data)            * 00000000.00A18000
 
RFLAGS Processor Flags                        00000000.00000006
       CF = 0   PF = 1   AF = 0   ZF = 0   SF = 0   TF = 0
       IF = 0   DF = 0   OF = 0  IOPL= 0   NT = 0   RF = 0   VM = 0
       AC = 0   VIF= 0   VIP= 0   ID = 0
 
Miscellaneous Registers:
Interrupt Priority Level (IPL)                1f
Stack Align                                   1e0
PPrev Mode                                    0
Previous Mode                                 0
Interrupt Depth                               0
 
General Registers:
RAX  00000000.00000000     RBX  00000000.00838E90     RCX  00000000.00838E08
RDX  00000000.788D3C18     RSI  00000000.00000000     RDI  00000000.00000300
RSP  00000000.7888AF68     RBP  00000000.7888AFE0
R8   00000000.00FFFFFF     R9   00000000.00000006     R10  00000000.FFFFFFFF
R11  00000000.00000300     R12  00000000.00020000     R13  00000000.00962500
R14  00000000.00962550     R15  00000000.00962528
 
 
******************************************
* Using INIBRK to get help from Xdelta!  *
******************************************
 
**************************************************************
* Exception taken before exception handler has been loaded!  *
* Unable to take crashdump.                                  *
**************************************************************
 
* Exception Frame Display: *
 
Exception taken at RIP 00000000.008DA0C1 from Kernel mode
Exception Frame at 00000000.7888AA80
X86 Vector  3 (Breakpoint)
 
* = Value read directly from the register rather than the frame
 
Control Registers:
CR0    System Control Flags                 * 00000000.80010013
       PE = 1   MP = 1   EM = 0   TS = 0   ET = 1   NE = 0
       WP = 1   AM = 0   NW = 0   CD = 0   PG = 1
CR2    Page-Fault Linear Address            * FFFF8300.AA394E80
CR3    Paging Control                       * 00000000.6B4C2000
       PWT= 0   PCD= 0  PGDB= 00000000.6B4C2000
CR4    Architectural Extension Flags        * 00000000.00070668
       VME= 0   PVI= 0   TSD= 0   DE = 1   PSE= 0   PAE= 1
       MCE= 1   PGE= 0   PCE= 0  FXSR= 1 XMMXC= 1  UMIP= 0
      LA57= 0  VMXE= 0  SMXE= 0  FSGS= 1 PCIDE= 1 XSAVE= 1
      SMEP= 0  SMAP= 0   PKE= 0
CR8    Task Priority Register (TPR)           * 00000000.0000000F
GSBASE GS Segment Base (SWIS data)            * 00000000.00A18000
 
RFLAGS Processor Flags                        00000000.00000006
       CF = 0   PF = 1   AF = 0   ZF = 0   SF = 0   TF = 0
       IF = 0   DF = 0   OF = 0  IOPL= 0   NT = 0   RF = 0   VM = 0
       AC = 0   VIF= 0   VIP= 0   ID = 0
 
Miscellaneous Registers:
Interrupt Priority Level (IPL)                1f
Stack Align                                   1e0
PPrev Mode                                    0
Previous Mode                                 0
Interrupt Depth                               0
The machine as it is installed now, fails to boot when the tape drive is present, and fails right after systartup_vms.com starts to run.
Top

Topic author
pocketprobe
Valued Contributor
Posts: 68
Joined: Sat Apr 15, 2023 11:53 pm
Reputation: 0
Status: Offline

Re: Is there a supported way to attach a Tape Drive to OpenVMS 9.2-2

Post by pocketprobe » Thu Mar 28, 2024 2:23 pm

I moved the tape drive and controller to another machine, with a different controller type for the system disk. As requested.

Code: Select all

SDA> clue crash
Crashdump Summary Information:
------------------------------
Crash Time:        28-MAR-2024 00:53:23.60
Bugcheck Type:     PGFIPLHI, Pagefault with IPL too high
Node:              AVALON  (Standalone)
CPU Type:          To Be Filled By O.E.M. To Be Filled By O.E.M.
VMS Version:       V9.2-2
Current Process:   NULL
Current Image:     <not available>
Failing PC:        FFFF8300.07CA72DE    IO_ROUTINES+800746DE   (IOBD + 00001E5E
/ line 44155)
Failing PS:        00000000.00000000
Module:            IO_ROUTINES    (Link Date/Time:  9-NOV-2023 12:31:32.08)
Offset:            800746DE

Boot Time:         28-MAR-2024 00:51:23.00
System Uptime:               0 00:02:00.60
Crash/Primary CPU: 4./0.
System/CPU Type:   0000
Saved Processes:   12
Pagesize:          8 KByte (8192 bytes)

    Press RETURN for more.
SDA>
Crashdump Summary Information:
------------------------------
Physical Memory:   32735 MByte (9043968 PFNs, discontiguous memory)
Dumpfile Pagelets: 0 blocks
Dump Flags:        olddump,errlogcomp
Dump Type:         raw,full,shared_mem
EXE$GL_FLAGS:      init,bugdump
Paging Files:      1 Pagefile and 0 Swapfiles installed

Stack Pointers:
KSP = FFFFFFFF.8D09B460   ESP = FFFFFFFF.8CD34F00   SSP = FFFFFFFF.8CD1B000
USP = FFFFFFFF.8CD1B000

General Registers:
RAX = 00000000.00000600   RDI = 00000000.00100002   RSI = 00000000.0000035C
RDX = FFFFFFFF.8D09B800   RCX = 00000000.00000008   R8  = 00000000.00000000
R9  = 00000000.00000008   RBX = FFFFFFFF.8D09BF00   RBP = FFFFFFFF.8D09B580
R10 = 00000000.0000035C   R11 = 00000000.0000035C   R12 = FFFFFFFF.8D09B478
R13 = 00000000.00000000   R14 = FFFFFFFF.8A904400   R15 = 00000000.00009706
RIP = FFFF8300.0839F9D2   RSP = FFFFFFFF.8D09B468   SS  = 00000000.00000010


    Press RETURN for more.
SDA>
Crashdump Summary Information:
------------------------------
Pagefault Information:
Faulting Virtual Address        00000000.00000008
Memory Management Flags         00000000.00000000   (Read Data Fault)
Faulting IPL                    00000008

Exception Frame:
Exception taken at RIP FFFF8300.07CA72DE from Kernel mode
Trap Type      0000000E (Page Fault)
Address      = FFFFFFFF.8D09B800         Prev Frame     = FFFFFFFF.8CD33A50
RAX = 00000000.00000100   RDI = 00000000.00000000   RSI = 00000000.00000000
RDX = 00000000.00000001   RCX = 00000000.00000001   R8  = FFFFFFFF.804BF0C8
R9  = 00000000.0000042E   RBX = FFFFFFFF.8D09BF00   RBP = FFFFFFFF.8D09BA60
R10 = 00000000.00000001   R11 = FFFF8300.07CA5D70   R12 = FFFFFFFF.8D09BAC8
R13 = 00000000.00000000   R14 = FFFFFFFF.8A904400   R15 = 00000000.00004600
RIP = FFFF8300.07CA72DE   RSP = FFFFFFFF.8D09B9E0   SS  = 00000000.00000010

System Registers:
Page Table Base Register (PTBR)                           00000000.00669198
Processor Base Register (PRBR)                            FFFFFFFF.8CD18000

    Press RETURN for more.
SDA>
Crashdump Summary Information:
------------------------------
Privileged Context Block Base (PCBB)                      FFFFFFFF.8CD18080
System Control Block Base (SCBB)                          00000000.00000000
Software Interrupt Summary Register (SISR)                00000000.00000000
Address Space Number (ASN)                                00000000.00000000
AST Summary / AST Enable (ASTSR_ASTEN)                    00000000.00000000
Interrupt Priority Level (IPL)                            00000000.00000008














    Press RETURN for more.
SDA>
Crashdump Summary Information:
------------------------------
Failing Instruction:
IOBD + 00001E5E / line 44155:  movzwl  08(%rdi),%eax

Instruction Stream (about last 10 instructions):
IOBD + 00001E1E / line 44139:  (bad)   prefix rex.rb
IOBD + 00001E1F / line 44139:  loopne  48
IOBD + 00001E21 / line 44139:  movl    $00000000,(%rax)
IOBD + 00001E27 / line 44140:  jmpb    -17
IOBD + 00001E29 / line 44142:  jmpb    00
IOBD + 00001E2B / line 44142:  jmpb    00
IOBD + 00001E2D / line 44142:  jmpq    -0000013C
IOBD + 00001E32 / line 44142:  nop
IOBD + 00001E33 / line 44142:  nop
IOBD + 00001E34 / line 44142:  nop
IOBD + 00001E35 / line 44142:  nop
IOBD + 00001E36 / line 44142:  nop
IOBD + 00001E37 / line 44142:  nop
IOBD + 00001E38 / line 44142:  nop
IOBD + 00001E39 / line 44142:  nop

    Press RETURN for more.
SDA>
Crashdump Summary Information:
------------------------------
IOBD + 00001E3A / line 44142:  nop
IOBD + 00001E3B / line 44142:  nop
IOBD + 00001E3C / line 44142:  nop
IOBD + 00001E3D / line 44142:  nop
IOBD + 00001E3E / line 44142:  nop
IOBD + 00001E3F / line 44142:  nop
IOBD + 00001E40 / line 44152:  pushq   %rbp
IOBD + 00001E41 / line 44152:  movq    %rsp,%rbp
IOBD + 00001E44 / line 44152:  pushq   %r15
IOBD + 00001E46 / line 44152:  pushq   %r14
IOBD + 00001E48 / line 44152:  pushq   %r12
IOBD + 00001E4A / line 44152:  pushq   %rbx
IOBD + 00001E4B / line 44152:  subq    $60,%rsp
IOBD + 00001E4F / line 44152:  movq    %rdi,-38(%rbp)
IOBD + 00001E53 / line 44154:  movl    $00000C43,-24(%rbp)
IOBD + 00001E5A / line 44155:  movq    -38(%rbp),%rdi
IOBD + 00001E5E / line 44155:  movzwl  08(%rdi),%eax
IOBD + 00001E62 / line 44155:  movl    %eax,-28(%rbp)
IOBD + 00001E65 / line 44156:  movq    -38(%rbp),%rdi

    Press RETURN for more.
SDA>
Crashdump Summary Information:
------------------------------
IOBD + 00001E69 / line 44156:  movzbl  20(%rdi),%eax
IOBD + 00001E6D / line 44156:  shll    $1B,%eax
SDA>
Top

roberbrooks
VSI Expert
Contributor
Posts: 20
Joined: Thu Jun 20, 2019 11:48 am
Reputation: 0
Status: Offline

Re: Is there a supported way to attach a Tape Drive to OpenVMS 9.2-2

Post by roberbrooks » Thu Mar 28, 2024 8:15 pm

Thanks for the output; I'll take a look at it on Friday to figure out where things went wrong.

-- Rob
Top

Topic author
pocketprobe
Valued Contributor
Posts: 68
Joined: Sat Apr 15, 2023 11:53 pm
Reputation: 0
Status: Offline

Re: Is there a supported way to attach a Tape Drive to OpenVMS 9.2-2

Post by pocketprobe » Mon Apr 15, 2024 2:58 pm

I've finally had a cable come in to let me attach my tape drive to another controller (LSI 1068e) and I have the same crash occur. I've never had good luck with crashdumps with this controller.

One other thing I can try is passing through the controllers to a VM inside of ESXi and see if it still occurs.
Top
Post Reply

Return to “x86-64”