>When i understand you, than is the application coressponding with the st 
>driver, the st driver is coressponding with the sg driver and the sg driver 
>is coressponding with the physical device. 

Close enough.

I doubt st actually talks to sg (it probably has a more direct path to
the hardware), but the basic idea is the same.

>Hm...the tape haven't and hasn't SCSI ID 5 ...

But earlier you said:

  Before i installed a new hard drive in the system (only scsi devices),
  the changer device was /dev/sg6 and the tape device was /dev/sg5.

I took that to mean the tape drive used to be ID 5.

Not that it really matters.  The problem is that it doesn't work now.

>No, i have removed the device /dev/nst0 and rebooted the system, but this 
>device isn't come back, so that i must create it from hand.
>
>I made this with "mknod /dev/nst0 c 9 128 but it don't work :-(

I found a Linux system and read up on the major and minor device numbers
for the st device so I see where 9 and 128 came from.

I don't know enough about Linux to know where you find this out for
sure (e.g. some boot time log messages or the like), but I suspect what
might be happening is that the driver found something else it thought
of as the first (zero'th) "sequential access device" and so 128 is the
wrong minor number to have picked.  You might try creating a few others
(/dev/nst1, etc) per the man page and see if any of them will answer to
a simple "mt -f /dev/whatever rewind".

One other possibility is that when you added the disk the tape drive
went "dead" (unable to be accessed by the st driver) for some reason.
For instance, it's in the wrong place on the SCSI chain (narrow after
wide, for instance), or termination is now wrong.  That's less likely
since, if I understood correctly, you can do some simple (info) mtx
things to it.

Other than that, I think you need some real Linux help here.  Until you
can get /dev/nstN to work with normal mt commands, this is not really
an Amanda issue.

Not that there aren't good Linux folks listening in.

>Juergen

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

P.S.  Before anyone starts quoting chapter and verse about how the st
driver works, including that it will pass SCSI commands through, I was
deliberatly simplifying the description in this discussion to try and
clear up some confusion rather than add to it :-).

Reply via email to