Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!paladin.american.edu!europa.eng.gtefsd.com!uunet!ogicse!cs.uoregon.edu!news.uoregon.edu!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.questions Subject: Re: [FreeBSD-1.0] Streamer LED burns after 1st access!! Message-ID: <2dioch$t4c@pdq.coe.montana.edu> Date: 1 Dec 93 18:39:13 GMT Article-I.D.: pdq.2dioch$t4c References: <CHD9En.Dnt@hermes.hrz.uni-bielefeld.de> Organization: Montana State University, Bozeman MT Lines: 33 NNTP-Posting-Host: bsd.coe.montana.edu In article <CHD9En.Dnt@hermes.hrz.uni-bielefeld.de>, Lars Koeller <uphya001@odie.uni-bielefeld.de> wrote: >-- > >My Wangtek 5525ES SCSI tape drive is running very well. The only problem >occured is the fact that the access LED on the tape is burning after the >first open of the device, and only swiches off after the 'mt off' command. >The device I use is /dev/rst0! I'm assuming 'burning' means is lit-up and does not mean is causing heat and smoke. :-) On my SCSI drive, the light is always on until I tell the drive to go offline as well, and it has been this way since I bought it 2 years ago, so I don't think anything is wrong. Mine is a TANDBERG if that matters. >All this doesn't matter anything, but when the LED is burning after some >time a kernel 'device st0 timed out error' occured and sometimes the device >don't return any more after accessing again. This could be a bug in the scsi tape driver, but Julian would know more. There have been some fixes recently to the scsi code, so it's possible that it is now fixed. Nate -- nate@bsd.coe.montana.edu | Freely available *nix clones benefit everyone, nate@cs.montana.edu | so let's not compete with each other, let's work #: (406) 994-4836 | compete with folks who try to tie us down to home #: (406) 586-0579 | proprietary O.S.'s (Microsloth) - Me