Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

problem restoring image

 
SOLVED
Go to solution
tim lloyd_1
Frequent Advisor

problem restoring image

Hi, I inherited an Itanium server running VMS 8.2 from another company. A few months ago the system disk died. And at this point I hadn't backed up the disk!

So, I created an image backup of the disk of another computer, got my hands on an old HDD of the same model and restored the tape.

I was just sort of expecting the system to boot from the hard drive but no joy. At startup I get the message:

Warning[55]: Invalid or inaccessible system ID(s)

When I boot from the hard drive I see:

PKA0.0 failed: not found

I got into the shell prompt to have a look around and I got this:

Shell> sysset
System Information:
Manufacturer: hp
Product Name: server rx2600
Product Number: AD012AF
Secondary Product Number is Inaccessible - Different
Serial number: SG45121864
Secondary Serial Number is Inaccessible - Different
UUID: FED2858F-6B20-11D9-80FA-D76B4E513EAA (Valid)
Secondary UUID is Inaccessible - Different
Product ID: 0x103

Shell>

I am guessing that there is a conflict between the image I restored and the CPU on the computer. Would this be correct? I can supply more info if required.



15 REPLIES 15
John McL
Trusted Contributor

Re: problem restoring image

What other computer did you create the image Backup on?
Was it Alpha hardware or Integrity?
Was it in a cluster or standalone?

"System ID" sounds like the [SYSn] on the new disk. Does this number (n in SYSn) match the value used when booting?
Shriniketan Bhagwat
Trusted Contributor

Re: problem restoring image

Hi,

Please post the output of below command from EFI Shell

Shell> info all

This command displays most of the server information. This is just to confirm that every thing in the server is correct.

Regards,
Ketan
tim lloyd_1
Frequent Advisor

Re: problem restoring image

The "other" computer was the same model Integrity - RX2600. It only has 2 disks while the new computer has 3.

Not sure what you mean sabout SYSn. Can you advise how I can find this pls? FYI

Shriniketan Bhagwat
Trusted Contributor

Re: problem restoring image

Hi,

Please refer below threads, which discusses about the similar problem. Here the suggestion was to contact HP support.

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1436788
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1264468

You may also want to contact HP support to fix this issue.

Regards,
Ketan

Hein van den Heuvel
Honored Contributor

Re: problem restoring image

Tim,

You may want to google for +openvms +efi +backup

And read for example:
http://labs.hoffmanlabs.com/node/343

You might need a $ SET BOOTBLOCK command.

Good luck,
Hein
Hein van den Heuvel
Honored Contributor

Re: problem restoring image

Another thought...

Do a fresh install of 8.3-1H1 and apply all patches. Nice, clean.
Next polute it some with all layered products you know you'll need.

Now 'merge' over that unbootable restored system disk.
Copy over pretty much all DAT files and non-version;1 COM files: SYSUAF, RIGHTSLIST, SYLOGICALS, LMF$LICENSE.LDB...

Good luck,
Hein
tim lloyd_1
Frequent Advisor

Re: problem restoring image

Hi, here is the result of "info all":

Shell> info all

SYSTEM INFORMATION

Date/Time: Oct 8, 2008 15:53:55 (20:08:10:08:15:53:55)
Manufacturer: hp
Product Name: server rx2600
Product Number: AD012AF
Serial Number: SG45121864
UUID: FED2858F-6B20-11D9-80FA-D76B4E513EAA
System Bus Frequency: 200 MHz

PROCESSOR MODULE INFORMATION

# of L3 L4 Family/
CPU Logical Cache Cache Model Processor
Slot CPUs Speed Size Size (hex.) Rev State
---- ------- -------- ------ ------ ------- --- ------------
0 1 1.4 GHz 1.5 MB None 1F/01 B1 Active



MEMORY INFORMATION

---- DIMM A ----- ---- DIMM B -----
DIMM Current DIMM Current
--- ------ ---------- ------ ----------
0 256MB Active 256MB Active
1 256MB Active 256MB Active
2 512MB Active 512MB Active
3 512MB Active 512MB Active
4 ---- ----
5 ---- ----

