Date: Thu, 5 Nov 1998 16:46:26 -0700 (MST) From: "Kenneth D. Merry" <ken@plutotech.com> To: wilhelm@milkyway.stdio.com (Nick Wilhelm-Olsen) Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SDT-7000 density woes Message-ID: <199811052346.QAA27077@panzer.plutotech.com> In-Reply-To: <199811052249.RAA09611@terra.milkyway.stdio.com> from Nick Wilhelm-Olsen at "Nov 5, 98 05:49:43 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Nick Wilhelm-Olsen wrote... > > Hello, > > I posted this yesterday to freebsd-questions and have gotten > no answers and a couple of 'me too's. So I'm reposting here > in the hopes that someone will look at this. This same > problem has also been seen on a friends system w/ an > Archive Python running 3.0-current. > > I didn't mention it originally, but I am using 120m tapes. > I also didn't mention that this worked great with the old > non-CAM st tape driver. > > I am running 3.0-RELEASE on Compaq EISA box with a fairly > stock kernel, using an Adaptec 2742 (ahc) for SCSI. I have > a Sony SDT-7000 DDS-2 4mm tape drive attached to the system > that properly shows up as sa0. > > ...<snip>... > ahc0: <Adaptec 274X SCSI host adapter> at 0x4c00-0x4cff irq 11 on eisa0 slot 4 > ahc0: aic7770 >= Rev E, Twin Channel, A SCSI Id=7, B SCSI Id=7, primary A, 4/255 SCBs > ..<snip>... > Waiting 15 seconds for SCSI devices to settle > sa0 at ahc0 bus 0 target 4 lun 0 > sa0: <SONY SDT-7000 0215> Removable Sequential Access SCSI2 device > sa0: 10.0MB/s transfers (10.0MHz, offset 15) > > My first attempt at dumping to the tape device worked ok, > except for the fact that I ran out of tape well before I > should have, before writing 2G to the device. I immediately > smacked myself for forgeting to set the density to DDS-2 and > enable compression (mode 0x24 from mt(1)): > > # mt -f /dev/nrsa0 density 0x24 > mt: /dev/nrsa0: density: invalid argument > (sa0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 0 0 0 c 0 > (sa0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0 > (sa0:ahc0:0:4:0): Invalid field in parameter list sks:8f,4 This means that the drive doesn't like the density you're trying to set. Most likely, it means that the tape you've got in the drive isn't recognized as a DDS-2 (120 meter) tape. Or maybe you don't have media in the drive. For instance on my SDT-5000, when I don't have any media in the drive, I get the following when I try the above command: (sa0:ahc0:0:5:0): MODE SELECT(06). CDB: 15 0 0 0 c 0 (sa0:ahc0:0:5:0): ILLEGAL REQUEST asc:26,0 (sa0:ahc0:0:5:0): Invalid field in parameter list sks:8d,4 i.e., similar error. > Sure enough, I check the densities that the device thinks that > it supports and 0x24 is not listed: > > # mt -f /dev/nrsa0 status > Mode Density Blocksize bpi Compression > Current: X3B5/88-185A 512 bytes 61000 DCLZ > ---------available modes--------- > 0: X3B5/88-185A 512 bytes 61000 DCLZ > 1: X3B5/88-185A 512 bytes 61000 DCLZ > 2: X3B5/88-185A 512 bytes 61000 DCLZ > 3: X3B5/88-185A 512 bytes 61000 DCLZ > > What?!? Why does the sa device only think that DDS is supported? > What is wrong here? Is this a fundamental user error or something > else? > > Please help as I am now officially quite confused. Well, the mt(1) command in CAM works a little differently than it did under the old SCSI layer. The "available modes" are bogus. The stuff that's printed out is basically just a summary of the current status of the drive. And it's printed out 5 times. :) Try putting a 120 meter tape in the drive and do an mt status. It should detect that you've got a 120 meter tape in, and the density should show up as DDS-2. If the density doesn't show up as DDS-2 with a tape in, then try setting the density to 0x24. Let me know how it goes. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811052346.QAA27077>