bosboot: Boot image is 22995 512 byte blocks.

10 More Discussions You Might Find Interesting

1. AIX

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...

2. Hardware

How to Clone a Drive with 512 byte Sectors to a Drive with 4096 bytes/sector (AF)?

I have a 320 GB drive which dual boots Windows and Debian: Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal):...

3. Shell Programming and Scripting

how to split this file into blocks and then send these blocks as input to the tool called Yices?

Hello, I have a file like this: FILE.TXT: (define argc :: int) (assert ( > argc 1)) (assert ( = argc 1)) <check> # (define c :: float) (assert ( > c 0)) (assert ( = c 0)) <check> # now, i want to separate each block('#' is the delimeter), make them separate files, and then send them as...

4. UNIX for Dummies Questions & Answers

Convert 512-blocks to 4k blocks

I'm Unix. I'm looking at "df" on Unix now and below is an example. It's lists the filesystems out in 512-blocks, I need this in 4k blocks. Is there a way to do this in Unix or do I manually convert and how? So for container 1 there is 7,340,032 in size in 512-blocks. What would the 4k block be...

5. 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

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:...

7. 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: #...

8. 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...

9. 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

10. 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:

LEARN ABOUT HPUX

fscat_vxfs

fscat_vxfs(1M)															    fscat_vxfs(1M)

NAME

       fscat_vxfs: fscat - cat a VxFS file system

SYNOPSIS

       output-file] offset] length] block_size] special

DESCRIPTION

       provides an interface to a VxFS snapshot file system, similar to that provided by invoked on the block or character special file of regular
       VxFS file systems.  works when executed on the special device of any VxFS file system.

       On most VxFS file systems, the block or character special file for the file system provides access to a raw image of  the  file	system	to
       back  up  the  file system to tape.  On a snapshot file system, access to the corresponding block or character special file provides little
       useful information.  provides a stream of bytes representing the file system snapshot.  This datastream is written by default  to  standard
       output,	although  the  output-file  option can be used to specify another destination.	The datastream on standard output can be processed
       several ways, such as in a pipeline, or written to a tape.

       By default, the output is a stream of bytes that starts at the beginning of the file system and continues to the last byte.  On a  snapshot
       file  system, data is read from the file system using special ioctls on the mount point.  On other VxFS file systems, data is read from the
       specified special file.	Unless otherwise specified, data is written to standard output.

       All numbers entered as option arguments can have as a prefix to indicate octal, or as a prefix  to  indicate  hexadecimal.   A  or  can	be
       appended  to  indicate  the  value  is  in  512-byte  blocks, a or to indicate the value is in kilobytes, an or to indicate the value is in
       megabytes, or a or to indicate the value is in gigabytes.  An appended letter can be separated from the number by a space,  in  which  case
       the letter and number should be enclosed in a set of quotes. For example:

       All numbers entered as options must be in multiples of 512 bytes.  For example, a value of 5713 as an offset is rejected.

   Options
       recognizes the following options:

       Specify the output block size, in bytes.
		      block_size must be less than or equal to 1 megabyte.

       Specify the VxFS file system type.

       Specify an output file in which to write the datastream.

       Specify the transfer length, in bytes.
		      A length of includes the remainder of the file system after the specified offset.

       Specify the starting offset in bytes.

   Operands
       recognizes the following operand:

	      special	     Name of the special device from which the VxFS file system is accessed.

   Notes
       Snapshot file systems are only available with the HP OnLineJFS product.

       A snapshot file system cannot be written to.

       A snapshot file system exists only as long as it is mounted; once unmounted, the special file no longer contains a snapshot file system.

       When  is  run  on a mounted VxFS snapshot, the content of free blocks (that is, blocks not allocated to any file or metadata) is undefined.
       The content of free blocks can change after additional data is written to the primary file system, but blocks associated with files  always
       display the content they had when the snapshot was created.

       does not work with Storage Checkpoints.

SEE ALSO

       dd(1), fs_vxfs(4), vxfsio(7).

																    fscat_vxfs(1M)

AIX