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 ULTRIX

tz

tz(4) Kernel Interfaces Manual tz(4)

Name
tz - SCSI magnetic tape interface

Syntax
VAX NCR 5380:
adapter uba0 at nexus?
controller scsi0 at uba0 csr 0x200c0080 vector szintr
tape tz0 at scsi0 drive 0

VAX DEC SII:
adapter ibus0 at nexus?
controller sii0 at ibus? vector sii_intr
tape tz0 at sii0 drive 0

RISC DEC SII:
adapter ibus0 at nexus?
controller sii0 at ibus? vector sii_intr
tape tz0 at sii0 drive 0

RISC DEC KZQ:
adapter uba0 at nexus?
controller kzq0 at ibus? csr 0761300vector sii_intr
tape tz0 at kzq0 drive 0

RISC NCR ASC:
adapter ibus0 at nexus?
controller asc0 at ibus? vector ascintr
tape tz0 at asc0 drive 0

Description
The SCSI tape driver provides a standard tape drive interface as described in This is a driver for any Digital SCSI tape device.

For the TZK10 QIC format tape drive, the densities supported are QIC-24 (read only) block size of 512 byte blocks, QIC-120, and QIC-150
read/write block size of 512 byte blocks, and QIC-320 read/write block size of 1024 byte blocks. With QIC format style tapes all reads and
writes must be in multiple of the block size. This is a requirement of fixed block tape drives because record boundaries are not pre-
served. The QIC densities are selected using the following special device names:

QIC-24 Fixed block size.
QIC-120 Fixed block size.
QIC-150 Fixed block size.
QIC-320 Fixed block size.

With all fixed block tape devices a of a file to the tape must be padded out. An example of this is a of which has a size of approximately
3800 bytes.
dd if=/etc/gettytab of=/dev/rmt0h bs=10k conv=sync
or
dd if=/etc/gettytab of=/dev/rmt0l bs=512 conv=sync
The option of pads the output to block size.

This driver also supports n-buffered reads and writes to the raw tape interface (used with streaming tape drives). See for further
details.

Tape Support
TZ30, TZK50, TLZ04, TSZ05, TKZ08, TZK10

Diagnostics
All diagnostic messages are sent to the error logger subsystem.

Files
See Also
mtio(4), nbuf(4), SCSI(4), MAKEDEV(8), uerf(8), tapex(8)
Guide to the Error Logger

tz(4)

AIX