Sponsored Content
Full Discussion: How to make a bootable disk?
Operating Systems Solaris How to make a bootable disk? Post 302102711 by reborg on Friday 12th of January 2007 08:57:46 AM
Old 01-12-2007
What architecture?
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Bootable disk

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. UNIX for Dummies Questions & Answers

recover DIsk and make bootable

Hello all, I'm trying to recover from backup file to a new system with a new disk. I'm able to partition my new hard drive the same way as my old drive, but I'm unable to boot off of it. I have set the fdisk to toogle as a boot flag. But it does not seem to be working. Does anyone know how to... (4 Replies)
Discussion started by: larryase
4 Replies

3. Solaris

iso files to make bootable dvd image

Hey all, I'm a newbie to iso files and I just downloaded the 2 iso files for *cough* ms2003 R2 *cough* trial software. After I downloaded the iso files I just dragged them to my burn software gui and sure enough it burned to dvd 2 iso files. When I attempted to boot the image using VMware... (0 Replies)
Discussion started by: bdsffl
0 Replies

4. Filesystems, Disks and Memory

Make non-bootable scsi drive, bootable

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

Creating a bootable disk in 9.10

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

Linux make bootable archive

Can anybody suggest me software to backup Linux server and to make them boot able (1 Reply)
Discussion started by: Vit0_Corleone
1 Replies

7. Fedora

make bootable usb from iso

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

8. UNIX for Dummies Questions & Answers

how to make pxe file bootable

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

9. Solaris

Make an iSCSI LUN clone bootable

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

10. SuSE

How To make bootable USB with multiple ISO Files?

Hi All, I would need your assistance to make a bootable USB with SUSE LINUX Enterprise Server I have already downloaded relevant OS (Trail Version) packages @ 1) SLES-11-SP4-DVD-i586-GM-DVD1 2) SLES-11-SP4-DVD-i586-GM-DVD2 when I tried to open these packages with PowerISO one of the... (7 Replies)
Discussion started by: Leaner_963
7 Replies
restore(1M)															       restore(1M)

