Cannot eject tape drive

[Raz316]

SCO Openserver 5.0.5 Unix
Seagate 12-24 DAT driver

I am unable to eject the tape. The drive L.E.D indicates that a tape is inserted, but not actually doing anything.

Can anyone think of anything to look for within Unix that could resolve this? I tried google, but suprisingly, I can't find anyone else who has had this happen!

ta!

E> Unix does think the device (rStp0) is busy when you tried and reset it from the command line.

[directhex]

lsof | grep -i rstp0

should tell you what processes (if any) are using the device

i've not used any tape drives outside of windows 3.1, but might it be mounted? /me knows not

[Raz316]

ta hex, is that command the same as 'ps -ef' because, it doesnay work on our sco box.
ps -ef | grep Rstp0 - shows nowt though

It could be mounted, any idea how I found out where, if at all (/mnt shows nothing)

E> Running 'tape status' returns /dev/xtc0 : Device busy, but grepping for a process using xtc0 still shows nothing.

[daniel_owen_uk]

Can't you just power off then reboot with the eject button held in? Usually works for me.

[Raz316]

its a server, so being able to avoid rebooting is preferable. However, we have 'booked' a reboot incase we don't resolve it.

[directhex]

ta hex, is that command the same as 'ps -ef' because, it doesnay work on our sco box.

lsof lists all open files, and what process is using that file. i got it onto my debian system by means of the package named, appropriately, lsof.

e.g. lsof | grep ogg
rhythmbox 1320 directhex 19r REG 0,30 5309937 36695 /spike/music/Ash/Intergalactic Sonic 7_s/01 - Burn Baby Burn.ogg

[Raz316]

ahh sounds quite useful

Im a wuss, so I probably wont install it on the Sco Box, but I'll remember it!

Oh and the server has been rebooted now, tape ejected and all.

Ta!

[ikonia]

always worth a go using mt

mt -f /dev/$tapedevice status

if this reports a nice status

try mt -f /dev/$tapedevice offline
or mt -f /dev/$tapedevice rewind then offline it

[Raz316]

cheers ikonia

sorry I should have said, we did actually try them, but just got Device Busy.