restore mksysb 5.2 ml01

[nogg123]

i have a customer wants to recover an f50 running aix 5.2 ml01.

using customer cd (ml00) and tape gives after o/mounting:
Symbol _sigqueue (number 171) is not exported from dependent
module /unix.
Examine .loader section symbols with the 'dump -Tv' command.
Could not load program sleep:
Symbol resolution failed for /usr/ccs/lib/libc.a(shr.o) because:
Symbol _sigqueue (number 171) is not exported from dependent
module /unix.
Examine .loader section symbols with the 'dump -Tv' command.
Could not load program /usr/bin/sh:
Symbol resolution failed for 74 Over mounting /./usr/ccs/lib/libc.a(shr.o) because:
Symbol _sigqueue (number 171) is not exported from dependent
/unix. module
Examine .loader section symbols with the 'dump -Tv' command.
Could not load program /usr/bin/sh:
Symbol resolution failed for /usr/ccs/lib/libc.a(shr.o) because:
Symbol _sigqueue (number 171) is not exported from dependent
module /unix.
Examine .loader section symbols with the 'dump -Tv' command.
Could not load program sleep:
Symbol resolution failed for /usr/ccs/lib/libc.a(shr.o) because:
Symbol _sigqueue (number 171Could not load program ) is not exported from dependent
module /usr/bin/sh/unix:
.
Symbol resolution failed for Examine .loader section symbols with the 'dump -Tv' command.
/usr/ccs/lib/libc.a(shr.o) because:
Symbol _sigqueue (number 171) is not exported from dependent
module /unix



which is the usual rubbish if the cd does not match the tape.
========================================================

However booting from tape (f50 onto another f50 - scsi disks only) I get the following:

Approximate Elapsed time
% tasks complete (in minutes)


cp: /etc/objrepos/CuAt and /../etc/objrepos/CuAt are identical (not copied).
cp: /etc/objrepos/CuAt.vc and /../etc/objrepos/CuAt.vc are identical (not copied).
cp: /etc/objrepos/CuDep and /../etc/objrepos/CuDep are identical (not copied).
cp: /etc/objrepos/CuDv and /../etc/objrepos/CuDv are identical (not copied).
cp: /etc/objrepos/CuDvDr and /../etc/objrepos/CuDvDr are identical (not copied).
cp: /etc/objrepos/CuPath and /../etc/objrepos/CuPath are identical (not copied).
cp: /etc/objrepos/CuPath.vc and /../etc/objrepos/CuPath.vc are identical (not copied).
cp: /etc/objrepos/CuPathAt and /../etc/objrepos/CuPathAt are identical (not copied).
cp: /etc/objrepos/CuPathAt.vc and /../etc/objrepos/CuPathAt.vc are identical (not copied).
cp: /etc/objrepos/CuVPD and /../etc/objrepos/CuVPD are identical (not copied).
BOS Install: Could not copy customized device object classes to disk.
ID# OPTION
1 Continue
2 Perform System Maintenance and Then Continue
Enter ID number:


followed by bootblock not written etc.
=======================================================

I tried ml04 cd as a shot in the dark but gave similar output to 1st cd above.

Anyone got any ideas where I can go next?

 

[normntwrk]

try this
If your system fails to boot from a mksysb tape, you might have encountered a problem that can be identified and resolved with the following instructions:
Note:
This procedure does not work on machine types 7028, 7029, 7038, and 7040 and should not be used. For information about how to boot these machine types from a mksysb tape, see Alternate mksysb Solution. Affected systems include all CHRP architecture systems, beginning with the F50 model.

1. Access the firmware command line prompt, which usually appears as an option in the SMS menus.
2. At the firmware command line prompt, type the following commands:
3. setenv real-base 1000000
reset-all
The system will reboot.

Norm

 

[nogg123]

this assumes a system exists to be booted - mine is a failed install

all it did was boot the vanilla system which I installed yesterday on a different disk.

 

[RodKnowlton]

You could boot to the vanilla system and then use alt_disk_install to restore the mksysb.

- Rod


IBM Certified Advanced Technical Expert pSeries and AIX 5L
CompTIA Linux+
CompTIA Security+

Wish you could view posts with a fixed font? Got Firefox & Greasemonkey? Give yourself the option.

 

[DukeSSD]

nogg123, normntwrk's solution does not assume the system can be booted, re-read it.
the command is run from the firmware command line, not the AIX command line.
although I don't think it will fix your problem...
i think you need to order a media refresh at the same AIX version and ML as your mksysb tape.

 

[nogg123]

dukessd
i did run it from firmware ok prompt -it wouldn't work from aix would it?!

reread my comment and it says 'it couldn't boot the just failed install, as the bootlist hadn't been updated from yesterdays successful install'

i don't think there is a media set for 5.2 ml01
i don't think it is still in support
================================================
Rod
i am not sure what you mean by 'install a vanilla system (of which release?) and then use alt-disk to restore...?'

 

[RodKnowlton]

nogg123,

You said "all it did was boot the vanilla system which I installed yesterday on a different disk".

Boot that vanilla system and then use the alt_disk_install command to install your mksysb image from tape to another disk.

DukeSSD: I believe the firmware fix is for a mksysb not booting. nogg123's mksysb boots, it just won't install.

IBM Certified Advanced Technical Expert pSeries and AIX 5L
CompTIA Linux+
CompTIA Security+

Wish you could view posts with a fixed font? Got Firefox & Greasemonkey? Give yourself the option.

 

[nogg123]

'that vanilla system' is at ml00 (from the cd) so it will go the way of the cd plus tape install.

besides, how do you get a 'vanilla install' to ask for restore-a-system-backup?

what good is installing it to a different disk?
it restores all the data no problem, it just bails out with odm stuff after o/mounting.
i can't spend a lot of time trying to fix this, it was just a shot in the dark, posting it for a new clue or option to try.

 

[RodKnowlton]

'that vanilla system' is at ml00 (from the cd) so it will go the way of the cd plus tape install.

besides, how do you get a 'vanilla install' to ask for restore-a-system-backup?

Sorry, I had a bad link before. This link should show you the alt_disk_install command man page. alt_disk_install can be used on the running vanilla system to install your mksysb tape image onto another disk. To restate that, you boot and log in to your vanilla system, then run the alt_disk_install command to install the tape image to a disk other than the one you've booted from.

This could avoid the loader/symbol errors that you received before, since all commands would be run from an already running and complete instance of AIX.

- Rod


IBM Certified Advanced Technical Expert pSeries and AIX 5L
CompTIA Linux+
CompTIA Security+

Wish you could view posts with a fixed font? Got Firefox & Greasemonkey? Give yourself the option.