1832831 Members
2968 Online
110047 Solutions
New Discussion

Syslog error message

 
Ali Imran Abbas
Regular Advisor

Syslog error message

I am having the following error messages in the syslog.log file, wat does that mean:

Jan 8 08:21:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd044000 Failed open - st_san_safe enabled
Jan 8 08:21:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd055000 Failed open - st_san_safe enabled
Jan 8 08:21:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd193000 Failed open - st_san_safe enabled
Jan 8 08:21:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd043000 Failed open - st_san_safe enabled
Jan 8 08:21:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd1b3000 Failed open - st_san_safe enabled
Jan 8 08:21:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd044000 Failed open - st_san_safe enabled
Jan 8 08:21:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd1c3000 Failed open - st_san_safe enabled
Also can u please help me how to resolve that issue?

Regards,

Ali
5 REPLIES 5
Rita C Workman
Honored Contributor

Re: Syslog error message

Looks like it is saying your scsi tape unit failed to open and run some backup or tape write....

Check your tapes units cause it is showing several different addresses, so maybe it's a library or something.....

Just a thought,
Rita
Steven E. Protter
Exalted Contributor

Re: Syslog error message

Shalom Ali,

Please provide details about the device. ioscan -fnC tape

Whats the model number, what software has been installed to enable it? Who made it.

Some tape drives simply won't work with HP-UX.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Srikanth Arunachalam
Trusted Contributor

Re: Syslog error message

Hi,

If the st_san_safe kernel tunable is enabled on systems running OmniBackII A.04.00 or A.04.10, the following patches must also be installed:
OmniBackII A.04.00: PHSS_27586 and PHSS_27601
OmniBackII A.04.10: PHSS_27459 and PHSS_27588

Otherwise, make sure that no-rewind-on-close option is set.

Refer
SR:8606251513 CR:JAGae17578
While a host application is writing data to a tape, a
tape command like mt is issued from another host to the
same device using a device file without the
no-rewind-on-close option. On close(), a rewind is sent
to the drive between writes causing the tape to
reposition to beginning of tape (BOT). The host that
is writing has no knowledge that the tape was
repositioned and it continues writing from BOT
overwriting data previously written.


Resolution:
A new tunable called st_san_safe was added with a default state of disabled. When enabled, the tunable forces the stape driver to fail all opens to device files without the no-rewind-on-close option with the errno EINVAL. The stape driver will also log an entry into the syslog like the following:

vmunix: SCSI TAPE: dev = 0xcd002000 Failed open -st_san_safe enabled


When st_san_safe is enabled, mksf will not
create new device files without the no-rewind-on-close option. The mksf command will fail with an error indicating an invalid option was provided in the command
line arguments. With st_san_safe enabled, lssf will not fully decode the density attribute of a special device file.


Thanks,
Srikanth
Ali Imran Abbas
Regular Advisor

Re: Syslog error message

Dear Sir,

Here is the output of ioscan:

