Sponsored Content
Full Discussion: Partitioning DDS Tapes
Top Forums UNIX for Advanced & Expert Users Partitioning DDS Tapes Post 302074315 by dhaverstick on Monday 22nd of May 2006 03:51:37 PM
Old 05-22-2006
Partitioning DDS Tapes

Does anyone know how to partition 4mm DDS tapes in any flavor of UNIX besides HP-UX? My HP-UX box died and I have bunch of backup tapes with two partitions on them and I can't figure out how to read the second partition using other kinds of UNIX.

Thanks in advance,
Darren
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

from dos dir a: to similar to a dds tape?

is it possible to see what is in a dds tape? like in dos, we can write dir a: to see the contents of it? thanks PS : actually, i came from a DOS background. so most of the time, i will try to relate unix to dos. of course, dos never came close to unix. but unix is like many instances of dos... (3 Replies)
Discussion started by: yls177
3 Replies

2. UNIX for Dummies Questions & Answers

DDS Tape Drives

How do I find if a server contains a DDS3 or a DDS2 drive remotely ? I checked in SMIT and I noticed the description field according to tape drives, but is there another more thorough way? Thanks, Luke (0 Replies)
Discussion started by: Skywlkr235
0 Replies

3. UNIX for Dummies Questions & Answers

Partitioning DDS Tapes

Does anyone know how to partition 4mm DDS tapes in any flavor of UNIX besides HP-UX? My HP-UX box died and I have bunch of backup tapes with two partitions on them and I can't figure out how to read the second partition using other kinds of UNIX. Thanks in advance, Darren (1 Reply)
Discussion started by: dhaverstick
1 Replies

4. UNIX for Dummies Questions & Answers

DDS-2 Sun tape drive

Hey guys, I'm trying to mount a SUN DDS-2 tape drive on a SUN Ultra 80 machine running Solaris 9. I had the SCSI drive connected at time of install, I'm very new to Solaris so I don't know if Solaris would detect the drive like that and install some form of device driver. But, what im posting... (2 Replies)
Discussion started by: kingdbag
2 Replies

5. Solaris

Copy Tape Drive DDS-01.

Hello, I am trying to copy a boot tape DDS-01 with miniroot, but i donīt get this copy. i have already used the command dd, but donīt work. There are other way to get it. (0 Replies)
Discussion started by: carelias
0 Replies

6. UNIX for Dummies Questions & Answers

HP Unix 10.20 DDS Tape Driver Corruption

Dear Experts and Advanced User, I encounter a rare problem as mentioned above. I am not able to read the tape cartridge using the following command: #dd if=/dev/rmt/0mnb ibs=16k | tar tvf - It will prompt me with the message saying DD I/O error, broken pipe; everytime the above command... (1 Reply)
Discussion started by: stufftiger
1 Replies

7. UNIX for Dummies Questions & Answers

Need help with DDS data tape

Hi all I have BIG headache with an old unix server I have and I need some help and ideas how to solve them effectively. Thanks in advance ***Story*** I have an OLD SCO OpenServer 5 release 5 server with DDS4 tape device. I also have a box full of DDS4 tapes with data inside. I... (3 Replies)
Discussion started by: khaos83_2000
3 Replies

8. UNIX for Advanced & Expert Users

Need some information about Pacs and DDS Packets

Good Morning, All, I need to know what are PACs and DDS Packets in Unix and whats its advantage? Please help me in understanding this or refer me to some material so that I can have a better understanding of it. Thanks. (0 Replies)
Discussion started by: Samohd
0 Replies

9. AIX

Cleaning tape frequence for DDS

Hi All, Are there recommendations about the use of cleaning tapes in DDS devices? Should I clean the tape only when the drive indicates cleaning? Should I clean it once a month, week, even every day? Is it harmful to clean the tape every day? Thanks for your insights. --Peter (4 Replies)
Discussion started by: petervg
4 Replies

10. AIX

Testing the dds tape drive on AIX

Hi I need to make some restore tapes for our old AIX systems I have purchased some DDS2 tapes and cleaning tapes The tape drive is rmt0 what commands can I enter to run the cleaning tape through the drive and are the any commands I can enter to test these drives prior to using... (2 Replies)
Discussion started by: madmacher
2 Replies
idisk(1M)																 idisk(1M)