NAME
restore, rrestore - restore file system incrementally, local or across network SYNOPSIS
key [name ...] key [name ...] DESCRIPTION
The and commands read tapes previously dumped by the or command (see dump(1M) and rdump(1M)). Actions taken are controlled by the key argument where key is a string of characters containing not more than one function letter and pos- sibly one or more function modifiers. One or more name arguments, if present, are file or directory names specifying the files that are to be restored. Unless the modifier is specified (see below), the appearance of a directory name refers to the files and (recursively) subdi- rectories of that directory. Function Portion of key The function portion of the key is specified by one of the following letters: Read the tape and load into the current directory. should be used only after careful consideration, and only to restore a complete dump tape onto a clear file system, or to restore an incremental dump tape after a full level zero restore. Thus, is a typical sequence to restore a complete dump. Another or can then be performed to restore an incremental dump on top of this. Note that and leave a file in the root directory of the file system to pass information between incremental restore passes. This file should be removed when the last incremental tape has been restored. A or followed by a and a or is used to change the size of a file system (see newfs(1M)). and request a particular tape of a multivolume set on which to restart a full restore (see above). This provides a means for interrupting and restarting and Extract the named files from the tape. If the named file matches a directory whose contents had been written onto the tape, and the modifier is not specified, the directory is recursively extracted. The owner, modification time, and mode are restored (if possible). If no file argument is given, the root directory is extracted, which results in the entire contents of the tape being extracted, unless has been specified. Names of the specified files are listed if they occur on the tape. If no file argument is given, the root directory is listed, which results in the entire content of the tape being listed, unless has been specified. The next argument to is used as the dump file number to recover. This is useful if there is more than one dump file on a tape. This mode allows interactive restoration of files from a dump tape. After reading in the directory information from the tape, and provide a shell-like interface that allows the user to move around the directory tree selecting files to be extracted. The available commands are given below; for those commands that require an argument, the default is the current directory. The current directory or specified argument is added to the list of files to be extracted. If a directory is specified, it and all its descendents are added to the extraction list (unless the key is specified on the command line). File names on the extraction list are displayed with a leading when listed by Change the current working directory to the specified argument. The current directory or specified argument is deleted from the list of files to be extracted. If a directory is specified, it and all its descendents are deleted from the extraction list (unless is specified on the command line). The most expedient way to extract files from a directory is to add the directory to the extraction list, then delete unnecessary files. All files named on the extraction list are extracted from the dump tape. and ask which volume the user wants to mount. The fastest way to extract a few files is to start with the last volume, then work toward the first volume. List a summary of the available commands. List the current or specified directory. Entries that are directories are displayed with a trailing Entries marked for extraction are displayed with a leading If the verbose key is set, the inode number of each entry is also listed. Print the full path name of the current working directory. and immediately exit, even if the extraction list is not empty. Set the owner, modes, and times of all directories that are added to the extraction list. Nothing is extracted from the tape. This setting is useful for clean- ing up after a restore aborts prematurely. The sense of the modifier is toggled. When set, the verbose key causes the command to list the inode numbers of all entries. It also causes and to print out information about each file as it is extracted. Function Modifiers The following function modifier characters can be used in addition to the letter that selects the function desired: Specify the block size of the tape in kilobytes. If the option is not specified, and try to determine the tape block size dynamically. Specify the name of the archive instead of If the name of the file is reads from standard input. Thus, and can be used in a pipeline to dump and restore a file system with the command When using this key should be specified, and the next argument supplied should be of the form Extract the actual directory, rather than the files to which it refers. This prevents hierarchical restoration of complete subtrees from the tape, rather than the files to which it refers. Extract by inode numbers rather than by file name. This is useful if only a few files are being extracted and one wants to avoid regenerating the complete path name to the file. Type the name of each file and treat, preceded by its file type. Normally and do their work silently; the modifier specifies verbose output. Do not ask whether to abort the operation if and encounters a tape error. and attempt to skip over the bad tape block(s) and continue. creates a server, either or on the remote machine to access the tape device. DIAGNOSTICS
and complain about bad key characters. and complain if a read error is encountered. If the modifier has been specified, or the user responds and attempt to continue the restore. If the dump extends over more than one tape, and ask the user to change tapes. If the or function has been specified, and also ask which volume the user wants to mount. The fastest way to extract a few files is to start with the last volume and work towards the first volume. There are numerous consistency checks that can be listed by and Most checks are self-explanatory or can ``never happen''. Here are some common errors: The specified file name was listed in the tape directory but not found on the tape. This is caused by tape read errors while looking for the file, and from using a dump tape created on an active file system. A file not listed in the directory showed up. This can occur when using a dump tape created on an active file system. When doing an incremental restore, a tape that was written before the previous incremental tape, or that has too low an incremental level has been loaded. When doing an incremental restore, a tape that does not begin its coverage where the previous incremental tape left off, or that has too high an incremental level has been loaded. A tape read error has occurred. If a file name is specified, the contents of the restored files are probably partially wrong. If restore is skipping an inode or is trying to resynchronize the tape, no extracted files are corrupted, although files may not be found on the tape. After a tape read error, and may have to resynchronize themselves. This message indicates the number of blocks skipped over. WARNINGS
and can get confused when doing incremental restores from dump tapes that were made on active file systems. A level zero dump (see dump(1M)) must be done after a full restore. Since restore runs in user code, it has no control over inode alloca- tion; thus a full dump must be done to get a new set of directories reflecting the new inode numbering, even though the contents of the files are unchanged. AUTHOR
and were developed by the University of California, Berkeley. FILES
Default tape drive. File containing directories on the tape. Owner, mode, and time stamps for directories. Information passed between incremental restores. SEE ALSO
dump(1M), mkfs(1M), mount(1M), newfs(1M), rmt(1M), mt(7). restore(1M)
All times are GMT -4. The time now is 04:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy