One more point of info.... (ok, two) 1) The original problem you reported is not unusual for a device that has written off the end of the tape. 2) I use bru for tape backup ( www.tollisgroup.com ) and they have it noted on their website that kernel 2.4.19 misses the EOT indicator on some scsi devices and its not the hardware fault. On Monday 09 December 2002 04:41 pm, Donald Polak wrote:
Well, I managed to get the SDT-5200 working, and found out it's only a 4GB drive with no compression (swore I read it was DDS-2 8GB). The 24GB Seagate is useless. NO GO. I had to replace it with a 8GB Seagate, and it works fine.
The problem seems to be the ASUS SC-875 controller, and the Seagate 24GB Python. The Adaptec 2490 works, and now so do the other drives.
I want to thank everyone for their help. If ANYONE figures out how to make a Seagate STD224000N (PYTHON 04106-XXX) drive work with Linux, e-mail me.
Regards,
Don Polak
Graham Smith wrote:
On Tue, 10 Dec 2002 04:51 am, Graham Smith wrote:
On Tue, 10 Dec 2002 03:54 am, Donald Polak wrote:
They are all new or used in that drive before, but under a different format. I'll try the one tape that worked before to see what it says.
Don
What does mt -f <dev> status return? (subsitute <dev> with the tape device on mine it is /dev/st0 )
Also have you tried reading a tape?
Another thought, have you tried running 'rescan-scsi-bus.sh' Occassionally I have found that the drive is not detected on the Bus on boot-up. The above command comes with the scsi utilities if you don't find it installed.
-- Regards,
Graham Smith ---------------------------------------------------------
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- _________________________________________________ John Andersen / Juneau Alaska