Operating System - Tru64 Unix
1752761 Members
5158 Online
108789 Solutions
New Discussion юеВ

Re: MAKEDEV for HP DAT72 HOTPLUG TAPE DRIVE

 
Saju a r s
Advisor

MAKEDEV for HP DAT72 HOTPLUG TAPE DRIVE

Hi ,
Can anyone pls tell me the argument given to MAKEDEV for HP DAT72 HOTPLUG TAPE DRIVE ?
I need to mount this drive to restore files.
I tried with tz16 ,it dint work.
saju
5 REPLIES 5
Saju a r s
Advisor

Re: MAKEDEV for HP DAT72 HOTPLUG TAPE DRIVE

Some information :
It's a ES45 simplex Tru64 5.1B machine.
Steven Schweda
Honored Contributor

Re: MAKEDEV for HP DAT72 HOTPLUG TAPE DRIVE

Not knowing much, I normally use "doconfig"
to make a new kernel when I add hardware.

> I tried with tz16 ,it dint work.

You tried what? What didn't work? What,
exactly, did you do? What, exactly,
happened when you did it?
Saju a r s
Advisor

Re: MAKEDEV for HP DAT72 HOTPLUG TAPE DRIVE

Thanks Steven for replying .
My root file system has been deleted .So i need to restore from the backup .I have booted in single user mode using the cd and mounted the file system .Now i need to mount the tape drive to start the restoration .There's no device name for the tape drive in the output of hwmgr -v d .I tried MAKEDEV tz16 . That created special files like nrmt0h , which i tried to mount but failed .Now i checked the reference pages of Tru64, i found tms and mtio that can be given as parameters to MAKEDEV .But both of them did not work.I thought the tape drive may not be connected well.So just pulled it and put in again.But no changes .
Pls help !
Kapil Jha
Honored Contributor

Re: MAKEDEV for HP DAT72 HOTPLUG TAPE DRIVE

may be you can use
root#dn_setup ├в install_tape

now it'll work I hope ;)
I am in this small bowl, I wane see the real world......
Steven Schweda
Honored Contributor

Re: MAKEDEV for HP DAT72 HOTPLUG TAPE DRIVE

I booted my XP1000 from the V5.1B CD-ROM (and
exited from the installation procedure).

# ls -lL /dev/tape
ls: /dev/tape not found

# hwmgr -view devices
HWID: Device Name Mfg Model Location
------------------------------------------------------------------------------
3: (unknown)
4: (unknown)
5: (unknown)
47: /dev/disk/floppy0c 3.5in floppy fdi0-unit-0
54: /dev/disk/dsk0c FUJITSU MAB3091S SUN9.0G bus-0-targ-0-lun-0
55: /dev/disk/dsk1c SEAGATE ST19171W bus-0-targ-1-lun-0
56: /dev/disk/cdrom0c TSSTcorp CD/DVDW SH-S162A bus-2-targ-0-lun-0
57: (unknown)
58: (unknown)
59: (unknown) QUANTUM DLT7000 bus-1-targ-4-lun-0

This shows my tape drive (DLT7000).

# dn_setup -boot
[...]
dsfmgr: NOTE: creating device special files for system at /
+dmapi +scp_scsi +kevm +kevm.pterm +kevm.debug -kevm.debug +tty00 +tty01 +lp
0 +random +urandom +tape0 +tape0 +tape0c +tape0c +tape0_d0 +tape0_d0 +tape0_d1 +
tape0_d1 +tape0_d2 +tape0_d2 +tape0_d3 +tape0_d3 +tape0_d4 +tape0_d4 +tape0_d5 +
tape0_d5 +tape0_d6 +tape0_d6 +tape0_d7 +tape0_d7

Looks promising.

# ls -lL /dev/tape
total 0
crw-rw-rw- 1 root system 19, 66 Feb 22 04:30 tape0
crw-rw-rw- 1 root system 19, 70 Feb 22 04:30 tape0_d0
crw-rw-rw- 1 root system 19, 72 Feb 22 04:30 tape0_d1
crw-rw-rw- 1 root system 19, 74 Feb 22 04:30 tape0_d2
crw-rw-rw- 1 root system 19, 76 Feb 22 04:30 tape0_d3
crw-rw-rw- 1 root system 19, 78 Feb 22 04:30 tape0_d4
crw-rw-rw- 1 root system 19, 80 Feb 22 04:30 tape0_d5
crw-rw-rw- 1 root system 19, 82 Feb 22 04:30 tape0_d6
crw-rw-rw- 1 root system 19, 84 Feb 22 04:30 tape0_d7
crw-rw-rw- 1 root system 19, 68 Feb 22 04:30 tape0c

Now:

# hwmgr -view devices
HWID: Device Name Mfg Model Location
------------------------------------------------------------------------------
3: /dev/dmapi/dmapi
4: /dev/scp_scsi
5: /dev/kevm
47: /dev/disk/floppy0c 3.5in floppy fdi0-unit-0
54: /dev/disk/dsk0c FUJITSU MAB3091S SUN9.0G bus-0-targ-0-lun-0
55: /dev/disk/dsk1c SEAGATE ST19171W bus-0-targ-1-lun-0
56: /dev/disk/cdrom0c TSSTcorp CD/DVDW SH-S162A bus-2-targ-0-lun-0
57: /dev/random
58: /dev/urandom
59: /dev/ntape/tape0 QUANTUM DLT7000 bus-1-targ-4-lun-0


Looks good to me. I vote for "dn_setup
-boot".