NAME
idisk - create partitions for disks on an Integrity system SYNOPSIS
partition_description_file}] device DESCRIPTION
creates operating system partitions for disks on an Integrity system. It reads in the partition information from a data file that may be specified in the command string or redirected from stdin. By default, operates in read-only mode and displays the partition information that is currently on the disk. To write new partition infor- mation on the disk the user must specify the option. Options recognizes the following options: Print the primary EFI partition header and partition tables. Print the alternate EFI partition header and partition tables. Print the legacy partition table that resides in the master boot record. writes partition information for the first four partition in the partition table in used by legacy DOS and Win- dows. This information is used as a backup in the event all the EFI information is corrupted. Print the first usable and last usable block numbers that are available to create partitions. First usable is the first block a partition can start on. Last usable is the last block that can be contained in a partition. These numbers are relative to the whole disk and do not take into account any partitions that may exist. They represent the total disk space that can be partitioned. Use the option to only print the values without headings. Work silently. No user prompts or warnings. For use in shell scripts. Validate EFI partition information. Does the same checks the driver does verifying that both the primary and alternate EFI partition headers and tables are correct. Returns two if either is bad and zero if both are correct. Restore the EFI partition headers and tables. This option checks both the primary header and tables and the alternate header and tables. If one is found bad it is restored from the other good ver- sion. One of either the primary or alternate header and tables must be good for this option to succeed. The option must be specified for information to be written to the disk. Remove all EFI partition headers and tables from the disk. This option also destroys the information contained in the MBR (master boot record). The option must be specified for information to be written to the disk. The partition_description_file contains the number of partitions to be created and the type and requested size of each partition. The filename may be specified here or redirected from stdin when the dash is used. Enable write mode. By default operates in read-only mode. To create and write partition information to the disk you must specify the option. Partition Description File The first entry in the partition description file is the number of partitions to create. The maximum number of partitions allowed is 12. This is followed by a line containing the type and size for each of the partitions. Recognized partition types are: and At least one EFI partition is required to create a valid partition table. Size may be specified in megabytes or as a percentage of the whole disk. Internally, creates the partitions whose size is specified in MB first then creates those whose size was specified as a percentage. Those partitions specified as a percent are assigned space from what is available after the MB partitions are created. If the size of a parti- tion is specified as 100% then all space remaining is assigned to that partition. An example partition description file is shown below: The first entry specifies the number of partitions to create. The second specifies an EFI partition of 100 megabytes. The last entry specifies a HPUX partition consisting of all the remaining space on the disk after the EFI partition has been created. When creating partitions, the device file name must be that of the whole disk. Legacy device files must not have any partition number bits set in the minor number. For legacy disk devices, the last eight bits of the minor number represent the option bits. For Integrity system disks, the last four option bits are used to indicate the partition number. Since there are only four bits for parti- tion number, only one to fifteen partitions are supported. For example, a device node with a minor number of 0x008001 would indicate a disk at target eight, partition number one. A minor number of 0x00500F would indicate a disk at target 5 partition fifteen. A minor num- ber with no partition bits set would indicate the whole disk (for example, 0x008000 would be the same disk as above but represent the whole disk and not a partition). Persistent device special files do not use or contain minor number information. A detailed description on persistent device special files can be found in intro(7). Note: For partitions created by device special files must be created for each legacy hardware path to the disk and for the LUN hardware path using or (see intro(7) for details on legacy and agile modes). If legacy mode is disabled (see the descrip- tion of the option in rmsf(1M)), device special files must only be created for the LUN hardware path. Note has been ported to Windows NT 4.0 and 2000. RETURN VALUE
Exit values are: Successful completion. Error condition occurred. EXAMPLES
Create the partitions specified in the above description file, printing only the primary partition information: Create the partitions specified in the above description file, printing only the primary partition information using a persistent device special file (see intro(7)): Create the partitions specified in the above description file, printing all available information (default), redirecting input from stdin: Only read the disk, printing all tables (default) on the disk: Get the first and last usable block for partitioning on the disk: Destroy all partition information on the disk: Restore partition information from either a good primary or alternate header or table to the header or table that is bad: AUTHOR
was developed by HP. SEE ALSO
insf(1M), mksf(1M), efi(4), intro(7). Integrity Systems Only idisk(1M)
All times are GMT -4. The time now is 01:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy