[2770] in linux-scsi channel archive
Re: Diamond Fireport 40
daemon@ATHENA.MIT.EDU (Justin Miller)
Fri Nov 7 01:38:13 1997
To: msimons@saic1.com (Mike Simons)
Date: Fri, 7 Nov 1997 00:32:33 -0600 (CST)
Cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <199711070557.AAA27486@aura.saic1.com> from "Mike Simons" at Nov 7, 97 00:57:53 am
From: jhm@umr.edu (Justin Miller)
I tried some of the things you mentioned below: in cdp, i could change
tracks, without crashing, i couldn't just hit the 6 key, i had to hit the
8, then the 6 to go forward one track. The tar.gz thing i'm not sure
about, if there was a lot of data being compressed, the hard drive may
have not been able to put enough data through for the cdwriter, usually
when that happens, cdwrite just gives up and it stops writing. I would
suggest that next time you want to burn a cd you unplug your network
card, it will save you a lot of these kind of headaches.
When my system crashed, i had several of the same symptoms as you had; i
had to turn my computer off in order to get access to the cdwriter. and
there was some filesystem corruption. The cdwrite program is kind of
old, but i have been using it successfully on this drive for about a year
now. I have recently tried a program called cdrecord, it has lots of
nifty features, and it supports this drive. you can get if from
ftp://sunsite.unc.edu/pub/Linux/utils/disk-management/
I haven't had very many problems with my drive, but there is the
posibilty you ended up with a defective drive, you may consider calling
the hp tech support, they were very good about replacing my drive when i
fried it. It may also be that you have a problem with your controller,
my best suggestion would be to try the drive with another scsi
controller, hp suggests the adaptec conrollers, but i have successfully
using ncr based controllers. Hope this helped, if there is a test you
need me to do, email it to me and i'll try it.
>
> Sorry no good news in this post... just relaying similar problems
> with a different SCSI controller.
>
> > [...] I was writing a cdrom and
> > decided it was time to play an mp3, I tried playing one and then boom,
> > Kernel Panic!. unfortunately i couldn't save any of the info that it
> > spat out when it gave up but i did see ncr8xx mentioned on a couple of
> > lines. Since then I have burnt two cd's just fine, I was wondering if I
> > had configured the driver incorrectly. [...]
>
> > Attached devices:
> > Host: scsi0 Channel: 00 Id: 04 Lun: 00
> > Vendor: HP Model: CD-Writer 6020 Rev: 1.07
> > Type: CD-ROM ANSI SCSI revision: 02
>
> We have a dual-pentium machine with a BusLogic 948 SCSI controller,
> and this cd-worm drive. _I_ am convinced that this cd-worm is misbehaving,
> Since installing this drive 4 months ago, this machine has crashed
> many times with what appeared to scsi bus locks. (*)
> When using the cd-worm to play audio (via cdp or any other utility), I
> can normally crash the machine just repeatedly changing which track is
> being played. The cdrom that was here before never did that.
> We have done several successful cd burning sessions, but there was one
> horror... About 30 minutes into burning the 3rd copy of an image, someone
> else decided to create a tar.gz file of their home directory.
> I noticed what was going on and decided to go to their office and
> mention the burning session (which they already knew about) to ask
> them to suspend the tar. i got back to the machine to find it
> locked hard (required power cycle for the drives to respond)... rebooted
> to find massive filesystem corruption in *their* home directory, 30 mins
> later fsck and I turned every file they owned into inode numbered files =).
> It _could_ be the cdwrite program is to blame for that corruption (it has
> burned onto the last 2/3rd's of a new cd after a ^C to stop a test burn,
> then locked the bus after finishing the 'test burn'.
>
> Does anyone want to try some of the things above on their HP 6020
> to see what it does? I was hoping to test ours with some other scsi
> controllers (not that any of the scsi cards/drivers work better than the
> Buslogic one, just differently)
>
> Now I use this worm drive _only_ when everyone else is at home and
> _only_ to burn cd's that _must_ be burned. I have not used any other
> worm drives, but I will bet this is not "normal" for worm drives in Linux
> to crash the machine. ;)
> I've been meaning to put this drive in a different machine that
> I can bang away at it but haven't had the time. If anyone would like
> to give suggestions/tests/advice to I'll file them away for when I do
> get this drive in some other machine...
>
> --
>
> Later,
> Mike Simons
> Science Applications International Corporation
> msimons@saic1.com 703-925-5674
>
> *:
> don't send any of the standard, 'check the scsi cable/termination/etc'
> suggestions...
>
