Tape device 1cbn path not getting created


 
Thread Tools Search this Thread
Operating Systems Solaris Tape device 1cbn path not getting created
# 1  
Old 05-25-2011
Tape device 1cbn path not getting created

After we upgraded one PW450 machine from (networker 7.2 & solaris 9) to (networker 7.4 and solaris 10) through scratch installation

Only one of two HP tape drives is shown in inquire command
And we are getting strange logs in messages file (attached)
For 2nd drive 1cbn character specific file is absent.
But its patch is present in /etc/path_to_inst file

Any one has any idea how to solve this problem?


Code:
May 25 11:38:18 laho2b  <HP Ultrium>
May 25 11:38:27 laho2b scsi: [ID 193665 kern.info] sgen30 at fjulsa2: target 4 lun 0
May 25 11:38:27 laho2b genunix: [ID 936769 kern.info] sgen30 is /pci@80,2000/FJSV,ulsa@1/sgen@4,0
May 25 11:39:21 laho2b pseudo: [ID 129642 kern.info] pseudo-device: llc10
May 25 11:39:21 laho2b genunix: [ID 936769 kern.info] llc10 is /pseudo/llc1@0
May 25 11:39:21 laho2b pseudo: [ID 129642 kern.info] pseudo-device: fcp0
May 25 11:39:21 laho2b genunix: [ID 936769 kern.info] fcp0 is /pseudo/fcp@0
May 25 11:39:21 laho2b pseudo: [ID 129642 kern.info] pseudo-device: fcsm0
May 25 11:39:21 laho2b genunix: [ID 936769 kern.info] fcsm0 is /pseudo/fcsm@0
May 25 11:39:21 laho2b pseudo: [ID 129642 kern.info] pseudo-device: fbt0
May 25 11:39:21 laho2b genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt@0
May 25 11:39:21 laho2b pseudo: [ID 129642 kern.info] pseudo-device: profile0
May 25 11:39:21 laho2b genunix: [ID 936769 kern.info] profile0 is /pseudo/profile@0
May 25 11:39:21 laho2b pseudo: [ID 129642 kern.info] pseudo-device: systrace0
May 25 11:39:21 laho2b genunix: [ID 936769 kern.info] systrace0 is /pseudo/systrace@0
May 25 11:39:21 laho2b pseudo: [ID 129642 kern.info] pseudo-device: sdt0
May 25 11:39:21 laho2b genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt@0
May 25 11:39:21 laho2b pseudo: [ID 129642 kern.info] pseudo-device: winlock0
May 25 11:39:21 laho2b genunix: [ID 936769 kern.info] winlock0 is /pseudo/winlock@0

Code:
scsidev@3.3.0:HP      Ultrium 2-SCSI  S63U|Tape, /dev/rmt/0cbn



Code:
root@laho2b# ls -tlr /dev/rmt/0cbn
lrwxrwxrwx   1 root     root          48 May 20 16:00 /dev/rmt/0cbn -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:cbn
root@laho2b# ls -tlr /dev/rmt/1cbn
/dev/rmt/1cbn: No such file or directory 

root@laho2b# cat /etc/path_to_inst|grep "pci@80,2000/FJSV,ulsa@1/st@3"
"/pci@80,2000/FJSV,ulsa@1/st@3,0" 3 "st"
root@laho2b# cat /etc/path_to_inst|grep "pci@80,2000/FJSV,ulsa@1/st@4"
"/pci@80,2000/FJSV,ulsa@1/st@4,0" 4 "st"
root@laho2b#



root@laho2b# cfgadm -al
Ap_Id                          Type         Receptacle   Occupant     Condition
c2                             scsi-bus     connected    configured   unknown
c2::dsk/c2t0d0                 CD-ROM       connected    configured   unknown
usb0/1                         unknown      empty        unconfigured ok
usb0/2                         unknown      empty        unconfigured ok

# 2  
Old 05-25-2011
what's the output of "ls -l /dev/rmt/* "


did you try this command "devfsadm" ?
# 3  
Old 05-25-2011
Tape device 1cbn path not getting created

Yes i used devfsadm -v and i also rebooted system but problem was same.

