Discussion:
Issue with booting and/or seeing the SYSBOOT prompt
(too old to reply)
Dymaxion Development
2021-10-23 12:27:54 UTC
Permalink
Hi,

I am a OpenVMS newbie and I inherited trying to determine why a system no longer boots. It's an RX2600 running OpenVMS 8.4. The former system manager passed away so I really do not have any resources I could call upon.

The system starts up, loads the and see the disks...and then hangs. I cannot tell if it is waiting for an answer to a prompt or just doesn't proceed. I wanted to enable the SYSBOOT prompt to enable STARTUP_D2 to enable logging to see where it is hanging. But booting in conversational mode does the exact same thing. One of the boot options has VMS_FLAGS set to 0,1 for the same drive. And even I go into the EFI shell and set it, it hangs.

We have a backup drive which is a mirror of the system from a year ago. The MODPARAMS.DAT, AUTOPARAM.PAR and IA64VMSSYS.PAR are identical (the MODPARAMS.DAT compared via DIFF and the last two via CHECKSUM). I can successfully boot from that (we'd use it as the primary disk but it's a small drive and there is no client data on it nor would it fit). This drive also a conversational boot and it too hangs. In any case, the fact it does boot there are no hardware issues that could be preventing the system from booting.

I was hoping for tips on how to resolve being able to boot successfully or tell where in the boot process it is hanging. Or perhaps how I would go about transferring the OS from the backup disk to the primary disk.

Thanks in advance.

John
abrsvc
2021-10-23 13:03:02 UTC
Permalink
Post by Dymaxion Development
Hi,
I am a OpenVMS newbie and I inherited trying to determine why a system no longer boots. It's an RX2600 running OpenVMS 8.4. The former system manager passed away so I really do not have any resources I could call upon.
The system starts up, loads the and see the disks...and then hangs. I cannot tell if it is waiting for an answer to a prompt or just doesn't proceed. I wanted to enable the SYSBOOT prompt to enable STARTUP_D2 to enable logging to see where it is hanging. But booting in conversational mode does the exact same thing. One of the boot options has VMS_FLAGS set to 0,1 for the same drive. And even I go into the EFI shell and set it, it hangs.
We have a backup drive which is a mirror of the system from a year ago. The MODPARAMS.DAT, AUTOPARAM.PAR and IA64VMSSYS.PAR are identical (the MODPARAMS.DAT compared via DIFF and the last two via CHECKSUM). I can successfully boot from that (we'd use it as the primary disk but it's a small drive and there is no client data on it nor would it fit). This drive also a conversational boot and it too hangs. In any case, the fact it does boot there are no hardware issues that could be preventing the system from booting.
I was hoping for tips on how to resolve being able to boot successfully or tell where in the boot process it is hanging. Or perhaps how I would go about transferring the OS from the backup disk to the primary disk.
Thanks in advance.
John
There is not much to go on here...

Can you post what is presented on the terminal screen thus far?

Since you say the disks are seen and the system "starts up", what exactly does that mean? Again post what you see.

The resolution of this may require direct contact (and perhaps some cost). If you can, post an Email or allow replies directly to you (reply to author option).

