Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

daemon.log : Is error I/O or device configuration issue?

Status
Not open for further replies.

aego

Technical User
Aug 29, 2001
30
NL
Multiple errors found in daemon.log :

10/14/03 13:27:38 nsrd: media warning: /dev/rmt/1cbn reading: I/O error
(SEVERAL TIMES REPEATED)
10/14/03 13:27:38 nsrd: media notice: volume "xx1234" on device "/dev/rmt/1cbn": error decoding block, check system device configuration, disabling forward space record
10/14/03 13:27:38 nsrd: media info: can not read record 1683 of file 49 on dlt7000 tape "xx1234"


- This happens regularly with several different tapes (new and used).
- This happens every week.

I already reset counters for consecutive errors for this device , but to no avail...

Tapeunits and cabling have been replaced several times already.

What part of the "system device configuration" should i check ?

OS : Solaris 7
Jukebox Storedge L40 w. 2 DLT7000
Legato Networker/ Solstice Backup Version :5.5

I'm in yer face, even when you don't want me to be
 
This looks like a sporadic error and it is really difficult to help you with. If this would appear from the beginning, i would possibly blame
NW but this looks like you could not even run a successful backup even using OS commands.

Remember that NW only uses OS drivers, so please ensure that your
hardware works properly with tar and others before you use NW.
 
605, this is not the case...

A simple tar to the device will work also.

Backups are made, we even managed to restore a system from tape this week. It's very annoying as this happens primarily during weekends ( when no one is around to reset consecutive error counters ) and the full backup needs to be cloned.

___________
I'm in yer face, even when you don't want me to be
___________
 
It is hard to investigate or even isolate sporadic problems. It could also be due to a faulty controller, a power glitch, a bad terminator, necessary drive cleaning, bad media - there is no straight answer.
However, i do not expect NW to be the problem, because he at least
can react and tries to recover.
 
If he has written the media by himself, this is not the issue.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top