I have just checked problem is resolved by itself Smilie
I don't know how ?
Can some one help investigate

Now 1cbn is shown
Code:
root@laho2b# ls -l /dev/rmt/* 
lrwxrwxrwx   1 root     root          45 May 20 16:00 /dev/rmt/0 -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:
lrwxrwxrwx   1 root     root          46 May 20 16:00 /dev/rmt/0b -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:b
lrwxrwxrwx   1 root     root          47 May 20 16:00 /dev/rmt/0bn -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:bn
lrwxrwxrwx   1 root     root          46 May 20 16:00 /dev/rmt/0c -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:c
lrwxrwxrwx   1 root     root          47 May 20 16:00 /dev/rmt/0cb -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:cb
lrwxrwxrwx   1 root     root          48 May 20 16:00 /dev/rmt/0cbn -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:cbn
lrwxrwxrwx   1 root     root          47 May 20 16:00 /dev/rmt/0cn -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:cn
lrwxrwxrwx   1 root     root          46 May 20 16:00 /dev/rmt/0h -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:h
lrwxrwxrwx   1 root     root          47 May 20 16:00 /dev/rmt/0hb -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:hb
lrwxrwxrwx   1 root     root          48 May 20 16:00 /dev/rmt/0hbn -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:hbn
lrwxrwxrwx   1 root     root          47 May 20 16:00 /dev/rmt/0hn -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:hn
lrwxrwxrwx   1 root     root          46 May 20 16:00 /dev/rmt/0l -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:l
lrwxrwxrwx   1 root     root          47 May 20 16:00 /dev/rmt/0lb -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:lb
lrwxrwxrwx   1 root     root          48 May 20 16:00 /dev/rmt/0lbn -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:lbn
lrwxrwxrwx   1 root     root          47 May 20 16:00 /dev/rmt/0ln -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:ln
lrwxrwxrwx   1 root     root          46 May 20 16:00 /dev/rmt/0m -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:m
lrwxrwxrwx   1 root     root          47 May 20 16:00 /dev/rmt/0mb -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:mb
lrwxrwxrwx   1 root     root          48 May 20 16:00 /dev/rmt/0mbn -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:mbn
lrwxrwxrwx   1 root     root          47 May 20 16:00 /dev/rmt/0mn -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:mn
lrwxrwxrwx   1 root     root          46 May 20 16:00 /dev/rmt/0n -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:n
lrwxrwxrwx   1 root     root          46 May 20 16:00 /dev/rmt/0u -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:u
lrwxrwxrwx   1 root     root          47 May 20 16:00 /dev/rmt/0ub -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:ub
lrwxrwxrwx   1 root     root          48 May 20 16:00 /dev/rmt/0ubn -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:ubn
lrwxrwxrwx   1 root     root          47 May 20 16:00 /dev/rmt/0un -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@3,0:un
lrwxrwxrwx   1 root     root          45 May 25 11:39 /dev/rmt/1 -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:
lrwxrwxrwx   1 root     root          46 May 25 11:39 /dev/rmt/1b -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:b
lrwxrwxrwx   1 root     root          47 May 25 11:39 /dev/rmt/1bn -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:bn
lrwxrwxrwx   1 root     root          46 May 25 11:39 /dev/rmt/1c -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:c
lrwxrwxrwx   1 root     root          47 May 25 11:39 /dev/rmt/1cb -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:cb
lrwxrwxrwx   1 root     root          48 May 25 11:39 /dev/rmt/1cbn -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:cbn
lrwxrwxrwx   1 root     root          47 May 25 11:39 /dev/rmt/1cn -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:cn
lrwxrwxrwx   1 root     root          46 May 25 11:39 /dev/rmt/1h -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:h
lrwxrwxrwx   1 root     root          47 May 25 11:39 /dev/rmt/1hb -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:hb
lrwxrwxrwx   1 root     root          48 May 25 11:39 /dev/rmt/1hbn -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:hbn
lrwxrwxrwx   1 root     root          47 May 25 11:39 /dev/rmt/1hn -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:hn
lrwxrwxrwx   1 root     root          46 May 25 11:39 /dev/rmt/1l -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:l
lrwxrwxrwx   1 root     root          47 May 25 11:39 /dev/rmt/1lb -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:lb
lrwxrwxrwx   1 root     root          48 May 25 11:39 /dev/rmt/1lbn -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:lbn
lrwxrwxrwx   1 root     root          47 May 25 11:39 /dev/rmt/1ln -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:ln
lrwxrwxrwx   1 root     root          46 May 25 11:39 /dev/rmt/1m -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:m
lrwxrwxrwx   1 root     root          47 May 25 11:39 /dev/rmt/1mb -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:mb
lrwxrwxrwx   1 root     root          48 May 25 11:39 /dev/rmt/1mbn -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:mbn
lrwxrwxrwx   1 root     root          47 May 25 11:39 /dev/rmt/1mn -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:mn
lrwxrwxrwx   1 root     root          46 May 25 11:39 /dev/rmt/1n -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:n
lrwxrwxrwx   1 root     root          46 May 25 11:39 /dev/rmt/1u -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:u
lrwxrwxrwx   1 root     root          47 May 25 11:39 /dev/rmt/1ub -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:ub
lrwxrwxrwx   1 root     root          48 May 25 11:39 /dev/rmt/1ubn -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:ubn
lrwxrwxrwx   1 root     root          47 May 25 11:39 /dev/rmt/1un -> ../../devices/pci@80,2000/FJSV,ulsa@1/st@4,0:un


Last edited by kashif_islam; 05-25-2011 at 07:12 AM..
# 4  
Old 05-25-2011
I don't know, it looks fine to me now. Maybe you didn't reboot after patching the system ?

It looks fine now Smilie
# 5  
Old 05-30-2011
Problem resolved, root cause scsi ?

i did reboot the system but this didn't solve problem

Code:
root@laho2b# last reboot
reboot    system boot                   Tue May 24 16:46 
reboot    system down                   Tue May 24 16:43 
reboot    system boot                   Mon May 23 16:46 
reboot    system down                   Mon May 23 16:43

After the problem was resolved automatically i checked messages and found scsi errors related to HP tape drive.
somehow drive was automatically registered due to some scsi error i guess Smilie


Code:
May 25 15:27:59 laho2b scsi: [ID 107833 kern.warning] WARNING: /pci@80,2000/FJSV,ulsa@1/st@3,0 (st3):
May 25 15:27:59 laho2b  Error for Command: read                    Error Level: Fatal
May 25 15:27:59 laho2b scsi: [ID 107833 kern.notice]    Requested Block: 0                         Error Block: 0
May 25 15:27:59 laho2b scsi: [ID 107833 kern.notice]    Vendor: HP                                 Serial Number:             
May 25 15:27:59 laho2b scsi: [ID 107833 kern.notice]    Sense Key: Media Error
May 25 15:27:59 laho2b scsi: [ID 107833 kern.notice]    ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0x0
May 25 15:28:00 laho2b FJSVmadm[15145]: [ID 384459 user.error] laho2b:FJSVmadm:A:PCI#00-PORT#0-ID#3:st:Device Error(Media Error) (DRIVE vendor
=HP, product=Ultrium 2-SCSI)
May 25 15:29:16 laho2b scsi: [ID 107833 kern.warning] WARNING: /pci@80,2000/FJSV,ulsa@1/st@3,0 (st3):
May 25 15:29:16 laho2b  Error for Command: read                    Error Level: Fatal
May 25 15:29:16 laho2b scsi: [ID 107833 kern.notice]    Requested Block: 0                         Error Block: 0
May 25 15:29:16 laho2b scsi: [ID 107833 kern.notice]    Vendor: HP                                 Serial Number:             
May 25 15:29:16 laho2b scsi: [ID 107833 kern.notice]    Sense Key: Media Error
May 25 15:29:16 laho2b scsi: [ID 107833 kern.notice]    ASC: 0x14 (recorded entity not found), ASCQ: 0x0, FRU: 0x0
May 25 15:49:38 laho2b scsi: [ID 107833 kern.warning] WARNING: /pci@80,2000/FJSV,ulsa@1/st@3,0 (st3):
May 25 15:49:38 laho2b  Error for Command: read                    Error Level: Fatal
May 25 15:49:38 laho2b scsi: [ID 107833 kern.notice]    Requested Block: 0                         Error Block: 0
May 25 15:49:38 laho2b scsi: [ID 107833 kern.notice]    Vendor: HP                                 Serial Number:             
May 25 15:49:38 laho2b scsi: [ID 107833 kern.notice]    Sense Key: Media Error
May 25 15:49:38 laho2b scsi: [ID 107833 kern.notice]    ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0x0

Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Command to see the logical volume path, device mapper path and its corresponding dm device path