Dan
V***@SendSpamHere.ORG
2021-10-23 14:10:44 UTC
Permalink
On Saturday, October 23, 2021 at 8:27:55 AM UTC-4, Dymaxion Development wro=
Hi,=20
=20
I am a OpenVMS newbie and I inherited trying to determine why a system no=
longer boots. It's an RX2600 running OpenVMS 8.4. The former system manage=
r passed away so I really do not have any resources I could call upon.=20
=20
The system starts up, loads the and see the disks...and then hangs. I can=
not tell if it is waiting for an answer to a prompt or just doesn't proceed=
.. I wanted to enable the SYSBOOT prompt to enable STARTUP_D2 to enable logg=
ing to see where it is hanging. But booting in conversational mode does the=
exact same thing. One of the boot options has VMS_FLAGS set to 0,1 for the=
same drive. And even I go into the EFI shell and set it, it hangs.=20
=20
We have a backup drive which is a mirror of the system from a year ago. T=
he MODPARAMS.DAT, AUTOPARAM.PAR and IA64VMSSYS.PAR are identical (the MODPA=
RAMS.DAT compared via DIFF and the last two via CHECKSUM). I can successful=
ly boot from that (we'd use it as the primary disk but it's a small drive a=
nd there is no client data on it nor would it fit). This drive also a conve=
rsational boot and it too hangs. In any case, the fact it does boot there a=
re no hardware issues that could be preventing the system from booting.=20
=20
I was hoping for tips on how to resolve being able to boot successfully o=
r tell where in the boot process it is hanging. Or perhaps how I would go a=
bout transferring the OS from the backup disk to the primary disk.=20
=20
Thanks in advance.=20
=20
John
There is not much to go on here...
Can you post what is presented on the terminal screen thus far?
Since you say the disks are seen and the system "starts up", what exactly d=
oes that mean? Again post what you see.
The resolution of this may require direct contact (and perhaps some cost). =
If you can, post an Email or allow replies directly to you (reply to autho=
r option).
Dan
I'd suggest trying to boot from OpeVMS distribution media (DVD). If that goes
well, it's possible that the system disk is 1) bad or 2) corrupted or 3) boot
"parition" has been horked. Much more can be ascertained from VMS itself once
the DVD is booted.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG

I speak to machines with the voice of humanity.
Richard Brodie
2021-10-23 15:19:54 UTC
Permalink
Post by Dymaxion Development
We have a backup drive which is a mirror of the system from a year ago. The MODPARAMS.DAT, AUTOPARAM.PAR and IA64VMSSYS.PAR are identical (the MODPARAMS.DAT compared via DIFF and the last two via CHECKSUM). I can successfully boot from that (we'd use it as the primary disk but it's a small drive and there is no client data on it nor would it fit). This drive also a conversational boot and it too hangs. In any case, the fact it does boot there are no hardware issues that could be preventing the system from booting.
If your second drive is bootable but you can't get the conversational boot to work it sounds like a console problem. What are you using: local VGA, serial or iLO? If VGA, that may well be your problem.
abrsvc
2021-10-24 14:40:41 UTC
Permalink
Post by Richard Brodie
Post by Dymaxion Development
We have a backup drive which is a mirror of the system from a year ago. The MODPARAMS.DAT, AUTOPARAM.PAR and IA64VMSSYS.PAR are identical (the MODPARAMS.DAT compared via DIFF and the last two via CHECKSUM). I can successfully boot from that (we'd use it as the primary disk but it's a small drive and there is no client data on it nor would it fit). This drive also a conversational boot and it too hangs. In any case, the fact it does boot there are no hardware issues that could be preventing the system from booting.
If your second drive is bootable but you can't get the conversational boot to work it sounds like a console problem. What are you using: local VGA, serial or iLO? If VGA, that may well be your problem.
My conjecture is that it is prompting and that's why it seems to hang. But I cannot see the prompt. It's console attached via KVM using the VGA port. I do not have access to the ILO. I can try serial but do not know what's involved.
I am going to suggest that this machine was set up to use the serial port for the console and not the VGA port. This would explain why you see nothing. If the system is expecting input and is set this way, it is the serial connection that will provide the prompt and expect input.
Dan
John Tran
2021-10-24 14:42:43 UTC
Permalink
Post by Richard Brodie
Post by Dymaxion Development
We have a backup drive which is a mirror of the system from a year ago. The MODPARAMS.DAT, AUTOPARAM.PAR and IA64VMSSYS.PAR are identical (the MODPARAMS.DAT compared via DIFF and the last two via CHECKSUM). I can successfully boot from that (we'd use it as the primary disk but it's a small drive and there is no client data on it nor would it fit). This drive also a conversational boot and it too hangs. In any case, the fact it does boot there are no hardware issues that could be preventing the system from booting.
If your second drive is bootable but you can't get the conversational boot to work it sounds like a console problem. What are you using: local VGA, serial or iLO? If VGA, that may well be your problem.
My conjecture is that it is prompting and that's why it seems to hang. But I cannot see the prompt. It's console attached via KVM using the VGA port. I do not have access to the ILO. I can try serial but do not know what's involved.
I am going to suggest that this machine was set up to use the serial port for the console and not the VGA port. This would explain why you see nothing. If the system is expecting input and is set this way, it is the serial connection that will provide the prompt and expect input.
Dan
How do I go about connecting a serial connection?
Richard Brodie
2021-10-24 16:28:32 UTC
Permalink
Post by John Tran
How do I go about connecting a serial connection?
See this document: https://support.hpe.com/hpesc/public/docDisplay?docId=c01672119&docLocale=en_US
Scott Dorsey
2021-10-24 18:55:14 UTC
Permalink
Post by John Tran
How do I go about connecting a serial connection?
Plug a serial terminal into the console port. Note that some machines
require a nonstandard pinout, so check the pinout before you plug the
terminal in. Then unplug the VGA connector so that it will directly
go to the serial port as soon as it's turned on.

