ITEM: BE2727L
Network install sysback lsdev errors
Env:
AIX 4.1.4 for all the nodes
RISC SP2
sysback 3.3.1.19
Desc:
Customer is unable to install over the network from a sysback
full system backup. The customer boots over ethernet network
from the server
Gets these error message prior to the main menu:
lsdev: 0514-521 Cannot find information in the predefined device
configuration database for the customized device rmt0
lsdev: 0514-521 Cannot find information in the predefined device
configuration database for the customized device rmt1
lsdev: 0514-521 Cannot find information in the predefined device
configuration database for the customized device rmt2
lsdev: 0514-521 Cannot find information in the predefined device
configuration database for the customized device rmt3
lsdev: 0514-521 Cannot find information in the predefined device
configuration database for the customized device TMPCP0
lsdev: 0514-521 Cannot find information in the predefined device
configuration database for the customized device hdisk0
lsdev: 0514-521 Cannot find information in the predefined device
configuration database for the customized device hdisk1
lsdev: 0514-521 Cannot find information in the predefined device
configuration database for the customized device hdisk2
lsdev: 0514-521 Cannot find information in the predefined device
configuration database for the customized device hdisk3
The client has these tape drives on it.
I repeat these are on the client system not the server system
rmt0 - 3490, rmt1 and rmt2 - 7gb (7133) and rmt3 - 3490 on a
fast/wide adapter.
hdisk0 2.2gb, hdisk1, hdisk2 and hdisk3 are 4.5gb on a
fast/wide scsi adapter.
TMPCP0 is a controller point for the SP2
I noticed the customer does not have the Atape.driver code on
the server, but does have the support for all the hdisk\# on it.
Also when we start the install we get this message:
Making rootvg
Unable to make hdisk0 a Physical Volume.
We choose to continue and it created the lvs
and failed on the filesystems with this error message:
fshop_make: requested filesystem is bigger than the LV
I then tried to boot from just tape, The ram filesystem is 100%
full. Looks like the other problem you descripted to me today
about loading all the devices and running out of ram filesystem.
The customer is going to send me a mksysb of the server and a
sysback of the client on tape (5gb 8mm). On thing to note
when we ran the df in service mode from the client after a
network boot it showed about 60% full.
Action:
Both fix 3.3.1.22 and 3.3.1.23 will address the issue from booting
from a tape and booting from network boot image. Sending
3.3.1.23 to the customer via profs.
22 AIX 4.1.4 Sysback tapes will not boot properly if all
device support was installed on the system prior to
creating the backup. Results in numerous "out of space"
messages in the installation menus.
Workaround: Change the following file prior to performing
the backup. A new boot tape may also be created which
will allow restoration from an older tape.
/usr/lib/boot/{platform}.tape.proto (where platform is
the platform type)
Change line 1, "13312" to "16384". This will increase
the size if the RAM filesystem used in maintenance
mode to restore the installation files.
23 Above change applied also to network boot images.
If all device support installed on server, client
gets error messages from "lsdev" command before the
menus appear.
Workaround: Change first line in
/usr/lib/boot/network/*.*.proto files from 8196 to
16384, then rebuild network boot images.
Next Action:
Closing with customer approval
Support Line: Network install sysback lsdev errors ITEM: BE2727L
Dated: May 1996 Category: N/A
This HTML file was generated 99/06/24~13:30:22
Comments or suggestions?
Contact us