Currently I am using this laborious command lvdisplay | awk '/LV Path/ {p=$3} /LV Name/ {n=$3} /VG Name/ {v=$3} /Block device/ {d=$3; sub(".*:", "/dev/dm-", d); printf "%s\t%s\t%s\n", p, "/dev/mapper/"v"-"n, d}' Would like to know if there is any shorter method to get this mapping of... (2 Replies)
Discussion started by: royalibrahim
2 Replies

2. HP-UX

Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)

Hi, Unable to make tape backup, please help. /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00 * Creating local directories for configuration files and archive. ======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery. (Mon... (4 Replies)
Discussion started by: anuragr
4 Replies

3. AIX

Backup to a remote tape device. Is it possible?

Hi all The situation is as follows: We need to take an mksysb image from an AIX 6.1 server. From some reason (irrelevant to this discussion) this server does not have access to a local CD-ROM or a tape drive. We do have another server with AIX 6.1 (but different technology level) which got access... (1 Reply)
Discussion started by: abohmeed
1 Replies

4. AIX

Tape device temporarily unavailable

Hi All, After (by accident) closing a session that ran a restore command I can not access the tape drive anymore. I get the following error: # tctl -f /dev/rmt0 rewind /dev/rmt0: Resource temporarily unavailable But I cannot find any processes associated with the tape device: # ps... (2 Replies)
Discussion started by: petervg
2 Replies

5. HP-UX

tape device files constantly being recreated

Hi, We've been having problems with our NetWorker Silo servers (running HP-UX) concerning the tape device files under /dev/rmt. For some reason they are constantly being removed/recreated (up to a couple of times per hour): crw-rw-rw- 1 bin bin 205 0x240300 Apr 5 19:07... (1 Reply)
Discussion started by: piper28
1 Replies

6. UNIX for Dummies Questions & Answers

How to change tape device name.

I disconected external device which was configured as rmt0. When I connect it again and run cfgmgr device name has changed (internal drive which was rmt1 is now rmt0 and external drive was rmt0 and is rmt1) and I dont know how to back it out. The thing is that for all backups I use new modell... (2 Replies)
Discussion started by: fraydey
2 Replies

7. Solaris

flarcreate to remote tape device

Hi, Someone knows hot to create a flash archive to a remote tape device? Here is my try: $flarcreate -n nereus -S -t lisdev:/dev/rmt/1n WARNING: hash generation disabled when using tape (-t) current filter settings Creating the archive... ERROR: Unable to work archive. Regards (4 Replies)
Discussion started by: spacewalker
4 Replies

8. UNIX for Advanced & Expert Users

tape device

Hi, 1- how can I find my tape device on my server ? 2-I have a backup of a data base distributed on several file system. How using tar -x can I extract from tape to each apropriate file system ? For exemple the data base was on /d1 ; /d2 ; and /d3. Now I cd to which /dn and use tar -xvf /dev/nm0... (0 Replies)
Discussion started by: big123456
0 Replies

9. UNIX for Dummies Questions & Answers

Is it possible to ufsdump to a file instead of a tape device?

Eh... what the title says. :) (8 Replies)
Discussion started by: PSC
8 Replies

10. Programming

tape device

Hi, I have problem detecting my tape drive. In SAM, once I click on the either Automated Backups or Interactive Backup and Recovery icon, the screen will prompt searching for device and ..... nothing appears in the list. In the end, I have the kill the SAM process and reboot the system and... (1 Reply)
Discussion started by: jennifer
1 Replies
Login or Register to Ask a Question