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 V7

hp

HP(4)							     Kernel Interfaces Manual							     HP(4)

NAME

       hp - RH-11/RP04, RP05, RP06 moving-head disk

DESCRIPTION

       The octal representation of the minor device number is encoded idp, where i is an interleave flag, d is a physical drive number, and p is a
       pseudodrive (subsection) within a physical unit.  If i is 0, the origins and sizes of the pseudodisks on each drive, counted  in  cylinders
       of 418 512-byte blocks, are:

	    disk start	   length
	    0	 0    23
	    1	 23   21
	    2	 0    0
	    3	 0    0
	    4	 44   386
	    5	 430  385
	    6	 44   367
	    7	 44   771

       If  i  is  1, the minor device consists of the specified pseudodisk on drives numbered 0 through the designated drive number.  Successively
       numbered blocks are distributed across the drives in rotation.

       Systems distributed for these devices use disk 0 for the root, disk 1 for swapping, and disk 4 (RP04/5) or disk 7 (RP06) for a mounted user
       file system.

       The  block  files  access  the disk via the system's normal buffering mechanism and may be read and written without regard to physical disk
       records.

       A `raw' interface provides for direct transmission between the disk and the user's read or write buffer.   A  single  read  or  write  call
       results	in  exactly  one I/O operation and therefore raw I/O is considerably more efficient when many words are transmitted.  The names of
       the raw files conventionally begin with an extra `r.'  In raw I/O the buffer must begin on a word boundary, and raw I/O to  an  interleaved
       device is likely to have disappointing results.

FILES

       /dev/rp?, /dev/rrp?

SEE ALSO

       rp(4)

BUGS

       In  raw	I/O  read  and	write(2) truncate file offsets to 512-byte block boundaries, and write scribbles on the tail of incomplete blocks.
       Thus, in programs that are likely to access raw devices, read, write and lseek(2) should always deal in 512-byte multiples.

       Raw device drivers don't work on interleaved devices.

																	     HP(4)

AIX