Mksys / bosboot pb

[admincff]

Hi, i Encoutered this following problem when trying to save a RS/6000 F40 workgroup by mksysb command.
Has anyone encoutered this problem too ????
Thanks



mksysb -i /dev/rmt0

Creating information file (/image.data) for rootvg......

Creating tape boot image strip: shr.o -- 0654-400 Cannot open file.
No such file or directory
strip: shr.o -- 0654-400 Cannot open file.
No such file or directory
strip: shr.o -- 0654-400 Cannot open file.
No such file or directory
strip: shr.o -- 0654-400 Cannot open file.
No such file or directory
strip: shr.o -- 0654-400 Cannot open file.
No such file or directory
strip: shr.o -- 0654-400 Cannot open file.
No such file or directory

0301-154 bosboot: missing proto file: /tmp/libcfg.a

0512-016 mksysb: Attempt to create a bootable tape failed:
bosboot -d /dev/rmt0.1 -a failed with return code 41.

 

[gileb]

hi, do you have enough space in /tmp ?

 

[Ogzilal]

Hi,

It happens when you make your mksysb while some users are still working ( creating and deleting some files).
In a first step, mksysb makes a list of files to save.
In a second one, it makes the save based on the list of step 1.
If a file of the list has been deleted in between, you can experience some failure like this.

 

[bi]

Check the meaning and possible fixes for the error messages you are getting:

From IBM's error message site (

http://www16.boulder.ibm.com/pseries/en_US/infocenter/base/errorsearch.htm)

the second error code you are getting (0301-150):

Messages 0301-150 through 0301-176 are associated with the bosboot command.

And for error code 0512-016 there is a list of 5 possible causes, but none of them for return code 41. This is the list of possible causes:

The media is write-protected (return code 2).
--There is not enough space in the file systems (return code 5 or 1).
--The tape is defective (return code 11).
--The /usr/lib/boot/unix directory is damaged (0 length), or the link to the /unix directory is missing (return code 52 or 45).
--The tape drive cannot be written to or the /dev/blv/ directory cannot be read. This can be caused by an incorrect density setting for the tape-drive/tape-type/device-name combination, dirty tape drive heads, or a tape drive hardware problem.

The site gives some procedures for correcting some of the problems.


For the first error code you are getting(0654-400), it probably is caused by people being on the system.

What I find kind of odd is that your mksysb command uses device /dev/rmt0 and the error is for /dev/rmt0.1.