ioscan -fnC tape
Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
tape 25 0/0/1/1/0.3.0 stape CLAIMED DEVICE HP Ultrium 1-SCSI
/dev/rmt/25m /dev/rmt/c4t3d0BEST
/dev/rmt/25mb /dev/rmt/c4t3d0BESTb
/dev/rmt/25mn /dev/rmt/c4t3d0BESTn
/dev/rmt/25mnb /dev/rmt/c4t3d0BESTnb
tape 30 0/0/1/1/0.4.0 stape CLAIMED DEVICE HP C5683A
/dev/rmt/30m /dev/rmt/c4t4d0BEST
/dev/rmt/30mb /dev/rmt/c4t4d0BESTb
/dev/rmt/30mn /dev/rmt/c4t4d0BESTn
/dev/rmt/30mnb /dev/rmt/c4t4d0BESTnb
tape 21 0/0/1/1/1.5.0 stape CLAIMED DEVICE HP Ultrium 1-SCSI
/dev/rmt/21m /dev/rmt/c5t5d0BEST
/dev/rmt/21mb /dev/rmt/c5t5d0BESTb
/dev/rmt/21mn /dev/rmt/c5t5d0BESTn
/dev/rmt/21mnb /dev/rmt/c5t5d0BESTnb
tape 17 0/0/2/1/0/4/0.98.5.255.1.3.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2
/dev/rmt/17m /dev/rmt/c25t3d0BEST
/dev/rmt/17mb /dev/rmt/c25t3d0BESTb
/dev/rmt/17mn /dev/rmt/c25t3d0BESTn
/dev/rmt/17mnb /dev/rmt/c25t3d0BESTnb
tape 14 0/0/2/1/0/4/0.98.9.255.1.3.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2
/dev/rmt/14m /dev/rmt/c27t3d0BEST
/dev/rmt/14mb /dev/rmt/c27t3d0BESTb
/dev/rmt/14mn /dev/rmt/c27t3d0BESTn
/dev/rmt/14mnb /dev/rmt/c27t3d0BESTnb
tape 12 0/0/2/1/0/4/0.98.13.255.1.3.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2
/dev/rmt/12m /dev/rmt/c28t3d0BEST
/dev/rmt/12mb /dev/rmt/c28t3d0BESTb
/dev/rmt/12mn /dev/rmt/c28t3d0BESTn
/dev/rmt/12mnb /dev/rmt/c28t3d0BESTnb
tape 16 0/0/2/1/0/4/0.98.17.255.1.3.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2
/dev/rmt/16m /dev/rmt/c29t3d0BEST
/dev/rmt/16mb /dev/rmt/c29t3d0BESTb
/dev/rmt/16mn /dev/rmt/c29t3d0BESTn
/dev/rmt/16mnb /dev/rmt/c29t3d0BESTnb
tape 18 0/0/2/1/0/4/0.98.21.255.1.3.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2
/dev/rmt/18m /dev/rmt/c30t3d0BEST
/dev/rmt/18mb /dev/rmt/c30t3d0BESTb
/dev/rmt/18mn /dev/rmt/c30t3d0BESTn
/dev/rmt/18mnb /dev/rmt/c30t3d0BESTnb
tape 15 0/0/2/1/0/4/0.98.25.255.1.3.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2
/dev/rmt/15m /dev/rmt/c31t3d0BEST
/dev/rmt/15mb /dev/rmt/c31t3d0BESTb
/dev/rmt/15mn /dev/rmt/c31t3d0BESTn
/dev/rmt/15mnb /dev/rmt/c31t3d0BESTnb
tape 13 0/0/2/1/0/4/0.98.48.255.1.3.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2
/dev/rmt/13m /dev/rmt/c32t3d0BEST
/dev/rmt/13mb /dev/rmt/c32t3d0BESTb
/dev/rmt/13mn /dev/rmt/c32t3d0BESTn
/dev/rmt/13mnb /dev/rmt/c32t3d0BESTnb
tape 19 0/0/2/1/0/4/0.98.57.255.1.3.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2
/dev/rmt/19m /dev/rmt/c33t3d0BEST
/dev/rmt/19mb /dev/rmt/c33t3d0BESTb
/dev/rmt/19mn /dev/rmt/c33t3d0BESTn
/dev/rmt/19mnb /dev/rmt/c33t3d0BESTnb
tape 20 0/0/2/1/0/4/0.98.61.255.1.3.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2
/dev/rmt/20m /dev/rmt/c34t3d0BEST
/dev/rmt/20mb /dev/rmt/c34t3d0BESTb
/dev/rmt/20mn /dev/rmt/c34t3d0BESTn
/dev/rmt/20mnb /dev/rmt/c34t3d0BESTnb
tape 28 0/0/8/1/0.5.0 stape CLAIMED DEVICE HP Ultrium 1-SCSI
/dev/rmt/28m /dev/rmt/c6t5d0BEST
/dev/rmt/28mb /dev/rmt/c6t5d0BESTb
/dev/rmt/28mn /dev/rmt/c6t5d0BESTn
/dev/rmt/28mnb /dev/rmt/c6t5d0BESTnb
tape 29 0/0/8/1/1.5.0 stape CLAIMED DEVICE HP Ultrium 1-SCSI
/dev/rmt/29m /dev/rmt/c7t5d0BEST
/dev/rmt/29mb /dev/rmt/c7t5d0BESTb
/dev/rmt/29mn /dev/rmt/c7t5d0BESTn
/dev/rmt/29mnb /dev/rmt/c7t5d0BESTnb
tape 26 0/0/10/1/0.3.0 stape CLAIMED DEVICE HP Ultrium 1-SCSI
/dev/rmt/26m /dev/rmt/c35t3d0BEST
/dev/rmt/26mb /dev/rmt/c35t3d0BESTb
/dev/rmt/26mn /dev/rmt/c35t3d0BESTn
/dev/rmt/26mnb /dev/rmt/c35t3d0BESTnb
tape 27 0/0/10/1/1.5.0 stape CLAIMED DEVICE HP Ultrium 1-SCSI
/dev/rmt/27m /dev/rmt/c36t5d0BEST
/dev/rmt/27mb /dev/rmt/c36t5d0BESTb
/dev/rmt/27mn /dev/rmt/c36t5d0BESTn
/dev/rmt/27mnb /dev/rmt/c36t5d0BESTnb
tape 11 0/0/14/1/0/4/0.98.4.255.1.3.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2
/dev/rmt/11m /dev/rmt/c14t3d0BEST
/dev/rmt/11mb /dev/rmt/c14t3d0BESTb
/dev/rmt/11mn /dev/rmt/c14t3d0BESTn
/dev/rmt/11mnb /dev/rmt/c14t3d0BESTnb
tape 8 0/0/14/1/0/4/0.98.8.255.1.3.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2
/dev/rmt/8m /dev/rmt/c15t3d0BEST
/dev/rmt/8mb /dev/rmt/c15t3d0BESTb
/dev/rmt/8mn /dev/rmt/c15t3d0BESTn
/dev/rmt/8mnb /dev/rmt/c15t3d0BESTnb
tape 6 0/0/14/1/0/4/0.98.12.255.1.3.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2
/dev/rmt/6m /dev/rmt/c16t3d0BEST
/dev/rmt/6mb /dev/rmt/c16t3d0BESTb
/dev/rmt/6mn /dev/rmt/c16t3d0BESTn
/dev/rmt/6mnb /dev/rmt/c16t3d0BESTnb
tape 7 0/0/14/1/0/4/0.98.16.255.1.3.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2
/dev/rmt/7m /dev/rmt/c17t3d0BEST
/dev/rmt/7mb /dev/rmt/c17t3d0BESTb
/dev/rmt/7mn /dev/rmt/c17t3d0BESTn
/dev/rmt/7mnb /dev/rmt/c17t3d0BESTnb
tape 1 0/0/14/1/0/4/0.98.20.255.1.3.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2
/dev/rmt/1m /dev/rmt/c18t3d0BEST
/dev/rmt/1mb /dev/rmt/c18t3d0BESTb
/dev/rmt/1mn /dev/rmt/c18t3d0BESTn
/dev/rmt/1mnb /dev/rmt/c18t3d0BESTnb
tape 4 0/0/14/1/0/4/0.98.24.255.1.3.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2
/dev/rmt/4m /dev/rmt/c19t3d0BEST
/dev/rmt/4mb /dev/rmt/c19t3d0BESTb
/dev/rmt/4mn /dev/rmt/c19t3d0BESTn
/dev/rmt/4mnb /dev/rmt/c19t3d0BESTnb
tape 2 0/0/14/1/0/4/0.98.28.255.1.3.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2
/dev/rmt/2m /dev/rmt/c20t3d0BEST
/dev/rmt/2mb /dev/rmt/c20t3d0BESTb
/dev/rmt/2mn /dev/rmt/c20t3d0BESTn
/dev/rmt/2mnb /dev/rmt/c20t3d0BESTnb
tape 5 0/0/14/1/0/4/0.98.32.255.1.3.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2
/dev/rmt/5m /dev/rmt/c21t3d0BEST
/dev/rmt/5mb /dev/rmt/c21t3d0BESTb
/dev/rmt/5mn /dev/rmt/c21t3d0BESTn
/dev/rmt/5mnb /dev/rmt/c21t3d0BESTnb
tape 3 0/0/14/1/0/4/0.98.36.255.1.3.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2
/dev/rmt/3m /dev/rmt/c22t3d0BEST
/dev/rmt/3mb /dev/rmt/c22t3d0BESTb
/dev/rmt/3mn /dev/rmt/c22t3d0BESTn
/dev/rmt/3mnb /dev/rmt/c22t3d0BESTnb
tape 9 0/0/14/1/0/4/0.98.40.255.1.3.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2
/dev/rmt/9m /dev/rmt/c23t3d0BEST
/dev/rmt/9mb /dev/rmt/c23t3d0BESTb
/dev/rmt/9mn /dev/rmt/c23t3d0BESTn
/dev/rmt/9mnb /dev/rmt/c23t3d0BESTnb
tape 10 0/0/14/1/0/4/0.98.44.255.1.3.0 stape CLAIMED DEVICE IBM ULTRIUM-TD2
/dev/rmt/10m /dev/rmt/c24t3d0BEST
/dev/rmt/10mb /dev/rmt/c24t3d0BESTb
/dev/rmt/10mn /dev/rmt/c24t3d0BESTn
/dev/rmt/10mnb /dev/rmt/c24t3d0BESTnb

Its the main ignite backup machine, it was working fine before it started givinf this error message just for few days.
Srikanth Arunachalam
Trusted Contributor

Re: Syslog error message

Hi,

Check if the st_san_safe status is required to be set as enabled.

It seems you have more than one tape library based on ioscan output and that it is safe to leave this flag st_san_safe as enabled.

You need to make sure that there is no accidental sending of a rewind command on close.

Documentation is available in the below link :-

http://docs.hp.com/en/B2355-60105/st_san_safe.5.html

Thanks,
Srikanth