Sponsored Content
Operating Systems HP-UX HP-Unix 64 bit Tape Drive creating problem Post 302389298 by hellozishan on Sunday 24th of January 2010 04:32:18 AM
Old 01-24-2010
HP-Unix 64 bit Tape Drive creating problem

Hello All,

I have HP Openview storage data protector version 5.5. When I am going to write my backup I have an error message saying "Connot Open Device /dev/rmt/0mn"

Follownig is my output:

# ls -l /dev/rmt/0mn
crw-rw-rw- 2 bin bin 205 0x080140 Jan 17 16:41 /dev/rmt/0mn
# uname -a
HP-UX HPUXSRV B.11.23 U ia64 4122093358 unlimited-user license
#

Any help would be appreciated.

Regards,
Zishan
 

10 More Discussions You Might Find Interesting

1. Cybersecurity

Unix backup to tape drive

does anyone know how I can make an automatic backup of files to a tape drive under UNIX. I have so many commands, I don't know which goes where. I have commands for the task scheduler, Cron and other unix commands. Please help. Very Urgent. Thanks (3 Replies)
Discussion started by: Cute
3 Replies

2. UNIX for Dummies Questions & Answers

Tape Drive on Unix 7.1.1

I am trying to install a tape drive on this system (Unix 7.1.1) where will I start? 1. Do I need to load the driver on the on board scsi? How? 2. Is there a driver for the tape drive itself? Things done: 1. Terminated the device on the controller board. (4 Replies)
Discussion started by: a4tech
4 Replies

3. AIX

Problem reading a 4mm tape drive

I'm attempting to read a tape in a 4mm drive (AIX 4.3) using the following command... tar tvf /dev/rmt0 ...and I keep getting the following error message: tar: 0511-193 An error occurred while reading from the media. There is not enough memory available now. I've googled this error... (2 Replies)
Discussion started by: tdpearson
2 Replies

4. SCO

Tape drive problem

I replaced a HP Superstore Dat 40 with another HP Superstore Dat 40, but my backupedge software keeps putting up error code 1 (device not found) I have tried reinstaling the drive as DAT Alad stp 0 6 0 0. I'm not a computer expert but willing to have a go. I went into Backupedge to try and format a... (2 Replies)
Discussion started by: James Zwecker
2 Replies

5. AIX

Tape Drive Problem.

Dear all, I have ultriam3 tape. It is connected my LPAR. I have that the Sl.Nos. and slot number. but run the cfmgr i am not getting the tape drive. I have fired the command lsdev -Cc tape but no reply. how will i configure the tape in LPAR? Please suggest. It is very urgent. (3 Replies)
Discussion started by: pernasivam
3 Replies

6. Solaris

external tape drive DAT 72 problem

Hi all, I have solaris 10 sparc running and working very well but i have problem with external SCSI tape drive DAT 72 problem it seems to me the tape drive is manufactured by SUN microsystems when i ran ls -l /dev/rmt/0 it reveals the following output bash-3.00# mt -f /dev/rmt/0... (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies

7. UNIX for Dummies Questions & Answers

installing unix tape drive

Hi, i installed a unix tape drive on my alphaserver. when i use a mt command it tells me there is no tape or device. I have used the hardware manager and it shows the tape is present. Can anyone help me understand why it cannot pick up the tape as a default? (1 Reply)
Discussion started by: ryks
1 Replies

8. AIX

Tape Drive problem

Hi, I'm at AIX 5.3. My EOD program is giving following error while writing to tape: Can't write output cpio: Media Surface error Failed on Shell-script cd /; cpio -ocB 2 >> /autoline/misc/logs/bk.CopyToTape < /autoline/work/BACKUP.01022 1>/dev/rm0 I have tried with several new tapes,... (2 Replies)
Discussion started by: tayyabq8
2 Replies

9. Hardware

Help with scsi tape drive problem

I've had a scsi hard drive, scsi tape drive, and cd rom working off an adaptec 29160 controller. Everything worked great until a few days ago. I begin getting tar format errors (running sco 5.0.6) on the tape drive and occasionally the entire system would hang up while trying to access data on... (0 Replies)
Discussion started by: powwm
0 Replies

10. AIX

AIX 4.2.1 Tape Drive Problem

Hi, The problem I have is I want to restore my AIX machine. I have created a mksysb tape from my tape drive rmt0 and I changed the bootlist using this command "bootlist -m normal rmt0 hdisk0". However, when I display the bootlist "bootlist -om normal", it shows '-' hdisk0. I googled and... (2 Replies)
Discussion started by: AixNoob87
2 Replies
tapes(1M)						  System Administration Commands						 tapes(1M)