Our guess is that the machine begins to boot and along the way switches
to the serial port, which would be reasonable for a system that was
originally configured for serial access.

Once you have a real console you can see what is going on.
--scott
--
"C'est un Nagra. C'est suisse, et tres, tres precis."
Bob Gezelter
2021-10-23 19:02:21 UTC
Permalink
Post by Dymaxion Development
Hi,
I am a OpenVMS newbie and I inherited trying to determine why a system no longer boots. It's an RX2600 running OpenVMS 8.4. The former system manager passed away so I really do not have any resources I could call upon.
The system starts up, loads the and see the disks...and then hangs. I cannot tell if it is waiting for an answer to a prompt or just doesn't proceed. I wanted to enable the SYSBOOT prompt to enable STARTUP_D2 to enable logging to see where it is hanging. But booting in conversational mode does the exact same thing. One of the boot options has VMS_FLAGS set to 0,1 for the same drive. And even I go into the EFI shell and set it, it hangs.
We have a backup drive which is a mirror of the system from a year ago. The MODPARAMS.DAT, AUTOPARAM.PAR and IA64VMSSYS.PAR are identical (the MODPARAMS.DAT compared via DIFF and the last two via CHECKSUM). I can successfully boot from that (we'd use it as the primary disk but it's a small drive and there is no client data on it nor would it fit). This drive also a conversational boot and it too hangs. In any case, the fact it does boot there are no hardware issues that could be preventing the system from booting.
I was hoping for tips on how to resolve being able to boot successfully or tell where in the boot process it is hanging. Or perhaps how I would go about transferring the OS from the backup disk to the primary disk.
Thanks in advance.
John
John,

The parameter words, e.g. "0,1" can be set to a variety of HEXADECIMAL values:
- 0,1 does a simple conversational boot from the SYS0 directory.
- 1,0 does a non-conversational boot
- 0,30001 does a conversational bootstrap from SYS0 with detailed messages

Reference: Segment of the OpenVMS FAQ, maintained by Stephen "Hoff" Hoffman at http://hoffmanlabs.org/vmsfaq/vmsfaq_022.html

I would suggest turning on the bootstrap debugging messages, possibly only 0,20001 to start and see what is reported. Use a terminal emulator with output logging to capture the output, it can be voluminous.

In any event, the copy of the system disk is bootable, and you can use it to manually mount the misbehaving volume and at least get a backup. Once you have a backup, then your data is at least safe.

Have dealt with this kind of thing more than a few times, in years past, e.g., MicroVAX II, it could be a chore when storage was precious and the only removable media was 400KB floppies. With today's mass storage, it is far less of a chore. Take care with that backup, it is your safety net. So long as one's backup is intact, one can always restart the recovery process.

If you need detailed assistance, there are several of us in this forum, myself included, who do thing like this for a living.

