Date: Thu, 15 Mar 2001 10:38:08 +1100 From: "Andrew Reilly" <areilly@bigpond.net.au> To: "Justin T. Gibbs" <gibbs@scsiguy.com> Cc: Andrew Reilly <areilly@bigpond.net.au>, Jordan Hubbard <jkh@osd.bsdi.com>, stable@FreeBSD.ORG Subject: Re: Uh oh. Looks like something broke with the AHC driver.. Message-ID: <20010315103808.A847@gurney.reilly.home> In-Reply-To: <200103141401.f2EE1Ks71771@aslan.scsiguy.com>; from gibbs@scsiguy.com on Wed, Mar 14, 2001 at 07:01:20AM -0700 References: <20010314223403.A56449@gurney.reilly.home> <200103141401.f2EE1Ks71771@aslan.scsiguy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 14, 2001 at 07:01:20AM -0700, Justin T. Gibbs wrote: > >Here's a possible "me too". I haven't reported this before > >because (a) da2 is my backup Fujitsu MO drive, and it does do > >odd things occasionally, and (b) the backup disk is currently > >full and I haven't thrown the requisite round-tuit at it. > > This looks like a device problem. The driver believes that the > transaction that timesout has been sent to the device and the > device has disconnected never to return. Since the driver is > able to select the device to give it a BDR, the device isn't > dead. Perhaps it just doesn't like the command the system > decided to send it??? I won't discount the "device problem" theory out of hand, because I know that flaky things have happened in the past. It does tend to be a bit slow when responding to start commands too, so (again, in the past) it would sometimes take a couple of mount attempts before a disk would mount. Lately, though, it's been working like a top. Until last weekend's upgrade to 4.3-BETA. Now it won't even report the size of the disk in the drive at boot time. I've just tried a few camcontrol commands: $ sudo camcontrol devlist -v scbus0 on ahc0 bus 0: <FUJITSU M2513A 1300> at scbus0 target 6 lun 0 (pass0,da2) < > at scbus0 target -1 lun -1 () scbus-1 on xpt0 bus 0: < > at scbus-1 target -1 lun -1 (xpt0) $ sudo camcontrol eject da2 Error received from stop unit command $ sudo camcontrol eject da2 Unit stopped successfully, Media ejected (and it was. Pop it back in...) $ sudo camcontrol inquiry da2 pass0: <FUJITSU M2513A 1300> Removable Optical SCSI-2 device pass0: 10.000MB/s transfers (10.000MHz, offset 10) $ sudo camcontrol rescan 0:6:0 Re-scan of 0:6:0 was successful $ sudo mount /dev/da2c /mnt Well I'll be [...]. It worked that time. The last dozen times I tried that it told me "device not configured" or "IO error". I was going to ask the list what to do about a "device not configured" message, because that seems to be the most common occurrance, and seems to make the least sense to me, because the device most definitely has an entry in /dev and the dmesg.boot file certainly thinks that it exists. Weird. $ mount /dev/ad0s2a on / (ufs, local) /dev/ad0s2f on /usr (ufs, local, soft-updates) /dev/ad1s2f on /usr/obj (ufs, local, soft-updates) /dev/ad1s2g on /usr/local (ufs, local, soft-updates) /dev/ad0s2e on /var (ufs, local, soft-updates) procfs on /proc (procfs, local) /dev/da2c on /mnt (ufs, local) Happy as a lark now. Is my MO drive really on it's last legs, or has something been tightened up in the driver timeouts that is tripping me up now? Is it true that CD-RW drives and media behave in much the same way as these MO drives? (I.e., sectors that you can put file systems on with newfs.) Maybe I should be looking at using one of those for backups. They're pretty cheap now. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010315103808.A847>