Active Memory : 3072 MB
Installed Memory : 3072 MB


I/O INFORMATION


BOOTABLE DEVICES

Order Media Type Path
----- ---------- ---------------------------------------
1 CDROM Acpi(HWP0002,0)/Pci(2|0)/Ata(Primary,Master)/CDROM(Entry0)
2 HARDDRIVE Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part1,SigC1)
3 HARDDRIVE Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part4,SigC1)




Seg Bus Dev Fnc Vendor Device Slot
# # # # ID ID # Path
--- --- --- --- ------ ------ --- -----------
00 00 01 00 0x1033 0x0035 XX Acpi(HWP0002,0)/Pci(1|0)
00 00 01 01 0x1033 0x0035 XX Acpi(HWP0002,0)/Pci(1|1)
00 00 01 02 0x1033 0x00E0 XX Acpi(HWP0002,0)/Pci(1|2)
00 00 02 00 0x1095 0x0649 XX Acpi(HWP0002,0)/Pci(2|0)
00 00 03 00 0x8086 0x1229 XX Acpi(HWP0002,0)/Pci(3|0)
00 20 01 00 0x1000 0x0030 XX Acpi(HWP0002,100)/Pci(1|0)
00 20 01 01 0x1000 0x0030 XX Acpi(HWP0002,100)/Pci(1|1)
00 20 02 00 0x14E4 0x1645 XX Acpi(HWP0002,100)/Pci(2|0)
00 E0 01 00 0x103C 0x1290 XX Acpi(HWP0002,700)/Pci(1|0)
00 E0 01 01 0x103C 0x1048 XX Acpi(HWP0002,700)/Pci(1|1)
00 E0 02 00 0x1002 0x5159 XX Acpi(HWP0002,700)/Pci(2|0)



BOOT INFORMATION

Monarch CPU:

Current Preferred
Monarch Monarch Possible Warnings
------- --------- -----------------
0 0

AutoBoot: ON - Timeout is : 10 sec

Boottest:

BOOTTEST Settings Default Variable

OS is not speedy boot aware.

Selftest Setting
--------- --------------
early_cpu Run this test
late_cpu Run this test
platform Run this test
chipset Run this test
io_hw Run this test
mem_init Run this test
mem_test Run this test

LAN Address Information:

LAN Address Path
----------------- ----------------------------------------
Mac(00110A319826) Acpi(HWP0002,0)/Pci(3|0)/Mac(00110A319826))
*Mac(00110A316707) Acpi(HWP0002,100)/Pci(2|0)/Mac(00110A316707))



FIRMWARE INFORMATION

Firmware Revision: 2.31 [4411]

PAL_A Revision: 7.31/5.37
PAL_B Revision: 5.65

SAL Spec Revision: 3.01
SAL_A Revision: 2.00
SAL_B Revision: 2.31

EFI Spec Revision: 1.10
EFI Intel Drop Revision: 14.61
EFI Build Revision: 1.22

POSSE Revision: 0.10

ACPI Revision: 7.00

BMC Revision 1.52
IPMI Revision: 1.00
SMBIOS Revision: 2.3.2a
Management Processor Revision: E.02.29


WARNING AND STOP BOOT INFORMATION

Warning[55]: Invalid or inaccessible system ID(s)

CHIP REVISION INFORMATION

Chip Logical Device Chip
Type ID ID Revision
------------------- ------- ------ --------
Memory Controller 0 122b 0023
Root Bridge 0 1229 0023
Host Bridge 0000 122e 0032
Host Bridge 0001 122e 0032
Host Bridge 0002 122e 0032
Host Bridge 0003 122e 0032
Host Bridge 0004 122e 0032
Host Bridge 0006 122e 0032
Host Bridge 0007 122e 0032
Other Bridge 0 0 0002
Other Bridge 0 0 0007
Baseboard MC 0 0 0152


Shell>

Shriniketan Bhagwat
Trusted Contributor

Re: problem restoring image

Hi Tim,

>> WARNING AND STOP BOOT INFORMATION
>> Warning[55]: Invalid or inaccessible system ID(s)

May be firmware is not up to date.

>> Secondary Product Number is Inaccessible - Different
>> Secondary Serial Number is Inaccessible - Different

As I said earlier, you may want to check with HP support.

Regards,
Ketan
tim lloyd_1
Frequent Advisor

Re: problem restoring image

sorry, I should have mentioned that both the original computer and target computer are not part of a cluster and there is no RAID involved.
Shriniketan Bhagwat
Trusted Contributor

Re: problem restoring image

Hi Tim,

In my opinion, this issue is not related to cluster or with external storage.

Regards,
Ketan
Brian Reiter
Valued Contributor
Solution

Re: problem restoring image

Tim,

I can't comment on why it won't boot the disk. The serial number problem may point to a previous motherboard replacement, I believe there are a couple of modules which need to be migrated when the board is replaced - however when I had this problem with one of my servers the machine still booted.

Have you tried adding the new disk to the boot menu? i.e. add boot device from the boot options menu. Ive found in the past that system disk swaps are not always picked up.

cheers

Brian
Shriniketan Bhagwat
Trusted Contributor

Re: problem restoring image

Hi,

>> Ive found in the past that system disk swaps are not always picked up.

This is expected in case integrity machines. Because the boot options set for the disk on one machine is different than the disk on other machine. You need to validate the boot option for the disk using the procedure sys$startup:boot_options.com (once the machine is up) after swapping the disk between the machine. This can also be done from the EFI shell using the below command.
Shell> fs0:\efi\vms\vms_bcfg.efi boot add 1 fs0:\efi\vms\vms_loader.efi "v8.3" Where fs0: is the swapped disk.

Swapping the disk from one machine to another machine will only work without re-validation if both machines have previously had boot options set for that specific disk (or copy of it).

Regards,
Ketan
Hoff
Honored Contributor

Re: problem restoring image

The two and usually three Integrity consoles (arguably three and a half, if you count POSSE) found in your box tend to be arcane. And each of the three consoles uses syntax different from the others.

Put another way, don't carry over any impressions or assumptions around how this console stuff works, as EFI is very different.

Always delete the console aliases when you're swapping disks or when you're swapping BACKUP /IMAGE contents of disks; those aliases are tied to the disk partitioning structures, and - because VMS doesn't support partitioning - it is common to end up with dangling references.

HP regularly points to the BOOT_OPTIONS procedure (and which is easy) and (for many cases( you can use the console-level (cryptic) commands to clear and then set new boot aliases.

Swapping in a system disk from another system is less preferably to reloading from distro; changing the name of a VMS host is a massive hassle. Best to clean-install, in my experience.

EFI and alias stuff:

http://labs.hoffmanlabs.com/node/392
http://labs.hoffmanlabs.com/node/724

Low-level disk structures in the PDF download here:

http://labs.hoffmanlabs.com/node/28

The invalid system id is unrelated to the disk swap; this error is a firmware/hardware-level error, and HP tends to hold this area of the EFI configuration pretty closely. See if the box is current on its firmware, upgrade it as needed, then ring up HP hardware support for assistance.

http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1264468

Reposting this, as ITRC glitched again. Apologies on dups.
tim lloyd_1
Frequent Advisor

Re: problem restoring image

Hi All, Brian's response made a lot of sense (and was a reasonably simple approach). I figured if I added something to my boot configuration I wouldn't compromise the computer.

So, I added a boot option for my new disk, promoted this to the first boot device and hey presto, I can boot.

All looks fine at the moment. I need to change the IP address and this time I will back up the disk ASAP.

I will leave this thread open for a few more days just in case something horrible happens.

Thanks to all
tim lloyd_1
Frequent Advisor

Re: problem restoring image

created a new configuration entry for the system disk. Then I could use this entry to boot