06-30-2005
What hardware, OS, backup type? Without this information your question is oo vague to be answerable.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have a SCO Openserver 5.0.6 running Raid 5. and want to make a bootable disk but the boot image is 5MB ie unix file on root is around 5M and the size is obviously too large for a floppy diskette. Please help on how I can make any bootable device. The aim is to change the filesystem size.
... (6 Replies)
Discussion started by: sshokunbi
6 Replies
2. HP-UX
Hi
All of my unix forum friends. I mirrored my hp-ux o/s disk with the help of LVM on a disk array. Can any one tell me the procedure if the O/S disk fails then how could i recover the system disk from mirrored disk
Regards'
Alam (5 Replies)
Discussion started by: waqaralam
5 Replies
3. Solaris
The second disk that I'm trying to make bootable is to hold another version of Solaris (9).
I've created the partitions with format and labeled the disk - created the filesystems with newfs - created and mounted the directories.
...but I think I've missed something out like using fdisk to... (16 Replies)
Discussion started by: pondlife
16 Replies
4. Filesystems, Disks and Memory
In our HP/Unix system, our master scsi drive was bootable and our mirrored drive was non-bootable. Are any of these alternatives possible:
1) Make the non-bootable scsi drive bootable? How?
2) Create a bootable scsi drive, then copy the mirrored data to the newly created scsi drive?
I seek... (1 Reply)
Discussion started by: bfisk
1 Replies
5. HP-UX
I am trying to copy a HP-UX disk. Both the OS and H/W are quite old
HP-UX hpeval3 B.09.10 A 9000/382 080009789a46
I have a 1.5Gb disk and a new 2Gb disk. I have been using the following method to create the copy, which must be a bootable disk.
#mediainit /dev/rdsk/cEd1s0
(2Gb disk) cEd0s0... (9 Replies)
Discussion started by: malcqv
9 Replies
6. Red Hat
Hi To All,
I Have Unfortunately Deleted my Grub,Initrd,Vmlinuz files. And am adding these files By using Rescue Mode, But it is not properly working.
Give Me a Solution.
Iam looking forward from any one.
Thanks in Advance. (1 Reply)
Discussion started by: Sharath Kumar
1 Replies
7. Linux
Can anybody suggest me software to backup Linux server and to make them boot able (1 Reply)
Discussion started by: Vit0_Corleone
1 Replies
8. Fedora
I need to boot the ultimate boot cd from an usb stick. Do I just copy the iso image to the usb key?
How do I make the usb stick bootable? (4 Replies)
Discussion started by: locoroco
4 Replies
9. UNIX for Dummies Questions & Answers
hi,
i recently built a pxe file the problem is I don't know how to add it in the pxe server.
I was wondering if you guys know how to add my pxe file in the pxe server so that when I run the device we're using, I can go lan boot then at boot: I will just type a text and it will boot the built... (0 Replies)
Discussion started by: h0ujun
0 Replies
10. Solaris
trying to do this for a DR situation. I've cloned an iSCSI LUN to another server. I've created an LDOM on it. set the LDOM to auto-boot=false and exported the LUN as a raw disk to the new LDOM. After starting the LDOM and telnetting to it. I can get to the OK prompt and see the disk but when I try... (2 Replies)
Discussion started by: os2mac
2 Replies
RL(4) Kernel Interfaces Manual RL(4)
NAME
rl - RL-11/RL01, RL02 moving-head disk
SYNOPSIS
/sys/conf/SYSTEM:
NRL rl_drives # RL01/02
/etc/dtab:
#Name Unit# Addr Vector Br Handler(s) # Comments
rl ? 174400 160 5 rlintr # rl-01/02
major device number(s):
raw: 16
block: 7
minor device encoding:
bits 0007 specify partition of RL drive
bits 0070 specify RL drive
DESCRIPTION
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. There is also a `raw' interface which 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 (even) boundary, and counts should be a multiple of 512 bytes (a disk sector). Likewise seek
calls should specify a multiple of 512 bytes.
DISK SUPPORT
The RL01 drives are each 10240 blocks long and the RL02 drives are 20480 blocks long.
On a RL02 there is room for a full sized root ('a') partition and a reasonable sized swap ('b') partition. The RL01 can only (realisti-
cally) have a single 5mb partition.
FILES
/dev/rl[0-3][a-h] block files
/dev/rrl[0-3][a-h] raw files
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
SEE ALSO
hk(4), ra(4), ram(4), rk(4), rp(4), rx(4), si(4), xp(4), dtab(5), autoconfig(8)
DIAGNOSTICS
rl%d: hard error sn%d cs=%b da=%b. An unrecoverable error occurred during transfer of the specified sector of the specified disk. The
contents of the two error registers are also printed in octal and symbolically with bits decoded. The error was either unrecoverable, or a
large number of retry attempts could not recover the error.
rl%d: hard error sn%d mp=%b da=%b. An unrecoverable drive error occured during transfer of the specified sector of the specified disk.
The contents of the two error registers are also printed in octal and symbolically with bits decoded. The error was either unrecoverable,
or a large number of retry attempts could not recover the error.
rl%d: write locked. The write protect switch was set on the drive when a write was attempted. The write operation is not recoverable.
rl%d: can't get status. A ``get status'' command on the specified drive failed. The error is unrecoverable.
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.
DEC-standard error logging should be supported.
A program to analyze the logged error information (even in its present reduced form) is needed.
3rd Berkeley Distribution August 20, 1987 RL(4)