- Bob Gezelter, http://www.rlgsc.com
John Tran
2021-10-24 14:41:00 UTC
Permalink
Post by Dymaxion Development
Hi,
I am a OpenVMS newbie and I inherited trying to determine why a system no longer boots. It's an RX2600 running OpenVMS 8.4. The former system manager passed away so I really do not have any resources I could call upon.
The system starts up, loads the and see the disks...and then hangs. I cannot tell if it is waiting for an answer to a prompt or just doesn't proceed. I wanted to enable the SYSBOOT prompt to enable STARTUP_D2 to enable logging to see where it is hanging. But booting in conversational mode does the exact same thing. One of the boot options has VMS_FLAGS set to 0,1 for the same drive. And even I go into the EFI shell and set it, it hangs.
We have a backup drive which is a mirror of the system from a year ago. The MODPARAMS.DAT, AUTOPARAM.PAR and IA64VMSSYS.PAR are identical (the MODPARAMS.DAT compared via DIFF and the last two via CHECKSUM). I can successfully boot from that (we'd use it as the primary disk but it's a small drive and there is no client data on it nor would it fit). This drive also a conversational boot and it too hangs. In any case, the fact it does boot there are no hardware issues that could be preventing the system from booting.
I was hoping for tips on how to resolve being able to boot successfully or tell where in the boot process it is hanging. Or perhaps how I would go about transferring the OS from the backup disk to the primary disk.
Thanks in advance.
John
John,
- 0,1 does a simple conversational boot from the SYS0 directory.
- 1,0 does a non-conversational boot
- 0,30001 does a conversational bootstrap from SYS0 with detailed messages
Reference: Segment of the OpenVMS FAQ, maintained by Stephen "Hoff" Hoffman at http://hoffmanlabs.org/vmsfaq/vmsfaq_022.html
I would suggest turning on the bootstrap debugging messages, possibly only 0,20001 to start and see what is reported. Use a terminal emulator with output logging to capture the output, it can be voluminous.
In any event, the copy of the system disk is bootable, and you can use it to manually mount the misbehaving volume and at least get a backup. Once you have a backup, then your data is at least safe.
Have dealt with this kind of thing more than a few times, in years past, e.g., MicroVAX II, it could be a chore when storage was precious and the only removable media was 400KB floppies. With today's mass storage, it is far less of a chore. Take care with that backup, it is your safety net. So long as one's backup is intact, one can always restart the recovery process.
If you need detailed assistance, there are several of us in this forum, myself included, who do thing like this for a living.
- Bob Gezelter, http://www.rlgsc.com
Yes I have image backups for the boot disk and the backup disk. I agree I would be SOL if not for the backup disk.