NAME
tapes - creates /dev entries for tape drives attached to the system SYNOPSIS
/usr/sbin/tapes [-r root_dir] DESCRIPTION
devfsadm(1M) is now the preferred command for /dev and /devices and should be used instead of tapes. tapes creates symbolic links in the /dev/rmt directory to the actual tape device special files under the /devices directory tree. tapes searches the kernel device tree to see what tape devices are attached to the system. For each equipped tape drive, the following steps are performed: 1. The /dev/rmt directory is searched for a /dev/rmt/n entry that is a symbolic link to the /devices special node of the current tape drive. If one is found, this determines the logical controller number of the tape drive. 2. The rest of the special devices associated with the drive are checked, and incorrect symbolic links are removed and necessary ones added. 3. If none are found, a new logical controller number is assigned (the lowest-unused number), and new symbolic links are created for all the special devices associated with the drive. tapes does not remove links to non-existent devices; these must be removed by hand. tapes is run each time a reconfiguration-boot is performed, or when add_drv(1M) is executed. Notice to Driver Writers tapes(1M) considers all devices with the node type DDI_NT_TAPE to be tape devices; these devices must have their minor name created with a specific format. The minor name encodes operational modes for the tape device and consists of an ASCII string of the form [ l,m,h,c,u ][ b ][ n ]. The first character set is used to specify the tape density of the device, and are named low (l), medium (m), high (h), compressed (c), and ultra (u). These specifiers only express a relative density; it is up to the driver to assign specific meanings as needed. For example, 9 track tape devices interpret these as actual bits-per-inch densities, where l means 800 BPI, m means 1600 BPI , and h means 6250 BPI, whereas 4mm DAT tapes defines l as standard format, and m, h, c and u as compressed format. Drivers may choose to implement any or all of these format types. During normal tape operation (non-BSD behavior), once an EOF mark has been reached, subsequent reads from the tape device return an error. An explicit IOCTL must be issued to space over the EOF mark before the next file can be read. b instructs the device to observe BSD behav- ior, where reading at EOF will cause the tape device to automatically space over the EOF mark and begin reading from the next file. n or no-rewind-on-close instructs the driver to not rewind to the beginning of tape when the device is closed. Normal behavior for tape devices is to reposition to BOT when closing. See mtio(7I). The minor number for tape devices should be created by encoding the device's instance number using the tape macro MTMINOR and ORing in the proper combination of density, BSD behavior, and no-rewind flags. See mtio(7I). To prevent tapes from attempting to automatically generate links for a device, drivers must specify a private node type and refrain from using the node type string DDI_NT_TAPE when callingddi_create_minor_node(9F). OPTIONS
The following options are supported: -r root_dir Causes tapes to presume that the /dev/rmt directory tree is found under root_dir, not directly under /. ERRORS
If tapes finds entries of a particular logical controller linked to different physical controllers, it prints an error message and exits without making any changes to the /dev directory, since it cannot determine which of the two alternative logical to physical mappings is correct. The links should be manually corrected or removed before another reconfiguration boot is performed. EXAMPLES
Example 1: Creating Tape Device Nodes From Within the Driver's attach() Function This example demonstrates creating tape device nodes from within the xktape driver's attach(9E) function. #include <sys/mtio.h> struct tape_minor_info { char *minor_name; int minor_mode; }; /* * create all combinations of logical tapes */ static struct tape_minor_info example_tape[] = { {"", 0}, /* default tape */ {"l", MT_DENSITY1}, {"lb", MT_DENSITY1 | MT_BSD}, {"lbn", MT_DENSITY1 | MT_BSD | MT_NOREWIND}, {"m", MT_DENSITY2}, {"mb", MT_DENSITY2 | MT_BSD}, {"mbn", MT_DENSITY2 | MT_BSD | MT_NOREWIND}, {"h", MT_DENSITY3}, {"hb", MT_DENSITY3 | MT_BSD}, {"hbn", MT_DENSITY3 | MT_BSD | MT_NOREWIND}, {"c", MT_DENSITY4}, {"cb", MT_DENSITY4 | MT_BSD}, {"cbn", MT_DENSITY4| MT_BSD | MT_NOREWIND}, {NULL, 0}, }; int xktapeattach(dev_info_t *dip, ddi_attach_cmd_t cmd) { int instance; struct tape_minor_info *mdp; /* other stuff in attach... */ instance = ddi_get_instance(dip); for (mdp = example_tape; mdp->minor_name != NULL; mdp++) { ddi_create_minor_node(dip, mdp->minor_name, S_IFCHR, (MTMINOR(instance) | mdp->minor_mode), DDI_NT_TAPE, 0); } Installing the xktape driver on a Sun Fire 4800, with the driver controlling a SCSI tape (target 4 attached to an isp(7D) SCSI HBA) and performing a reconfiguration-boot creates the following special files in /devices. # ls -l /devices/ssm@0,0/pci@18,700000/pci@1/SUNW,isptwo@4 crw-rw-rw- 1 root sys 33,136 Aug 29 00:02 xktape@4,0: crw-rw-rw- 1 root sys 33,200 Aug 29 00:02 xktape@4,0:b crw-rw-rw- 1 root sys 33,204 Aug 29 00:02 xktape@4,0:bn crw-rw-rw- 1 root sys 33,152 Aug 29 00:02 xktape@4,0:c crw-rw-rw- 1 root sys 33,216 Aug 29 00:02 xktape@4,0:cb crw-rw-rw- 1 root sys 33,220 Aug 29 00:02 xktape@4,0:cbn crw-rw-rw- 1 root sys 33,156 Aug 29 00:02 xktape@4,0:cn crw-rw-rw- 1 root sys 33,144 Aug 29 00:02 xktape@4,0:h crw-rw-rw- 1 root sys 33,208 Aug 29 00:02 xktape@4,0:hb crw-rw-rw- 1 root sys 33,212 Aug 29 00:02 xktape@4,0:hbn crw-rw-rw- 1 root sys 33,148 Aug 29 00:02 xktape@4,0:hn crw-rw-rw- 1 root sys 33,128 Aug 29 00:02 xktape@4,0:l crw-rw-rw- 1 root sys 33,192 Aug 29 00:02 xktape@4,0:lb crw-rw-rw- 1 root sys 33,196 Aug 29 00:02 xktape@4,0:lbn crw-rw-rw- 1 root sys 33,132 Aug 29 00:02 xktape@4,0:ln crw-rw-rw- 1 root sys 33,136 Aug 29 00:02 xktape@4,0:m crw-rw-rw- 1 root sys 33,200 Aug 29 00:02 xktape@4,0:mb crw-rw-rw- 1 root sys 33,204 Aug 29 00:02 xktape@4,0:mbn crw-rw-rw- 1 root sys 33,140 Aug 29 00:02 xktape@4,0:mn crw-rw-rw- 1 root sys 33,140 Aug 29 00:02 xktape@4,0:n /dev/rmt will contain the logical tape devices (symbolic links to tape devices in /devices). # ls -l /dev/rmt /dev/rmt/0 -> ../../devices/[....]/xktape@4,0: /dev/rmt/0b -> ../../devices/[....]/xktape@4,0:b /dev/rmt/0bn -> ../../devices/[....]/xktape@4,0:bn /dev/rmt/0c -> ../../devices/[....]/xktape@4,0:c /dev/rmt/0cb -> ../../devices/[....]/xktape@4,0:cb /dev/rmt/0cbn -> ../../devices/[....]/xktape@4,0:cbn /dev/rmt/0cn -> ../../devices/[....]/xktape@4,0:cn /dev/rmt/0h -> ../../devices/[....]/xktape@4,0:h /dev/rmt/0hb -> ../../devices/[....]/xktape@4,0:hb /dev/rmt/0hbn -> ../../devices/[....]/xktape@4,0:hbn /dev/rmt/0hn -> ../../devices/[....]/xktape@4,0:hn /dev/rmt/0l -> ../../devices/[....]/xktape@4,0:l /dev/rmt/0lb -> ../../devices/[....]/xktape@4,0:lb /dev/rmt/0lbn -> ../../devices/[....]/xktape@4,0:lbn /dev/rmt/0ln -> ../../devices/[....]/xktape@4,0:ln /dev/rmt/0m -> ../../devices/[....]/xktape@4,0:m /dev/rmt/0mb -> ../../devices/[....]/xktape@4,0:mb /dev/rmt/0mbn -> ../../devices/[....]/xktape@4,0:mbn /dev/rmt/0mn -> ../../devices/[....]/xktape@4,0:mn /dev/rmt/0n -> ../../devices/[....]/xktape@4,0:n FILES
/dev/rmt/* logical tape devices /devices/* tape device nodes ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
add_drv(1M), devfsadm(1M), attributes(5), isp(7D), devfs(7FS), mtio(7I), attach(9E), ddi_create_minor_node(9F) Writing Device Drivers BUGS
tapes silently ignores malformed minor device names. SunOS 5.10 8 Nov 2002 tapes(1M)
All times are GMT -4. The time now is 09:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy