by Here's an interesting one for you all to have a go at!
I have (or rather had) an IBM F50 with AIX mirrored across two 4.5GB disks,
which were known as hdisk0 and hdisk2. I have a 7135 RAID array attached
via a F/W differential SCSI controller and this was configured as a single
RAID5 disk and appeared as hdisk1.
Being a good boy I painstakingly backed up my system with smitty mksysb and
selected to generate MAP files, and to generate a new image.data file.
Before going live with this system I wished to test a restore of the mksysb
tape, so I booted from it and attempted to reinstall. As soon as the
installation started it objected, saying that the disks were not the same as
they had been when the backup was made.
I tried using one of the 4.5GB disks (shown as being without a map file),
the other (with a map file), and both drives - without success. The install
failed complaining either that their was insufficient space, the LV policy
could not be kept strict enough, or indicating that there was a reference
to a non-existant disk in the image.data file.
Looking at this file in the 'limited function maintenance shell' (where did
'ls' go?) I could see that image.data referred to hdisk0 and hdisk2 but my
newly rebooted system had found the disks as hdisk0 and hdisk1. I presume
this is where it is getting confused.
Does anybody know how I can cause the system to recognise the drives with
their original hdisk numbers, or alternatively how I can modify the
image.data when I do not have access to another system with a DLT drive like
mine?
All help would be gratefully accepted.
Michael Benn
Technical Director
Datawright Computer Services Limited