Could I repair things by backing [SYS0...] from the backup disk over to the primary disk?
Dave Froble
2021-10-24 15:46:16 UTC
Permalink
Post by John Tran
Post by Dymaxion Development
Hi,
I am a OpenVMS newbie and I inherited trying to determine why a system no longer boots. It's an RX2600 running OpenVMS 8.4. The former system manager passed away so I really do not have any resources I could call upon.
The system starts up, loads the and see the disks...and then hangs. I cannot tell if it is waiting for an answer to a prompt or just doesn't proceed. I wanted to enable the SYSBOOT prompt to enable STARTUP_D2 to enable logging to see where it is hanging. But booting in conversational mode does the exact same thing. One of the boot options has VMS_FLAGS set to 0,1 for the same drive. And even I go into the EFI shell and set it, it hangs.
We have a backup drive which is a mirror of the system from a year ago. The MODPARAMS.DAT, AUTOPARAM.PAR and IA64VMSSYS.PAR are identical (the MODPARAMS.DAT compared via DIFF and the last two via CHECKSUM). I can successfully boot from that (we'd use it as the primary disk but it's a small drive and there is no client data on it nor would it fit). This drive also a conversational boot and it too hangs. In any case, the fact it does boot there are no hardware issues that could be preventing the system from booting.
I was hoping for tips on how to resolve being able to boot successfully or tell where in the boot process it is hanging. Or perhaps how I would go about transferring the OS from the backup disk to the primary disk.
Thanks in advance.
John
John,
- 0,1 does a simple conversational boot from the SYS0 directory.
- 1,0 does a non-conversational boot
- 0,30001 does a conversational bootstrap from SYS0 with detailed messages
Reference: Segment of the OpenVMS FAQ, maintained by Stephen "Hoff" Hoffman at http://hoffmanlabs.org/vmsfaq/vmsfaq_022.html
I would suggest turning on the bootstrap debugging messages, possibly only 0,20001 to start and see what is reported. Use a terminal emulator with output logging to capture the output, it can be voluminous.
In any event, the copy of the system disk is bootable, and you can use it to manually mount the misbehaving volume and at least get a backup. Once you have a backup, then your data is at least safe.
Have dealt with this kind of thing more than a few times, in years past, e.g., MicroVAX II, it could be a chore when storage was precious and the only removable media was 400KB floppies. With today's mass storage, it is far less of a chore. Take care with that backup, it is your safety net. So long as one's backup is intact, one can always restart the recovery process.
If you need detailed assistance, there are several of us in this forum, myself included, who do thing like this for a living.
- Bob Gezelter, http://www.rlgsc.com
Yes I have image backups for the boot disk and the backup disk. I agree I would be SOL if not for the backup disk.
Could I repair things by backing [SYS0...] from the backup disk over to the primary disk?
From what I've read, most likely your problem is not the disk, but the "console terminal".
Even if the disk has some problem, you will not be able to see it without a "console".
As several posters have mentioned, you might need to set up a serial console.

Do you have access to an actual VT terminal? That might make things easier.

Do you have support with VSI? That should be your first people to contact.
--
David Froble Tel: 724-529-0450
Dave Froble Enterprises, Inc. E-Mail: ***@tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA 15486
Simon Clubley
2021-10-24 16:00:47 UTC
Permalink
Post by Dave Froble
From what I've read, most likely your problem is not the disk, but the "console terminal".
Even if the disk has some problem, you will not be able to see it without a "console".
As several posters have mentioned, you might need to set up a serial console.
Does Itanium VMS still prompt for the system date and time at system
startup in some circumstances ?

I wonder if it could be as simple as that ?

Of course, he needs to try the serial console to find out...

