Date: Wed, 9 Feb 2000 09:15:47 -0800 From: "alex wetmore" <alex@phred.org> To: "Justin T. Gibbs" <gibbs@narnia.plutotech.com> Cc: <scsi@FreeBSD.org> Subject: Re: Problem with FreeBSD 2.2.2 and Archive Python 4586 DDS-2 autoloader (changer device not detected) Message-ID: <0aa301bf7321$4f7adbf0$01fa3b9d@AWETMOREDEV> References: <200002081948.MAA44751@narnia.plutotech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
From: "Justin T. Gibbs" <gibbs@narnia.plutotech.com> > In article <06a101bf725f$6159adf0$01fa3b9d@AWETMOREDEV> you wrote: > > I'm running FreeBSD 2.2.2 on a server machine and this weekend I added a > > DDS-2 autoloader to get automated backups. FreeBSD will recognize the drive > > as a DDS drive, but doesn't see it as a changer, so the ch device and chio > > programs do not work. > > > > Here is the kernel output during probe: > > (ahc0:5:0): "ARCHIVE Python 29987-XXX 5AB" type 1 removable SCSI 2 > > st0(ahc0:5:0): Sequential-Access density code 0x13, drive empty > > In 2.2.2, we did not probe luns above 0 by default. For this kind > of changer device, the manufacturer often advertizes the changer on > lun 1. Newer versions of FreeBSD scan higher luns by default and > will hopefully pick up the changer. Was this fixed in 3.x, or higher versions of 2.x? Upgrading to 3.x at this point is not an option (and I probably won't bother with a painful upgrade until 4.1 is out). If I describe the device completely, like: device ch0 target 5 lun 1 should that work with 2.2.2? thanks, alex 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?0aa301bf7321$4f7adbf0$01fa3b9d>