What you can do ist to configure the Controller with your itanium machine by using EFI and move the equipment back to your Alpha.
These days I'm looking for NOS 73G and above 15K 80pin 3.5 form
factor SCSI.
Yup - unobtainium :-(
\\
I'm getting close to trialing a SATA SSD solution for RX2600 units
w/OVMS boot support (new P410i PCIe controller and PCIX to PCIe adapter
plus cabling). The SATA drives will be deployed in an external
enclosure. I have a bill of materials drafted. Parts are trickling in
for the bench trial.
Alas, no Alpha boot support and even to use as a data disk requires
3.3V PCIx buss on DS15 and above.
https://groups.google.com/forum/#!topic/comp.os.vms/t7Mu4kEYTrw
Both the DS10 and the DS15 have the same PCI buss. From the
Technical Summary documents on both, it's a PCI V2.1 compliant bus
supporting either %.0V or 3.3V PCI cards.
But all the PICe to PCI converter boards I see say they are PCI V2.3
compliant so I don't know if they would work with the DS10/15 PCI bus.
This one is common on Amazon in the US StarTech PCIPEX1 -
<https://www.startech.com/Cards-Adapters/Slot-Extension/PCI-to-PCI-Express-Adapter-Card~PCI1PEX1>
Is there any chance a DS10 with V8.4 (HP, not VSI) could boot from a
P400 or P800 series SATA HBA?
Some limited success with OpenVMS Alpha V8.4. After updating the
device = "Smart Array P-series P400"
name = PK
driver = SYS$PKRDRIVER
adapter = PCI
id = 0x3230103C
boot_class = DK
boot_flags = HW_CTRL_LTR, UNIT_0
flags = CISS, PORT
end_device
device = "Smart Array P-series PMC PCIe"
name = PK
driver = SYS$PKRDRIVER
adapter = PCI
id = 0x323A103C
boot_class = DK
boot_flags = HW_CTRL_LTR, UNIT_0
flags = CISS, PORT
end_device
$ show dev p
Device Device Error
Name Status Count
PKB0: Online 0
PKA0: Online 0
PGA0: Online 0
PGB0: Online 0
PKC0: Online 0
PKA0: is the Smart Array P410. PKB0: and PKC0: are the two channels for
the 3X-KZPEA Adaptec SCSI.
Device PKA0:, device type HP Smart Array, is online, error logging is enabled.
Error count 0 Operations completed
2854
Owner process "" Owner UIC
[SYSTEM]
Owner process ID 00000000 Dev Prot
S:RWPL,O:RWPL,G,W
Reference count 0 Default buffer size
65535
Current preferred CPU Id 0 Fastpath
1
Current Interrupt CPU Id 0
Still no disks showing up, of course.
$ show dev d
Device Device Error Volume Free
Trans Mnt
Name Status Count Label Blocks Count Cnt
ASIMOV$DKB0: Mounted 0 ASIMOV084 14419878
313 1
ASIMOV$DKB100: Online 0
ASIMOV$DVA0: Online 0
ASIMOV$DQA0: Online 0
ASIMOV$DQA1: Offline 1
ASIMOV$DQB0: Offline 1
ASIMOV$DQB1: Offline 1
ASIMOV$DKC0: Online 0
So now when I run MSA$UTIL things work better.
$ mcr MSA$UTIL
MSA> show controller
Adapter: _PKA0: (DEFAULT)
P410 (c) HP PACCRID125002W7 Software 6.00
Port Address: 50014380-22aa92a0
Supported Redundancy Mode: Not Available.
912 megabyte read/write cache
Cache is not configured, and Cache is disabled.
No unflushed data in cache.
Battery is fully charged.
MSA>
My two Samsung 860EVO 256GB SSD disk show up as expected in bays 5 & 6
in the 6-bay SATA enclosure.
MSA> show disks
SATA device [Disk]
5, size 232.89 [250.06]GB
Disk 25505, # 0, size 488331632 blocks, (232.85 [250.03] GB), Unused.
SATA device [Disk]
6, size 232.89 [250.06]GB
Disk 25506, # 0, size 488331632 blocks, (232.85 [250.03] GB), Unused.
Here's where things go bad again. Trying to make units of the disks.
MSA> add unit 1000/disk=25505/jbod/partition=0
Specified disk is not a Valid disk
MSA> add unit 1000/disk=25505/jbod/partition=0/size=32gb
Specified disk is not a Valid disk
MSA> add unit 1000/disk=25505/jbod
Specified disk is not a Valid disk
MSA> add unit 1000/disk=25505/raid=1
Specified disk is not a Valid disk
MSA> add unit 1000/disk=25505
Specified disk is not a Valid disk
MSA> add unit 1000/disk=2550
Specified disk is not a Valid disk
MSA> add unit 1000/disk=5
The selected controller does not support this unit number only supports 64 units
MSA> add unit 10/disk=5/jbod
A non-existant/invalid partition was specified.
Partition numbers for units on a disk should be sequential.
Please create units with appropriate partition numbers.
MSA> add unit 10/disk=5/jbod/partition=0
A non-existant/invalid partition was specified.
Partition numbers for units on a disk should be sequential.
Please create units with appropriate partition numbers.
MSA> show disk 5
Disk 5 does not exist
MSA> show disk 255
Disk 255 does not exist
MSA> show disk 2555
Specified disk is not a Valid disk
MSA> show disk 25505
Specified disk is not a Valid disk
MSA> show disks
SATA device [Disk]
5, size 232.89 [250.06]GB
Disk 25505, # 0, size 488331632 blocks, (232.85 [250.03] GB), Unused.
SATA device [Disk]
6, size 232.89 [250.06]GB
Disk 25506, # 0, size 488331632 blocks, (232.85 [250.03] GB), Unused.
MSA>
Anyone have any ideas? Next on my list is to try to update the
firmware to 6.65 but I didn't see anything in the release notes that
might indicate a fix for this.
Also, the MSA$UTIL has a firmware loading option. Anyone used it?
FLASH
FIRMWARE
FLASH FIRMWARE is used to update the firmware of a given
controller. Specify the firmware filename to be used.
FLASH FIRMWARE <file name> / <qualifiers>
Parameters Qualifiers
/VERBOSE
Restrictions
--
John H. Reinhardt
_______________________________________________
Info-vax mailing list
http://rbnsn.com/mailman/listinfo/info-vax_rbnsn.com