ITEM: V8304L
Sysback error: 0301-150 bosboot: Invalid or no boot device specified!
Env:
AIX 3.2.5 (tape server)
AIX 4.1 (client)
Sysback 3.2.1.14
Desc:
The customer is trying to do a remote backup from an
AIX 4.1 machine to a tape drive that is on a 3.2.5
machine. Both machines have the same version of Sysback
(3.2.1.14). The backup fails and the customer receives
the message:
Rewinding device /dev/rmt0 ..
Generating Table of Contents. Please wait ..
Changing tape block size to 512 ..
Placing boot image on tape ..
0301-150 bosboot: Invalid or no boot device specified!
usage: bosboot -a [-d device] [-p proto] [-k kernel] [-l lvdev]
[-b file] [-M serv|norm|both] [-D|-I] [-LOUq]
bosboot -w file [-d device] [-q]
bosboot -r file [-d device] [-l lvdev] [-M serv|norm|both] [-q]
Where:
-a Create boot image and write to device or file.
-w file Copy given boot image file to device.
-r file Create ROS emulation network boot image.
-d device Device for which to create the boot image.
-U Create uncompressed boot image.
-p proto Use given proto file for RAM disk file system.
-k kernel Use given kernel file for boot image.
-l lvdev Target boot logical volume for boot image.
-b file Use given file name for boot image name.
-D Load Low Level Debugger.
-I Load and Invoke Low Level Debugger.
-M norm|serv|both Boot mode - normal or service.
-O offset boot image offset for CDROM file system.
-q Query disk space required to create boot image.
Action:
This error is happening because when Sysback 3.2 is backing
up an AIX 4.1 machine over a network it will build the boot
image and write it to a pseudo tape drive (rmt99) on the local
machine (4.1). This image is then copied to the remote
tape drive over the network using dd.
You will get a error if you do not have tape drive
support installed on your local 4.1 system.
The work around for this is to install
the fileset devices.scsi.tape.
Next:
Closing item.
Support Line: Sysback error: 0301-150 bosboot: Invalid or no boot device specified! ITEM: V8304L
Dated: June 1995 Category: N/A
This HTML file was generated 99/06/24~13:30:34
Comments or suggestions?
Contact us