SEO

Hello All,

I was able to succesfully backup bare AIX5.2 (no ML installed) with
mksysb -i -vmX /dev/rmt0 command.


After system upgrade to ML4 an attemt to create a bootable bakup
resulted in the following message:

# lsdev -Cc tape
rmt0 Available 10-89-00-0,0 Other SCSI Tape Drive
# mksysb -i -m -v -X /dev/rmt0

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

Creating tape boot image............................................. ......
bosboot: Boot image is 25356 512 byte blocks.

***** ATTENTION *****
The boot image you just created might fail to boot because
the size exceeds the system limit. For information about
fixes or workarounds, see /usr/lpp/bos.sysmgt/README.
***** ATTENTION *****

0301-161 bosboot: dd failed to copy /dev/rmt0.1.

0301-165 bosboot: WARNING! bosboot failed - do not attempt to boot
device.

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


# mt -f /dev/rmt0 rewind
/dev/rmt0: There is a request to a device or address that does not
exist.
You have mail in /usr/spool/mail/root
# lsdev -Cc tape
rmt0 Defined 10-89-00-0,0 Other SCSI Tape Drive
# mgrcfg
# lsdev -Cc tape
rmt0 Defined 10-89-00-0,0 Other SCSI Tape Drive
# cfgmgr -i /dev/rmt0
cannot open /dev/rmt0: No such device or address
Please mount volume 1 on /dev/rmt0
....and press Enter to continue installp: The specified device
/dev/rmt0
is not a valid device or file.
# lsdev -Cc tape
rmt0 Defined 10-89-00-0,0 Other SCSI Tape Drive

Does anyone has an idea of what is going on and what should be done to
make /dev/rmt0 available? Why whould bootable image exceed system
limit?


Thank you,
Alona

Is this an internal or external tape drive? If external, is it cabled to
the server and plugged in with the same scsi id as prior to the update.
I would verify the above then rmdev -l rmt0 -d
lsdev -Cc tape (should be no tape drives)
cfgmgr
If tape drive is good, you will get rmt0 back, if not, call hardware support
and have a CE come out and replace the tape drive or scsi card.
Doug

"Alona" <allab@sympatico.ca> wrote in message
news:93d97bd1.0411101521.1be892e5@posting.google.c om...
> Hello All,
>
> I was able to succesfully backup bare AIX5.2 (no ML installed) with
> mksysb -i -vmX /dev/rmt0 command.
>
>
> After system upgrade to ML4 an attemt to create a bootable bakup
> resulted in the following message:
>
> # lsdev -Cc tape
> rmt0 Available 10-89-00-0,0 Other SCSI Tape Drive
> # mksysb -i -m -v -X /dev/rmt0
>
> Creating information file (/image.data) for rootvg..
>
> Creating tape boot
image............................................. ......
> bosboot: Boot image is 25356 512 byte blocks.
>
> ***** ATTENTION *****
> The boot image you just created might fail to boot because
> the size exceeds the system limit. For information about
> fixes or workarounds, see /usr/lpp/bos.sysmgt/README.
> ***** ATTENTION *****
>
> 0301-161 bosboot: dd failed to copy /dev/rmt0.1.
>
> 0301-165 bosboot: WARNING! bosboot failed - do not attempt to boot
> device.
>
> 0512-016 mksysb: Attempt to create a bootable tape failed:
> bosboot -d /dev/rmt0.1 -a failed with return code 48.
>
>
> # mt -f /dev/rmt0 rewind
> /dev/rmt0: There is a request to a device or address that does not
> exist.
> You have mail in /usr/spool/mail/root
> # lsdev -Cc tape
> rmt0 Defined 10-89-00-0,0 Other SCSI Tape Drive
> # mgrcfg
> # lsdev -Cc tape
> rmt0 Defined 10-89-00-0,0 Other SCSI Tape Drive
> # cfgmgr -i /dev/rmt0
> cannot open /dev/rmt0: No such device or address
> Please mount volume 1 on /dev/rmt0
> ...and press Enter to continue installp: The specified device
> /dev/rmt0
> is not a valid device or file.
> # lsdev -Cc tape
> rmt0 Defined 10-89-00-0,0 Other SCSI Tape Drive
>
> Does anyone has an idea of what is going on and what should be done to
> make /dev/rmt0 available? Why whould bootable image exceed system
> limit?
>
>
> Thank you,
> Alona

"Alona" <allab@sympatico.ca> schrieb im Newsbeitrag
news:93d97bd1.0411101521.1be892e5@posting.google.c om...
> Hello All,
>
> I was able to succesfully backup bare AIX5.2 (no ML installed) with
> mksysb -i -vmX /dev/rmt0 command.
> After system upgrade to ML4 an attemt to create a bootable bakup
> resulted in the following message:
> # lsdev -Cc tape
> rmt0 Available 10-89-00-0,0 Other SCSI Tape Drive
> # mksysb -i -m -v -X /dev/rmt0
>
> Creating information file (/image.data) for rootvg..
>
> Creating tape boot
image............................................. ......
> bosboot: Boot image is 25356 512 byte blocks.
>
> ***** ATTENTION *****
> The boot image you just created might fail to boot because
> the size exceeds the system limit. For information about
> fixes or workarounds, see /usr/lpp/bos.sysmgt/README.
> ***** ATTENTION *****
>
> 0301-161 bosboot: dd failed to copy /dev/rmt0.1.
>
> 0301-165 bosboot: WARNING! bosboot failed - do not attempt to boot
> device.
>
> 0512-016 mksysb: Attempt to create a bootable tape failed:
> bosboot -d /dev/rmt0.1 -a failed with return code 48.
>
>
> # mt -f /dev/rmt0 rewind
> /dev/rmt0: There is a request to a device or address that does not
> exist.
> You have mail in /usr/spool/mail/root
> # lsdev -Cc tape
> rmt0 Defined 10-89-00-0,0 Other SCSI Tape Drive
> # mgrcfg
> # lsdev -Cc tape
> rmt0 Defined 10-89-00-0,0 Other SCSI Tape Drive
> # cfgmgr -i /dev/rmt0
> cannot open /dev/rmt0: No such device or address
> Please mount volume 1 on /dev/rmt0
> ...and press Enter to continue installp: The specified device
> /dev/rmt0
> is not a valid device or file.
> # lsdev -Cc tape
> rmt0 Defined 10-89-00-0,0 Other SCSI Tape Drive
>
> Does anyone has an idea of what is going on and what should be done to
> make /dev/rmt0 available? Why whould bootable image exceed system
> limit?
>
> Thank you,
> Alona

Hallo Alona,

better read /usr/lpp/bos.sysmgt/README as the error message suggests ;-) And
check the following link:
http://groups.google.com/groups?hl=e...x%26start%3D25

HTH,
Andreas