Simon.
--
Simon Clubley, ***@remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.
John Tran
2021-10-24 16:42:10 UTC
Permalink
Post by Simon Clubley
Post by Dave Froble
From what I've read, most likely your problem is not the disk, but the "console terminal".
Even if the disk has some problem, you will not be able to see it without a "console".
As several posters have mentioned, you might need to set up a serial console.
Does Itanium VMS still prompt for the system date and time at system
startup in some circumstances ?
I wonder if it could be as simple as that ?
Of course, he needs to try the serial console to find out...
Simon.
--
Walking destinations on a map are further away than they appear.
Hm there is an option from the drive select menu to set the system date and time? If I set that, and if it is asking for the date and time, will that prompt not appear?
Simon Clubley
2021-10-24 16:02:56 UTC
Permalink
Sorry, no VT terminal and no VSI support. :(
I have a laptop and I could install a terminal emulator. I do not know how to connect to the RX2600.
Are you saying you do not have a serial cable and don't know how
to make one up ?

Are there any serial cables you can borrow ?

Simon.
--
Simon Clubley, ***@remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.
John Tran
2021-10-24 16:39:55 UTC
Permalink
Post by Simon Clubley
Sorry, no VT terminal and no VSI support. :(
I have a laptop and I could install a terminal emulator. I do not know how to connect to the RX2600.
Are you saying you do not have a serial cable and don't know how
to make one up ?
Are there any serial cables you can borrow ?
Simon.
--
Walking destinations on a map are further away than they appear.
The laptop does not have a serial port. I have USB to serial (M) and a F-to-F crossover cable. I plugged that into the Console serial port (serial port A).

I use Van Dyke CRT terminal emulator and configured it for 9600 baud, 8 data bits, no parity, 1 stop bit, XON/XOFF flow control, VTxxx emulation. This was from notes my predecessor left. I don't know if I have connected to right port or not on the RX2600. Should I disconnect the KVM?

Anyways I rebooted and nothing is showing.

Under Boot Options there is the selecting the consoles for Input, Output and Error. I do not see any new entries for my laptop.
Stephen Hoffman
2021-10-24 17:13:28 UTC
Permalink
Post by Dymaxion Development
I am a OpenVMS newbie and I inherited trying to determine why a system
no longer boots. It's an RX2600 running OpenVMS 8.4. The former system
manager passed away so I really do not have any resources I could call
upon.
...
See if the management processor is connected online. Ping the whole
subnet and see what answers (e.g. ping 10.20.30.255/24) and see what
answers that you do and do not know about (a temporarily-configured
switch and a completely private local network makes this easier), or
check the local hosts database or local DNS database for something that
looks like the name of an iLO IP address.

Alternatively, manually reset the iLO and re-configure it at a known
address. Instructions are in the iLO 2 manual.

If you can't find the iLO IP address, hard-reset the iLO to factory
defaults (press the iLO reset button for five or ten seconds), then use
the MAC address shown on the iLO sticker (usually looks like
mp005300005300, with the digits differing), and a command such as
arp -s 203.0.113.1 00-53-00-00-53-00
And where the IP address shown (203.0.113.1) is replaced with an
available and unused address within your local network subnet, and the
MAC shown (00-53-00-00-53-00) with the iLO MAC.
Once you have that arp entry, you can now access the iLO via the
network via that address.

If this was managed with the serial line (how quaint), then you'll be
looking for a Plugable or other PL2303{letters}-series USB-to-serial
adapter to connect into the management processor serial port. This
PL2303-series adapter would be most typical (as support for the PL2303
series chip is common across most platforms), absent some local client
computer still with a DB9 connector thatcan be used. If you have an
AlphaServer or Itanium that's working for instance, that DB9 serial
port can be used with a DB9 via SET HOST /DTE. Or a DB9 cable and a
working VT terminal, if you're also running a hardware museum as a
sideline.

Using the iLO is easier than USB adapters and the console serial line,
other posts here to the contrary. Unless you already have a box of
parts and some experience with USB serial adapters and a host app that
is compatible with the USB-to-serial serial adapter.
--
Pure Personal Opinion | HoffmanLabs LLC
Scott Dorsey
2021-10-24 18:59:33 UTC
Permalink
Post by Stephen Hoffman
Using the iLO is easier than USB adapters and the console serial line,
other posts here to the contrary. Unless you already have a box of
parts and some experience with USB serial adapters and a host app that
is compatible with the USB-to-serial serial adapter.
Sadly this is true. USB-to-serial adaptors are total disasters even
if you happen to find one that isn't counterfeit. I am fine with
serial ports and always keep some PCI serial cards around because
I have spent far too much time fighting to get a serial adaptor to work.

If you put a paperclip between pins 2 and 3, characters should be
echoed back to the screen when you type. When you remove the clip,
the characters should stop being echoed. If this is not the case
then your serial port or terminal emulator is not functioning. This
is the number one first step toward getting any serial port running.
--scott
--
"C'est un Nagra. C'est suisse, et tres, tres precis."
Dymaxion Development
2021-10-25 13:39:46 UTC
Permalink
Post by Dymaxion Development
Hi,
I am a OpenVMS newbie and I inherited trying to determine why a system no longer boots. It's an RX2600 running OpenVMS 8.4. The former system manager passed away so I really do not have any resources I could call upon.
The system starts up, loads the and see the disks...and then hangs. I cannot tell if it is waiting for an answer to a prompt or just doesn't proceed. I wanted to enable the SYSBOOT prompt to enable STARTUP_D2 to enable logging to see where it is hanging. But booting in conversational mode does the exact same thing. One of the boot options has VMS_FLAGS set to 0,1 for the same drive. And even I go into the EFI shell and set it, it hangs.
We have a backup drive which is a mirror of the system from a year ago. The MODPARAMS.DAT, AUTOPARAM.PAR and IA64VMSSYS.PAR are identical (the MODPARAMS.DAT compared via DIFF and the last two via CHECKSUM). I can successfully boot from that (we'd use it as the primary disk but it's a small drive and there is no client data on it nor would it fit). This drive also a conversational boot and it too hangs. In any case, the fact it does boot there are no hardware issues that could be preventing the system from booting.
I was hoping for tips on how to resolve being able to boot successfully or tell where in the boot process it is hanging. Or perhaps how I would go about transferring the OS from the backup disk to the primary disk.
Thanks in advance.
John
The KVM console display though it says serial is not serial, just a VGA display. Once I got a serial connection in place, it turns out the problem was that there was no VMS IA64 license in place or not found. :( It's there in the backup disk but not in the primary boot disk. As a result, the system did not continue with the boot process and just logged off.

I will copy the license from the recovery to the primary disk and see where that takes me.

Thanks to all with serial connection help and other boot process tips. You certainly gave this newbie some insight on where to go to get things working.
John Tran
2021-10-25 15:22:56 UTC
Permalink
Post by Dymaxion Development
Post by Dymaxion Development
Hi,
I am a OpenVMS newbie and I inherited trying to determine why a system no longer boots. It's an RX2600 running OpenVMS 8.4. The former system manager passed away so I really do not have any resources I could call upon.
The system starts up, loads the and see the disks...and then hangs. I cannot tell if it is waiting for an answer to a prompt or just doesn't proceed. I wanted to enable the SYSBOOT prompt to enable STARTUP_D2 to enable logging to see where it is hanging. But booting in conversational mode does the exact same thing. One of the boot options has VMS_FLAGS set to 0,1 for the same drive. And even I go into the EFI shell and set it, it hangs.
We have a backup drive which is a mirror of the system from a year ago. The MODPARAMS.DAT, AUTOPARAM.PAR and IA64VMSSYS.PAR are identical (the MODPARAMS.DAT compared via DIFF and the last two via CHECKSUM). I can successfully boot from that (we'd use it as the primary disk but it's a small drive and there is no client data on it nor would it fit). This drive also a conversational boot and it too hangs. In any case, the fact it does boot there are no hardware issues that could be preventing the system from booting.
I was hoping for tips on how to resolve being able to boot successfully or tell where in the boot process it is hanging. Or perhaps how I would go about transferring the OS from the backup disk to the primary disk.
Thanks in advance.
John
The KVM console display though it says serial is not serial, just a VGA display. Once I got a serial connection in place, it turns out the problem was that there was no VMS IA64 license in place or not found. :( It's there in the backup disk but not in the primary boot disk. As a result, the system did not continue with the boot process and just logged off.
I will copy the license from the recovery to the primary disk and see where that takes me.
Thanks to all with serial connection help and other boot process tips. You certainly gave this newbie some insight on where to go to get things working.
If you're going to use VMS for commercial purposes, you really should
become a VSI customer and subscribe to support. Get and use the latest
version of VMS.
--
David Froble Tel: 724-529-0450
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA 15486
Something to keep in mind. Apparently there are a number of legacy owncode applications there that will need to be migrated, so we are stuck at a certain version level. That decision is above my pay grade, but certainly worth recommending to do them.

Thanks for all the help!
Arne Vajhøj
2021-10-25 15:52:46 UTC
Permalink
Post by John Tran
If you're going to use VMS for commercial purposes, you really should
become a VSI customer and subscribe to support. Get and use the latest
Something to keep in mind. Apparently there are a number of legacy
owncode applications there that will need to be migrated, so we are
stuck at a certain version level. That decision is above my pay
grade, but certainly worth recommending to do them.
I would not expect:

HPE VMS 8.anything -> VSI VMS 8.4-latest

to give any problems with applications.

Arne

Loading...