Re: bosboot error
This sounds like a permission's issue. Were you logged in as root? Regards Neil Sharp [EMAIL PROTECTED], Technical Support TSM Consultant Direct Line : 01256-306686 Mobile: 07811-199312 Office : 01256-811125 Ext 223 Syan Limited, Riverside View, Basing Road,Old Basing, Basingstoke, Hampshire, RG24 7AL Lawrence McMahon [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu 23/11/2005 19:13 Please respond to ADSM: Dist Stor Manager ADSM-L@vm.marist.edu To ADSM-L@vm.marist.edu cc Subject bosboot error Hi; I'm trying to install TSM 5.3.0.0 on 2 new p550 9113 machines to replace our current machines. I have AIX 5.3.2 installed. I tried to install TSM, and got the following. I talked to IBM, and they said they thought it might be a problem with TSM, but I don't see how. They are suggesting I reinstall AIX, and try again. Does anyone have any ideas what might cause this, and whey does the TSM install do a bosboot? Installing TSM 5.3.0.0 Finished processing all filesets. (Total time: 2 mins 0 secs). 0503-409 installp: bosboot verification starting... installp: bosboot verification completed. 0503-408 installp: bosboot process starting... 0301-101 /usr/lib/boot/bin/mkboot_chrp: Device open failure: /tmp/bosboot_23854_ /unix_15463.Z 0301-158 bosboot: mkboot failed to create bootimage. 0301-165 bosboot: WARNING! bosboot failed - do not attempt to boot device. The installation or updating script is unable to continue 0503-407 installp: An error occurred during bosboot processing. Please correct the problem and rerun installp. +--- --+ Summaries: +--- --+ Installation Summary NameLevel PartEvent Result --- tivoli.tsm.server.com 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.server.com 5.3.0.0 ROOTAPPLY SUCCESS tivoli.tsm.server.aix5.rte6 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.server.aix5.rte6 5.3.0.0 ROOTAPPLY SUCCESS tivoli.tsm.msg.en_US.server 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.loc.server.ela 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.license.cert 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.license.aix5.rte 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.devices.aix5.rte 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.devices.aix5.rte 5.3.0.0 ROOTAPPLY SUCCESS tivoli.tsm.server.webcon5.3.0.0 USR APPLY SUCCESS tivoli.tsm.msg.en_US.device 5.3.0.0 USR APPLY SUCCESS Lawrence McMahon Senior Programmer Analyst 341 Computing Center, North Campus 645-3579
bosboot error
Hi; I'm trying to install TSM 5.3.0.0 on 2 new p550 9113 machines to replace our current machines. I have AIX 5.3.2 installed. I tried to install TSM, and got the following. I talked to IBM, and they said they thought it might be a problem with TSM, but I don't see how. They are suggesting I reinstall AIX, and try again. Does anyone have any ideas what might cause this, and whey does the TSM install do a bosboot? Installing TSM 5.3.0.0 Finished processing all filesets. (Total time: 2 mins 0 secs). 0503-409 installp: bosboot verification starting... installp: bosboot verification completed. 0503-408 installp: bosboot process starting... 0301-101 /usr/lib/boot/bin/mkboot_chrp: Device open failure: /tmp/bosboot_23854_ /unix_15463.Z 0301-158 bosboot: mkboot failed to create bootimage. 0301-165 bosboot: WARNING! bosboot failed - do not attempt to boot device. The installation or updating script is unable to continue 0503-407 installp: An error occurred during bosboot processing. Please correct the problem and rerun installp. +--- --+ Summaries: +--- --+ Installation Summary NameLevel PartEvent Result --- tivoli.tsm.server.com 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.server.com 5.3.0.0 ROOTAPPLY SUCCESS tivoli.tsm.server.aix5.rte6 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.server.aix5.rte6 5.3.0.0 ROOTAPPLY SUCCESS tivoli.tsm.msg.en_US.server 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.loc.server.ela 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.license.cert 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.license.aix5.rte 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.devices.aix5.rte 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.devices.aix5.rte 5.3.0.0 ROOTAPPLY SUCCESS tivoli.tsm.server.webcon5.3.0.0 USR APPLY SUCCESS tivoli.tsm.msg.en_US.device 5.3.0.0 USR APPLY SUCCESS Lawrence McMahon Senior Programmer Analyst 341 Computing Center, North Campus 645-3579
Re: bosboot error
Hi Lawrence, Does /tmp have enough free space to hold the boot image? Does a bosboot -a give the same results? Is the rootvg mirrored? Any stale partitions then? Met vriendelijke groet, With kind regards, Richard van Denzel. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Lawrence McMahon Sent: woensdag 23 november 2005 20:14 To: ADSM-L@VM.MARIST.EDU Subject: bosboot error Hi; I'm trying to install TSM 5.3.0.0 on 2 new p550 9113 machines to replace our current machines. I have AIX 5.3.2 installed. I tried to install TSM, and got the following. I talked to IBM, and they said they thought it might be a problem with TSM, but I don't see how. They are suggesting I reinstall AIX, and try again. Does anyone have any ideas what might cause this, and whey does the TSM install do a bosboot? Installing TSM 5.3.0.0 Finished processing all filesets. (Total time: 2 mins 0 secs). 0503-409 installp: bosboot verification starting... installp: bosboot verification completed. 0503-408 installp: bosboot process starting... 0301-101 /usr/lib/boot/bin/mkboot_chrp: Device open failure: /tmp/bosboot_23854_ /unix_15463.Z 0301-158 bosboot: mkboot failed to create bootimage. 0301-165 bosboot: WARNING! bosboot failed - do not attempt to boot device. The installation or updating script is unable to continue 0503-407 installp: An error occurred during bosboot processing. Please correct the problem and rerun installp. +--- + --+ Summaries: +--- + --+ Installation Summary NameLevel PartEvent Result --- tivoli.tsm.server.com 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.server.com 5.3.0.0 ROOTAPPLY SUCCESS tivoli.tsm.server.aix5.rte6 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.server.aix5.rte6 5.3.0.0 ROOTAPPLY SUCCESS tivoli.tsm.msg.en_US.server 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.loc.server.ela 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.license.cert 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.license.aix5.rte 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.devices.aix5.rte 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.devices.aix5.rte 5.3.0.0 ROOTAPPLY SUCCESS tivoli.tsm.server.webcon5.3.0.0 USR APPLY SUCCESS tivoli.tsm.msg.en_US.device 5.3.0.0 USR APPLY SUCCESS Lawrence McMahon Senior Programmer Analyst 341 Computing Center, North Campus 645-3579
Re: bosboot error
Richard, Yes, /tmp has space. /dev/hd3 786432608948 23% 134 1% /tmp (I should mention that this worked fine on the other machine with the same ammount of /tmp. The only difference is that after I ran into this problem; at IBM's suggestion I upgraded the AIX to V 5.3.3 on the other server, and then did the TSM install there with no problem.) bosboot -a gives the exact same results. In working with IBM, they had me break the mirror, re-mirror, relink the ipl_device, delete and reset up hd5, and I still get the same results. That's why they are suggesting to re-install AIX. rootvg is currently re-mirrored, with no stale partitions. thanks, Larry McMahon Richard van Denzel writes: Hi Lawrence, Does /tmp have enough free space to hold the boot image? Does a bosboot -a give the same results? Is the rootvg mirrored? Any stale partitions then? Met vriendelijke groet, With kind regards, Richard van Denzel. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Lawrence McMahon Sent: woensdag 23 november 2005 20:14 To: ADSM-L@VM.MARIST.EDU Subject: bosboot error Hi; I'm trying to install TSM 5.3.0.0 on 2 new p550 9113 machines to replace our current machines. I have AIX 5.3.2 installed. I tried to install TSM, and got the following. I talked to IBM, and they said they thought it might be a problem with TSM, but I don't see how. They are suggesting I reinstall AIX, and try again. Does anyone have any ideas what might cause this, and whey does the TSM install do a bosboot? Installing TSM 5.3.0.0 Finished processing all filesets. (Total time: 2 mins 0 secs). 0503-409 installp: bosboot verification starting... installp: bosboot verification completed. 0503-408 installp: bosboot process starting... 0301-101 /usr/lib/boot/bin/mkboot_chrp: Device open failure: /tmp/bosboot_23854_ /unix_15463.Z 0301-158 bosboot: mkboot failed to create bootimage. 0301-165 bosboot: WARNING! bosboot failed - do not attempt to boot device. The installation or updating script is unable to continue 0503-407 installp: An error occurred during bosboot processing. Please correct the problem and rerun installp. +--- + --+ Summaries: +--- + --+ Installation Summary NameLevel PartEvent Result --- tivoli.tsm.server.com 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.server.com 5.3.0.0 ROOTAPPLY SUCCESS tivoli.tsm.server.aix5.rte6 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.server.aix5.rte6 5.3.0.0 ROOTAPPLY SUCCESS tivoli.tsm.msg.en_US.server 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.loc.server.ela 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.license.cert 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.license.aix5.rte 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.devices.aix5.rte 5.3.0.0 USR APPLY SUCCESS tivoli.tsm.devices.aix5.rte 5.3.0.0 ROOTAPPLY SUCCESS tivoli.tsm.server.webcon5.3.0.0 USR APPLY SUCCESS tivoli.tsm.msg.en_US.device 5.3.0.0 USR APPLY SUCCESS Lawrence McMahon Senior Programmer Analyst 341 Computing Center, North Campus 645-3579 Lawrence McMahon Senior Programmer Analyst 341 Computing Center, North Campus 645-3579
Re: bosboot error
On Nov 23, 2005, at 3:01 PM, Lawrence McMahon wrote: Yes, /tmp has space. /dev/hd3 786432608948 23% 134 1% /tmp Well, it has space at the time the 'df' command was issued; but it may have run out of space during an operation, and as part of operation recovery, the operation may have removed the partial work from /tmp. I would check the AIX Error Log, where AIX usually creates an entry (e.g., JFS_FS_FULL) when a file system has filled. Also try the bosboot -q option. Richard Sims
Re: bosboot error
Richard, Nothing in the error log. # bosboot -a -q Filesystem KB required /tmp20582 # df -k |grep /tmp /dev/hd3 786432608948 23% 134 1% /tmp Larry Richard Sims writes: On Nov 23, 2005, at 3:01 PM, Lawrence McMahon wrote: Yes, /tmp has space. /dev/hd3 786432608948 23% 134 1% /tmp Well, it has space at the time the 'df' command was issued; but it may have run out of space during an operation, and as part of operation recovery, the operation may have removed the partial work from /tmp. I would check the AIX Error Log, where AIX usually creates an entry (e.g., JFS_FS_FULL) when a file system has filled. Also try the bosboot -q option. Richard Sims Lawrence McMahon Senior Programmer Analyst 341 Computing Center, North Campus 645-3579
Re: bosboot error
Richard,
Nothing in the error log.
# bosboot -a -q
Filesystem KB required
/tmp20582
# df -k |grep /tmp
/dev/hd3 786432608948 23% 134 1% /tmp
Here's the problem. Notice how it complains it can't open
/tmp/bosboot_67756_18272/unix_1704.Z? If I do repeated ls's on that dir
as the command runs, I see this:
(3:43pm)[new-tsmserver1]{/tmp} sudo ls -al bosboot*
total 40616
drwx-- 2 root system 512 Nov 23 15:42 .
drwxrwxrwt 12 bin bin1536 Nov 23 15:42 ..
-rw-r--r-- 1 root system 7660080 Nov 23 15:42 Bootram.fs
-r-xr-xr-x 1 root system 10485742 Nov 23 15:42 unix_1704
-rw--- 1 root system 2637824 Nov 23 15:43 unix_1704.gz
and on the working server:
(3:44pm)[new-tsmserver2]{/tmp} sudo ls -al bosboot*
total 23648
drwx-- 2 root system 512 Nov 23 15:44 .
drwxrwxrwt 11 bin bin2048 Nov 23 15:44 ..
-rw-r--r-- 1 root system 7460981 Nov 23 15:44 Bootram.fs
-r 1 root system12485 Nov 23 15:44 bootinfo.txt
-rw-r--r-- 1 root system0 Nov 23 15:44 dd.out
-rw-r--r-- 1 root system 153 Nov 23 15:44 filesystems
-rw-r--r-- 1 root system0 Nov 23 15:44 mkboot.out
-r-xr-xr-x 1 root system 4614307 Nov 23 15:44 unix_3950.Z
So, it's using gzip, but expecting compress?
mmmso, why the difference? How does it decide what compression
program to use?
Larry
Richard Sims writes:
On Nov 23, 2005, at 3:01 PM, Lawrence McMahon wrote:
Yes, /tmp has space.
/dev/hd3 786432608948 23% 134 1% /tmp
Well, it has space at the time the 'df' command was issued; but it
may have run out of space during an operation, and as part of
operation recovery, the operation may have removed the partial work
from /tmp.
I would check the AIX Error Log, where AIX usually creates an entry
(e.g., JFS_FS_FULL) when a file system has filled. Also try the
bosboot -q option.
Richard Sims
Lawrence McMahon
Senior Programmer Analyst
341 Computing Center, North Campus
645-3579
Steve Roder
University at Buffalo
([EMAIL PROTECTED] | (716)645-3564)
Re: bosboot error
On Wed, 23 Nov 2005, Steve Roder wrote:
Richard,
Nothing in the error log.
# bosboot -a -q
Filesystem KB required
/tmp20582
# df -k |grep /tmp
/dev/hd3 786432608948 23% 134 1% /tmp
.
The failing machine:
(4:06pm)[new-tsmserver1]{~} ls -al /usr/bin/gzip
lrwxrwxrwx 1 root system 26 Jul 27 14:53 /usr/bin/gzip -
/usr/opt/freeware/bin/gzip
(4:06pm)[new-tsmserver1]{~} ls -al /usr/bin/compress
-rwxr-xr-x 3 bin bin 66303 Nov 20 2002 /usr/bin/compress
It could be in the shell, but what is strange is the working server has
the same link for gzip, but a very different compress:
4:11pm)[new-tsmserver2]{~} ls -al /usr/bin/gzip
lrwxrwxrwx 1 root system 26 Jul 27 08:13 /usr/bin/gzip -
/usr/opt/freeware/bin/gzip
(4:11pm)[new-tsmserver2]{~} ls -al /usr/bin/compress
-r-xr-xr-x 3 bin bin 17498 Jul 27 08:09 /usr/bin/compress
They are at different ML levels (ML02 on the broken one, ML03 on the
working one), but the one that works did not have this issue on ML02.
By copying /usr/bin/compress from the working machine to the broken
machine, I was able to run bosboot -a.
So, the problem is fixed, but how did it get to this state? IBM did the
AIX pre-installs.
thinking about a fresh reinstall..
:-)
Here's the problem. Notice how it complains it can't open
/tmp/bosboot_67756_18272/unix_1704.Z? If I do repeated ls's on that dir
as the command runs, I see this:
(3:43pm)[new-tsmserver1]{/tmp} sudo ls -al bosboot*
total 40616
drwx-- 2 root system 512 Nov 23 15:42 .
drwxrwxrwt 12 bin bin1536 Nov 23 15:42 ..
-rw-r--r-- 1 root system 7660080 Nov 23 15:42 Bootram.fs
-r-xr-xr-x 1 root system 10485742 Nov 23 15:42 unix_1704
-rw--- 1 root system 2637824 Nov 23 15:43 unix_1704.gz
and on the working server:
(3:44pm)[new-tsmserver2]{/tmp} sudo ls -al bosboot*
total 23648
drwx-- 2 root system 512 Nov 23 15:44 .
drwxrwxrwt 11 bin bin2048 Nov 23 15:44 ..
-rw-r--r-- 1 root system 7460981 Nov 23 15:44 Bootram.fs
-r 1 root system12485 Nov 23 15:44 bootinfo.txt
-rw-r--r-- 1 root system0 Nov 23 15:44 dd.out
-rw-r--r-- 1 root system 153 Nov 23 15:44 filesystems
-rw-r--r-- 1 root system0 Nov 23 15:44 mkboot.out
-r-xr-xr-x 1 root system 4614307 Nov 23 15:44 unix_3950.Z
So, it's using gzip, but expecting compress?
mmmso, why the difference? How does it decide what compression
program to use?
Larry
Richard Sims writes:
On Nov 23, 2005, at 3:01 PM, Lawrence McMahon wrote:
Yes, /tmp has space.
/dev/hd3 786432608948 23% 134 1% /tmp
Well, it has space at the time the 'df' command was issued; but it
may have run out of space during an operation, and as part of
operation recovery, the operation may have removed the partial work
from /tmp.
I would check the AIX Error Log, where AIX usually creates an entry
(e.g., JFS_FS_FULL) when a file system has filled. Also try the
bosboot -q option.
Richard Sims
Lawrence McMahon
Senior Programmer Analyst
341 Computing Center, North Campus
645-3579
Steve Roder
University at Buffalo
([EMAIL PROTECTED] | (716)645-3564)
Steve Roder
University at Buffalo
([EMAIL PROTECTED] | (716)645-3564)
