frecover(2114): read error from input device (I/O error)

[Sagar Sirdesai]

Hi
I've 11.11 server which had Ultrium 1-SCSI drive.

I used fbackup to backup data with no config file. After the fbackup is done .. The tape is verified using the frecover -Xn command.

This procedure worked fine for several months withoit any errors but recently after the fbackup completes successfully the frecover failes with the below error.

frecover(2114): read error from input device (I/O error)
frecover(2114): read error from input device (I/O error)
frecover(2113): unable to resync backup media

I've read other posts which all refer similar issue while fbackup is run . But I see this error when the frecover is run with -Xn
Please advise

Sagar

[Dennis Handly]

Have you tried replacing your tape?
Have you looked at your hardware error logs?

[sarfaraj ahmad]

have you tried in another server with same tape? what is the result over there?

please take a small backup on new tape and check, same error is coming or its successful?

[Jose Mosquera]

Hi,

Do you can an index file from your fbackup's tape:
#frecover -I /anyplace/indexfile -f /dev/rmt/yourdevice (-I is capitalized character i)

Your stored space have increased significantly in this time?
Have you the last fbackup/frecover (and related) cumulative patch?
Go to http://www11.itrc.hp.com/service/patch/searchHPUXPatchSet.do
then select [Fbackup] as patch set, and [hpux:11.11] as OS revision.

May be you need reduces the blocksperrecord and records default factors (man fbackup, -c config option), check this similar post may be useful to you:
http://h30499.www3.hp.com/t5/System-Administration/fbackup-and-DLT/m-p/3264713#M177574

Rgds.

[Bill Hassell · Accepted solution]

> frecover -Xn command

This simply reads the tape and checks the data for valid records, ordering, etc. However, the read error and I/O error message are direct from the tape drive -- the tape is unreadable. There isn't issue with frecover, this is simply a bad tape (which is why you run the frecover test), or a bad tape drive (they do wear out and must be replaced).

[Sagar Sirdesai]

A new tape was used which resolved the issue