Sponsored Content
Full Discussion: Boot image for VIO
Operating Systems AIX Boot image for VIO Post 302543371 by jpmei on Sunday 31st of July 2011 10:46:29 AM
Old 07-31-2011
Boot image for VIO

i've installed vios 2.2 on blade PS700
there are 2 disk, hdisk0 dan hdisk1 and i want to mirror it
but blv (boot logic volume) does not appear on hdisk1 (bootlist -mode normal -ls) only on hdisk0
i've already did command (bootlist -mode normal hdisk0 hdisk1"

does anyone know the command to create boot image just like bosboot on AIX

thanks
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Boot Diskette Image

Where can I find the boot floppy disk image file(*.vfd)of SCO UNIX 5.0.5?:confused: (1 Reply)
Discussion started by: whiteknight
1 Replies

2. AIX

mksysb and boot.image

hello i saved my system this morning, mksysb tape, and i have the message: "boot.image exceeded the size....." i have not the end because the message is disappeared. where can i find the mksysb message in a log ? the message is scary ? thank you (6 Replies)
Discussion started by: pascalbout
6 Replies

3. AIX

bosboot: Boot image is 22995 512 byte blocks.

My mksysb scripts gives the following text on standard error: bosboot: Boot image is 22995 512 byte blocks. How come on a Aix 5200-07 aix-system. I thought this message meant that the tape (/dev/rmt0) is not bootable, but I read about a limit of 12 MB and 22995 block is less than 12 MB ... (0 Replies)
Discussion started by: frankwiel
0 Replies

4. AIX

has bosboot command changed characteristics of boot image?

hi all i just found one of my p650 server showing a warning message when i tried to run bosboot command after upgrading TL to AIX 530803. i also tried to run chpv -c hdisk0 and chpv -c hdisk1 to clear out the old boot info in hdisk0 and hdisk1 and rerun bosboot -a. it still showed... (0 Replies)
Discussion started by: rs6000er
0 Replies

5. Red Hat

redhat xen will not boot winXP cdrom image

I'm running redhat linux: 2.6.18-128.1.6.el5xen #1 SMP Tue Mar 24 12:28:27 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux as my Dom0. I have several other DomU's running on this system, but for this test I've shut them down. I'm attempting to boot winXP from an image. Here is my config file: #... (3 Replies)
Discussion started by: willjw1
3 Replies

6. Filesystems, Disks and Memory

Boot Sequence changed After Image Restore

Hello All, I backed up my RHEL 4 as an image. Then I restored the image on my machine. Everything went fine but I dont get the normal boot sequence as it used to come when I freshly installed RHEL4. The messages that are shown when the system boots are something like- " ..... EXT3-fs:... (2 Replies)
Discussion started by: shamik
2 Replies

7. AIX

vio server and vio client

Hi, I want to know wheather partition size for installation of vio client can be specified on vio server example If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Discussion started by: manoj.solaris
1 Replies

8. UNIX for Advanced & Expert Users

Making one binary image containing boot loader and linux

Hi, I want to have one binary image that contains both my boot loader as well as the OS(linux) image at pre defined offsets which i can use to program flash . Can anyone help in this direction? Regards Subrata (0 Replies)
Discussion started by: subratasaharia
0 Replies

9. Solaris

flar restore with svm mirrors failing to create boot image

In a Solaris9 environment I'm trying to restore flash archive (flar) with SVM mirrored devices to same server via jumpstart server and it is failing to create boot file and drops down to a command prompt in single user mode, metastat -i and metastat -p output looks good when compared to the ones... (0 Replies)
Discussion started by: mbak
0 Replies

10. AIX

vio server ethernet to vio client ethernet(concepts confusing)

Hi In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID. Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies
installboot(1M) 														   installboot(1M)

NAME
installboot - install bootblocks in a disk partition SYNOPSIS
installboot bootblk raw-disk-device The boot(1M) program, ufsboot, is loaded from disk by the bootblock program which resides in the boot area of a disk partition. The ufs boot objects are platform-dependent, and reside in the /usr/platform/platform-name/lib/fs/ufs directory. The platform name can be found using the -i option of uname(1). The installboot utility is a SPARC only program. It is not supported on the architecture. users should use installgrub(1M) instead. bootblk The name of the bootblock code. raw-disk-device The name of the disk device onto which the bootblock code is to be installed; it must be a character device which is read- able and writable. Naming conventions for a SCSI or IPI drive are c?t?d?s? and c?d?s? for an IDE drive. Example 1: Installing UFS Boot Block To install a ufs boot block on slice 0 of target 0 on controller 1 of the platform where the command is being run, use: example# installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c1t0d0s0 /usr/platform/platform-name/lib/fs/ufs directory where ufs boot objects reside. /platform/platform-name/ufsboot second level program to boot from a disk or CD See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ od(1), uname(1), boot(1M), init(1M), kadb(1M), kernel(1M), monitor(1M), reboot(1M), rpc.bootparamd(1M), init.d(4), attributes(5) WARNINGS
The installboot utility fails if the bootblk or openfirmware files do not exist or if the raw disk device is not a character device. 11 Apr 2005 installboot(1M)
All times are GMT -4. The time now is 03:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy